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

Re: [Xen-devel] Booting DomU


  • To: "Kurt Garloff" <garloff@xxxxxxx>
  • From: Stephan Böni <boeni@xxxxxx>
  • Date: Wed, 19 Oct 2005 16:57:36 +0200
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 19 Oct 2005 14:54:53 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcXUtaGsC2x0q/zFTKSLkNJ2U76+IAABV01A
  • Thread-topic: [Xen-devel] Booting DomU

Hi Kurt

> > After trying a dozen times to create my domU the root filesystem
> > has been mounted, but not all of the others.
> 
> OK, not all block devs have been set up apparently.
> 
> > > What distro?
> > 
> > SUSE 10.0
> 
> So do I (surprise!).
> 
> Your /etc/udev/rules.d/40-xen.rules
> should point to /sbin/xen-vbd and xen-vif;

Yes, it looks like. Here is the file content:

# xen-backend block devices
SUBSYSTEM=="xen-backend", ENV{XENBUS_TYPE}=="vbd", ACTION=="add",    
RUN+="/sbin/xen-vbd %k up"
SUBSYSTEM=="xen-backend", ENV{XENBUS_TYPE}=="vbd", ACTION=="remove", 
RUN+="/sbin/xen-vbd %k down"
 
# xen-backend network devices
SUBSYSTEM=="xen-backend", ENV{XENBUS_TYPE}=="vif", ACTION=="online", 
RUN+="/sbin/xen-vif %k up"
SUBSYSTEM=="xen-backend", ENV{XENBUS_TYPE}=="vif", ACTION=="remove", 
RUN+="/sbin/xen-vif %k down"

> you could add logger calls
> there, so you can see what hotplug events reached your dom0 in the
> syslog.

How do i that? Can you explain me the syntax or just write me the needed 
entries?

> > > - What's /proc/sys/kernel/hotplug
> > 
> > # cat /proc/sys/kernel/hotplug
> > 
> > (nothing)
> 
> That's correct as well, as udevd already eats all the hotplug events.
> But my fear is that the events just don't arrive :-(

Yes, but only some of these events do not arrive. In my domU it looks
like that:

# ls /dev/hd*
/dev/hda1   /dev/hda13  /dev/hda3  /dev/hda8  /dev/hdb1
/dev/hda11  /dev/hda14  /dev/hda7  /dev/hda9  /dev/hdc1

The set of available hd* devices changes on every domU restart.
Sometimes i can't start my domU. I think that's when the root device
hda1 isn't present.

But in my config file are always the following devices defined:

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' ]

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®.