All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: xen-devel <xen-devel@lists.xensource.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Qemu 2.0 regression with xen: qemu crash on any domUs S.O. start
Date: Tue, 01 Apr 2014 17:01:18 +0200	[thread overview]
Message-ID: <533AD4BE.8080101@m2r.biz> (raw)

Today I tried latest qemu 2.0 compiled from git (commit 
63678e17cf399ff81b93417fe7bee8d6ef6b6b1b) on this dom0:
Debian 7 (Wheezy) 64 bit with kernel from package 
linux-image-3.2.0-4-amd64 version 3.2.54-2 and all dependency packages 
for xen, spice and usb redirection.
Seabios 1.7.3-3, spice 0.12.4-0nocelt2 and usbredir 0.6-2 compiled from 
debian unstable sources.
The xen-unstable upstream commit is 
4787f667bcee205c56a27da59b766a53e1e929eb, plus these patches not upstream:
tools: various things just to build test
tools: Improve make debball
libxl: Add qxl vga interface support for upstream qemu
libxl: add basic spice support for pv domUs

Qemu crashes always on domU S.O. start, on both pv and hvm domUs.

Same dom0 with qemu 1.6 from xen-unstable repository used for some tests 
yesterday and was full working.
I also update seabios to 1.7.4-4 compiled from debian unstable sources 
but the problem persists.

I looked on dom0 logs, qemu logs and xl dmesg and I found only a qemu 
segfault related on each domU in dom0 syslog, for example the latest:
[  844.273170] qemu-system-i38[3545]: segfault at 8 ip 00007fa905dcc4c1 
sp 00007fff41220810 error 4 in qemu-system-i386[7fa905ad5000+598000]

If you need more informations, tests and/or logs tell me and I'll post them.

Thanks for any reply.

WARNING: multiple messages have this Message-ID (diff)
From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: xen-devel <xen-devel@lists.xensource.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Qemu 2.0 regression with xen: qemu crash on any domUs S.O. start
Date: Tue, 01 Apr 2014 17:01:18 +0200	[thread overview]
Message-ID: <533AD4BE.8080101@m2r.biz> (raw)

Today I tried latest qemu 2.0 compiled from git (commit 
63678e17cf399ff81b93417fe7bee8d6ef6b6b1b) on this dom0:
Debian 7 (Wheezy) 64 bit with kernel from package 
linux-image-3.2.0-4-amd64 version 3.2.54-2 and all dependency packages 
for xen, spice and usb redirection.
Seabios 1.7.3-3, spice 0.12.4-0nocelt2 and usbredir 0.6-2 compiled from 
debian unstable sources.
The xen-unstable upstream commit is 
4787f667bcee205c56a27da59b766a53e1e929eb, plus these patches not upstream:
tools: various things just to build test
tools: Improve make debball
libxl: Add qxl vga interface support for upstream qemu
libxl: add basic spice support for pv domUs

Qemu crashes always on domU S.O. start, on both pv and hvm domUs.

Same dom0 with qemu 1.6 from xen-unstable repository used for some tests 
yesterday and was full working.
I also update seabios to 1.7.4-4 compiled from debian unstable sources 
but the problem persists.

I looked on dom0 logs, qemu logs and xl dmesg and I found only a qemu 
segfault related on each domU in dom0 syslog, for example the latest:
[  844.273170] qemu-system-i38[3545]: segfault at 8 ip 00007fa905dcc4c1 
sp 00007fff41220810 error 4 in qemu-system-i386[7fa905ad5000+598000]

If you need more informations, tests and/or logs tell me and I'll post them.

Thanks for any reply.

             reply	other threads:[~2014-04-01 15:01 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 15:01 Fabio Fantoni [this message]
2014-04-01 15:01 ` Qemu 2.0 regression with xen: qemu crash on any domUs S.O. start Fabio Fantoni
2014-04-01 16:24 ` [Qemu-devel] " Laszlo Ersek
2014-04-01 16:24   ` Laszlo Ersek
2014-04-02 11:13   ` [Qemu-devel] " Fabio Fantoni
2014-04-02 13:31     ` Laszlo Ersek
2014-04-02 13:31       ` Laszlo Ersek
2014-04-02 14:37       ` [Qemu-devel] " Fabio Fantoni
2014-04-02 16:03     ` Anthony PERARD
2014-04-02 16:03       ` Anthony PERARD
2014-04-02 16:27       ` [Qemu-devel] [Xen-devel] " Ian Campbell
2014-04-02 16:27         ` [Qemu-devel] " Ian Campbell
2014-04-03  8:15       ` Fabio Fantoni
2014-04-03  8:15         ` Fabio Fantoni
2014-04-03  8:45         ` [Qemu-devel] [Xen-devel] " Ian Campbell
2014-04-03  8:45           ` [Qemu-devel] " Ian Campbell
2014-04-03 10:13           ` [Qemu-devel] [Xen-devel] " Fabio Fantoni
2014-04-03 10:13             ` Fabio Fantoni
2014-04-07  9:59             ` [Qemu-devel] " Fabio Fantoni
2014-04-07  9:59               ` [Xen-devel] [Qemu-devel] " Fabio Fantoni
2014-04-07 10:20               ` [Qemu-devel] [Spice-devel] [Xen-devel] " Christophe Fergeau
2014-04-07 10:20                 ` [Xen-devel] [Qemu-devel] " Christophe Fergeau
2014-04-07 13:19                 ` [Qemu-devel] [Spice-devel] [Xen-devel] " Fabio Fantoni
2014-04-07 13:19                   ` [Xen-devel] [Qemu-devel] " Fabio Fantoni
2014-04-07 14:25                   ` [Qemu-devel] [Spice-devel] [Xen-devel] " Fabio Fantoni
2014-04-07 14:25                     ` [Xen-devel] [Qemu-devel] " Fabio Fantoni
2014-04-01 20:05 ` John Baboval
2014-04-02 16:05 ` Anthony PERARD
2014-04-02 16:05   ` Anthony PERARD
2014-04-03  8:20   ` [Qemu-devel] " Fabio Fantoni
2014-04-03  8:20     ` Fabio Fantoni

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=533AD4BE.8080101@m2r.biz \
    --to=fabio.fantoni@m2r.biz \
    --cc=qemu-devel@nongnu.org \
    --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 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.