VM is running but its not?

[adamb]

First time I have ran into this issue. This is a windows 10 VM. It will run aok for a few days, then the little green triangle next to the VM goes away and I can no longer access the VM. Sleep and hibernation are disabled on the VM.

The upper right buttons in proxmox have start grayed out as if the VM is running, but if I right click the VM, it offers me the option of start. If I try to start it, it says its allready running.

Does anyone have any ideas?

 

[adamb]

Kind of interesting as well.

I hit "reset", at that point the "resume" button popped up in place of "start", I hit resume and the VM came up aok, but the uptime was fresh so it seemed like a new boot.

 

[dcsapak]

i guess the vm did go into a suspended or hibernate state which can happen on a default windows install (energy plans)

 

[adamb]

i guess the vm did go into a suspended or hibernate state which can happen on a default windows install (energy plans)

Interesting, its definitely disabled and set to "never". I will have to dig some more.

 

[dcsapak]

if it occurs again, please post the status that is on the summary page, this should contain the qmp status

 

[adamb]

if it occurs again, please post the status that is on the summary page, this should contain the qmp status

Will do, thanks for the input.

 

[adamb]

Here is the status.

root@K-110580-49565:~# qm status 100
status: internal-error

 

[dcsapak]

would it be possible to get the output of

qm status ID --verbose

?

also the syslog/journal would be interesting

 

[adamb]

would it be possible to get the output of

qm status ID --verbose

?

also the syslog/journal would be interesting

I will have to get that output when it happens again as I had to kick the VM over.

 

[dcsapak]

mhmm.. not much to see

but i see you use pci passthrough, maybe an upgrade (incl kernel) helps here.

 

[adamb]

I was thinking the same thing. We have about 100 of these units in the field and they have been rock solid for over a year now. I am wondering if some windows updates have brought some issues to the for front that maybe a proxmox upgrade would address.

That will probably be my next step, moving them to 5.3.

 

[dcsapak]

if it only occurs on that one unit, maybe its a hardware problem? what are the pci devices passed through (i guess a graphics card and usb controller?) ?

 

[adamb]

if it only occurs on that one unit, maybe its a hardware problem? what are the pci devices passed through (i guess a graphics card and usb controller?) ?

Yep its a graphics card and usb controller. This specific unit its happening on is a brand new install/setup, so it could be hardware. However I am working on a fresh image and I have run into similar issues with a base 1803 install, but I can't seem to reproduce it very easily. These types of issues are always fun to figure out.

 

[dcsapak]

also possible is: gpu/mainboard firmware/bios