@vague said in Bitten by XSA-474: starting up database engine D:2a59ed50ccb5 failed with exception Xmlm.Error(2:317874, "malformed character stream") My guess is that your xapi database has been corrupted, if you dont have a backup this will be a rough one. To add some content I'll summarize what you wrote on IRC: You got an error, it was not resolved. You then decided to start upgrading your xcp installation Now the database is corrupt, not sure it it was already or if it happend in step 2.

Hi according to gh, it looks like there is traction on this feature: https://github.com/xcp-ng/xcp-ng-release/pull/53#discussion_r2642865515 So it might be merged soon... rzr opened this pull request in xcp-ng/xcp-ng-release open s/c/e/profile.d/history.sh: Add timestamps to history #53

@exetico I have updated my script. Please use your previous install file (if you have it saved) to remove your previous version (remember to save your config before running uninstall), before you proceed to install the new version.

@Greg_E said in Building XCP-ng from source code: @olivierlambert Ok, thanks. Yes I'm eagerly awaiting XCP-ng 9 for testing. Hi, check this thread: https://xcp-ng.org/forum/topic/11698/xcp-ng-9.0-demonstrator-early-preview More coming...

@dinhngtu Thanks. We plan to migrate all Windows VMs from the Citrix tools down the road and only have a handful of VMs running these so far so will maybe hold off until the next version. Have been running the Linux rust tools for over a year with zero issues..

Hello, Thanks for your work ! We have some hypervisors of tests at Gladhost, we can use them with pleasure to test your work on xcp-ng 8.3 ! Best regards

@m4rCsi Very nice, thanks for sharing the repo. We will defintely look carefully as we are also working on writing a XO CSI Driver. Ping @Cyrille

Testing the agent out on Arch Linux (mainly due to the spotty 'support' in the AUR/generally) and it is working fine - better than what I had before (which did not report VM info properly). I've set it up as a systemd service to replace the previous one I had, also working as expected. This would be fun to contribute towards.

@bleader just checked the Excel assessment file I got from the security team. They used Crowdstrike (sensor is not installed on xcp-ng hosts). The funny thing is, the asset that it reports as vulnerable is the VM that is running XOA (official image provided by XCP-NG). It is deployed recently, so everything is up-to-date, but even then I don't understand how it reports the XOA VM as the one containing the vulnerabilities.

Hi, There is an issue and/or a PR (I don't remember where though) to have a specific extra file to manage user config without overwriting it. Until then, it will be overwritten after updates. @Team-XAPI-Network could provide the link to the issue (or PR?) and check to make it merged when possible

Hello everyone, I absolutely understand the point regarding datacenters. I am using xcp-ng for years in smaller - non datacenter - environments and its great. Therefore I added the nut packages (8.2 and 8.3) and it works like a charm. It's installation is well explained in: https://xcp-ng.org/forum/topic/4300/performing-automated-shutdown-during-a-power-failure-using-a-usb-ups-with-nut-xcp-ng-8-2/13?_=1742229073030 However, I agree with @Kajetan321 that it would be great if the nut package could be included in the standard "updated" packages repo since its added quite some benefits (imho) for "smaller" IT environments. However, I do not know how much effort it takes to maintain that.

Yes, you can install Windows Server 2022 Essentials as a VM on XCP-ng, but the issue is likely due to using a DELL ROK DVD. ROK media checks for DELL hardware during setup and won’t work properly in a virtual environment like XCP-ng. Instead, download the standard Microsoft ISO for Server 2022 Essentials and install that. If your DELL key doesn’t work or you need a new one, you can get a genuine key from Noxkeys.com for around $20 worked perfectly for me. Activation was smooth after that.

@bogikornel As discussed in the thread, pygrub doesn't work. (It might be fixable, because copying kernel and initrd to dom-0 and directly setting PV-kernel, PV-ramdisk and PV-args works, which is basically what pygrub is supposed to do. But I stopped investigating as pvhgrub is a much better option which acually works.) You have 3 options copy kernel and initrd do dom-0 and configure xe vm-param-set uuid=... domain-type=pvh xe vm-param-set uuid=... PV-kernel=/dom-0/path/to/kernel xe vm-param-set uuid=... PV-ramdisk=/dom-0/path/to/initrd xe vm-param-set uuid=... PV-args="root=... ro console=hvc0 ..." xe vm-param-clear uuid=... param-name=PV-bootloader Not a very practical option, just PoC. use pvh-ovmf, but this requires UEFI-enabled VM (ie. GPT disk layout with EFI partition and some EFI bootloader or kernel directly in EFI with proper config (or as UKI) use pvhgrub. You need a recent grub2 to build the image for i386-xen_pvh target. Or just get the blob - this one is from Alpine package curl https://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/grub-xenhost-2.12-r8.apk | tar -xzf - --strip-components=3 usr/lib/grub-xen/grub-i386-xen_pvh.bin Save it to dom-0 (e.g. to /var/lib/xcp/guest/grub-i386-xen_pvh.bin) and configure the VM xe vm-param-set uuid=... domain-type=pvh xe vm-param-set uuid=... PV-kernel=/var/lib/xcp/guest/grub-i386-xen_pvh.bin xe vm-param-clear uuid=... param-name=PV-ramdisk xe vm-param-clear uuid=... param-name=PV-args xe vm-param-clear uuid=... param-name=PV-bootloader If the VM has valid grub2 config, it should work. Of course, you need a linux kernel with CONFIG_XEN_PVH enabled.

@ronan-a Thanks! I've installed the plugin, and configured it. Now to wait until the next power outage. (or until I get time this weekend to test it and annoy my family)

Upon further testing, it seems that initiating a rescan of the 0 byte SR fixes the size issue. However, I should not be having to do this but at least it appears to be more easily dealt with than I previously assessed.

@TeddyAstie I ran iperf3 tests between two VMs on Xeon E5-2680v2 and average results were within 2% of each other with the patch being slower. Peak speed was 14.5 vs. 13.7 Gbits/sec.

@gduperrey Got it, thank you for your assistance, this is super helpful.

@olivierlambert Fabulous! This is great news!

@LonnieTC Don't try to install XCP-ng as if it's any other Linux OS. It's an appliance, you need to download the XCP-ng ISO directly, install this to your hardware and then setup your management interface (Xen Orchestra). Xen Orchestra is installable to Ubuntu.

xe is a XAPI client, like XO is a XAPI client too. The issue with this, is if you have 1 pool it's OK. If you have many pools, it's a lot better to use XO API.