Hi there, When I am trying to ''boot'' my domU kernel (debian etch) using Xen 3.3.0, I encountered the error message of register_blkdev: cannot get major 8 for sd, I have read in the wiki somewhere that the solution is CONFIG_SCSI=n. However, even setting this environment variable, I noticed that the SCSI subsystem is still initialized as I fire up the domU kernel using xm create -c mydomain.cfg Can someone offer some advice on this? Thank you, - billy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Sep 12, 2008 at 4:07 PM, billy lau <billylau@umich.edu> wrote:> Hi there, > > When I am trying to ''boot'' my domU kernel (debian etch) using Xen 3.3.0, I > encountered the error message of > > register_blkdev: cannot get major 8 for sd, > > I have read in the wiki somewhere that the solution is CONFIG_SCSI=n. > However, even setting this environment variable, I noticed that the SCSI > subsystem is still initialized as I fire up the domU kernel using >CONFIG_SCSI is a kernel option. I wouldn''t expect that to be your problem though. What dom0 and domU kernels are you using and where did they come from? Can you give more of the output and exactly what is going wrong? Do you get to a busybox prompt for example? -- Todd Deshane http://todddeshane.net check out our book: http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > > CONFIG_SCSI is a kernel option. > > I wouldn''t expect that to be your problem though. >Okay..> > What dom0 and domU kernels are you using and where did they come from? >I am using Debian etch, from debian.org> > Can you give more of the output and exactly what is going wrong? > > Do you get to a busybox prompt for example? > >Okay, I''ll paste the output here: Started domain mydomain VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize loop: loaded (max 8 devices) Xen virtual console successfully installed as xvc0 Event-channel device installed. netfront: Initialising virtual ethernet driver. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice xen-vbd: registered block device major 8 blkfront: sda1: barriers enabled md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 NET: Registered protocol family 1 NET: Registered protocol family 17 blkfront: sda2: barriers enabled XENBUS: Device with no driver: device/console/0 BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. Sending DHCP requests ..., OK IP-Config: Got DHCP answer from ***.***.***.***, my address is ***.***.***.*** IP-Config: Complete: device=eth0, addr=***.***.***.***, mask=***.***.***.***, gw=***.***.***.***, host=***.***.***.***, domain=sth.com, nis-domain=(none), bootserver=***.***.***.***, rootserver=***.***.***.***, rootpathFreeing unused kernel memory: 176k freed usbcore: registered new driver usbfs usbcore: registered new driver hub USB Universal Host Controller Interface driver v3.0 usbcore: registered new driver hiddev usbcore: registered new driver usbhid /home/user/src/xen-3.3.0/linux-2.6.18-xen.hg/drivers/usb/input/hid-core.c: v2.6:USB HID core driver usbcore: registered new driver usbkbd /home/user/src/xen-3.3.0/linux-2.6.18-xen.hg/drivers/usb/input/usbkbd.c: :USB HID Boot Protocol keyboard driver SCSI subsystem initialized register_blkdev: cannot get major 8 for sd Kernel panic - not syncing: Attempted to kill init! Hope that information is more useful... thanks, - billy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Sep 15, 2008 at 10:30 AM, billy lau <billylau@umich.edu> wrote:> >> >> >> CONFIG_SCSI is a kernel option. >> >> I wouldn''t expect that to be your problem though. > > Okay.. >> >> What dom0 and domU kernels are you using and where did they come from? > > I am using Debian etch, from debian.org >I am pretty sure that you need to rebuild your initrd for your guest. Can you search the mailing list archives (xen.markmail.org) for things like debian and initrd, mkinitramfs and scsi, and combinations of those? If still no luck, let us know, probably someone who has built a initrd on debian recently could advise. Hope that helps. Cheers, Todd>> >> Can you give more of the output and exactly what is going wrong? >> >> Do you get to a busybox prompt for example? >> > > Okay, I''ll paste the output here: > > Started domain mydomain > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > Initializing Cryptographic API > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > rtc: IRQ 8 is not free. > Non-volatile memory driver v1.2 > RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize > loop: loaded (max 8 devices) > Xen virtual console successfully installed as xvc0 > Event-channel device installed. > netfront: Initialising virtual ethernet driver. > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx > PNP: No PS/2 controller found. Probing ports directly. > i8042.c: No controller found. > mice: PS/2 mouse device common for all mice > xen-vbd: registered block device major 8 > blkfront: sda1: barriers enabled > md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 > md: bitmap version 4.39 > NET: Registered protocol family 1 > NET: Registered protocol family 17 > blkfront: sda2: barriers enabled > XENBUS: Device with no driver: device/console/0 > BIOS EDD facility v0.16 2004-Jun-25, 0 devices found > EDD information not available. > Sending DHCP requests ..., OK > IP-Config: Got DHCP answer from ***.***.***.***, my address is > ***.***.***.*** > IP-Config: Complete: > device=eth0, addr=***.***.***.***, mask=***.***.***.***, > gw=***.***.***.***, > host=***.***.***.***, domain=sth.com, nis-domain=(none), > bootserver=***.***.***.***, rootserver=***.***.***.***, rootpath> Freeing unused kernel memory: 176k freed > usbcore: registered new driver usbfs > usbcore: registered new driver hub > USB Universal Host Controller Interface driver v3.0 > usbcore: registered new driver hiddev > usbcore: registered new driver usbhid > /home/user/src/xen-3.3.0/linux-2.6.18-xen.hg/drivers/usb/input/hid-core.c: > v2.6:USB HID core driver > usbcore: registered new driver usbkbd > /home/user/src/xen-3.3.0/linux-2.6.18-xen.hg/drivers/usb/input/usbkbd.c: > :USB HID Boot Protocol keyboard driver > SCSI subsystem initialized > register_blkdev: cannot get major 8 for sd > Kernel panic - not syncing: Attempted to kill init! > > > Hope that information is more useful... > > thanks, > - billy >-- Todd Deshane http://todddeshane.net check out our book: http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Sep 15, 2008 at 11:44 AM, Todd Deshane <deshantm@gmail.com> wrote:> On Mon, Sep 15, 2008 at 10:30 AM, billy lau <billylau@umich.edu> wrote: > > > >> > >> > >> CONFIG_SCSI is a kernel option. > >> > >> I wouldn''t expect that to be your problem though. > > > > Okay.. > >> > >> What dom0 and domU kernels are you using and where did they come from? > > > > I am using Debian etch, from debian.org > > > > > > > I am pretty sure that you need to rebuild your initrd for your guest. Can > you > search the mailing list archives (xen.markmail.org) for things like debian > and > initrd, mkinitramfs and scsi, and combinations of those?So, what you mean is I just need to create another (separate) initrd for domU? I''ve just did that, and the same problem still occurs. Btw, I am using mkinitrd.yaird to create the image. Thanks, - billy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Don''t forget to include the correct drivers (needed) for scsi on you initrd. That fixed the problem to me weeks ago. Regards Bruno _____ De: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] Em nome de billy lau Enviada em: segunda-feira, 15 de setembro de 2008 13:37 Para: deshantm@gmail.com Cc: xen-users@lists.xensource.com Assunto: Re: [Xen-users] Problems with SCSI On Mon, Sep 15, 2008 at 11:44 AM, Todd Deshane <deshantm@gmail.com> wrote: On Mon, Sep 15, 2008 at 10:30 AM, billy lau <billylau@umich.edu> wrote:> >> >> >> CONFIG_SCSI is a kernel option. >> >> I wouldn''t expect that to be your problem though. > > Okay.. >> >> What dom0 and domU kernels are you using and where did they come from? > > I am using Debian etch, from debian.org >I am pretty sure that you need to rebuild your initrd for your guest. Can you search the mailing list archives (xen.markmail.org) for things like debian and initrd, mkinitramfs and scsi, and combinations of those? So, what you mean is I just need to create another (separate) initrd for domU? I''ve just did that, and the same problem still occurs. Btw, I am using mkinitrd.yaird to create the image. Thanks, - billy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Sep 15, 2008 at 1:14 PM, Bruno Bertechini < bruno.bertechini@acensco.com> wrote:> Don''t forget to include the correct drivers (needed) for scsi on you > initrd. > > >Do you mind showing me an example of doing that? Because at this point, I am not even sure which drivers are needed for the scsi. thanks, - billy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
You have to append these modules while creating your initrd image file scsi_mod sg sd_mod And, of course, the filesystem driver (ext3, reiserfs) you''re using on you disk. Regards Bruno P.S.: You can find information on how to create initrd images on Google. _____ De: billylau1@gmail.com [mailto:billylau1@gmail.com] Em nome de billy lau Enviada em: segunda-feira, 15 de setembro de 2008 14:18 Para: Bruno Bertechini Cc: deshantm@gmail.com; xen-users@lists.xensource.com Assunto: Re: [Xen-users] Problems with SCSI On Mon, Sep 15, 2008 at 1:14 PM, Bruno Bertechini <bruno.bertechini@acensco.com> wrote: Don''t forget to include the correct drivers (needed) for scsi on you initrd. Do you mind showing me an example of doing that? Because at this point, I am not even sure which drivers are needed for the scsi. thanks, - billy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Sep 15, 2008 at 1:27 PM, Bruno Bertechini < bruno.bertechini@acensco.com> wrote:> You have to append these modules while creating your initrd image file > > > > scsi_mod > > sg > > sd_mod > > > > And, of course, the filesystem driver (ext3, reiserfs) you''re using on you > disk. >Hi, thank you for the suggestions, as I guess that solved the problem (partially), because now, the vm sort of just died off with no error message and returned control to the terminal. The printout from the console is as below: md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. RAMDISK: cramfs filesystem found at block 0 RAMDISK: Loading 4712KiB [1 disk] into ram disk... user@machine: When I do a xm list, I only have my domain0. I tried digging in the xen log file, DEBUG (__init__:1072) Destroying device model DEBUG (__init__:1072) Releasing devices DEBUG (__init__:1072) Removing vif/0 DEBUG (__init__:1072) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 DEBUG (__init__:1072) Removing vbd/2049 DEBUG (__init__:1072) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2049 DEBUG (__init__:1072) Removing vbd/2050 DEBUG (__init__:1072) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2050 DEBUG (__init__:1072) Removing console/0 DEBUG (__init__:1072) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0 DEBUG (__init__:1072) No device model [2008-09-15 15:35:14 3212] DEBUG (__init__:1072) Releasing devices I couldn''t make sense out of the logged messages. Thanks again, - billy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sorry, I might missed your config file for this domU. Can you please post it again ? (you can send me on pvt if you want to) - ot avoid flood on the mail-list. I probably have deleted your first messages so, can you pls send me these info: Dom0 Linux distro domU Linux distro domU config file how did you perform the installation on domU []''s Bruno _____ De: billylau1@gmail.com [mailto:billylau1@gmail.com] Em nome de billy lau Enviada em: segunda-feira, 15 de setembro de 2008 16:41 Para: Bruno Bertechini Cc: deshantm@gmail.com; xen-users@lists.xensource.com Assunto: Re: [Xen-users] Problems with SCSI On Mon, Sep 15, 2008 at 1:27 PM, Bruno Bertechini <bruno.bertechini@acensco.com> wrote: You have to append these modules while creating your initrd image file scsi_mod sg sd_mod And, of course, the filesystem driver (ext3, reiserfs) you''re using on you disk. Hi, thank you for the suggestions, as I guess that solved the problem (partially), because now, the vm sort of just died off with no error message and returned control to the terminal. The printout from the console is as below: md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. RAMDISK: cramfs filesystem found at block 0 RAMDISK: Loading 4712KiB [1 disk] into ram disk... user@machine: When I do a xm list, I only have my domain0. I tried digging in the xen log file, DEBUG (__init__:1072) Destroying device model DEBUG (__init__:1072) Releasing devices DEBUG (__init__:1072) Removing vif/0 DEBUG (__init__:1072) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 DEBUG (__init__:1072) Removing vbd/2049 DEBUG (__init__:1072) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2049 DEBUG (__init__:1072) Removing vbd/2050 DEBUG (__init__:1072) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2050 DEBUG (__init__:1072) Removing console/0 DEBUG (__init__:1072) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0 DEBUG (__init__:1072) No device model [2008-09-15 15:35:14 3212] DEBUG (__init__:1072) Releasing devices I couldn''t make sense out of the logged messages. Thanks again, - billy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users