The domU guest os (suse10) says:
Loading reiserfs
Waiting for device /dev/sda1 to appear: ok
rootfs: major=8 minor=1 devn=2049
Mounting root /dev/sda1
mount: No such device
Kernel panic - not syncing: Attempted to kill init!
xend.log says:
[2005-12-29 20:53:13 xend] DEBUG (blkif:24) exception looking up device number
for sda1: [Errno 2] No such file or directory: ''/dev/sda1''
[2005-12-29 20:53:13 xend] DEBUG (DevController:256) DevController: writing
{''virtual-device'': ''2049'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/vbd/2/2049''} to
/local/domain/2/device/vbd/2049.
Any hints?
I got no clue where the problem is - is it a xen problem or am i missing
something? I got these errors beside the vif errors (see other thread).
Dirk
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Dirk Estreng wrote:>The domU guest os (suse10) says: > >Loading reiserfs >Waiting for device /dev/sda1 to appear: ok >rootfs: major=8 minor=1 devn=2049 >Mounting root /dev/sda1 >mount: No such device >Kernel panic - not syncing: Attempted to kill init! > > >I had the same problem when my domU kernel had scsi compiled into it. Removing scsi from the kernel fixed the problem. My guess is the scsi drivers prevented the vbd drivers from attaching to device 8,1. Dan. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 12/29/05, Dirk Estreng <dirk.estreng@gmx.de> wrote:> The domU guest os (suse10) says: > > Loading reiserfs > Waiting for device /dev/sda1 to appear: ok > rootfs: major=8 minor=1 devn=2049 > Mounting root /dev/sda1 > mount: No such device > Kernel panic - not syncing: Attempted to kill init! > > xend.log says: > > [2005-12-29 20:53:13 xend] DEBUG (blkif:24) exception looking up device number > for sda1: [Errno 2] No such file or directory: ''/dev/sda1'' > [2005-12-29 20:53:13 xend] DEBUG (DevController:256) DevController: writing > {''virtual-device'': ''2049'', ''backend-id'': ''0'', ''backend'': > ''/local/domain/0/backend/vbd/2/2049''} to > /local/domain/2/device/vbd/2049. > > > Any hints? > I got no clue where the problem is - is it a xen problem or am i missing > something? I got these errors beside the vif errors (see other thread). > > DirkDirk, If you are using the rpms from Garloff, and the kernel from the rpms, the problem should be something with your configuration file. Just show it for us, please? I have Xen 3 + Suse 10 and see no errors like that. -- Bye, Fernando Maior LPIC/1(31908) LinuxCounter(391325) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mr Fernando I''m using Xen3 + Suse 10 also .. but I''m having the same exact problem with the following config memory = 220 # kernel = "/boot/vmlinuz-xen" # ramdisk = "/boot/initrd-xen" kernel = "/var/lib/xen/images/domain2/vmlinuz-2.6.13-15-xen" ramdisk = "/var/lib/xen/images/domain2/inst-initrd" name = "domain2" dhcp = "dhcp" extra = "3" root = "/dev/sda1" disk = [ ''phy:/dev/sdb1,sda1,w'' ] On 12/29/05, Dirk Estreng <dirk.estreng@xxxxxx> wrote:> The domU guest os (suse10) says: > > Loading reiserfs > Waiting for device /dev/sda1 to appear: ok > rootfs: major=8 minor=1 devn=2049 > Mounting root /dev/sda1 > mount: No such device > Kernel panic - not syncing: Attempted to kill init! > > xend.log says: > > [2005-12-29 20:53:13 xend] DEBUG (blkif:24) exception looking updevice number> for sda1: [Errno 2] No such file or directory: ''/dev/sda1'' > [2005-12-29 20:53:13 xend] DEBUG (DevController:256) DevController:writing> {''virtual-device'': ''2049'', ''backend-id'': ''0'', ''backend'': > ''/local/domain/0/backend/vbd/2/2049''} to > /local/domain/2/device/vbd/2049. > > > Any hints? > I got no clue where the problem is - is it a xen problem or am i missing > something? I got these errors beside the vif errors (see other thread). > > DirkDirk, If you are using the rpms from Garloff, and the kernel from the rpms, the problem should be something with your configuration file. Just show it for us, please? I have Xen 3 + Suse 10 and see no errors like that. -- Bye, Fernando Maior LPIC/1(31908) LinuxCounter(391325) _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I think I figure the problem It is not configuration but update the xen rpm package to the follow rpm will work just fine ... Thanks http://www.suse.de/~garloff/linux/xen/RPMs-100/ Alex Lau wrote:> Mr Fernando > > I''m using Xen3 + Suse 10 also .. but I''m having the same exact > problem with the following config > > > memory = 220 > # kernel = "/boot/vmlinuz-xen" > # ramdisk = "/boot/initrd-xen" > kernel = "/var/lib/xen/images/domain2/vmlinuz-2.6.13-15-xen" > ramdisk = "/var/lib/xen/images/domain2/inst-initrd" > name = "domain2" > dhcp = "dhcp" > extra = "3" > root = "/dev/sda1" > disk = [ ''phy:/dev/sdb1,sda1,w'' ] > > > On 12/29/05, Dirk Estreng <dirk.estreng@xxxxxx> wrote: >> The domU guest os (suse10) says: >> >> Loading reiserfs >> Waiting for device /dev/sda1 to appear: ok >> rootfs: major=8 minor=1 devn=2049 >> Mounting root /dev/sda1 >> mount: No such device >> Kernel panic - not syncing: Attempted to kill init! >> >> xend.log says: >> >> [2005-12-29 20:53:13 xend] DEBUG (blkif:24) exception looking up > device number >> for sda1: [Errno 2] No such file or directory: ''/dev/sda1'' >> [2005-12-29 20:53:13 xend] DEBUG (DevController:256) DevController: > writing >> {''virtual-device'': ''2049'', ''backend-id'': ''0'', ''backend'': >> ''/local/domain/0/backend/vbd/2/2049''} to >> /local/domain/2/device/vbd/2049. >> >> >> Any hints? >> I got no clue where the problem is - is it a xen problem or am i missing >> something? I got these errors beside the vif errors (see other thread). >> >> Dirk > > Dirk, > > If you are using the rpms from Garloff, and the kernel from the rpms, the > problem should be something with your configuration file. Just show it > for us, please? I have Xen 3 + Suse 10 and see no errors like that. > > -- > Bye, > Fernando Maior > LPIC/1(31908) > LinuxCounter(391325) > > _______________________________________________ > Xen-users mailing list > Xen-users@xxxxxxxxxxxxxxxxxxx > http://lists.xensource.com/xen-users > > _______________________________________________ > 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