From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Adrian Freihofer <adrian.freihofer@neratec.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] runqemu-internal: add NIC to kernel parameters
Date: Thu, 29 May 2014 12:15:58 +0100 [thread overview]
Message-ID: <1401362158.2607.85.camel@ted> (raw)
In-Reply-To: <1634957.0tvEDlpPGg@chl500346>
On Tue, 2014-05-27 at 12:22 +0200, Adrian Freihofer wrote:
> Fixes [YOCTO #6356]
>
> Problem: If QEMU parameters are extended to emulate additional
> network interfaces, NFS boot does not work. Example:
> runqemu ... qemuparams="-net nic,model=virtio... -net tap, ..."
> This is solved by extending the kernel parameters by "::eth0:on"
> ---
> scripts/runqemu-internal | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal
> index d317dfd..30d6514 100755
> --- a/scripts/runqemu-internal
> +++ b/scripts/runqemu-internal
> @@ -249,7 +249,7 @@ else
> n1=$(($n0 * 2 + 1))
> n2=$(($n1 + 1))
>
> - KERNEL_NETWORK_CMD="ip=192.168.7.$n2::192.168.7.$n1:255.255.255.0"
> + KERNEL_NETWORK_CMD="ip=192.168.7.$n2::192.168.7.$n1:255.255.255.0::eth0:on"
> QEMU_TAP_CMD="-net tap,vlan=0,ifname=$TAP,script=no,downscript=no"
> if [ "$KVM_ACTIVE" = "yes" ]; then
> QEMU_NETWORK_CMD="-net nic,model=virtio $QEMU_TAP_CMD,vhost=on"
Unfortunately this results in failures in all our automated sanity
tests:
https://autobuilder.yoctoproject.org/main/builders/nightly-ipk/builds/94/steps/Running%20Sanity%20Tests_1/logs/stdio
Cheers,
Richard
next prev parent reply other threads:[~2014-05-29 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 10:22 [PATCH] runqemu-internal: add NIC to kernel parameters Adrian Freihofer
2014-05-29 11:15 ` Richard Purdie [this message]
2014-05-29 12:02 ` Stefan Stanacar
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=1401362158.2607.85.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=adrian.freihofer@neratec.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