[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] domU boot/mount errors


  • To: "Arnd Schmitter" <arnd_xen@xxxxxxxx>
  • From: Stephan Böni <boeni@xxxxxx>
  • Date: Wed, 19 Oct 2005 11:00:05 +0200
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 19 Oct 2005 08:57:31 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcXUij5xupYdcoWZQe2yu3jFy8xGJwAAM5/Q
  • Thread-topic: [Xen-devel] domU boot/mount errors

> Stephan Böni wrote:
> > When i start my domU, often there are not all filesystems 
> mounted, as 
> > defined in /etc/fstab. In all cases the device nodes, like 
> > /dev/hda3, are missing. After every reboot of my domU some other 
> > device nodes are gone and others are now there, but never 
> all of them. 
> > That's really ugly.
> >  
> > # mount
> > /dev/hda1 on / type reiserfs (rw,acl,user_xattr)
> > proc on /proc type proc (rw)
> > /dev/hda13 on /usr type reiserfs (rw)
> > /dev/hda2 on /cdb type reiserfs (rw)
> > /dev/hda4 on /data/docarchive type reiserfs (rw)
> > /dev/hda5 on /home type reiserfs (rw)
> > /dev/hda7 on /data/mailserver type reiserfs (rw)
> > /dev/hda8 on /data/pos type reiserfs (rw)
> > /dev/hda9 on /data/pub type reiserfs (rw)
> > /dev/hda11 on /tmp type reiserfs (rw)
> > /dev/hda12 on /data/transfer type reiserfs (rw)
> > /dev/hda14 on /var type reiserfs (rw)
> > #
> > # mount /dev/hda10
> > mount: special device /dev/hda10 does not exist
> > #
> > # mount /dev/hda3
> > mount: special device /dev/hda3 does not exist
> >  
> > In the config file are all devices defined. Does anybody know a 
> > solution for this problem?
>
> Are you using loop-Devices ?
> I don't know if i'm right. But is there not a limit on the count of 
> loop-devices ?
> 
No, i don't use loop devices. These are all lvm volumes. Here is my
config file:

------------------------------------------------
#  -*- mode: python; -*-
 
# configuration name:
name    = "inhouse"
 
# usable ram:
memory  = 2048
 
# kernel und initrd:
kernel  = "/boot/vmlinuz-xen"
ramdisk = "/boot/initrd-xen"
 
# network interface:
vif  = [ 'mac=FE:FF:FF:FF:FF:01, bridge=xenbr0' ]
#dhcp = "dhcp"
hostname = name
 
# storage devices:
disk = [ 'phy:xenvg/inhouse-root,hda1,w',
         'phy:xenvg/inhouse-cdb,hda2,w',
         'phy:xenvg/inhouse-comserver,hda3,w',
         'phy:xenvg/inhouse-docarchive,hda4,w',
         'phy:xenvg/inhouse-home,hda5,w',
         'phy:xenvg/inhouse-journal,hda6,w',
         'phy:xenvg/inhouse-mailserver,hda7,w',
         'phy:xenvg/inhouse-pos,hda8,w',
         'phy:xenvg/inhouse-pub,hda9,w',
         'phy:xenvg/inhouse-srv,hda10,w',
         'phy:xenvg/inhouse-tmp,hda11,w',
         'phy:xenvg/inhouse-transfer,hda12,w',
         'phy:xenvg/inhouse-usr,hda13,w',
         'phy:xenvg/inhouse-var,hda14,w',
         'phy:xenvg/inhouse-swap,hdb1,w',
         'phy:xenvg/susedvd,hdc1,r' ]
 
# boot device:
root    = "/dev/hda1"
 
# boot to run level:
extra   = "3"
------------------------------------------------

Stephan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.