esSJae's Virtualization Blog

Virtualization and other IT topics

Archive for March, 2017

VirtualBox 5.1.16 Maintenance Release

Posted by essjae on March 8, 2017

Download here: https://www.virtualbox.org/wiki/Downloads

This is a maintenance release.

The following items were fixed and/or added: Changelog https://www.virtualbox.org/wiki/Changelog

  • VMM: don’t access the MSR_IA32_SMM_MONITOR_CTL MSR if dual-monitor treatment is not available (KVM workaround, bug #14965)
  • VMM: another fix for handling certain MSRs on ancient CPUs without VT-x support for MSR bitmaps
  • VMM: fixed VERR_SSM_LOAD_CPUID_MISMATCH errors when restoring a saved state with SMP guests on hosts without the CPUID/HTT bit set (bug #16428)
  • VMM: fixed a bug in call gate emulation
  • VMM: FWAIT instruction fix
  • VMM: fixed a sporadic guest hang under certain conditions
  • GUI: hide the mini-toolbar from the taskbar and the pager on certain X11 hosts
  • GUI: better error handling on the global settings / network / host-only / DHCP server settings
  • GUI: fixes for full-screen with multiple screens
  • Host-only Network: fixed host-only adapter creation issue preventing VirtualBox installation on Windows 10 hosts (bug #16379)
  • NAT network: fixed two potential crashes in the DHCP server
  • ICH9: fixed incorrect initialization of the primary bus for PCI bridges (5.1.14 regression)
  • Storage: LsiLogic fix for Windows 10
  • USB: fixed not being able to attach certain USB devices having invalid characters in the device strings (5.0.18 regression; bug #15956)
  • USB: several fixes for the USB/IP support (bug #16462)
  • VBoxSVC: fixed another crash during shutdown under rare circumstances
  • VBoxSVC: fixed a stack overflow on (Windows debug builds only; bug #16409)
  • OVF: when importing an appliance handle more than 10 network adapters if the OVA was created by VirtualBox (bug #16401)
  • OVF: fixes for exporting and importing appliances with many disks (bug #16402)
  • VBoxManage: fixed regression with modifyhd –resize (bug #16311)
  • rdesktop-vrdp: source code tarball fixes
  • Linux Installers: do not rebuild kernel modules unnecessarily (bug #16408)
  • Linux hosts: added an action for opening the VM manager window to the .desktop file
  • Linux hosts / guests: Linux 4.11 compile fixes (bug #16506)
  • Linux Additions: added vboxsf FS modules alias (bug #16404)
  • Linux Additions: fix for the shared folders kernel module to compile on Linux 4.10
  • Linux Additions: properly install the Linux kernel module override rule on distributions without /etc/depmod.d
  • Windows Additions: fixed a crash with recent Windows 10 builds if 3D is disabled (bug #15973)
Advertisements

Posted in VirtualBox, Virtualization | Tagged: , , , | Leave a Comment »

Hyper-V VMGuest.iso for older Windows OSes in Win10/2016

Posted by essjae on March 2, 2017

If you’re playing around with older OSes in the latest versions of Hyper-V, you’re missing one thing, the Integration Components (IC).

With Win10/Server2016 they no longer include this ISO as the current “supported” OSes all get their IC viaWindows Update.

You can get the IC from Hyper-V 2012/2012R2 Server, a free download, here:

https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2012-r2 ( to extract, you’ll need to mount the ISO, open the x:\sources\install.wim file with something like 7zip, browse to Windows\system32, and extract the vmguest.iso or install Hyper-V Server in a VM to get the vmguest.iso)

Or, if you’ve got a Windows 8/8.1/2012/2012R2 VM/system available with Hyper-V installed you’ll find it in the C:\windows\system32\ folder.

I’ve got a copy from Hyper-V 2012 R2 here: https://1drv.ms/u/s!AnbqFQxI6C6pidtRrLfIRLDSHKeYmw

Hyper-V 2008 R2 here: https://1drv.ms/u/s!AnbqFQxI6C6pio4TpkS4Yi9Pl0_Ejg 

Hyper-V 2008 here: https://1drv.ms/u/s!AnbqFQxI6C6pio4UYt3Jn_VLbrQs4w

No guarantees how long MS will allow it will stay up here, though it’s freely distributed with Hyper-V Server.

After installing the IC on OSes older than Windows Server 2012R2,  you will still see 2 unknown devices.  Per Microsoft, this is expected: https://support.microsoft.com/en-us/help/2925727/unknown-device-vmbus-in-device-manager-in-virtual-machine-for-avma

If you view the properties of these devices and check driver details, Hardware IDs or Compatible IDs, they will show the following:

  • vmbus\{4487b255-b88c-403f-bb51-d1f69cf17f87}
  • vmbus\{3375baf4-9e15-4b30-b765-67acb10d607b}
  • vmbus\{99221fa0-24ad-11e2-be98-001aa01bbf6e}
  • vmbus\{f8e65716-3cb3-4a06-9a60-1889c5cccab5}

These Virtual Devices (VDev) are provided for Automatic Virtual Machine Activation (AVMA) to communicate with the host. AVMA is only supported on virtual machines running Windows Server 2012 R2 or later versions of operating systems.

Windows XP Pro running in Hyper-V. Device Manager shows the 2 unknown devices after the IC have been installed.

Update:  The Integration Components won’t install in the Home and Starter versions of Windows.

Posted in Hyper-V, Virtualization, W2012, Windows 10, Windows 2012, Windows 2012 r2, Windows 2016, Windows 8, Windows 8.1 | Tagged: , , , , | 3 Comments »