64 hosts tops. But in general, people tends to use around 16 to 20 hosts max in a pool. Don't forget about support

Check dmesg in the VM

I am back to the office and I am troubleshooting different settings and connection setups. I appreciate all your input. The issue is configuring the right NIC0/NIC1/WAN/ and LAN. Once I am done I post my setting. Thanks again for everyone.

Wow, didn't know it was possible to violate those rules!

Yep.. that did it... started it on the older host, and can now migrate it backwards and forwards with on issues... Thanks Olive... as always. Peter.

@r1 @olivierlambert Hello! There is nothing in any logs at all, on either the Dom_0 or Dom_U at the time of the crash, the journal on the Dom_U stops updating at the instant of the freeze and only resumes after it has been destroyed and re-started. We are in the process of moving sites to HVM, that is an ongoing part of our plan, 1 down... We've not tried running a screen session, but that is a very good idea, and we'll do that - thanks! I don't believe we've tried running in debug mode either, so will pursue that too. Thanks for the advice, I appreciate it - I know it isn't anything even remotely related to your work, but as an XCP-ng user personally, I wasn't sure where else to try. Thanks, Mark

Also you might use http://irqbalance.github.io/irqbalance/ to help "spreading" the load on various CPUs.

In XO: Advanced tab of the VM. Enable nested virt, then boot the VM. That's it!

In FreeNAS. exports file you should have fsid=123, with a unique number for each exported path. If not it can cause a problem if the nfs server is rebooted while the pool is up. https://linux.die.net/man/5/exports https://www.suse.com/support/kb/doc/?id=000017897 The stale mounts are in xcp-ng. But this is just a theory. During the power outage. Did all xcp-ng hosts and the FreeNAS as boxes go down? How did you boot up? You wrote you set up fresh servers?

Okay, this makes sense, thank you for the clarification. The reason I was asking I've been having crazy issues with xcp-ng on my server with VMs crashing all the time on boot etc and have been trying to troubleshoot and just wanted to look into this as I've done every other thing I can possibly think of. thanks again!

Yes, for this generation of CPU, you can't run ESXi superior to 6.5.

@gofm not sure on windows but on linux the walltime is written in UTC to the CMOS when you shutdown or when you explicitly call hwclock command. the time written in the virtualized CMOS should contain an offset to the host clock so when the VM start it read the host time plus the offset. I suppose that if you disable the time sync in windows, set the time and reboot you will come up with a correct clock. I have no link to point you at, this is just a sum of things I remember but may be dated and/or wrong still if you can reboot your Windows VM could be worth testing.

Hi, It's because of cache. Check more closely what's displayed in htop.

RC will be out this week (Wed. or Thursday). Mainly minor stuff before going to the release one. So I don't think you'll have issue with it.

@pnunn Got it.... guest tools hadn't installed correctly. Manually installed them.. ran the xscontainer-prepare-vm again and now have a container tab on the core OS machine showing the containers running. P.

I think you've opened a ticket right? Let's see there

Thanks! Just needed to be 200% sure!

I'm not entirely sure it could work without having serious issues. Maybe nested will be in better shape in 8.1, but it's a known 'thing' that nested virt code is a bit fragile at the moment.

@MajorTom thanks that could be a solution. In the end I moved my single-machine Homelab to Proxmox, because I have way better control in this specific use-case - I can see IOMMU groupings and figure out which USB controller I can also passthrough. And this works fine, I'm posting this from this VM. XCPng isn't bad, it´s just not suited to my very specific use case. Cheers, Clément