XenServer developers recently contributed a patch series that removes a bit of technical debt from Xen, doing which was one of the steps towards proper nested virtualization support. There still remains a large amount of work onwards.
administrators
Private
Posts
-
RE: Nested Virtualization of Windows Hyper-V on XCP-ng
-
RE: visual bug in backup data
Hey, thanks for flagging this. I think what may be happening is that after the merge at the end of the retention chain, the UI might be picking up the full VM size (2.17 TB) instead of the actual KEY file size on disk (9.1 GB).
If you can confirm the key file is genuinely 9.1 GB on your storage, that would point to a display bug rather than a data issue.
Could you please check, and if so, it might be worth opening an issue on the XO GitHub with the numbers? I'm not entirely sure of the exact mechanism here, so @Team-XO-Backend would know better than me. -
RE: XCP-ng 8.3 updates announcements and testing
XO isn't subtle and will ask for reboot regardless of the type of update (because for now there's no way to know if reboot is required)
-
RE: XCP-ng 8.3 updates announcements and testing
Indeed, no reboot required if those are the only patches that you are applying, as indicated in the blog post.
-
RE: Understanding Auto Power On | Auto Start
As far as I understand, @john.c has it right: both the pool-level and VM-level flags need to be on for it to work.
On what actually triggers it (or what I think I understood): it's XAPI itself running on the host, not XO. XO is just showing you a toggle for a value that lives in the hypervisor config, so if XOA goes down it doesn't affect the auto-start behaviour, right?
For start order: I honestly don't know enough about this part to give a confident answer, but I think there's a
start_orderparameter in XAPI'sother-configfor each VM that controls it.
Someone more familiar with the internals here would know for sure. The main docs don't seem to cover it well, which might be worth flagging.https://docs.xen-orchestra.com/xo5/manage_infrastructure#auto-power-vm
https://docs.xcp-ng.org/guides/autostart-vm#with-the-cli -
RE: VM Migration | PIF is not attached
The "PIF is not attached" usually means the network interface selected as the migration network isn't currently active on the target host.
It can happen after upgrades if the host hasn't been fully rebooted.
Worth checking whether a reboot of both hosts changes anything, and runningxe pif-listto see whether that specific PIF showscurrently-attached: trueon the target.
If the PIF looks attached in xe but migration still fails, might be worth a ping to Team-XAPI-Network.
