From: Guenter Roeck <linux@roeck-us.net>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: "qemu-devel@nongnu.org >> QEMU Developers"
<qemu-devel@nongnu.org>, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] Problems with qemu "modern" virtio on sparc64
Date: Fri, 6 Jan 2017 10:34:36 -0800 [thread overview]
Message-ID: <20170106183436.GA19862@roeck-us.net> (raw)
In-Reply-To: <3a90611b-a7c4-31c4-b373-3a16ddae5f4c@ilande.co.uk>
On Fri, Jan 06, 2017 at 05:04:58PM +0000, Mark Cave-Ayland wrote:
> On 30/12/16 19:57, Guenter Roeck wrote:
>
> Disabling "modern" mode enables boot to proceed as normal:
>
> $ ./qemu-system-sparc64 \
> -drive
> file=debian-9.0-sparc64-NETINST1.iso,if=none,index=0,id=cd,media=cdrom \
> -device virtio-blk-pci,disable-modern=on,drive=cd \
> -nographic \
> -bios openbios-builtin.elf.nostrip \
> -m 256
>
...
>
> Guenter, can you try a similar command line and confirm whether it fixes
> the issue for you under QEMU 2.7 and 2.8? I have no idea as to why the
> difference in legacy/non-legacy codepaths should crash the kernel though.
>
Unfortunately, my qemu command line wizard capabilities are somewhat lacking.
I had tried that before, but just could not figure out how to change my command
line to include "disable-modern=on". If you have an idea, please let me know.
Here it is:
${QEMU} -M ${mach} -cpu "${cpu}" -m 512 \
-drive file=${rootfs},if=virtio \
-net nic,model=virtio \
-kernel arch/sparc/boot/image -no-reboot \
-append "root=/dev/vda init=/sbin/init.sh console=ttyS0" \
-nographic
Thanks,
Guenter
next prev parent reply other threads:[~2017-01-06 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 18:11 [Qemu-devel] Problems with qemu "modern" virtio on sparc64 Guenter Roeck
2016-12-30 18:18 ` Mark Cave-Ayland
2016-12-30 19:57 ` Guenter Roeck
2017-01-06 17:04 ` Mark Cave-Ayland
2017-01-06 18:34 ` Guenter Roeck [this message]
2017-01-06 19:42 ` Mark Cave-Ayland
2017-01-06 21:05 ` Guenter Roeck
2017-01-06 21:48 ` Michael S. Tsirkin
2017-01-06 23:23 ` Guenter Roeck
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=20170106183436.GA19862@roeck-us.net \
--to=linux@roeck-us.net \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mst@redhat.com \
--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.