From: Stefan Priebe <s.priebe@profihost.ag>
To: Avi Kivity <avi@redhat.com>
Cc: mtosatti@redhat.com, kvm@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: KVM segfaults with 3.5 while installing ubuntu 12.04
Date: Sun, 05 Aug 2012 17:52:27 +0200 [thread overview]
Message-ID: <501E96BB.5060702@profihost.ag> (raw)
In-Reply-To: <501E4AFD.3020806@redhat.com>
Am 05.08.2012 12:29, schrieb Avi Kivity:
> On 08/05/2012 01:08 PM, Stefan Priebe wrote:
>> Am 01.08.2012 11:53, schrieb Avi Kivity:
>>> On 08/01/2012 12:42 PM, Stefan Priebe - Profihost AG wrote:
>>>> Am 01.08.2012 11:33, schrieb Avi Kivity:
>>>>>> So here are 3 backtraces from booting the rescue system:
>>>>>> http://pastebin.com/raw.php?i=xCy2pEcP
>>>>>>
>>>>>> To me they all look the same.
>>>>>
>>>>> They are. What version of qemu are you using?
>>>>
>>>> latest stable-1.1 branch (1.1.1) - which works fine with latest RHEL6
>>>> kernel.
>>>
>>> This could be due to a kernel bug, or due to a different code path taken
>>> in qemu because of differing features exposed to kvm.
>>>
>>> Please try qemu-kvm.git master and report.
>>
>> qemu-kvm.git master just hangs after the 2nd screen with using 100% CPU
>> and doing nothing... so i can't test with qemu-kvm.master
>
> Please provide your command line and I will try to reproduce.
ulimit -c unlimited; /usr/bin/qemu-x86_64 -chardev
socket,id=qmp,path=/var/run/qemu-server/103.qmp,server,nowait -mon
chardev=qmp,mode=control -pidfile /var/run/qemu-server/103.pid
-daemonize -usbdevice tablet -name kvmcrash -smp sockets=1,cores=8
-nodefaults -boot menu=on -vga cirrus -k de -drive
file=/dev/VGiSCSItarget0/vm-103-disk-1,if=none,id=drive-virtio0,aio=native,cache=none
-device
virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100
-drive
file=/var/lib/vz/template/iso/ubuntu-12.04-server-amd64.iso,if=none,id=drive-ide0,media=cdrom,aio=native
-device ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=200
-m 4096 -netdev
type=tap,id=net0,ifname=tap103i0,script=/var/lib/qemu-server/pve-bridge,vhost=on
-device
virtio-net-pci,mac=BA:5B:86:AD:14:3A,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300
> Which iso image are you running?
ubuntu-12.04-server-amd64.iso
next prev parent reply other threads:[~2012-08-05 15:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 11:59 KVM segfaults with 3.5 while installing ubuntu 12.04 Stefan Priebe - Profihost AG
2012-07-31 14:54 ` Avi Kivity
2012-07-31 17:30 ` Stefan Priebe
2012-07-31 17:37 ` Stefan Priebe
2012-08-01 8:44 ` Avi Kivity
2012-08-01 9:24 ` Stefan Priebe - Profihost AG
2012-08-01 9:33 ` Avi Kivity
2012-08-01 9:42 ` Stefan Priebe - Profihost AG
2012-08-01 9:53 ` Avi Kivity
2012-08-01 11:29 ` Stefan Priebe - Profihost AG
2012-08-01 15:15 ` Avi Kivity
2012-08-05 10:08 ` Stefan Priebe
2012-08-05 10:29 ` Avi Kivity
2012-08-05 15:52 ` Stefan Priebe [this message]
2012-08-05 19:00 ` Stefan Priebe
2012-08-06 8:36 ` Avi Kivity
2012-08-06 8:46 ` Stefan Priebe - Profihost AG
2012-08-06 12:12 ` Avi Kivity
2012-08-06 12:37 ` Avi Kivity
2012-08-06 12:48 ` Avi Kivity
2012-08-06 13:11 ` Stefan Priebe - Profihost AG
2012-08-08 5:51 ` Stefan Priebe
2012-08-08 8:06 ` Stefan Hajnoczi
2012-08-08 8:29 ` Stefan Priebe
2012-08-10 15:14 ` Stefan Hajnoczi
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=501E96BB.5060702@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.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