qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] RFC: guest-side retrieval of fw_cfg file


From: Gabriel L. Somlo
Subject: Re: [Qemu-devel] RFC: guest-side retrieval of fw_cfg file
Date: Tue, 14 Jul 2015 14:31:55 -0400
User-agent: Mutt/1.5.23 (2014-03-12)

On Tue, Jul 14, 2015 at 02:23:14PM -0400, Gabriel L. Somlo wrote:
> On Tue, Jul 14, 2015 at 10:43:46AM +0100, Richard W.M. Jones wrote:
> > On Mon, Jul 13, 2015 at 04:09:37PM -0400, Gabriel L. Somlo wrote:
> > > 3. I'm currently only handling x86 and I/O ports. I could drop the
> > >    fw_cfg_dmi_whitelist and just check the signature, using mmio where
> > >    appropriate, but I don't have a handy-dandy set of VMs for those
> > >    architectures on which I could test. Wondering if that's something
> > >    we should have before I officially try to submit this to the kernel,
> > >    or whether it could wait for a second iteration.
> > 
> >   $ virt-builder --arch armv7l fedora-22
> > or:
> >   $ virt-builder --arch aarch64 fedora-22
> > then:
> >   $ virt-builder --get-kernel fedora-22.img
> > 
> > and then boot is using the right qemu command, probably something
> > like:
> > 
> >   $ qemu-system-arm \
> >       -M virt,accel=tcg \
> >       -cpu cortex-a15 \
> >       -kernel vmlinuz-4.0.4-301.fc22.armv7hl+lpae \
> >       -initrd initramfs-4.0.4-301.fc22.armv7hl+lpae.img \
> >       -append "console=ttyAMA0 root=/dev/vda3 ro" \
> >       -drive file=fedora-22.img,if=none,id=hd \
> >       -device virtio-blk-device,drive=hd \
> >       -serial stdio
> > 
> > The root password is printed in virt-builder output.
> 
> Thanks, that should help (once I figure out how to *really* start it,
> right now it hangs at "reached target basic system", and spews garbage
> if I hit 'escape', probably in an attempt to paint the text-mode
> progress bar... Then it throws me into a dracut prompt, complaining
> that it can't find /dev/vda3...
> 
> But I'm sure I'll sort it out eventually :)

And I did figure it out, and it was a dumb typo, so nevermind this
part of the thread going forward :)

Thanks much,
--Gabriel



reply via email to

[Prev in Thread] Current Thread [Next in Thread]