qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aijaz.Baig@protonmail.com
To: 'Peter Maydell' <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: RE: Qemu doesn't detect hard drive
Date: Fri, 03 Apr 2020 08:01:24 +0000	[thread overview]
Message-ID: <001201d6098e$0ef0b3b0$2cd21b10$@protonmail.com> (raw)
In-Reply-To: <CAFEAcA_-aRethWOmzaKqft8yMg6dGUUwvf1kX36R4+R=yWS2RA@mail.gmail.com>

Thanks for the tip Pete. It is always tiny tidbits like these that can waste hours of time for someone coming from x86 😉. 

Ok I changed the command line and it looks like this now:
sudo qemu-system-arm -m 1024M -M vexpress-a9 -D qemu.log -sd armdisk.img -kernel buildroot-2019.02.5/output/images/zImage -dtb buildroot-2019.02.5/output/images/vexpress-v2p-ca9.dtb -append "root=/dev/ram 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

I am looking at 'dumping' a Debian like rootfs on the MMC and then use that as the default rootfs instead of the busybox one. Is there an easy to follow guide that you can point me at?  Would save me a couple hours. Also, merely specifying that partition as the kernel 'root' parameter should suffice right?

-----Original Message-----
From: Peter Maydell <peter.maydell@linaro.org> 
Sent: Friday, April 3, 2020 1:10 PM
To: Aijaz.Baig <Aijaz.Baig@protonmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: Qemu doesn't detect hard drive


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 :-))

More generally, the vexpress-a9 board does not support hard disks.
This is because the real hardware we're modelling here has no disk drive interfaces and no PCI or similar bus that you could plug a scsi controller into. The best it can do for storage is an SD card emulation, which works but the performance is not great.

thanks
-- PMM




  reply	other threads:[~2020-04-03  8:02 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 [this message]
2020-04-03  8:45     ` Peter Maydell
2020-04-03 11:07   ` Philippe Mathieu-Daudé
2020-04-03 12:11     ` Markus Armbruster

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='001201d6098e$0ef0b3b0$2cd21b10$@protonmail.com' \
    --to=aijaz.baig@protonmail.com \
    --cc=peter.maydell@linaro.org \
    --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).