public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: kvm@vger.kernel.org
Subject: Re: nfsroot stays 'readonly'
Date: Sun, 29 Jun 2008 12:16:07 +0300	[thread overview]
Message-ID: <486752D7.4090405@qumranet.com> (raw)
In-Reply-To: <20080627090006.GA26993@apartia.fr>

Louis-David Mitterrand wrote:
> Hi, 
>
> To provide an emergency off-site backup server for a client, I'm trying
> to use kvm on a nightly rsync'ed copy of their server. To avoid the use
> of a disk image I was advised to try nfsroot. This the command I am
> running:
>
> 	# kvm -nographic -hda ~/empty.qcow2 
> 		-kernel /boot/vmlinuz-2.6.25.7-1-pyrrhus64
> 		-append "3 root=/dev/nfs
> 		nfsroot=10.0.3.1:/backup/client.server.com/current/ ip=dhcp
> 		console=ttyS0 early_printk=ttyS0" -serial stdio -net nic -net
> 		tap,script=/etc/kvm/kvm-ifup-zenon -m 1024
>
> wich mostly works, the remaining problems I have are:
>
> 1) the nfsroot fs stays 'readonly' even though I modified the backup's
> fstab to read:
>
> 	10.0.3.1:/backup/client.server.com/current / nfs defaults,rw 0 0
>   

try sticking a 'mount -o remount,rw /' somewhere in the boot initscripts.

> 2) the boot lingers a long time after "activating swap" even though
> there is no swap entry in the modified fstab
>
> 3) the login: prompt is not reached, the kernel hangs at:
>
> 	Running local boot scripts (/etc/rc.local).
>   

Try to find out what it's doing there with some echos.  It may be due to 
the root filesystem being readonly.

> 4) also I'm not sure what the "console=" and "early_printk=" do; is it
> at the nfsroot or kvm level?
>
>   

These are Linux kernel options, see Documentation/kernel-parameters.txt.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2008-06-29  9:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27  9:00 nfsroot stays 'readonly' Louis-David Mitterrand
2008-06-29  9:16 ` Avi Kivity [this message]

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=486752D7.4090405@qumranet.com \
    --to=avi@qumranet.com \
    --cc=kvm@vger.kernel.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