@TheMonkeyBrain Hi ! Let me find the link I had or reupload the file. I'll give it to you via DM ASAP If you need to uplaod the appliance, you need to replace sda to xvda on this two files: /opt/dell/omc/utilities/tui/bin/ome_disk_config.sh /opt/dell/mcsi/appliance/scripts/appliance_ressource.sh

Hi, Do you have any error message? What's happening? Anything visible or not?

@PaulDCL [image: 1757633451167-9eb17eb5-9a99-4743-9df5-51edcc2b1847-image.png] This benchmark was taken inside the Windows Server VM on that iSCSI device. The iSCSI host is a QNAP NAS with Toshiba 18 TB drives configured in RAID-6. I think this is a decent speed for non-flash storage. Both devices are on a 10Gbit network. If you need more specific details, I'll be happy to help.

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

@mdavico said in Debian 9 virtual machine does not start in xcp-ng 8.3: Update: If I change the vCPU configuration to 1 socket with 4 cores per socket the VM starts correctly Interesring. First time I heard it had any effect at all on a VM.

We don't have any feedback on that, so I can't tell

It's not the first approach, you have KubeVirt for example.

I worked with ChatGPT on this for a bit. We have narrowed it down to an issue with the NFS Storage that I ship the backups to. "When you recreated storage and moved data back, OMV is technically exporting a different underlying filesystem object than before. NFS clients that had an old handle cached (your XCP-ng host) try to access it and get ESTALE. That explains the initial backup errors and why deleting/re-adding the SR is failing now." I had to remove the NFS storage from XCP-ng, then delete the NFS share from OMV, then add the NFS share back to OMV, and then add it back to XCP-ng. I probably could have resolved this with a reboot, but I didn't wanna. This issue is resolved now.

Before the end of this month.

I had this tab still open which lets me realize that despite we packaged vmfs6-tools and updated the documentation at https://docs.xcp-ng.org/installation/migrate-to-xcp-ng/#local-migration-same-host, we didn't inform you here. Now it's done

@Andrew said in Is it possible to convert a BIOS to UEFI and introduce vTPM into an existing VM?: I have not converted windows as I normally started newer versions as UEFI and older version work better with BIOS For peeps that stumble on this post looking for answers, the answer is yes you can for Windows. You can use the built in Windows mbr2gpt program to do so. However, things to consider before attempting are? You can only have 3 partitions on the C driver. This is due to MBR only supporting 4. the 4th partition will be used during conversion it also has to shrink some space from the end of the drive You might have to move the recovery partition if it is at the end of the disk Basic steps are, to first run the command below. This will tell you if conversion should works mbr2gpt /validate /allowfullos Then the following to start the conversion mbr2gpt /convert /allowfullos Hope it helps someone

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.

I have not had time to work on this, and my lab changed significantly, had to spend a bunch of money to move it to a new rack and that rack has been disconnected for months so no real work in XCP or vSphere and learning to migrate VMs from vSphere to XCP which was one of my big intentions. But a recent post confirms that this "oddity" of trying to create a UEFI VM from XO-lite is still present. I'd bet money that this gets fixed before or when the full release is provided. https://xcp-ng.org/forum/topic/11227/boot-new-vm-to-iso-in-xo-lite Workaround is to either click the button provided to download XOA, or install Linux and XO from sources in BIOS mode. Then you have the full XO to work with to bring everything else up the way you want it. I see it as a minor annoyance right now, not really a bug or problem.

Release v2.2.0 This new version introduces a new field, 'memory_min', for the VM resource and makes a slight change to the 'memory_max' field, which now sets both the dynamic and static maximum memory limits and providing better control of VM memory. What's Changed feat: Update TF provider to get VM memory improvements by @gCyrille in https://github.com/vatesfr/pulumi-xenorchestra/pull/420 Full Changelog: https://github.com/vatesfr/pulumi-xenorchestra/compare/v2.1.0...v2.2.0 JavaScript/TypeScript: @vates/pulumi-xenorchestra Python: pulumi-xenorchestra Go: github.com/vatesfr/pulumi-xenorchestra/sdk .NET: Pulumi.Xenorchestra gCyrille opened this pull request in vatesfr/pulumi-xenorchestra closed feat: Update TF provider to get VM memory improvements #420

Fix committed upstream.

@DustinB it's there on mine as well. Going to test it in a couple of weeks. Lots on the docket! Thanks again, everyone.

I just had this problem with a ubuntu VM. With recovery mode selected press e to edit. Remove nomodeset. Here is an example. From: linux /vmlinuz-5.4.0-65-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro recovery nomodeset dis_ucode_ldr To: linux /vmlinuz-5.4.0-65-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro recovery dis_ucode_ldr The link below helped me solve this issue. https://portal.nutanix.com/page/documents/kbs/details?targetId=kA07V000000LWLrSAO