Hi PROXMOX community,
Happy you exist. I am pretty much a complete noob here with proxmox, so any help would be greatly appreciated. I've done research and troubleshooting for the past 3 days and I can't figure out this issue. I will provide as much context as I can below.
General Description:
I am running PROXMOX VE on a custom built computer. I have only 2 VMs. One VM is running Windows Server 2019 and it's hosting a Papercut Printing server for a LAN. The plain and simple description of the issue is, about every hour, the VM just completely stops. I open Proxmox, hit start, it fires back up, and everything is peachy for about an hour until it does the exact same thing again.
Specific Troubleshooting Considerations:
Proxmox VE Errors Thrown:
- There is one error being thrown by Proxmox on this VM and it is "Error: Failed to run vncproxy." Here are some screenshots related to this error:
Event Viewer Errors: When I look through the Windows Server Event Viewer there are 2 primary event viewer errors that are coming up fairly consistently.
Device Manager Observations: I also noticed there are a few things in the device manager that could be contributing factors. I tried asking the VM To update these drivers but I'm not entirely sure how that works or what's going on there exactly.
1. Other PCI Device & PCI Simple Communications Controller Devices Seem to Be Uninstalled?
2. Hyper-V Bus Driver Seems to be not working or something?
Any help the community might be able to provide me with this issue will help an entire non-profit campus with their printing woes.
I have spent a quite a bit of time researching this thus far to no avail. Some research I did said it could be hardware related and to check temperatures and such, those seem to be fine and my other VM is not experiencing any issues. Others said it had something to do with registry permissions, I tried editing those and making sure the Windows Server user was able to perform all of the necessary activities to launch things. Issue persisted.
I appreciate any responses you might offer in advance.
Thank you,
Ruach
Happy you exist. I am pretty much a complete noob here with proxmox, so any help would be greatly appreciated. I've done research and troubleshooting for the past 3 days and I can't figure out this issue. I will provide as much context as I can below.
General Description:
I am running PROXMOX VE on a custom built computer. I have only 2 VMs. One VM is running Windows Server 2019 and it's hosting a Papercut Printing server for a LAN. The plain and simple description of the issue is, about every hour, the VM just completely stops. I open Proxmox, hit start, it fires back up, and everything is peachy for about an hour until it does the exact same thing again.
Specific Troubleshooting Considerations:
Proxmox VE Errors Thrown:
- There is one error being thrown by Proxmox on this VM and it is "Error: Failed to run vncproxy." Here are some screenshots related to this error:
Event Viewer Errors: When I look through the Windows Server Event Viewer there are 2 primary event viewer errors that are coming up fairly consistently.
- Event 124, Kernel-boot. "The virtualization-based security enablement policy check at phase 0 failed with status: The request is not supported"
- Event 41, Hyper-V-Hypervisor. "Hypervisor launch failed; Either VMX not present or not enabled in BIOS."
Device Manager Observations: I also noticed there are a few things in the device manager that could be contributing factors. I tried asking the VM To update these drivers but I'm not entirely sure how that works or what's going on there exactly.
1. Other PCI Device & PCI Simple Communications Controller Devices Seem to Be Uninstalled?
2. Hyper-V Bus Driver Seems to be not working or something?
Any help the community might be able to provide me with this issue will help an entire non-profit campus with their printing woes.
I have spent a quite a bit of time researching this thus far to no avail. Some research I did said it could be hardware related and to check temperatures and such, those seem to be fine and my other VM is not experiencing any issues. Others said it had something to do with registry permissions, I tried editing those and making sure the Windows Server user was able to perform all of the necessary activities to launch things. Issue persisted.
I appreciate any responses you might offer in advance.
Thank you,
Ruach
Last edited:
ve:000035A6:1ACC3350:61A8DA11:vncproxy:101:root@pam:
