@stormi said in Nested Virtualization of Windows Hyper-V on XCP-ng: Actually, Xen never officially supported Nested Virtualization. It was experimental, and broke when other needed changes were made to Xen. Now there's work to be done to make it fully supported, and this won't happen before the final release of XCP-ng 8.3. This will be documented in the release notes. This is also an issue for us internally as we create a lot of virtual pools for our tests. I read through a lot of the earlier posts and finally started scrolling to find this, which is the answer I was looking for. Why do I care? There is a Microsoft evaluation learning lab for things like Intune that runs in Hyper-V, basically a bunch of VHD (x) that get spawned as needed. Applications I need to teach myself. Running XCP-NG 8.3 current updates for this lab. If it doesn't happen, then I'll just need to throw an eval version of Windows Server on something else like an HP T740 to run these labs, not the biggest issue for me. Link for the labs if anyone is curious (free with an email registration like all the evals): https://www.microsoft.com/en-us/evalcenter/evaluate-mem-evaluation-lab-kit I'd think direct Docker support would be a higher priority than nested virtualization with a focus on Hyper-V. But that's just me.

Hello! My apologies -- I hadn't gotten around to trying this solution out until now. I just did and it appears to have fixed the issue! VMs are booting correctly and I can interact with them normally through the console. Can also confirm it works on both the 1.29 Dell FW from my original post, as well as the latest 1.32 FW available as of this post. Much thanks @andyhhp and @stormi for both your time and effort in packaging this -- I greatly appreciate it!

A VM's UEFI variables are not supposed to be erased after a migration . What kind of migration was it? Can you describe the exact operations, and whether the storage is local or shared?

I initially did try grub directly but never got the results I needed. (Could be user error) It's nice to change the resolution down because a lot of our installs have service monitors...ie monitors in the corner that were dusted off and used. I would like to see that "boot to firmware" option either in the boot loader hierarchy or as a select-able toggle. It would help on those few times I need to adjust things but my trigger finger is too atrophied to nail that esc.

@olivierlambert Meant to reply to a message in a different forum - Thanks.

@topsecret Another option is to run a hardware network time server which uses an atomic clock. Then point the NTP client for the systems of your client at that hardware time server. You can choose one of the following hardware time servers:- https://www.microchip.com/en-us/products/clock-and-timing/systems/enterprise-network-time-servers/syncserver-s600 https://timetoolsltd.com/products/network-time-server-appliances/ https://www.oscilloquartz.com/en/products-and-services/ntp-servers https://chronos.uk/products/sync-timing/ https://safran-navigation-timing.com/solution/timing-and-synchronization/ For clients which can't have internet at all even for NTP time synchronisation then running a hardware time server is a must for the network. That way all of the clocks will then be in sync with each other.

There's 2 things: VM placement during VM start, which is decided by XAPI (the host toolstack). Due to the amount of resources, there's no reason to spread the boot on different hosts. This might change depending on various factors. VM balancing while it's running, that's for XO load balancer plugin. But there's also some rules to have enough resources usages to trigger In other words: everything is normal in your case.

@olivierlambert You are totally right. I 'thought' I had added a firewall rule to allow incoming NTP requests, but I added it again and reloaded and now all three hosts are syncing. Thanks!

@melthoab Try changing your static max to 8GB.

See my reply in your other thread. Your VM is either our of disk space or your Redis database is damaged.

We experience the exact same issue with CloudLinux OS 8, seemingly random after live migration. This has been ongoing for years. Seems to happen far less now with shared storage. My theory somehow the kernel and/or PVE module doesn't handle the freeze during live migration, longer freeze, more risk of this happening. VMs start to crash random amount of time after live migration, never immideate. Could be hours, or days even, making it hard to diagnose. No crash dump, nothing, just 100% CPU on all cores and frozen console. One consistent thing we see, that happens almost every time, is that top and other tools stop working, they are frozen in a state were no CPU load etc is reported, but there is load on the server. We've been going back and forth with CloudLinux support and they did some changed to tuned profile regarding disk buffers/cache that made things at bit more stable but not gone 100%. We don't see the same error in AlmaLinux 9 and CloudLinux OS 9. More busy VM = more chance of happening. Uptime may be a factor, too.

@melthoab See the documentation -- https://docs.xcp-ng.org/vms/#️-guest-tools

@KPS it should be "yes" of course. Typo!

@KPS I don't know why my brain has decided to index all the xcp-ng forum, so when I read your post, I immediately remember the post with the clonezilla issue

@hvm said in Guest receiving passthrough SATA controllers does not see attached drives: @Teddy-Astie Hello @Teddy-Astie Have you had the opportunity to review the log file output? The past few weeks I have spent a lot of time trying to find a solution. But unfortunately after all the things I have tried, none of them have solved or did changed something to the problem. We are investigating the possibilities to run our branch locations environments with XCP-NG. This requires a working PoC where passthrough of this SATA controller is necessary.

@Andrew It's interesting because I actually had one of the previous versions of the OVA running in XCP and now that VM halts in the same place so it appears something changed on the XCP-NG side.

@Danp It is quite a varied basket. All VM's are linux. Some VM's migration directly from vmware, some were imported vmdk, some were OVA's. The several Ubuntu VMs used the Ubuntu template, some of the other's were AlmaLinux 8. Most were modified in the Advanced settings after the VM was up and running. All have CPU weight at 256. Hyperthreading and Turbo are all enabled.

@FTSSupport Got it! I'm not sure there is a way around hyper-v complaining on that front unfortunately.