All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] NFS-root
Date: Mon, 31 May 2004 07:39:04 +0600	[thread overview]
Message-ID: <40BA8CB8.5010300@ums.usu.ru> (raw)

[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]

I have experimented with NFS-root linux installations in qemu recently. 
Results follow. All of them are obtained with this command or its 
variations:

qemu -nographic -hda hda.dsk -m 64 -kernel bzImage -append 
"console=ttyS0 root=/dev/nfs ro nfsroot=10.0.2.2:/jail 
ip=10.0.2.15:10.0.2.2:::::off init=/bin/sh ide0=noprobe ide1=noprobe 
ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe" -user-net

In /jail, there are dev/console, dev/null, bin/sh and libraries it 
depends upon. The directory is exported in /etc/exports in the following 
way:

/jail        (ro,insecure)

The .config file for 2.6.6 linux kernel used for this experiment is 
attached.

1) I have to create a dummy hard disk image because of that "-kernel 
requires -hda" check. The diskless configuration is perfectly valid, 
please remove the check.

2) Everything works perfectly with tun-tap networking (of course with IP 
addresses adjusted).

3) I cannot make the kernel mount the root filesystem via NFS over UDP 
if I use -user-net. However, if I replace nfsroot=10.0.2.2:/jail with 
nfsroot=10.0.2.2:/jail,tcp everything works.

Why does the difference exist between tun-tap and slirp cases when UDP 
is used? Is this a bug?

-- 
Alexander E. Patrakov

[-- Attachment #2: config.gz --]
[-- Type: application/x-eprint-tar, Size: 4307 bytes --]

                 reply	other threads:[~2004-05-31  1:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=40BA8CB8.5010300@ums.usu.ru \
    --to=patrakov@ums.usu.ru \
    --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 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.