[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

HVM failing on 4.16.0 without qemu-xen-traditional


  • To: xen-devel@xxxxxxxxxxxxxxxxxxxx
  • From: Michael Young <m.a.young@xxxxxxxxxxxx>
  • Date: Sat, 8 Jan 2022 12:48:35 +0000 (GMT)
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=durham.ac.uk; dmarc=pass action=none header.from=durham.ac.uk; dkim=pass header.d=durham.ac.uk; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=q958oM6Jo2p1RLwZttT9K1OzYrJ5oE2vlck489M8j38=; b=I4piwqzozFhEb1A2r+j5t+oh9bxp5wUZWK5FxOLG2tZiKBnlPQ01l8BYJUqZwmRtWw+NpVdauKA5riKy/1NsUNW/i+48t3lpfCirwQFmN2r6xGPZ0O1ZIVBRlXZJPXQoUnvSVxksVpBbWZl9N8+cWVtvwxnvD2sE/f0Z8eiSttitBEBJHu4UVpb/MdWa7IzHTxG4Vl07IDpJg0G3lcFURCZ5DoMSJtiQqX0TlwlAHFm3wnX9QZSMMseJU2SELeOPS2vTppYpIah5oLq2IeaQ+c0HwugaVaelEVuKyZtiSXrW5H4kPHwjd4Wv4kMqXszODSv5Rf61y087zu+UsTpwIg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=HtEycXUp2PBamoLfAA5gghTYHprGdZWJFgMsMaUBsC7E+shbE9AQO3uFBXX5trA8UudyNcLo8aVAfPJ3MxSBf6pSzUPoWmu7SnwTJYJUfSgpBWHolDuB0D/25T5ELO8f2gtH/IZVCqjgHDKEHBawstxqCvmZ8oH0E1zO3bvEh8i/AFH5dTra/rKx+45gZ6VKsewlaz2esa+8GHgTTcju/GyMvUWQ7gIztZcuC8l0t9IEumpolKxk946ibAHPN6i5D+fcu2vCRgrNRfuLjzXI691g0QJgnDDa2NUwdiTGZkOosFUwnlboxuvavX2E3pNA31L+cixn3Fr0ZrKrnp5/hA==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=durham.ac.uk;
  • Delivery-date: Sat, 08 Jan 2022 12:48:53 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

I have been trying to build xen 4.16.0 on Fedora without qemu-xen-traditional, but it is failing to start HVM guests. xl dmesg gives the

(XEN) MMIO emulation failed (1): d1v0 32bit @ 0008:ffff11ec ->
(XEN) d1v0 Triple fault - invoking HVM shutdown action 1
(XEN) *** Dumping Dom1 vcpu#0 state: ***
(XEN) ----[ Xen-4.16.0  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    1
(XEN) RIP:    0008:[<00000000ffff11ec>]
(XEN) RFLAGS: 0000000000010046   CONTEXT: hvm guest (d1v0)
(XEN) rax: 0000000000000000   rbx: 0000000000000000   rcx: 00000000ffff11ec
(XEN) rdx: 0000000000000059   rsi: 0000000000000000   rdi: 0000000000000000
(XEN) rbp: 0000000000000000   rsp: 0000000000006fe0   r8:  0000000000000000
(XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 0000000000000000
(XEN) r12: 0000000000000000   r13: 0000000000000000   r14: 0000000000000000
(XEN) r15: 0000000000000000   cr0: 0000000000000011   cr4: 0000000000000000
(XEN) cr3: 0000000000000000   cr2: 0000000000000000
(XEN) fsb: 0000000000000000   gsb: 0000000000000000   gss: 0000000000000000
(XEN) ds: 0010   es: 0010   fs: 0010   gs: 0010   ss: 0010   cs: 0008

The full output is atttached. The same guest will boot if I build xen with qemu-xen-traditional re-enabled. The builds have --with-system-seabios= set but if I boot the guest with bios_path_override= pointing to the same file then it does boot. Is this a known issue and is there anything I can do to help debug it?

        Michael Young

Attachment: xl-dmesg.txt
Description: full xl dmesg output


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.