From: "Michael S. Tsirkin" <mst@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
"qemu-devel@nongnu.org >> QEMU Developers"
<qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Problems with qemu "modern" virtio on sparc64
Date: Fri, 6 Jan 2017 23:48:37 +0200 [thread overview]
Message-ID: <20170106234743-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20170106210546.GA27764@roeck-us.net>
On Fri, Jan 06, 2017 at 01:05:46PM -0800, Guenter Roeck wrote:
> On Fri, Jan 06, 2017 at 07:42:19PM +0000, Mark Cave-Ayland wrote:
> > On 06/01/17 18:34, Guenter Roeck wrote:
> >
> > > 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
> >
> > If you apply the same principles from my example above to your command
> > line then you should end up with something like:
> >
> > ${QEMU} -M ${mach} -cpu "${cpu}" -m 512 \
> > -drive file=${rootfs},if=none,id=hd \
> > -device virtio-blk-pci,disable-modern=on,drive=hd \
> > -net nic,model=virtio \
> > -kernel arch/sparc/boot/image -no-reboot \
> > -append "root=/dev/vda init=/sbin/init.sh console=ttyS0" \
> > -nographic
> >
> That works, but only if I drop "-net nic,model=virtio". Otherwise I get
> the same crash again. Any idea how to set the network configuration
> the same way ?
>
> Thanks,
> Guenter
Replace it with -device virtio-net-pci.
--
MST
next prev parent reply other threads:[~2017-01-06 21:48 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
2017-01-06 19:42 ` Mark Cave-Ayland
2017-01-06 21:05 ` Guenter Roeck
2017-01-06 21:48 ` Michael S. Tsirkin [this message]
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=20170106234743-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=linux@roeck-us.net \
--cc=mark.cave-ayland@ilande.co.uk \
--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).