From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com
Subject: XEN) vmx.c:2652:d1 Bad vmexit (reason 31) with Xen 4.0.1-rc7-pre (cs/ 23029)
Date: Thu, 17 Mar 2011 16:26:05 -0400 [thread overview]
Message-ID: <20110317202605.GA25684@dumpdata.com> (raw)
I've been hitting this only on my Intel boxes. And only on
the Nehelem ones. The older Core2Duo don't seem to encounter this.
The guest config is quite simple:
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory=1024
#maxmem=1024
maxvcpus = 4
serial='pty'
vcpus = 2
disk = [ 'file:/mnt/lab/latest/root_image.iso,hdc:cdrom,r']
boot="dn"
vif = [ 'type=ioemu,model=e1000,mac=00:0F:4B:00:00:71, bridge=switch' ]
vfb = [ 'vnc=1, vnclisten=0.0.0.0,vncunused=1']
And this is what shows up after I do 'xm create hvm.xm' (or xl create hvm.xm).
alloc irq_desc for 4223 on node -1
alloc kstat_irqs on node -1
(XEN) vmx.c:2652:d1 Bad vmexit (reason 31)
(XEN) domain_crash called from vmx.c:2653
(XEN) Domain 1 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-4.1.0-rc7-pre x86_64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: 0000:[<0000000000000000>]
(XEN) RFLAGS: 0000000000010002 CONTEXT: hvm guest
(XEN) rax: 0000000000000001 rbx: 0000000000000000 rcx: 0000000000000000
(XEN) rdx: 0000000000000000 rsi: 0000000000000000 rdi: 0000000000000000
(XEN) rbp: 0000000000000000 rsp: 0000000000000000 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) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: 0000
switch: port 2(tap1.0) entering disabled state
switch: port 2(tap1.0) entering disabled state
The Dom0 is 2.6.32.32 + for-2.6.32/bug-fixes, but the bug-fixes branch
has only bootup fixes so it should not affect this.
If I try the same exact guest configuration on a
Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz
It works without trouble.
Here is what 'xl info' has to say about this machine:
[konrad@tst009 install]$ sudo xl info
host : tst009.dumpdata.com
release : 2.6.32.32-stock-01616-g9b34843
version : #27 SMP PREEMPT Thu Mar 17 15:58:57 EDT 2011
machine : x86_64
nr_cpus : 16
nr_nodes : 2
cores_per_socket : 8
threads_per_core : 1
cpu_mhz : 2000
hw_caps : bfebfbff:28100800:00000000:00003b40:00bce3bd:00000000:00000001:00000000
virt_caps : hvm
total_memory : 12279
free_memory : 1656
free_cpus : 0
xen_major : 4
xen_minor : 1
xen_extra : .0-rc7-pre
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : Fri Mar 11 18:22:23 2011 +0000 23029:a8fee4ad3ad0
xen_commandline : guest_loglvl=all loglvl=all console=com1,vga com1=115200,8n1 console_to_ring cpuinfo apic=debug iommu=verbose,off
cc_compiler : gcc version 4.4.4 20100630 (Red Hat 4.4.4-10) (GCC)
cc_compile_by : konrad
cc_compile_domain : dumpdata.com
cc_compile_date : Mon Mar 14 12:52:11 EDT 2011
xend_config_format : 4
next reply other threads:[~2011-03-17 20:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 20:26 Konrad Rzeszutek Wilk [this message]
2011-03-17 20:34 ` XEN) vmx.c:2652:d1 Bad vmexit (reason 31) with Xen 4.0.1-rc7-pre (cs/ 23029) Konrad Rzeszutek Wilk
2011-03-17 23:27 ` Keir Fraser
2011-03-18 0:10 ` Konrad Rzeszutek Wilk
2011-03-18 0:47 ` Konrad Rzeszutek Wilk
2011-03-18 7:55 ` Jan Beulich
2011-03-18 15:31 ` Keir Fraser
2011-03-20 20:37 ` Konrad Rzeszutek Wilk
2011-03-20 22:43 ` Kay, Allen M
2011-03-21 11:35 ` Konrad Rzeszutek Wilk
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=20110317202605.GA25684@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/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).