XCP-ng 8.1.0 beta now available!
-
-
@gdixon so I just added a virtual disk to an XCP-ng 8.1 VM (I often use nested virtualisation for testing) that appeared as
sdc
. I connected that XCP-ng host to Xen Orchestra and used XO to create anext
SR.That SR was created as ext4. No need for
sm-additional-drivers
for ext4 in XCP-ng 8.1.Extract from fstab
/dev/mapper/XSLocalEXT--d0866df5--f9fe--2c3a--1332--8d549468dce7-d0866df5--f9fe--2c3a--1332--8d549468dce7 on /run/sr-mount/d0866df5-f9fe-2c3a-1332-8d549468dce7 type ext4 (rw,relatime)
Note: even for
ext
local SRs, XCP-ng uses an LVM layer on top, hence the output of lsblk. -
About VM autostart: as @r1 found out, there's a missing symlink in an XCP-ng updated via yum. That's a bug in the upgrade scripts that is present in CH 8.1 too, and we reported it to them.
Here's the fix:
systemctl enable xapi-wait-init-complete.service
-
-
Thanks for the feedback
-
-
Indeed, also we reported the problem to Citrix, they might provide a fix one way or another.
-
Announcement about our former experimental
ext4
SR driver:It is now deprecated in 8.1. For a good reason: in XCP-ng 8.1 and above, following upstream changes, the ext driver now formats new SRs as EXT4.
There is no easy way to convert an existing SR created with our driver, so those using it will need to move the VDIs out (to another SR or to export them), destroy the SR and create an EXT SR instead. Make sure to do this on XCP-ng 8.1.
The
sm-additional-drivers
package remains available in XCP-ng 8.1 in order to ease the transition (update: and also because it contains the XFS driver). However I've broken thesr-create
command on purpose. Any attempt to create a SR of typeext4
will result in an error with a message that explains that you need to use theext
type instead.Our experimental driver will be completely removed in a later release, possibly XCP-ng 8.2. Unless someone convinces me to delay the removal for a good reason. I will accept reasons such as "I know I shouldn't have used the experimental driver in production, but I did and need more time to convert my SR while at the same time I really need feature xxx from XCP-ng 8.2", but I really would prefer to drop it in 8.2.
Feedback from people doing the transition is welcome to make sure we document the transition in the best way possible.
-
@stormi
what's the status of the xfs driver? Are you expecting that to be removed/deprecated as well? -
No, it's still there and still working but not officially supported.
-
New leaf coalesce logic using dynamic limits
I have backported patches from
sm
's master branch, that implement a new, smarter, logic for leaf coalescing.Just update your 8.1 beta, restart the toolstack, and that should be it.
Those interested in the patches, see https://github.com/xcp-ng-rpms/sm/commit/ed1a55d727846cf5777c8258e6a8f3b068e8a35b (python code).
-
@stormi plus this update?
https://support.citrix.com/article/CTX269586 -
All my SRs are using the ext4 driver.
So I just need to export the VMs, (to a NAS for example), destroy the SR, and recreate the SR, then import the VMs?
I guess I’ll need to use XCP Center for this since I use XO community running on the SR that needs to be destroyed/recreated in a Debian VM.
-
Did anyone try VM export/import to see how much the performance has been improved?
More interesting would be if someone tried it with 10G or making backups with XOA. -
When will the final version of XCP-ng 8.1.0. be available?
-
RC should be there pretty soon. https://github.com/xcp-ng/xcp/issues/328
-
I’ll wait till 8.1 drops before I mess with changing SR storage types.
-
@_danielgurgel said in XCP-ng 8.1.0 beta now available!:
@stormi plus this update?
https://support.citrix.com/article/CTX269586That kernel update is already available on 8.1 indeed, through yum update.
-
@nikade said in XCP-ng 8.1.0 beta now available!:
Did anyone try VM export/import to see how much the performance has been improved?
More interesting would be if someone tried it with 10G or making backups with XOA.Not yet but I'd be really grateful to anyone who could benchmark this!
-
So, the main remaining development before RC is an updated installer to allow it to boot the alternate kernel in cases where the main kernel has issues. And also an option to boot with only 2G of RAM to workaround Ryzen APU "black screen" issues.