xen domU read only filesystem
I have another question on xen. I cannot get xen to create a guest that
has read/write access to its own file system. I've been Googling this
and reading documentation but so far haven't been able to find anything
on this. I have two different systems run xen now. One is 32-bit, the
other 64-bit. They both exhibit the same behavior.
Once the domU system boots I have tried looking around at
/var/log/syslog and it doesn't exist as the system can't write to its
filesystem. I can't use touch as root to create a file either. Here's
the error:
test:~# touch test
touch: cannot touch `test': Read-only file system
Here's typical output from the domU console while the guest is booting up:
[ 7.149690] ReiserFS: xvda2: warning: bad value "remount-ro" for
option "errors"
[ 7.150981] ReiserFS: xvda2: warning: bad value "remount-ro" for
option "errors"
mount: / not mounted already, or bad option
Setting the system clock.
Unable to set System Clock to: Wed Feb 4 16:55:16 UTC 2009 (warning).
Cleaning up ifupdown....
Loading kernel modules...done.
Checking file systems...fsck 1.41.3 (12-Oct-2008)
done.
Setting kernel variables (/etc/sysctl.conf)...done.
Mounting local filesystems...done.
Activating swapfile swap...done.
rm: cannot remove `.X*-lock': Read-only file system
rm: cannot remove `/tmp/.clean': Read-only file system
bootclean: Failure deleting '/tmp/.clean'. failed!
rm: cannot remove `./motd': Read-only file system
bootclean: Failure cleaning /var/run. failed!
rm: cannot remove `/var/lock/.clean': Read-only file system
bootclean: Failure deleting '/var/lock/.clean'. failed!
Setting up networking....
Configuring network interfaces...Internet Systems Consortium DHCP Client
V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
can't create /var/lib/dhcp3/dhclient.eth0.leases: Read-only file system
Listening on LPF/eth0/00:16:3e:96:02:9d
Sending on LPF/eth0/00:16:3e:96:02:9d
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPOFFER from 192.168.1.28
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.28
rm: cannot remove `/etc/resolv.conf.dhclient-new': Read-only file system
/sbin/dhclient-script: line 20: /etc/resolv.conf.dhclient-new: Read-only
file system
/sbin/dhclient-script: line 37: /etc/resolv.conf.dhclient-new: Read-only
file system
/sbin/dhclient-script: line 41: /etc/resolv.conf.dhclient-new: Read-only
file system
chown: cannot access `/etc/resolv.conf.dhclient-new': No such file or
directory
chmod: cannot access `/etc/resolv.conf.dhclient-new': No such file or
directory
mv: cannot stat `/etc/resolv.conf.dhclient-new': No such file or directory
can't create /var/lib/dhcp3/dhclient.eth0.leases: Read-only file system
bound to 192.168.1.2 -- renewal in 1567 seconds.
if-up.d/mountnfs[eth0]: lock /var/run/network/mountnfs exist, not
mounting failed!
done.
rm: cannot remove `.X*-lock': Read-only file system
rm: cannot remove `/tmp/.clean': Read-only file system
bootclean: Failure deleting '/tmp/.clean'. failed!
rm: cannot remove `./motd': Read-only file system
bootclean: Failure cleaning /var/run. failed!
rm: cannot remove `/var/lock/.clean': Read-only file system
bootclean: Failure deleting '/var/lock/.clean'. failed!
/etc/rcS.d/S55bootmisc.sh: line 29: /var/run/utmp: Read-only file system
rm: cannot remove `/var/lib/urandom/random-seed': Read-only file system
mkdir: cannot create directory `/tmp/.X11-unix': Read-only file system
Here's the output from xm list:
Name ID Mem VCPUs State
Time(s)
Domain-0 0 7603 2 r-----
3202.2
test.gawako.local 15 512 1
-b---- 3.3
Reply to: