No problem, and it's not your fault, it's far from being intuitive. It will be a lot easier in XO 6.
Also, enjoy discovering the cool little things hidden in this view (like trying XO in Chinese )
Developers of XCP-ng
No problem, and it's not your fault, it's far from being intuitive. It will be a lot easier in XO 6.
Also, enjoy discovering the cool little things hidden in this view (like trying XO in Chinese )
In your user zone, "user" icon in the main/left menu, at the bottom:
Then, "Customize filters":
We are introducing an XO task to monitor the RPU process. That will be easier to track the whole process
Yes, it should work if the migration doesn't fail It's hard to know exactly why it failed in your case, but it's unrelated on being XO VM.
@fatek No. I removed this param, it's useless now.
No worries @Rhodderz happy to know it works for you now!
It's hard to give an answer because we are not inside your infrastructure. How long your host took to reboot in the end?
Hello,
As some of you may know, there is currently a problem with disks with blocksize of 4KiB not being compatible to be a SR disk.
It is an error with the vhd-util
utilities that is not easily fixed.
As such, we quickly developed a SMAPI driver using losetup
ability to emulate another sector size to be able to workaround the problem for the moment.
The real solution will involve SMAPIv3, which the first driver is available to test: https://xcp-ng.org/blog/2024/04/19/first-smapiv3-driver-is-available-in-preview/
To go back to the LargeBlock driver, it is available in 8.3 in sm 3.0.12-12.2.
To set it up, it is as simple as creating a EXT SR with xe
CLI.
xe sr-create host-uuid=<host UUID> type=largeblock name-label="LargeBlock SR" device-config:device=/dev/nvme0n1
It does not support using multiple devices because of quirks with LVM and the EXT SR driver.
It automatically creates a loop device with a sector size of 512b on top of the 4KiB device and then creates a EXT SR on top of this emulated device.
This driver is a workaround, we have automated tests but they can't catch all things.
If you have any feedbacks or problems, don't hesitate to share here