[SOLVED] W2008R2 Unkown Device

[bensode]

I've been a busy poster here and thanks for all the help and tips thusfar I've been able to correctly get all of the VirtIO drivers working on 2012R2 but am still finding that there is one unknown device within W2008R2 that I've been unable to identify.

I have the VirtIO drivers installed for storage, network and baloon. There is still an Unknown device that I've not been able to identify that IDs itself as an ACPI/QEMUVGID. Any ideas?

 

[spirit]

do you have enable qemu agent in vm options ? this need virtio-serial driver.

you can try to simple add a driver, and choose autosearch on root of virtio cdrom, it should auto find it.

 

[dcsapak]

this is most likely the vm generation id
see https://docs.microsoft.com/en-us/windows/desktop/hyperv_v2/virtual-machine-generation-identifier

 

[t.lamprecht]

also see https://pve.proxmox.com/pve-docs/chapter-qm.html#_vm_generation_id
You can also delete it (see link) but it does no harm and is normally even useful & wanted for backup restore or snapshot rollback.

 

[bensode]

Yep that's it. Also noticed I was viewing hidden objects once I turned that off in the Device Manager display it was gone.

 

[gabrielpons]

Hi, I have exactly the same problem, with the Windows Server 2008 R2 and the unknown device (ACPI\QEMUGID) that I can't solve.

@bensode how did you solve it?

Best regards

 

[tom]

This looks not like a real issue. As you run really old OS like windows 2008r2, you got some not supported features and missing/bad driver support in future.

I would Just ignore it.

 

[gabrielpons]

This looks not like a real issue. As you run really old OS like windows 2008r2, you got some not supported features and missing/bad driver support in future.

I would Just ignore it.

OK, thanks!

 

[IgorSinelnikov]

.. if anyone needs to get rid of those unknown devices --- I finally tracked down proper cab files x64 and x86 that needs to be installed on guest Windows VMs. Email me if you wish direct download links...

 

[youring]

For the record to newbies:
1. Download windows update KB3063109 (this update from this page) to desktop. File name is windows6.x-hypervintegrationservices-x64.cab
2. Run PowerShell as Administrator:

Dism /online /Add-Package /PackagePath:C:\Users\Administrator\Desktop\windows6.x-hypervintegrationservices-x64.cab

3. Restart and the unknown device is gone.

 

[gabrielpons]

For the record to newbies:
1. Download windows update KB3063109 (this update from this page) to desktop. File name is windows6.x-hypervintegrationservices-x64.cab
2. Run PowerShell as Administrator:

Dism /online /Add-Package /PackagePath:C:\Users\Administrator\Desktop\windows6.x-hypervintegrationservices-x64.cab

3. Restart and the unknown device is gone.

Thank you very much!

 

[Roopee]

For the record to newbies:
1. Download windows update KB3063109 (this update from this page) to desktop. File name is windows6.x-hypervintegrationservices-x64.cab
2. Run PowerShell as Administrator:

Dism /online /Add-Package /PackagePath:C:\Users\Administrator\Desktop\windows6.x-hypervintegrationservices-x64.cab

3. Restart and the unknown device is gone.

Thank you, that worked for me too

 

[AN_HELL]

For the record to newbies:
1. Download windows update KB3063109 (this update from this page) to desktop. File name is windows6.x-hypervintegrationservices-x64.cab
2. Run PowerShell as Administrator:

Dism /online /Add-Package /PackagePath:C:\Users\Administrator\Desktop\windows6.x-hypervintegrationservices-x64.cab

3. Restart and the unknown device is gone.

solved great job man..

 

[somebodyoverthere]

the solution works also on Win7 x86 but with windows6.x-hypervintegrationservices-x86.cab

 

[josbmw]

For the record to newbies:

1. Download windows update KB3063109 (this update from this page) to desktop. File name is windows6.x-hypervintegrationservices-x64.cab
2. Run PowerShell as Administrator:

Dism /online /Add-Package /PackagePath:C:\Users\Administrator\Desktop\windows6.x-hypervintegrationservices-x64.cab

3. Restart and the unknown device is gone.

I have the same issue on a Server 2008 (64-bit, not R2). Old environment, currently not possible to migrate.

DISM isn't available in this Server 2008 version (DISM started with S2008 R2).
So I unpacked the cab file and had device manager search in the uppacked cab folder.
It installs Microsoft Hyper-V generation counter as device, but the driver can't be loaded in memory, error 39.
Reboot doesn't help and this is not a hidden device.

Whatever I try, I can't get this to work. There seem to be no other drivers for hardware ID ACPI\QEMUVGID for Server 2008 (or Vista, should also work).
And it's not the virtio-serial driver. I tested a lot of older driver ISO's for Proxmox, there just is no driver available what is recognized.

The VM runs fine, that's not the issue.
But I would like to get the guest agent working...