All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lock, Joshua G" <joshua.g.lock@intel.com>
To: "Eggleton, Paul" <paul.eggleton@intel.com>,
	"Yang, Liezhi (Wind River)" <liezhi.yang@windriver.com>,
	"srifenbark@gmail.com" <srifenbark@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Migration info - runqemu
Date: Fri, 14 Oct 2016 08:35:58 +0000	[thread overview]
Message-ID: <1476434156.3083.2.camel@intel.com> (raw)
In-Reply-To: <2371a296-57bd-affa-0b1f-1304ce81e0dc@windriver.com>

On Fri, 2016-10-14 at 10:12 +0800, Robert Yang wrote:
> Hi Paul and Scott,
> 
> Here it is, and please feel free to comment, most of them are from
> qemuboot.bbclass:
> 
> The new runqemu is a python script, it requires a
> <image-name>-<machine>.qemuboot.conf to boot the bsp, the
> qemuboot.conf
> is generated by qemuboot.bbclass during build rootfs, qemu boot
> arguments can be set in bsp's conf file, and qemuboot.bbclass will
> save
> them to qemuboot.conf.

Can we also document when qemuboot.conf required and what benefits it
brings? Previous usage patterns should also be supported, right?

Thanks,

Joshua

> 
> Note, "QB" means Qemu Boot, the following vars can be set in conf
> files, such as <bsp.conf> to make it can be boot by runqemu:
> 
> QB_SYSTEM_NAME: qemu name, e.g., "qemu-system-i386"
> QB_OPT_APPEND: options to append to qemu, e.g., "-show-cursor"
> QB_DEFAULT_KERNEL: default kernel to boot, e.g., "bzImage"
> QB_DEFAULT_FSTYPE: default FSTYPE to boot, e.g., "ext4"
> QB_MEM: memory, e.g., "-m 512"
> QB_MACHINE: qemu machine, e.g., "-machine virt"
> QB_CPU: qemu cpu, e.g., "-cpu qemu32"
> QB_CPU_KVM: the similar to QB_CPU, but used when kvm, e.g., '-cpu
> kvm64',
>              set it when support kvm.
> QB_KERNEL_CMDLINE_APPEND: options to append to kernel's -append
>                            option, e.g., "console=ttyS0 console=tty"
> QB_DTB: qemu dtb name
> QB_AUDIO_DRV: qemu audio driver, e.g., "alsa", set it when support
> audio
> QB_AUDIO_OPT: qemu audio option, e.g., "-soundhw ac97,es1370", used
>                when QB_AUDIO_DRV is set.
> QB_KERNEL_ROOT: kernel's root, e.g., /dev/vda
> QB_TAP_OPT: netowrk option for 'tap' mode, e.g.,
>              "-netdev tap,id=net0,ifname=@TAP@,script=no,downscript=n
> o -device 
> virtio-net-device,netdev=net0"
>               Note, runqemu will replace "@TAP@" with the one which
> is used, 
> such as tap0, tap1 ...
> QB_SLIRP_OPT: network option for SLIRP mode, e.g.,
>              "-netdev user,id=net0 -device virtio-net-
> device,netdev=net0"
> QB_ROOTFS_OPT: used as rootfs, e.g.,
>                "-drive id=disk0,file=@ROOTFS@,if=none,format=raw
> -device 
> virtio-blk-device,drive=disk0"
>               Note, runqemu will replace "@ROOTFS@" with the one
> which is used, 
> such as core-image-minimal-qemuarm64.ext4.
> QB_SERIAL_OPT: serial port, e.g., "-serial mon:stdio"
> QB_TCPSERIAL_OPT: tcp serial port option, e.g.,
>                    " -device virtio-serial-device -chardev 
> socket,id=virtcon,port=@PORT@,host=127.0.0.1 -device
> virtconsole,chardev=virtcon"
>                    Note, runqemu will replace "@PORT@" with the port
> number 
> which is used.
> 
> Usage:
> IMAGE_CLASSES += "qemuboot"
> See "runqemu help" for more info
> 
> // Robert
> 
> On 10/14/2016 09:48 AM, Paul Eggleton wrote:
> > 
> > Hi folks,
> > 
> > We need some info for the migration section of the 2.2 manual about
> > what the
> > user needs to do to adapt to the new python-based runqemu. Robert /
> > Joshua,
> > can one of you please write something short that explains what
> > users need to
> > do (i.e. changes to the metadata for BSPs, or any other changes in
> > operation)?
> > It doesn't need to be polished, Scott Rifenbark will take care of
> > that. Just
> > replying to this email with Scott on CC should be sufficient.
> > 
> > Thanks,
> > Paul
> > 
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

  parent reply	other threads:[~2016-10-14  8:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14  1:48 Migration info - runqemu Paul Eggleton
2016-10-14  2:12 ` Robert Yang
2016-10-14  8:01   ` robert.berger@gmane
2016-10-14  8:35   ` Lock, Joshua G [this message]
2016-10-14  9:16     ` Robert Yang
2016-10-15 21:22       ` Trevor Woerner
     [not found]       ` <CAFNP8Ou9P=v+ohhXMr0gC2Kb4kwiuk2DuTrhJDHgxVLFLZvqOg@mail.gmail.com>
2016-10-19  9:31         ` Lock, Joshua G
2016-10-19  9:52           ` Robert Yang

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=1476434156.3083.2.camel@intel.com \
    --to=joshua.g.lock@intel.com \
    --cc=liezhi.yang@windriver.com \
    --cc=paul.eggleton@intel.com \
    --cc=srifenbark@gmail.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.