From: Chegu Vinod <chegu_vinod@hp.com>
To: KVM <kvm@vger.kernel.org>, qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] 3.10-rc1 guest kernel panic : known issue ?
Date: Tue, 14 May 2013 19:31:45 -0700 [thread overview]
Message-ID: <5192F391.9020703@hp.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1550 bytes --]
Hello,
On a Westmere EX system I tried to boot a 3.10-rc1 kernel in the guest
and tripped over a panic.
[ 'was only able to capture part of the info. on the guest console...
Pl. see the JPG file and also the qemu command line below. ]
'am using qemu (from qemu.git 1.4.91) that is about a day old. This
worked fine with 3.9-rc7 kernels in the guest.
I had also tried smaller guests with and without VFIO and huge pages
etc...and got the same panic.
Is this a known issue [or an operator error on my part] ?
Thanks
Vinod
/usr/local/bin/qemu-system-x86_64 \
-enable-kvm \
-cpu host \
-name vm1 \
-smp sockets=8,cores=10,threads=1 \
-numa node,nodeid=0,cpus=0-9,mem=96g \
-numa node,nodeid=1,cpus=10-19,mem=96g \
-numa node,nodeid=2,cpus=20-29,mem=96g \
-numa node,nodeid=3,cpus=30-39,mem=96g \
-numa node,nodeid=4,cpus=40-49,mem=96g \
-numa node,nodeid=5,cpus=50-59,mem=96g \
-numa node,nodeid=6,cpus=60-69,mem=96g \
-numa node,nodeid=7,cpus=70-79,mem=96g \
-m 786432 \
-mem-path /dev/hugepages \
-chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/vm1.monitor,server,nowait \
-drive
file=/dev/libvirt_lvm3/vm1,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=native
\
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
\
-monitor stdio \
-net nic,model=virtio,macaddr=52:54:00:71:01:01,netdev=nic-0 \
-netdev tap,id=nic-0,ifname=tap0,script=no,downscript=no,vhost=on \
-device vfio-pci,host=05:00.0,id=hostdev0 \
-device vfio-pci,host=05:00.1,id=hostdev1 \
-vnc :4
[-- Attachment #2: vm_panic.JPG --]
[-- Type: image/jpeg, Size: 103568 bytes --]
reply other threads:[~2013-05-15 2:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5192F391.9020703@hp.com \
--to=chegu_vinod@hp.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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).