From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] isapc: Fix segfault during initialization
Date: Sun, 15 Jan 2012 15:40:40 +0100 [thread overview]
Message-ID: <4F12E568.2020800@web.de> (raw)
In-Reply-To: <4F12E4E4.8030001@codemonkey.ws>
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
On 2012-01-15 15:38, Anthony Liguori wrote:
> On 01/14/2012 07:12 AM, Jan Kiszka wrote:
>> From: Jan Kiszka<jan.kiszka@siemens.com>
>>
>> Linking the RTC device state to the PIIX does not belong into the
>> common path that is shared with the isapc. QEMU crashes otherwise.
>>
>> Signed-off-by: Jan Kiszka<jan.kiszka@siemens.com>
>
> Does isapc actually work for you? I tried to write a qemu-test test
> case (attached below) to help prevent future regressions. I can
> reproduce your SEGV but with your patch applied, I get no output (not
> even the BIOS runs).
>
> Here's the command line. Even a simple 'qemu-system-x86_64 -M isapc'
> reproduces it:
>
> /home/anthony/build/qemu/x86_64-softmmu/qemu-system-x86_64 -kernel
> bin/vmlinuz-3.0 -initrd .tmp-3510/initramfs-3510.img.gz -append
> console=ttyS0 seed=24689 -M isapc -pidfile .tmp-3510/pidfile-3510.pid
> -qmp unix:.tmp-3510/qmpsock-3510.sock,server,nowait
You need to update seabios to the last release at least (should have
been done much earlier), and it only works for KVM (as that mode ignores
some ROM write protections where seabios obviously has some troubles with).
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-01-15 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 13:12 [Qemu-devel] [PATCH] isapc: Fix segfault during initialization Jan Kiszka
2012-01-14 14:37 ` Andreas Färber
2012-01-15 14:38 ` Anthony Liguori
2012-01-15 14:40 ` Jan Kiszka [this message]
2012-01-15 16:12 ` Anthony Liguori
2012-01-15 16:16 ` Jan Kiszka
2012-01-15 16:20 ` Anthony Liguori
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=4F12E568.2020800@web.de \
--to=jan.kiszka@web.de \
--cc=anthony@codemonkey.ws \
--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).