Nested Virt - Xen 4.4 through 4.6 - Hyper-V; Can't boot after enabling Hyper-V

From: mailing lists <thelists@gmail.com>
To: xen-devel@lists.xen.org
Subject: Nested Virt - Xen 4.4 through 4.6 - Hyper-V; Can't boot after enabling Hyper-V
Date: Mon, 6 Apr 2015 21:42:30 -0400	[thread overview]
Message-ID: <CAETssNaeyaK6Pn3d37pTVkx18hEeKyw4pTtWkRpoe09W=GiJ9Q@mail.gmail.com> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 1659 bytes --]

Hi --

I've been trying to get nested virtualization working with Xen so that I
could boot Windows and use Hyper-V related features, however I have not had
much success.  Using Windows 8.1 or Windows 2012r2, I'm able to install
Windows, select and install Hyper-V features, and start rebooting.
However, at that point, the Windows VM only partially boots, then drops me
to a screen stating:

Your PC needs to restart.
Please hold down the power button.
Error Code: 0x0000001E
Parameters:
0xFFFFFFFFC0000096
0xFFFFF80315430485
0x0000000000000000
0x0000000000000000

Restarting does not yield any different results.

I've set up Xen in accordance with the notes for patches and config options
here:

http://wiki.xenproject.org/wiki/Nested_Virtualization_in_Xen

Trying Xen 4.4.2 stable, 4.5.1 staging, and 4.6 staging.  I applied the
patch labeled (2/2) from the wiki link above, compiled, and used the three
options provided for the DomU running Windows (hap, nestedhvm, and cpuid
mask).  Windows installs and allows me to turn on HyperV features on all
versions of Xen listed above, however all give the same or similar message
on reboot... I'm never able to get to a running state.

I've tried this on two separate systems.  One has an Intel E5-1620 v2, and
the other is a n E5-1650 (original, v1 I guess).  All the virtualization
options are enabled in the BIOS.

If the cpuid mask is removed from the DomU config, Windows boots, however
I'm unable to start any virtual machines (there was a message in the
Windows event log about a component not being started in regards to Hyper
V).

Has anyone else run into similar issues?  Any thoughts on next steps?

[-- Attachment #1.2: Type: text/html, Size: 2122 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel