Search results

Also, did you have the error'd "HID Button over Interrupt Driver" device in the device manager and now it's gone?

And the Qemu agent is installed and running?

Did you also go into the options on the VM and add CPU to the hotplug list?

I just saw this error as well. Installing mysql in an ubuntu 18.04 container

I've never done the NAT'ing for a guest, but since there isn't a GUI way of configuring it, I looked back at your host config and looked at the wiki entry on how to configure it. There is one thing that may be off and possibly contributing...

Not MAC address, IP address. From the symptoms, it sounds like you have 2 devices on the network configured with the same IP address, ie 192.168.1.x

Sounds like it's a damaged GPU. I've seen systems in the past work fine with a GPU until an actual GPU driver tries to load. So I bet ESXi isn't trying to initialize the GPU with an actual GPU driver like the nouveau driver does as if a GUI is going to be loaded. Try to boot in single user mode...

One time I've seen this behavior it was duplicate IPs on the network. Check the ARP table on your router/firewall and see if the MAC address for host IP is correct. Or shut your hosts down and then ping their IP's from another machine, if you get a response then something else is using the same IP.

Judging by the large subnet your static IP is in, I'm assuming your 5 IPs are all contiguous and in the same subnet. Is that true? Or are the 4 other addresses in a separate subnet? In the case where they are all in the same subnet then the routing option, at least as it's outlined in the...

nouveau is the open source nvidia display driver, could possibly be a problem with the GPU you have in the system. Any idea what GPU you have in there?

I'm not using Proxmox in a clustered scenario yet, so I'm not 100% sure how backup jobs operate in that situation, but I'm curious how many backup jobs/tasks you're running? If you have all your VMs in one job, does it start a backup of a VM from each node simultaneously, so you end up with 18...

the workaround mentioned above doesn't necessarily play well with windows kernel scheduler. see this thread for how to fix Server 2016 to allow proper hotplugging with QEMU/Proxmox https://forum.proxmox.com/threads/windows-2016-cpu-hot-plug-support.42302/

I too had issues with CPU hotplugging on Proxmox inside a Windows Server 2016 guest. Getting it working required fixing some things inside the guest. My digging actually found a bug reported to Redhat for QEMU that is really an ACPI bug in Server 2016 (and Win10). I'll refer to this link -...

Thanks pixelbaker! That was me about a year ago. I'd never touched Proxmox before v5 came out. I never ran into that problem with 2016, but thanks for adding to this little migration KB thread here. I love it when I find posts like this that keep me from having to reinvent the wheel!

Just updated the guide to include using the qm importdisk command suggested by aderumier. Preserving my previous version here as I believe it may work on older versions of Proxmox, although I have not tested that. Document critical settings such as NIC configuration (will be lost by migrating...

Oh shoot, I did not get that at all from the man page. I think on my next import, I will definitely use this and update the guide if it works. One of the reasons I liked convert and copy steps was that it left me an untouched/freshly converted copy so if I trashed the one copied to the VM trying...

I tried quite a bit to get OVMF to boot the GPT partitioning that's the default from the Hyper-V Gen2 Windows guests. Never could get it to work, but I don't know how much of that has been caused by the massive problems that Proxmox has been having with Windows guests in general since 5.1. The...

I think the reasoning for many packages not to be included in the Proxmox repositories is that you generally want your hypervisor to be very thin. It’s not too common to see hypervisors also acting as DNS and other infrastructure servers. The common thing would be to run these services inside...

Let me know if you have any suggestions that would improve or simplify the process and I'll add it to the guide.

Hi all, My home lab previously consisted of Windows servers, 2012 R2 and 2016, running Hyper-V. I had many guest VMs running that were Gen 2 VMs (aka UEFI with GPT disk partition/layout). After finally starting to tinker with Proxmox when 5.0 came out, I've decided to convert the whole thing to...