From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	"Aijaz.Baig" <Aijaz.Baig@protonmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: Qemu doesn't detect hard drive
Date: Fri, 03 Apr 2020 14:11:38 +0200	[thread overview]
Message-ID: <87d08opy4l.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <5c877825-dbf0-295e-20b7-6949e15be745@redhat.com> ("Philippe Mathieu-Daudé"'s message of "Fri, 3 Apr 2020 13:07:37 +0200")
Philippe Mathieu-Daudé <philmd@redhat.com> writes:
> On 4/3/20 9:39 AM, Peter Maydell wrote:
>> On Fri, 3 Apr 2020 at 06:18, Aijaz.Baig <Aijaz.Baig@protonmail.com> wrote:
>>> I would now like to add a hard disk for persistent storage and then transfer control from busybox initrd based rootfs over to the full fledged version offered with Linux. So I add it to the command line
>>>
>>> `sudo qemu-system-arm -m 1024M -M vexpress-a9 -D qemu.log -drive if=none,format=raw,file=disk.img -kernel buildroot-2019.02.5/output/images/zImage -dtb buildroot-2019.02.5/output/images/vexpress-v2p-ca9.dtb -append "console=ttyAMA0,115200 kgdboc=kbd,ttyAMA0,115200 ip=dhcp nokaslr" -initrd buildroot-2019.02.5/output/images/rootfs.cpio -nographic -net nic -net bridge,br=mybridge -s
>>
>> This command line creates a "drive" object but doesn't plug it in to anything
>> (it's like asking QEMU to model a board, with a hard drive sat next to it
>> on the desk but no cable between them :-))
>
> Should QEMU warn the user about unplugged drives?
>
> Or is it an expected feature (these drives might be hot-plugged later?)
For what it's worth, it warns about unused network backends, but not
about unused block or character backends.  All of them can be connected
later in the monitor.
     prev parent reply	other threads:[~2020-04-03 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03  5:16 Qemu doesn't detect hard drive Aijaz.Baig
2020-04-03  7:39 ` Peter Maydell
2020-04-03  8:01   ` Aijaz.Baig
2020-04-03  8:45     ` Peter Maydell
2020-04-03 11:07   ` Philippe Mathieu-Daudé
2020-04-03 12:11     ` Markus Armbruster [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=87d08opy4l.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=Aijaz.Baig@protonmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@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).