From: Igor Mammedov <imammedo@redhat.com>
To: Asias He <asias@cloudius-systems.com>
Cc: Dmitry Fleytman <dmitry@daynix.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] vmw_pvscsi: QEMU stuck in SeaBIOS when pvscsi is enabled
Date: Wed, 17 Sep 2014 09:05:17 +0200 [thread overview]
Message-ID: <20140917090517.15c67604@nial.usersys.redhat.com> (raw)
In-Reply-To: <CAO1GqFYm+vkpqCffrueS996yXNLhvMZXhkU82cdr1VWV898f4A@mail.gmail.com>
On Wed, 17 Sep 2014 07:12:42 +0800
Asias He <asias@cloudius-systems.com> wrote:
> Hello Paolo,
>
>
> On Tue, Sep 16, 2014 at 10:33 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> > Il 16/09/2014 16:25, Igor Mammedov ha scritto:
> > > Current master cc35a44cf7b522b,
> > >
> > > QEMU is not able to boot an stuck in SeaBIOS (only SeaBIOS version was
> > printed)
> > > when started with "-device pvscsi" CLI option.
> > >
> > > I've used following CLI in my test case:
> > > qemu-system-x86_64 -enable-kvm -m 1024 -snapshot -monitor stdio -device
> > pvscsi,id=pvscsi -drive if=none,id=fc,file=fc18x64 -device
> > scsi-disk,drive=fc,bus=pvscsi.0
> >
> > Asias, we talked about this a few months ago I think? Did you ever
> > debug it?
>
>
> Last time I checked, I remember I could't compile the latest SeaBIOS and
> pvscsi disk is able to attach as a non-boot disk. It is probably a SeaBIOS
> bug.
>
Only this time QEMU is stuck with pvscsi as non-boot disk also,
it's sufficient for pvscsi controller to be present even without disk
to cause above issue.
prev parent reply other threads:[~2014-09-17 7:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 14:25 [Qemu-devel] vmw_pvscsi: QEMU stuck in SeaBIOS when pvscsi is enabled Igor Mammedov
2014-09-16 14:33 ` Paolo Bonzini
2014-09-16 23:12 ` Asias He
2014-09-17 7:05 ` Igor Mammedov [this message]
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=20140917090517.15c67604@nial.usersys.redhat.com \
--to=imammedo@redhat.com \
--cc=asias@cloudius-systems.com \
--cc=dmitry@daynix.com \
--cc=pbonzini@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 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).