I have a problem mounting filesystems in a Xen3 domU. Often some device nodes
are missing. Am i right, that normally udev creates the needed device nodes? It
seams now, that udev in a domU does not work correct. Or has anyone a solution,
why some devices are missing?
# ls -l /dev/hda*
brw-r----- 1 root disk 3, 1 Oct 18 11:19 /dev/hda1
brw-r----- 1 root disk 3, 11 Oct 18 11:19 /dev/hda11
brw-r----- 1 root disk 3, 14 Oct 18 11:19 /dev/hda14
brw-r----- 1 root disk 3, 8 Oct 18 11:19 /dev/hda8
Even if i try to create the missing device node with the mknod command, i cannot
mount it.
# mknod /dev/hda3 b 3 3
# mount /dev/hda3
mount: /dev/hda3 is not a valid block device
Appending the needed devices in /etc/udev/static_devices.txt does not help.
Here is my domU configuration:
# cat inhouse | grep -v ^#
name = "inhouse"
memory = 2048
maxcpus = 1
kernel = "/boot/vmlinuz-xen"
ramdisk = "/boot/initrd-xen"
vif = [ ''mac=aa:cc:00:00:00:01, bridge=xenbr0'' ]
hostname = name
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'' ]
root = "/dev/hda1"
extra = "3"
I have no hda devices configured in my dom0.
Now i''m looking very puzzled, because on every restart of my domU there
are other hda devices missing. Does anyone know how to solve this problem?
Stephan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
I have a problem mounting filesystems in a Xen3 domU. Often
some device nodes are missing. Am i right, that normally udev
creates the needed device nodes? It seams now, that udev in a
domU does not work correct. Or has anyone a solution, why
some devices are missing?
# ls -l /dev/hda*
brw-r----- 1 root disk 3, 1 Oct 18 11:19 /dev/hda1
brw-r----- 1 root disk 3, 11 Oct 18 11:19 /dev/hda11
brw-r----- 1 root disk 3, 14 Oct 18 11:19 /dev/hda14
brw-r----- 1 root disk 3, 8 Oct 18 11:19 /dev/hda8
Even if i try to create the missing device node with the
mknod command, i cannot mount it.
# mknod /dev/hda3 b 3 3
# mount /dev/hda3
mount: /dev/hda3 is not a valid block device
Appending the needed devices in /etc/udev/static_devices.txt
does not help.
Here is my domU configuration:
# cat inhouse | grep -v ^#
name = "inhouse"
memory = 2048
maxcpus = 1
kernel = "/boot/vmlinuz-xen"
ramdisk = "/boot/initrd-xen"
vif = [ ''mac=aa:cc:00:00:00:01, bridge=xenbr0'' ]
hostname = name
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'' ]
root = "/dev/hda1"
extra = "3"
I have no hda devices configured in my dom0.
Now i''m looking very puzzled, because on every restart of my
domU there are other hda devices missing. Does anyone know
how to solve this problem?
Stephan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Hi Stephan, On Tue, Oct 18, 2005 at 02:02:42PM +0200, Stephan Böni wrote:> # mknod /dev/hda3 b 3 3 > # mount /dev/hda3 > mount: /dev/hda3 is not a valid block device >[...]> I have no hda devices configured in my dom0. > > Now i''m looking very puzzled, because on every restart of my > domU there are other hda devices missing. Does anyone know > how to solve this problem?Somehow, hotplug events get lost somewhere. Most probably in dom0, otherwise the mknod+mount would work. Look for syslog messages in dom0: You should find things like logger: /etc/xen/scripts/block: Writing backend/vbd/1/769/physical-device 0x0700 backend/vbd/1/769/node /dev/loop0 to xenstore. there. Use xenstore-read backend/vbd/DOM/DEVNO to check what the scripts have set up in dom0. (DEVNO = 256*major+minor) Best, -- Kurt Garloff <kurt@garloff.de> [Koeln, DE] Physics:Plasma modeling <garloff@plasimo.phys.tue.nl> [TU Eindhoven, NL] Linux: SUSE Labs (Director) <garloff@suse.de> [Novell Inc] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi Kurt> > Now i''m looking very puzzled, because on every restart of my > > domU there are other hda devices missing. Does anyone know > > how to solve this problem? > > Somehow, hotplug events get lost somewhere. > Most probably in dom0, otherwise the mknod+mount would work. > > Look for syslog messages in dom0: You should find things like > logger: /etc/xen/scripts/block: Writing > backend/vbd/1/769/physical-device > 0x0700 backend/vbd/1/769/node /dev/loop0 to xenstore. > there.Yes, the "bind" was made for every device, but the "Writing backend" only for some devices. If it has made, i can see the devices in my domU.> Use xenstore-read backend/vbd/DOM/DEVNO to check what the scripts > have set up in dom0. (DEVNO = 256*major+minor)It says nothing. Stephan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Wed, Oct 19, 2005 at 06:26:30PM +0200, Stephan Böni wrote:> > > Now i''m looking very puzzled, because on every restart of my > > > domU there are other hda devices missing. Does anyone know > > > how to solve this problem? > > > > Somehow, hotplug events get lost somewhere. > > Most probably in dom0, otherwise the mknod+mount would work. > > > > Look for syslog messages in dom0: You should find things like > > logger: /etc/xen/scripts/block: Writing > > backend/vbd/1/769/physical-device > > 0x0700 backend/vbd/1/769/node /dev/loop0 to xenstore. > > there. > > Yes, the "bind" was made for every device, but the "Writing > backend" only for some devices. If it has made, i can see the > devices in my domU.OK, so the events get triggered, but the scripts to set things up hang or fail. Strange.> > Use xenstore-read backend/vbd/DOM/DEVNO to check what the scripts > > have set up in dom0. (DEVNO = 256*major+minor) > > It says nothing.xenstore-list would have been the right command, sorry. Best, -- Kurt Garloff, Director SUSE Labs, Novell Inc. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi Kurt> > > > Now i''m looking very puzzled, because on every restart of my > > > > domU there are other hda devices missing. Does anyone know > > > > how to solve this problem? > > > > > > Somehow, hotplug events get lost somewhere. > > > Most probably in dom0, otherwise the mknod+mount would work. > > > > > > Look for syslog messages in dom0: You should find things like > > > logger: /etc/xen/scripts/block: Writing > > > backend/vbd/1/769/physical-device > > > 0x0700 backend/vbd/1/769/node /dev/loop0 to xenstore. > > > there. > > > > Yes, the "bind" was made for every device, but the "Writing > > backend" only for some devices. If it has made, i can see the > > devices in my domU. > > OK, so the events get triggered, but the scripts to set things > up hang or fail. Strange. > > > > Use xenstore-read backend/vbd/DOM/DEVNO to check what the scripts > > > have set up in dom0. (DEVNO = 256*major+minor) > > > > It says nothing. > > xenstore-list would have been the right command, sorry.If it works: | xenstore-list backend/vbd/11/782 domain params frontend-id type dev frontend physical-device node sectors info sector-size else: | xenstore-list backend/vbd/11/773 domain params frontend-id type dev frontend Stephan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi Kurt> > > > Now i''m looking very puzzled, because on every restart of my > > > > domU there are other hda devices missing. Does anyone know > > > > how to solve this problem? > > > > > > Somehow, hotplug events get lost somewhere. > > > Most probably in dom0, otherwise the mknod+mount would work. > > > > > > Look for syslog messages in dom0: You should find things like > > > logger: /etc/xen/scripts/block: Writing > > > backend/vbd/1/769/physical-device > > > 0x0700 backend/vbd/1/769/node /dev/loop0 to xenstore. > > > there. > > > > Yes, the "bind" was made for every device, but the "Writing > > backend" only for some devices. If it has made, i can see the > > devices in my domU. > > OK, so the events get triggered, but the scripts to set things > up hang or fail. Strange. > > > > Use xenstore-read backend/vbd/DOM/DEVNO to check what the scripts > > > have set up in dom0. (DEVNO = 256*major+minor) > > > > It says nothing. > > xenstore-list would have been the right command, sorry.If it works: | xenstore-list backend/vbd/11/782 domain params frontend-id type dev frontend physical-device node sectors info sector-size else: | xenstore-list backend/vbd/11/773 domain params frontend-id type dev frontend Stephan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel