From: Marcelo Tosatti <mtosatti@redhat.com>
To: Peter Lieven <pl@dlhnet.de>
Cc: Peter Lieven <pl@dlh.net>, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: race condition in qemu-kvm-1.0.1
Date: Wed, 4 Jul 2012 23:02:51 -0300 [thread overview]
Message-ID: <20120705020251.GA3652@amt.cnet> (raw)
In-Reply-To: <4FF4150E.2030201@dlhnet.de>
On Wed, Jul 04, 2012 at 12:03:58PM +0200, Peter Lieven wrote:
> On 07/03/12 17:54, Marcelo Tosatti wrote:
> >On Wed, Jun 27, 2012 at 12:35:22PM +0200, Peter Lieven wrote:
> >>Hi,
> >>
> >>we recently came across multiple VMs racing and stopping working. It
> >>seems to happen when the system is at 100% cpu.
> >>One way to reproduce this is:
> >>qemu-kvm-1.0.1 with vnc-thread enabled
> >>
> >>cmdline (or similar):
> >>/usr/bin/qemu-kvm-1.0.1 -net
> >>tap,vlan=141,script=no,downscript=no,ifname=tap15,vnet_hdr -net
> >>nic,vlan=141,model=virtio,macaddr=52:54:00:ff:00:f7 -drive format=host_device,file=/dev/mapper/iqn.2001-05.com.equallogic:0-8a0906-efdf4e007-16700198c7f4fead-02-debug-race-hd01,if=virtio,cache=none,aio=native
> >>-m 2048 -smp 2,sockets=1,cores=2,threads=1 -monitor
> >>tcp:0:4026,server,nowait -vnc :26 -qmp tcp:0:3026,server,nowait
> >>-name 02-debug-race -boot order=dc,menu=off -cdrom
> >>/home/kvm/cdrom//root/ubuntu-12.04-server-amd64.iso -k de -pidfile
> >>/var/run/qemu/vm-221.pid -mem-prealloc -cpu
> >>host,+x2apic,model_id=Intel(R) Xeon(R) CPU L5640 @
> >>2.27GHz,-tsc -rtc base=utc -usb -usbdevice tablet -no-hpet -vga
> >>cirrus
> >Is it reproducible without vnc thread enabled?
> Yes, it is. I tried it with and without. It is also even happnig
> with 0.12.5 where
> no vnc thread (and i think also iothread) is available.
Do you have traces without vnc-thread enabled?
WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Peter Lieven <pl@dlhnet.de>
Cc: Peter Lieven <pl@dlh.net>, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] race condition in qemu-kvm-1.0.1
Date: Wed, 4 Jul 2012 23:02:51 -0300 [thread overview]
Message-ID: <20120705020251.GA3652@amt.cnet> (raw)
In-Reply-To: <4FF4150E.2030201@dlhnet.de>
On Wed, Jul 04, 2012 at 12:03:58PM +0200, Peter Lieven wrote:
> On 07/03/12 17:54, Marcelo Tosatti wrote:
> >On Wed, Jun 27, 2012 at 12:35:22PM +0200, Peter Lieven wrote:
> >>Hi,
> >>
> >>we recently came across multiple VMs racing and stopping working. It
> >>seems to happen when the system is at 100% cpu.
> >>One way to reproduce this is:
> >>qemu-kvm-1.0.1 with vnc-thread enabled
> >>
> >>cmdline (or similar):
> >>/usr/bin/qemu-kvm-1.0.1 -net
> >>tap,vlan=141,script=no,downscript=no,ifname=tap15,vnet_hdr -net
> >>nic,vlan=141,model=virtio,macaddr=52:54:00:ff:00:f7 -drive format=host_device,file=/dev/mapper/iqn.2001-05.com.equallogic:0-8a0906-efdf4e007-16700198c7f4fead-02-debug-race-hd01,if=virtio,cache=none,aio=native
> >>-m 2048 -smp 2,sockets=1,cores=2,threads=1 -monitor
> >>tcp:0:4026,server,nowait -vnc :26 -qmp tcp:0:3026,server,nowait
> >>-name 02-debug-race -boot order=dc,menu=off -cdrom
> >>/home/kvm/cdrom//root/ubuntu-12.04-server-amd64.iso -k de -pidfile
> >>/var/run/qemu/vm-221.pid -mem-prealloc -cpu
> >>host,+x2apic,model_id=Intel(R) Xeon(R) CPU L5640 @
> >>2.27GHz,-tsc -rtc base=utc -usb -usbdevice tablet -no-hpet -vga
> >>cirrus
> >Is it reproducible without vnc thread enabled?
> Yes, it is. I tried it with and without. It is also even happnig
> with 0.12.5 where
> no vnc thread (and i think also iothread) is available.
Do you have traces without vnc-thread enabled?
next prev parent reply other threads:[~2012-07-05 2:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 10:35 race condition in qemu-kvm-1.0.1 Peter Lieven
2012-07-03 15:54 ` Marcelo Tosatti
2012-07-03 15:54 ` [Qemu-devel] " Marcelo Tosatti
2012-07-04 10:03 ` Peter Lieven
2012-07-04 10:03 ` [Qemu-devel] " Peter Lieven
2012-07-05 2:02 ` Marcelo Tosatti [this message]
2012-07-05 2:02 ` Marcelo Tosatti
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=20120705020251.GA3652@amt.cnet \
--to=mtosatti@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pl@dlh.net \
--cc=pl@dlhnet.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.