Windows Server TechCenter >
Windows Server Forums
>
Hyper-V
>
Error 23012: Device VMBus incompatible with virtualization stack
Error 23012: Device VMBus incompatible with virtualization stack
- Hyper-V reports error 23012 regarding one of the virtual machines (WinServer 2008 R2 Beta). Is it saying that the network adapter driver in that machine is not compatible with Hyper-V?
The machine had the guest OS additions installed, but running "upgrade or repair this installation" gives me "An error has occurred: Unable to launch one of the update programs."
Any clues?
Thanks!
---
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Date: 4/14/2009 10:35:17 AM
Event ID: 23012
Task Category: None
Level: Error
Keywords:
User: NETWORK SERVICE
Computer: DL380G5.DV411.local
Description:
Device 'VMBus' in 'WinServer 2008 R2 Beta' cannot load because it is incompatible with virtualization stack. Server version 13 Client version 65537 (Virtual machine 14F1F0B0-EBA3-427B-9662-6A343A6A8B19).
---- Edited byAlex - DV411 Tuesday, April 14, 2009 6:05 PM
- Edited byAlex - DV411 Tuesday, April 14, 2009 6:06 PM
Answers
- The R2 Beta Integration Components are not compatible with the Hyper-V v1 release components.
There are enhancements and changes in R2 that consider its Integration Components beyond those of Hyper-V v1.
Integration Components are already present in WS08 and WS08 R2 - you can only upgrade, not downgrade.
If you want to run an R2 Beta build in a VM on Hyper-V v1 then you will need to use a Legacy NIC for the VM.
The networking stack has changed in the R2 release and the R2 beta ICs are expecting those modificaitons to be present.
Brian Ehlert (hopefully you have found this useful)- Marked As Answer byAlex - DV411 Tuesday, April 14, 2009 6:47 PM
All Replies
Here is a related error on the guest VM:
---
Log Name: System
Source: vmbus
Date: 4/14/2009 10:35:16 AM
Event ID: 2
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: WS2008E-R2-BETA.DV411.local
Description:
The parent partition uses a different VMBus version. You need to Install a matching VMBus version in this guest installation.
---- The R2 Beta Integration Components are not compatible with the Hyper-V v1 release components.
There are enhancements and changes in R2 that consider its Integration Components beyond those of Hyper-V v1.
Integration Components are already present in WS08 and WS08 R2 - you can only upgrade, not downgrade.
If you want to run an R2 Beta build in a VM on Hyper-V v1 then you will need to use a Legacy NIC for the VM.
The networking stack has changed in the R2 release and the R2 beta ICs are expecting those modificaitons to be present.
Brian Ehlert (hopefully you have found this useful)- Marked As Answer byAlex - DV411 Tuesday, April 14, 2009 6:47 PM
If you want to run an R2 Beta build in a VM on Hyper-V v1 then you will need to use a Legacy NIC for the VM.
Brian Ehlert (hopefully you have found this useful)
Thank you - very useful.
If you want to run an R2 Beta build in a VM on Hyper-V v1 then you will need to use a Legacy NIC for the VM.
Brian Ehlert (hopefully you have found this useful)
Hi BrianEh,
I installed a R2 beta in a VM on Hyper-V v1, the synthetic network adapter working properly.
Best regards,
Vincent Hu- Now we have the complexity of:
What beta build? (7000 or one of the later beta builds only available to TAP and MSFT).
What Hyper-V patch level?
And in this case only an incompatibility error is being noted. My experience was not that "it wouldn't work" - because they did. I just stated that they are not compatible - in a technical sence they aren't, thus the error.
However, if you want to rid yourself of the errors, you must use the Legacy NIC.
I beleive that the origional question was - "I have these errors. what do they mean? I can't install older ICs. They concern me. How do I make the errors go away?"
We have no idea what Alex was attempting to test or evaluate.
What I don't know is if there is any negative performance impact on the VM or Host due to the miss-match in ICs. (newer in the VM with older on the host)
That might be pertinent information.
Brian Ehlert (hopefully you have found this useful)
