Please share the error message from the side of Windows Server (screenshot) and your VM configuration
I have tried ti install: qemufwcfg
-------
Installed the driver and reboot. but the vport was there.
But it was not working.
Windows 10 has the same problem, is has to do ofcourse with the virtio drivers......
-------
- Open a command prompt with Administrative privileges
- At the command prompt, type the following lines, pressing ENTER after each line
set devmgr_show_nonpresent_devices=1
cd\%SystemRoot%\System32
devmgmt.msc
- In Device Manager go to View > Show hidden devices.
Installed the driver and reboot. but the vport was there.
But it was not working.
Windows 10 has the same problem, is has to do ofcourse with the virtio drivers......
Last edited:
I have seen also this on the forum:
Just to update this, as I don't think the full process is very clear and hopefully the Wiki can be tidied up:
First you need to install the guest agent. This is available in an ISO from Fedora. This in itself is a shade obscure - starting:
https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers
Then under "Windows OS support":
https://docs.fedoraproject.org/en-U...tual-machines-using-virtio-drivers/index.html
Then under "Direct downloads" is the link to the full ISO:
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso
Download that to your administrative desktop. Then in Proxmox you need to upload that to your local storage using the [Upload] button within "Contents". Once uploaded go to the hardware within your Windows Guest and mount the virtio-win.iso to the cdrom of that guest.
Then install the qemu-ga-x64.msi (64-bit) or qemu-ga-x86.msi (32-bit) from the mounted iso in the guest. You could get the msi to there from downloading within the guest or copying it over via other means - doesn't matter. But you're gonna need a further driver off the ISO anyway so I just went with mounting that.
Now this is the bit I missed initially, you've to shutdown your guest _before_ going into Options of the guest and enabling the checkbox for "QEMU Guest Agent". The vm has to be off for this to take effect - setting whilst booted and rebooting won't work.
Once that's done then you can boot the vm from cold then open Device Manager in the guest and the "PCI Simple Communications Controller" shows up. Then install the driver from driveletter:\vioserial\"OSversion". I'll prompt to trust the Redhat signed driver etc.
It doesn't seem to need a further reboot after that's installed, the Summary screen for the VM shows guest agent info under the IP information successfully.
-------------------------------------------
This was also no solution
Greetings,
Albert
Just to update this, as I don't think the full process is very clear and hopefully the Wiki can be tidied up:
First you need to install the guest agent. This is available in an ISO from Fedora. This in itself is a shade obscure - starting:
https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers
Then under "Windows OS support":
https://docs.fedoraproject.org/en-U...tual-machines-using-virtio-drivers/index.html
Then under "Direct downloads" is the link to the full ISO:
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso
Download that to your administrative desktop. Then in Proxmox you need to upload that to your local storage using the [Upload] button within "Contents". Once uploaded go to the hardware within your Windows Guest and mount the virtio-win.iso to the cdrom of that guest.
Then install the qemu-ga-x64.msi (64-bit) or qemu-ga-x86.msi (32-bit) from the mounted iso in the guest. You could get the msi to there from downloading within the guest or copying it over via other means - doesn't matter. But you're gonna need a further driver off the ISO anyway so I just went with mounting that.
Now this is the bit I missed initially, you've to shutdown your guest _before_ going into Options of the guest and enabling the checkbox for "QEMU Guest Agent". The vm has to be off for this to take effect - setting whilst booted and rebooting won't work.
Once that's done then you can boot the vm from cold then open Device Manager in the guest and the "PCI Simple Communications Controller" shows up. Then install the driver from driveletter:\vioserial\"OSversion". I'll prompt to trust the Redhat signed driver etc.
It doesn't seem to need a further reboot after that's installed, the Summary screen for the VM shows guest agent info under the IP information successfully.
-------------------------------------------
This was also no solution
Greetings,
Albert
