You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have two GPUs. However, this leads to Smart Reboot not being able to complete. Which leads to it aborting the operation, and reverts the suspending of VMs. Instead I'm met with the error message, as described below.
GPU0: AMD RX6400 (attached through GUI)
GPU1: Nvidia GTX1060 (attached through CLI as per compute-docs)
Have GPUs attached through PCI-passthrough (I have two)
Issue a smart reboot from Host/Advanced.
Expected behavior
If it isn't possible to issue and do a Smart Reboot due to PCI devices being attached. Then this should disable the Smart Reboot button altogether. Preferably with a note that makes it clear why the button is disabled.
Screenshots
No response
Node
20.18.1
Hypervisor
XCP-NG 8.3
Additional context
No response
The text was updated successfully, but these errors were encountered:
Are you using XOA or XO from the sources?
XO from the sources
Which release channel?
None
Provide your commit number
fd9c9
Describe the bug
Raising bug report, as per Oliviers request in thread https://xcp-ng.org/forum/topic/10232/feature-request-disable-smart-reboot-if-guests-have-pci-passthru
I have two GPUs. However, this leads to Smart Reboot not being able to complete. Which leads to it aborting the operation, and reverts the suspending of VMs. Instead I'm met with the error message, as described below.
GPU0: AMD RX6400 (attached through GUI)
GPU1: Nvidia GTX1060 (attached through CLI as per compute-docs)
Error message
To reproduce
Have GPUs attached through PCI-passthrough (I have two)
Issue a smart reboot from Host/Advanced.
Expected behavior
If it isn't possible to issue and do a Smart Reboot due to PCI devices being attached. Then this should disable the Smart Reboot button altogether. Preferably with a note that makes it clear why the button is disabled.
Screenshots
No response
Node
20.18.1
Hypervisor
XCP-NG 8.3
Additional context
No response
The text was updated successfully, but these errors were encountered: