From: Laszlo Ersek <lersek@redhat.com>
To: Fabio Fantoni <fabio.fantoni@m2r.biz>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
seabios <seabios@seabios.org>,
mjt@tls.msk.ru, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
pkg-qemu-devel@lists.alioth.debian.org,
Kevin O'Connor <kevin@koconnor.net>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] Test report for xen-unstable and qemu-xen
Date: Wed, 14 Aug 2013 11:56:34 +0200 [thread overview]
Message-ID: <520B5452.4090004@redhat.com> (raw)
In-Reply-To: <520B4B94.2080506@m2r.biz>
On 08/14/13 11:19, Fabio Fantoni wrote:
> Tried with qemu 1.4.2 and it works also with 4 gb of ram.
> This ram regression seems to be introduced with qemu 1.5, and there is
> another regression more critical with qemu 1.6.
Can you save qemu's stderr for the 1.5->1.6 regression?
> Tried to add seabios debug options to domU xl configuration file...
>
> device_model_args=["-chardev
> stdio,id=seabios","-device","isa-debugcon,iobase=0x402,chardev=seabios"]
>
> But it doesn't boot
>
> /var/log/xen/qemu-dm-W7.log
> qemu-system-x86_64: -chardev stdio,id=seabios: invalid option
That's probably because you forgot to break up this option into
separate python list entries:
device_model_args=["-chardev", "stdio,id=seabios", "-device", "isa-debugcon,iobase=0x402,chardev=seabios"]
Laszlo
next prev parent reply other threads:[~2013-08-14 9:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5208F96D.3010101@m2r.biz>
2013-08-13 9:16 ` [Qemu-devel] Test report for xen-unstable and qemu-xen Fabio Fantoni
2013-08-13 10:04 ` Laszlo Ersek
2013-08-13 10:33 ` Fabio Fantoni
2013-08-13 11:09 ` Laszlo Ersek
2013-08-13 13:26 ` Fabio Fantoni
2013-08-13 23:58 ` Kevin O'Connor
2013-08-14 9:19 ` Fabio Fantoni
2013-08-14 9:56 ` Laszlo Ersek [this message]
2013-08-14 10:54 ` Fabio Fantoni
2013-08-14 11:16 ` Laszlo Ersek
2013-08-14 11:21 ` Michael S. Tsirkin
2013-08-16 13:59 ` Fabio Fantoni
2013-08-14 12:29 ` Kevin O'Connor
2013-08-14 12:50 ` 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=520B5452.4090004@redhat.com \
--to=lersek@redhat.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=fabio.fantoni@m2r.biz \
--cc=ian.campbell@citrix.com \
--cc=kevin@koconnor.net \
--cc=kraxel@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=pkg-qemu-devel@lists.alioth.debian.org \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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 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).