From: Saul Wold <sgw@linux.intel.com>
To: Cristian Iorga <cristian.iorga@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] qemux86-64: Support for KVM, paravirt and virtio added
Date: Tue, 18 Sep 2012 19:29:56 -0700 [thread overview]
Message-ID: <50592E24.8070701@linux.intel.com> (raw)
In-Reply-To: <1347973078-12399-1-git-send-email-cristian.iorga@intel.com>
On 09/18/2012 05:57 AM, Cristian Iorga wrote:
> KVM, paravirtualization and virtio drivers are now activated
> in runqemu using the kvm option flag for qemux86-64.
> Host CPU features are also exported to guest OS (Yocto Linux).
> Usage example: runqemu qemux86-64 core-image-x11 kvm
>
> Implements [YOCTO #2550].
>
> Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
> ---
> meta/recipes-kernel/linux/linux-yocto_3.4.bb | 3 ++-
> scripts/runqemu-internal | 4 ++--
> 2 files changed, 4 insertions(+), 3 deletions(-)
>
This seems to be an incremental change over the last one, and I have
lost track of which applies against which, can you please resend a
versioned patch (ie [PATCH v2] ) that is complete.
Thanks
Sau!
> diff --git a/meta/recipes-kernel/linux/linux-yocto_3.4.bb b/meta/recipes-kernel/linux/linux-yocto_3.4.bb
> index 32ae02b..06dd677 100644
> --- a/meta/recipes-kernel/linux/linux-yocto_3.4.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto_3.4.bb
> @@ -15,7 +15,7 @@ SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;nocheckou
>
> LINUX_VERSION ?= "3.4.10"
>
> -PR = "${INC_PR}.1"
> +PR = "${INC_PR}.3"
> PV = "${LINUX_VERSION}+git${SRCPV}"
>
> KMETA = "meta"
> @@ -28,4 +28,5 @@ KERNEL_FEATURES_append = " features/netfilter"
> KERNEL_FEATURES_append_qemux86=" cfg/sound"
> KERNEL_FEATURES_append_qemux86-64=" cfg/sound"
> KERNEL_FEATURES_append_qemux86=" cfg/paravirt_kvm"
> +KERNEL_FEATURES_append_qemux86-64=" cfg/paravirt_kvm"
> KERNEL_FEATURES_append = " ${@bb.utils.contains("TUNE_FEATURES", "mx32", " cfg/x32", "" ,d)}"
> diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal
> index f2c8d83..6e20dd7 100755
> --- a/scripts/runqemu-internal
> +++ b/scripts/runqemu-internal
> @@ -350,8 +350,8 @@ if [ "$MACHINE" = "qemux86-64" ]; then
> QEMU=qemu-system-x86_64
> QEMU_UI_OPTIONS="$QEMU_UI_OPTIONS -vga vmware"
> if [ "$FSTYPE" = "ext3" -o "$FSTYPE" = "btrfs" ]; then
> - KERNCMDLINE="vga=0 root=/dev/hda rw mem=$QEMU_MEMORY $KERNEL_NETWORK_CMD"
> - QEMUOPTIONS="$QEMU_NETWORK_CMD -hda $ROOTFS $QEMU_UI_OPTIONS"
> + KERNCMDLINE="vga=0 root=$DROOT rw mem=$QEMU_MEMORY $KERNEL_NETWORK_CMD"
> + QEMUOPTIONS="$QEMU_NETWORK_CMD $ROOTFS_OPTIONS $QEMU_UI_OPTIONS"
> fi
> if [ "$FSTYPE" = "nfs" ]; then
> if [ "x$ROOTFS" = "x" ]; then
>
next prev parent reply other threads:[~2012-09-19 2:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 12:57 [PATCH] qemux86-64: Support for KVM, paravirt and virtio added Cristian Iorga
2012-09-19 2:29 ` Saul Wold [this message]
2012-09-19 6:20 ` Iorga, Cristian
-- strict thread matches above, loose matches on Subject: below --
2012-09-19 7:06 [PATCH V2 0/2] qemux86 and qemux86-64 with KVM, paravirt and virtio Cristian Iorga
2012-09-19 7:06 ` [PATCH] qemux86-64: Support for KVM, paravirt and virtio added Cristian Iorga
2012-09-19 7:10 ` Iorga, Cristian
2012-09-18 12:48 Cristian Iorga
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=50592E24.8070701@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=cristian.iorga@intel.com \
--cc=openembedded-core@lists.openembedded.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