Updated packages addressing this issue are available for testing on XCP-ng 8.2: https://xcp-ng.org/forum/post/41480

Check https://www.oftc.net/

We are also on Discord https://discord.gg/f8FcuBDq

This looks like it was a problem with the VDI's on a network shared storage.
Unpausing the VM's would "start" them but they never actually boot - no console would appear.

In the end, migrating all other VM off the host and then rebooting the host cleared whatever was causing these VMs to be stuck and we were able to delete them

We're currently trialing a new storage provider, so this is definitely something we'll be looking into more with their support.

@toby4213

It would show as many GPU as phisical procesors available.

Also what performance could I expect from one VM with a passed through GPU?
Regarding the use of GPU full , other performace depends of other resurces alocated for the VM. (disk, memory,...)

With passthrough does NVENC work in the VM?
YES

With the use of docker you can do as 20 nvenc per GPU... with K1,, we do 14 max with K2200 (1 GPU visible and passed thru to one machine)

@darkbeldin I believe that it was created in UEFI mode but I am not certain.

When starting the .VHD file in UEFI mode I get the following screen:

efiBoot.PNG

It doesn't detect the hard drive at all as far as I can see....

Hard to tell without knowing all the details. Maybe there's other services to restart, I don't remember 🤷

For accessing a Windows VM from a remote Windows workstation using RDP multiple monitors can be used by selecting "Use all my monitors for remote session" checkbox on the display tab of the Remote Desktop Connection application on the Windows workstation. This works for me with 3 monitors.

You should probably ask OpenNebula community 🙂

What do you want to use/need with it exactly?

@danp Belatedly, many thanks

I never said THAT was impossible, as long the OS kernel started, you can use whatever drivers you like. I was just answering the fact PVHVM was a real mode since the start, and it's not. You can't have a PVHVM template, it doesn't make sense (unless you have already an OS installed).

That's all I said 🤷 You are moving the goalposts every time.

No worries 🙂

I was able to make NUT work with XCP-NG. I used and followed the instructions in this post.

On issuing the command:

[21:56 xenserver1 ups]# ./xen-shutdown.sh

All VMs shutdown EXCEPT for the Xen Orchestra. I tried remove and reinstall Xen Tools

apt install xe-guest-utilities

I'm on Ubuntu 18.04

Is there something that should be done with Xen Orchestra? Like I said, all other VMs shutdown quickly and properly. I only have Ubuntu 18.04 and one instance of FreePBX. FreePBX shutdown properly too.

Update: it seems that after 5-10 minutes (not sure yet as I haven't timed it), the entire XCP-NG does shutdown but not sure if it was a forced of graceful shutdown on the VM running XO.

@olivierlambert Thanks. I tried that right now, booting with mitigations=off and saw no improvements unfortunately.

Before:

[09:06 VIRTUAL33 ~]# grep . /sys/devices/system/cpu/vulnerabilities/* /sys/devices/system/cpu/vulnerabilities/itlb_multihit:Not affected /sys/devices/system/cpu/vulnerabilities/l1tf:Not affected /sys/devices/system/cpu/vulnerabilities/mds:Not affected /sys/devices/system/cpu/vulnerabilities/meltdown:Not affected /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Vulnerable /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: usercopy/swapgs barriers and __user pointer sanitization /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling /sys/devices/system/cpu/vulnerabilities/srbds:Not affected /sys/devices/system/cpu/vulnerabilities/tsx_async_abort:Not affected

After:

[12:18 VIRTUAL33 ~]# grep . /sys/devices/system/cpu/vulnerabilities/* /sys/devices/system/cpu/vulnerabilities/l1tf:Not affected /sys/devices/system/cpu/vulnerabilities/meltdown:Not affected /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Vulnerable /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user pointer sanitization /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling

@olivierlambert

Just a update, I have moved from the Single Socket Server to the Dell R710 with 128GB of RAM successfully all VMs are working I have also updated to 8.2

@asai Thanks for the response! Not only do I have the same messages but the C Drive was wiped (almost like every file was deleted except those which were open, the server has 6 other drives which weren't affected). I'm suspecting an issue with the Storage Repository because it's the only drive on that repository. I do have a weekly backup that runs on Sundays through Xen Orchestra. So extremely odd that it happened on the 24th, I was only googling the error message from the log! Ugh!

I ordered a new server ($$$$) which I'll transition all the VMs to and then I'll wipe and reload the current one and test/validate it from scratch since I don't trust it at this point.

@sapcode
Found a description here: https://linux.die.net/man/1/xm
But no idea why it starts some CPUs in the pause state....
Will do some testing with C states and govenor performance....

STATES

The State field lists 6 states for a Xen Domain, and which ones the current Domain is in.
r - running      The domain is currently running on a CPU
b - blocked     The domain is blocked, and not running or runnable. This can be caused because the domain is waiting on IO (a traditional wait state) or has gone to sleep because there was nothing else for it to do.
p - paused       The domain has been paused, usually occurring through the administrator running xm pause. When in a paused state the domain will still consume allocated resources like memory, but will not be eligible for scheduling by the Xen hypervisor.
s - shutdown   The guest has requested to be shutdown, rebooted or suspended, and the domain is in the process of being destroyed in response.
c - crashed      The domain has crashed, which is always a violent ending. Usually this state can only occur if the domain has been configured not to restart on crash. See xmdomain.cfg for more info.
d - dying         The domain is in process of dying, but hasn't completely shutdown or crashed.

Any thoughts on this topic? I noticed that Alpine from XO HUB didn't use irqbalance by default.

This means your XAPI is down for some reasons. Try a xe-toolstack-restart or check the logs as explained in our documentation: https://xcp-ng.org/docs/troubleshooting.html

@jmccoy555 got it. Thank you for being with me during this amazing journey 🙂