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

Re: [Xen-devel] domU crash


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Ewan Mellor" <ewan@xxxxxxxxxxxxx>, "Ted Kaczmarek" <tedkaz@xxxxxxxxxxxxx>
  • From: Stephan BÃni <boeni@xxxxxx>
  • Date: Mon, 17 Oct 2005 19:01:43 +0200
  • Delivery-date: Mon, 17 Oct 2005 16:59:12 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcXTIva1Uht+Vld/TeiWEA4BRPqC5AADkbNAAACjtuAAAgXFYA==
  • Thread-topic: [Xen-devel] domU crash

Deleting the /etc/mtab solved this.

Stephan

> -----UrsprÃngliche Nachricht-----
> Von: Stephan BÃni 
> Gesendet: Montag, 17. Oktober 2005 18:11
> An: xen-devel@xxxxxxxxxxxxxxxxxxx; Ewan Mellor; Ted Kaczmarek
> Betreff: Re: [Xen-devel] domU crash
> 
> 
> Very strange things occure, when starting my domU called 
> "inhouse". It has a lot problems with mounting my drives. 
> Here is the configuration file:
> 
> #  -*- mode: python; -*-
>  
> # configuration name:
> name    = "inhouse"
>  
> # usable ram:
> memory  = 2048
> 
> # usable cpus:
> cpu     = 0
> maxcpus = 1
>  
> # kernel und initrd:
> kernel  = "/boot/vmlinuz-xen"
> ramdisk = "/boot/initrd-xen"
>  
> # boot device:
> root    = "/dev/hda1"
>  
> # boot to run level:
> extra   = "3"
>  
> # network interface:
> vif  = [ 'mac=aa:cc:00:00:00:01, bridge=xenbr0' ]
> 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' ]
> 
> And here you see, what the mount displays after successful 
> boot of this domU, which is rarely:
> 
> # mount
> /dev/sda8 on / type reiserfs (rw,acl,user_xattr)
> proc on /proc type proc (rw)
> sysfs on /sys type sysfs (rw)
> tmpfs on /dev/shm type tmpfs (rw)
> devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
> usbfs on /proc/bus/usb type usbfs (rw)
> /dev/mapper/xenvg-inhouse--root on / type reiserfs (rw)
> 
> Well, /dev/sda8 is another bootable disk. Horrible but true: 
> it mounts realy strange things. The /etc/fstab file looks like that:
> 
> /dev/hda1   /                 reiserfs  defaults  1 1
> /dev/hda2   /cdb              reiserfs  defaults  1 2
> /dev/hda3   /data/comserver   reiserfs  defaults  1 2
> /dev/hda4   /data/docarchive  reiserfs  defaults  1 2
> /dev/hda5   /home             reiserfs  defaults  1 2
> /dev/hda6   /journal          reiserfs  defaults  1 2
> /dev/hda7   /data/mailserver  reiserfs  defaults  1 2
> /dev/hda8   /data/pos         reiserfs  defaults  1 2
> /dev/hda9   /data/pub         reiserfs  defaults  1 2
> /dev/hda10  /srv              reiserfs  defaults  1 2
> /dev/hda11  /tmp              reiserfs  defaults  1 2
> /dev/hda12  /data/transfer    reiserfs  defaults  1 2
> /dev/hda13  /usr              reiserfs  defaults  1 2
> /dev/hda14  /var              reiserfs  defaults  1 2
> /dev/hda15  /data/webgate     reiserfs  defaults  1 2
> /dev/hdb1   swap              swap      pri=42    0 0
> /dev/hdc1   /setup/susedvd    reiserfs  ro,noauto
> 
> Do i something wrong or exists there a realy stange bug in Xen?
> 
> 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®.