Unknown device in Win7 VM

[Raptor039]

Hi,

since I upgraded my proxmox server to 5.3 and after installed a new Win7 VM, I'm facing with an issue. In the devices manager, a new uknown device appeared and for which there is no drivers found in the virtio driver iso.

It seems this new device (qemuvgid) is linked to a PVE new feature : VM Generation ID.

Do you know if I can found somewhere a driver for my Win 7 guest to solve this issue or I should just leave it unconfigured ?

Thanks for your help.

Kind Regards.

 

[dcsapak]

it seems windows 7 does not have native vm generation id support, see https://docs.microsoft.com/en-us/windows/desktop/hyperv_v2/virtual-machine-generation-identifier

 

[tobby]

I stumbled upon this when I searched for the unknown device. But I couldn't find a working solution... I tried for a while and found this solution:
1.) Download the Integration Services from Microsoft Download Center:
https://support.microsoft.com/en-us...nents-update-for-windows-virtual-machines-tha
2.) Open a Powershell with Admin-rights
3.) Execute this:
Dism /online /Add-Package /PackagePath:C:\packages\package.cab
(You have to change the path to the path where you put the downloaded cab file)

 

[stephenvr]

I stumbled upon this when I searched for the unknown device. But I couldn't find a working solution... I tried for a while and found this solution:
1.) Download the Integration Services from Microsoft Download Center:

2.) Open a Powershell with Admin-rights
3.) Execute this:
Dism /online /Add-Package /PackagePath:C:\packages\package.cab
(You have to change the path to the path where you put the downloaded cab file)

Resolved my issue. Thanks for the post.

 

[COMMARMOND Christian]

I had a problem starting the qemu-agent on Win7.

Install this solved the problem (after installing the qemu-agent, it just refused to start with error 1053. I had 3 unknown peripherals. Installing the drivers allowed the qemu agent to start)

I found online information nowhere. So I put this here, since it solved this issue.

Thanks to the previous posters for helping me too.

Then for those who did not find it, some other page pointed me to the last qemu agent:
New users cannot post links ... So, search qemu-ga-win-7.6.2-2.el7ev on your preferred search tool to find the latest and working qemu guest agent.
which solved the NO IP address in the summary page with (the old) qemu-agent installed


Christian

 

[stephenvr]

Helped me too thanks.

 

[tobby]

Your version of the guest agent was released in August of 2018. There is a newer version, released in February of 2019: https://fedorapeople.org/groups/vir...rchive-qemu-ga/qemu-ga-win-100.0.0.0-3.el7ev/

 

[COMMARMOND Christian]

ouarf... Thank you... I did not see that they are not sorted per version.

 

[tobby]

Yes, I got confused by their "order" (and their naming conventions), too...

 

[IgorSinelnikov]

old one... but I could help if anyone still interested in getting rid of those unknown devices..

 

[tom]

old one... but I could help if anyone still interested in getting rid of those unknown devices..

just post the solution to this forum.

 

[IgorSinelnikov]

The files are on the Microsoft support download site but they are hard to find.
Here is the link to my nextcloud folder. Try it out

https://nextcloud.facsci.ualberta.ca/s/AXHP47itHrCFSp4

Then you can google how to install cab-files.

 

[tobby]

I prefer downloading this from Microsoft over downloading from someones Nextcloud

The link to MS and also the guide how to install cab files has been posted in #3 already: https://forum.proxmox.com/threads/unknown-device-in-win7-vm.49698/#post-246732

 

[IgorSinelnikov]

agreed,,, especially downloading files off a nextcloud site owned by a russian.

The solution that have been posted is only for 64-bit OSes.
I had some headache trying to locate the needed cab file for 2008 32-bit server OS.
Regardless ... the moderator here can kill the post with the link if needed.

 

[tobby]

Hahaha yes

Look into #3, there is a link to the MS download page, which also includes the CABs for 32bit OSes. Server 2008 is based on the Vista-kernel, 2008 R2 on Windows 7. So for 2008 R2 32bit you should give the CAB for x86 Windows 7 a try.

 

[ChikiHh]

I stumbled upon this when I searched for the unknown device. But I couldn't find a working solution... I tried for a while and found this solution:
1.) Download the Integration Services from Microsoft Download Center:
https://support.microsoft.com/en-us...nents-update-for-windows-virtual-machines-tha
2.) Open a Powershell with Admin-rights
3.) Execute this:
Dism /online /Add-Package /PackagePath:C:\packages\package.cab
(You have to change the path to the path where you put the downloaded cab file)

Thanks! It works on VM with win serv 2008.

 

[Tittan]

Thanks! It works on VM with win serv 2008.

Hello all,
I have 2 VMS Windows Server 2008 SP2 x64 that I've successfully imported to my Proxmox VE. I have the VM_Gen_Counter unknown device in the device manager. I was trying to follow the ChikiHh instructions but I cannot run DISM on my VMS it seems I don't have DISM.exe on them. Can anyone help me? Thanks

 

[IgorSinelnikov]

As far as I remember there was no dism tool prior Windows 2008 R2. You just need to locate a proper cab file and install it manually.

Google how to do it or maybe read up this link:
https://techcommunity.microsoft.com...hes-manually-on-vista-server-2008/ba-p/322027

It's been years but I think it worked for a few of mine Windows 2008 SP2 32-bit VMs.

ps. But What do I know , - I'm a *nix guy.

 

[Roopee]

I stumbled upon this when I searched for the unknown device. But I couldn't find a working solution... I tried for a while and found this solution:
1.) Download the Integration Services from Microsoft Download Center:
https://support.microsoft.com/en-us...nents-update-for-windows-virtual-machines-tha
2.) Open a Powershell with Admin-rights
3.) Execute this:
Dism /online /Add-Package /PackagePath:C:\packages\package.cab
(You have to change the path to the path where you put the downloaded cab file)

Thank you @tobby - this worked for me
Windows 2008 R2 64-bit clean install on zfspool on Proxmox 7.2-3, after converting boot disk from IDE to VirtIO SCSI and installing QEMU Guest Agent - just had one unknown device left of type QEMUVGID.