From: James Dingwall <james-xen@dingwall.me.uk>
To: xen-devel@lists.xen.org
Subject: Nested Virtualisation and UEFI
Date: Fri, 4 Sep 2015 09:47:34 +0100 [thread overview]
Message-ID: <20150904084734.GA30909@dingwall.me.uk> (raw)
Hi,
I am trying to get a nested virtualisation environment working where it is started with bios='ovmf'. When my
hvm configuration is bios='seabios' and I use the xen.gz everything starts correctly. Using the xen.efi from
the same build when bios='ovmf' causesthe guest Linux kernel to block when accessing the emulated disk
controller (scsi or ide) as below.
Is this nested configuration expected to work? If so, are there other things that need to change apart from
switching the bios configuration value? I can provide more information from the guest XEN / kernel logs or the
guest configuration file if that would be useful.
[ 31.848214] ata1: lost interrupt (Status 0x50)
[ 31.855823] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 31.866516] ata1.00: failed command: READ DMA
[ 31.873472] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in
[ 31.873472] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 31.896759] ata1.00: status: { DRDY }
[ 31.902526] ata1: soft resetting link
[ 32.076309] ata1.00: configured for MWDMA2
[ 32.083559] ata1.00: device reported invalid CHS sector 0
[ 32.094014] ata1: EH complete
I am using some backported builds for Ubuntu 14.04:
dom0 (BIOS boot):
ovmf_0~20150106.5c2d456b-1build1_all.deb
qemu-system-x86_2.2+dfsg-5expubuntu9_amd64.deb
xen-hypervisor-4.5-amd64_4.5.0-1ubuntu4_amd64.deb
linux-image-generic-lts-vivid 3.19.0-26-generic
domU:
xen-4.4.3 (custom build from git release tag, also tried xen-4.5.1.efi with same behaviour)
linux-image-generic-lts-vivid 3.19.0-27-generic
Thanks,
James
next reply other threads:[~2015-09-04 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 8:47 James Dingwall [this message]
2015-09-04 9:17 ` Nested Virtualisation and UEFI Jan Beulich
2015-09-04 11:35 ` James Dingwall
2015-09-04 12:06 ` Jan Beulich
2015-09-04 13:03 ` James Dingwall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150904084734.GA30909@dingwall.me.uk \
--to=james-xen@dingwall.me.uk \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).