Hello, Can you check following entrys: Old: disk = [''phy:vm_volumes/root.dhcp1,sda1,w'', ''phy:vm_volumes/var.dhcp1,sda2,w'', ''phy:vm_volumes/swap.dhcp1,sda3,w''] New: disk = [''phy:/vm_volumes/root.dhcp1,sda1,w'', ''phy:/vm_volumes/var.dhcp1,sda2,w'', ''phy:/vm_volumes/swap.dhcp1,sda3,w''] I think the system can not find the images, test it plz. I hope this will help :-) Regards Stefan -----Ursprüngliche Nachricht----- Von: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] Im Auftrag von Angel L. Mateo Gesendet: Mittwoch, 8. März 2006 09:32 An: xen-users@lists.xensource.com Betreff: [*****SPAM***** HOM02EX - BA] - [Xen-users] Problem booting domU - Bayesian Filter detected spam Hello, I have just installed xen 3.0.1 in a debian sarge system. After some days of trying with binary distribution of xen, I found a debian sarge backport at http://packages.debianbase.de/sarge/i386/xen3, and this is the one I have installed. I have compiled my dom0''s custom kernel (I had to do it because the "standard" one doesn''t boot in my dell poweredge 750). Basically, the difference between the standard and mine is that I have included megaraid in the kernel, not as a module). With this custom kernel I have running my dom0. The problem I have is what domU. I created a debian system for domU (with debootsrap) and I compiled a new custom domU kernel. This kernel is the same as dom0 but I have also include raid support in the kernel (not as a module, in dom0 I have it as a module). The problem I have is that I can''t boot this domU, because I get the error: VFS: Cannot open root device "sda1" or unknown-block(8,1) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1) I have tried to boot domU with the same kernel as dom0, but I get the same behaviour. Any help? PS: attached is the full log I get when I try to boot domU and the configuration of this domU. -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica _(___V Tfo: 968367590 Fax: 968398337 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
El mié, 08-03-2006 a las 09:45 +0100, Stefan Mikuszeit escribió:> Hello, > > Can you check following entrys: > > Old: > disk = [''phy:vm_volumes/root.dhcp1,sda1,w'', > ''phy:vm_volumes/var.dhcp1,sda2,w'', > ''phy:vm_volumes/swap.dhcp1,sda3,w''] > > > New: > disk = [''phy:/vm_volumes/root.dhcp1,sda1,w'', > ''phy:/vm_volumes/var.dhcp1,sda2,w'', > ''phy:/vm_volumes/swap.dhcp1,sda3,w''] > > I think the system can not find the images, test it plz. >When I try this configuration I get: felis:/etc/xen# xm create dhcp1.cfg -c Using config file "dhcp1.cfg". Error: Device 2049 (vbd) could not be connected. Device /vm_volumes/root.dhcp1 is mounted in a guest domain, and so cannot be mounted now. -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica _(___V Tfo: 968367590 Fax: 968398337 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yes this is right at the moment, xen will find now the Drives, but can''t mount this drives. The Problem is you have mounted this drive in an other domain 0/U ! You will mount the Devices for more then one Domain ? This make better with samba or NFS, please read the xen HowTo''s for this Problem. Regards Stefan -----Ursprüngliche Nachricht----- Von: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] Im Auftrag von Angel L. Mateo Gesendet: Mittwoch, 8. März 2006 14:17 An: xen-users@lists.xensource.com Betreff: [*****SPAM***** HOM02EX - BA] - Re: AW: [Xen-users] Problem booting domU - Bayesian Filter detected spam El mié, 08-03-2006 a las 09:45 +0100, Stefan Mikuszeit escribió:> Hello, > > Can you check following entrys: > > Old: > disk = [''phy:vm_volumes/root.dhcp1,sda1,w'', > ''phy:vm_volumes/var.dhcp1,sda2,w'', > ''phy:vm_volumes/swap.dhcp1,sda3,w''] > > > New: > disk = [''phy:/vm_volumes/root.dhcp1,sda1,w'', > ''phy:/vm_volumes/var.dhcp1,sda2,w'', > ''phy:/vm_volumes/swap.dhcp1,sda3,w''] > > I think the system can not find the images, test it plz. >When I try this configuration I get: felis:/etc/xen# xm create dhcp1.cfg -c Using config file "dhcp1.cfg". Error: Device 2049 (vbd) could not be connected. Device /vm_volumes/root.dhcp1 is mounted in a guest domain, and so cannot be mounted now. -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica _(___V Tfo: 968367590 Fax: 968398337 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
El mié, 08-03-2006 a las 14:24 +0100, Stefan Mikuszeit escribió:> Yes this is right at the moment, xen will find now the Drives, > but can''t mount this drives. > > The Problem is you have mounted this drive in an other domain 0/U ! > > You will mount the Devices for more then one Domain ? >No, I don''t have this devices mounted. The only domain I''m running is dom0 and this is my mount: felis:~# mount /dev/sda2 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) so, as you can see, I don''t have any raid volume mounted. -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica _(___V Tfo: 968367590 Fax: 968398337 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
hello, probably you already know this but just for double-checking: make sure that your raid is NOT mounted in your dom0, otherwise the export to domU will fail. if this the case maybe creating separate logical raid-partitions for your dom0/domus is a solution. ours looks like this: each dom0 has it''s own physical boot-partition. each domU has it''s own logical logical volume on a lvm2 volumegroup. ciao, artur Am Mittwoch, den 08.03.2006, 14:17 +0100 schrieb Angel L. Mateo:> El mié, 08-03-2006 a las 09:45 +0100, Stefan Mikuszeit escribió: > > Hello, > > > > Can you check following entrys: > > > > Old: > > disk = [''phy:vm_volumes/root.dhcp1,sda1,w'', > > ''phy:vm_volumes/var.dhcp1,sda2,w'', > > ''phy:vm_volumes/swap.dhcp1,sda3,w''] > > > > > > New: > > disk = [''phy:/vm_volumes/root.dhcp1,sda1,w'', > > ''phy:/vm_volumes/var.dhcp1,sda2,w'', > > ''phy:/vm_volumes/swap.dhcp1,sda3,w''] > > > > I think the system can not find the images, test it plz. > > > When I try this configuration I get: > > felis:/etc/xen# xm create dhcp1.cfg -c > Using config file "dhcp1.cfg". > Error: Device 2049 (vbd) could not be connected. > Device /vm_volumes/root.dhcp1 is mounted in a guest domain, > and so cannot be mounted now. >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
El mié, 08-03-2006 a las 14:35 +0100, Artur Schiefer escribió:> hello, > > probably you already know this but just for double-checking: > make sure that your raid is NOT mounted in your dom0, otherwise the > export to domU will fail. if this the case maybe creating separate > logical raid-partitions for your dom0/domus is a solution. ours looks > like this: > each dom0 has it''s own physical boot-partition. > each domU has it''s own logical logical volume on a lvm2 volumegroup. >I have the same configuration. dom0 doesn''t use lvm and I don''t have any lvm volume mounted in dom0. -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica _(___V Tfo: 968367590 Fax: 968398337 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello, I have found the error :-) You tell xen that the Devices are Physical Drives, but there Files, is this right ? This Files are on an Array Drive/Partition, is this right ? Test This :-) Old: disk = [''phy:/vm_volumes/root.dhcp1,sda1,w'', ''phy:/vm_volumes/var.dhcp1,sda2,w'', ''phy:/vm_volumes/swap.dhcp1,sda3,w''] New: disk = [''file:/vm_volumes/root.dhcp1,sda1,w'', ''file:/vm_volumes/var.dhcp1,sda2,w'', ''file:/vm_volumes/swap.dhcp1,sda3,w''] Regards Stefan -----Ursprüngliche Nachricht----- Von: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] Im Auftrag von Angel L. Mateo Gesendet: Mittwoch, 8. März 2006 14:17 An: xen-users@lists.xensource.com Betreff: [*****SPAM***** HOM02EX - BA] - Re: AW: [Xen-users] Problem booting domU - Bayesian Filter detected spam El mié, 08-03-2006 a las 09:45 +0100, Stefan Mikuszeit escribió:> Hello, > > Can you check following entrys: > > Old: > disk = [''phy:vm_volumes/root.dhcp1,sda1,w'', > ''phy:vm_volumes/var.dhcp1,sda2,w'', > ''phy:vm_volumes/swap.dhcp1,sda3,w''] > > > New: > disk = [''phy:/vm_volumes/root.dhcp1,sda1,w'', > ''phy:/vm_volumes/var.dhcp1,sda2,w'', > ''phy:/vm_volumes/swap.dhcp1,sda3,w''] > > I think the system can not find the images, test it plz. >When I try this configuration I get: felis:/etc/xen# xm create dhcp1.cfg -c Using config file "dhcp1.cfg". Error: Device 2049 (vbd) could not be connected. Device /vm_volumes/root.dhcp1 is mounted in a guest domain, and so cannot be mounted now. -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica _(___V Tfo: 968367590 Fax: 968398337 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
have yo checked if hotplug/fxload is installed in your dom0 ? you also have to run a "vgchange -aly" on dom0 before the lvs are usable. Am Mittwoch, den 08.03.2006, 14:41 +0100 schrieb Angel L. Mateo:> El mié, 08-03-2006 a las 14:35 +0100, Artur Schiefer escribió: > > hello, > > > > probably you already know this but just for double-checking: > > make sure that your raid is NOT mounted in your dom0, otherwise the > > export to domU will fail. if this the case maybe creating separate > > logical raid-partitions for your dom0/domus is a solution. ours looks > > like this: > > each dom0 has it''s own physical boot-partition. > > each domU has it''s own logical logical volume on a lvm2 volumegroup. > > > I have the same configuration. dom0 doesn''t use lvm and I don''t have > any lvm volume mounted in dom0. >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
El mié, 08-03-2006 a las 15:42 +0100, Artur Schiefer escribió:> have yo checked if hotplug/fxload is installed in your dom0 ? you alsoI have got hotplug, but not fxload. I have installed too and I get the same result.> have to run a "vgchange -aly" on dom0 before the lvs are usable. >I tried this. The same behavior, the same error. -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica _(___V Tfo: 968367590 Fax: 968398337 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
hello angel, one mistake i once made, was formatting the lv''s without creating a partition first.(create logvol-> fdisk /dev/volgroup/logvol (new linux type partition)->(restart-> mkfs.ext3 on /dev/volgroup/logvol->vgchange -aly ->..) artur Am Donnerstag, den 09.03.2006, 11:04 +0100 schrieb Angel L. Mateo:> El mié, 08-03-2006 a las 15:42 +0100, Artur Schiefer escribió: > > have yo checked if hotplug/fxload is installed in your dom0 ? you also > > I have got hotplug, but not fxload. I have installed too and I get the > same result. > > > have to run a "vgchange -aly" on dom0 before the lvs are usable. > > > I tried this. The same behavior, the same error. >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
El jue, 09-03-2006 a las 12:38 +0100, Artur Schiefer escribió:> hello angel, > > one mistake i once made, was formatting the lv''s without creating a > partition first.(create logvol-> fdisk /dev/volgroup/logvol (new linux > type partition)->(restart-> mkfs.ext3 on /dev/volgroup/logvol->vgchange > -aly ->..) >Ok, I''ll try, but I don''t think this was the problem. This same volume worked with xen 2.0.6. No I''m trying to migrate it to xen 3.0.1. -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica _(___V Tfo: 968367590 Fax: 968398337 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello, El jue, 09-03-2006 a las 12:38 +0100, Artur Schiefer escribió:> hello angel, > > one mistake i once made, was formatting the lv''s without creating a > partition first.(create logvol-> fdisk /dev/volgroup/logvol (new linux > type partition)->(restart-> mkfs.ext3 on /dev/volgroup/logvol->vgchange > -aly ->..) >I have tried this, but it doesn''t work. I get a: felis:/etc/xen# xm create dhcp1.cfg -c Using config file "dhcp1.cfg". Error: Device 2049 (vbd) could not be connected. Device /dev/vm_volumes/root.dhcp1 is mounted in a guest domain, and so cannot be mounted now. I''ve checked and I don''t have any volume mounted. I have also try to completely stop lvm system with the same result. Christopher G. Stach II said:> > dom0 DOES need megaraid > dom0 DOES need LVM > dom0 DOES need block device backend > > domU DOES NOT need megaraid (or any other SCSI lowlevel drivers) > domU DOES NOT need LVM > domU DOES NOT need LVM RAID >OK, I have tried with a domU kernel that supports and that doesn''t support it with the same results.> domU DOES need block device frontend> After you rebuild your kernels and reboot, make sure that the volume > group(s) are recognized in dom0 and that you have /dev/<volume > group>/<logical volumes> available. I suppose for your volume group, > based on your configuration, it would be /dev/vm_volumes/var.dhcp1, > etc. >logical volumes are working right, as I can mount them in the dom0.> If those are not available in dom0, it obviously won''t work. Also, > your configuration should be like: > > phy:vm_volumes/root.dhcp1,sda1,w > > NOT > > phy:/vm_volumes/root.dhcp1,sda1,w > > To avoid any future confusion with SCSI major numbers, I would use > xvda1 > instead of sda1 in your config (and the domU''s fstab.) >If I try with this config: kernel = "/boot/xen-linux-2.6.12.6-atica-xenu" memory = 256 name = "dhcp1" vif = [ '''' ] disk = [''phy:vm_volumes/root.dhcp1,xvda1,w'', ''phy:vm_volumes/var.dhcp1,xvda2,w'', ''phy:vm_volumes/swap.dhcp1,xvda3,w''] root = "/dev/xvda1 ro" I get the same result: felis:/etc/xen# xm create dhcp1.cfg -c Using config file "dhcp1.cfg". Error: Device 51713 (vbd) could not be connected. Device /dev/vm_volumes/root.dhcp1 is mounted in a guest domain, and so cannot be mounted now. -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica _(___V Tfo: 968367590 Fax: 968398337 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello, Finally, it works. I have retried with the xenU kernel provided with xen and it works (I thought I have already tried, but...). -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica _(___V Tfo: 968367590 Fax: 968398337 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users