Problem booting guest with Linux 2.6.3x
Hi all!
I've compiled Linux 2.6.30.3 using the Debian way on guest Debian GNU/Linux Lenny and trying to boot the guest with this kernel, the bootstrapping is freeze on "Loading, please wait..." message.
In logs I don't get entries of the bootstrapping process with 2.6.30 (I think it is because the process in itself didn't start). Can it be due to a bug using 2.6.30.3 in guest with host KVM-88?
Also I was trying with kernel 2.6.31.2 compiled by myself and after to wait for some time, I obtain the following thing:
Booting 'Debian GNU/Linux, kernel 2.6.31.2-dgb'
root (hd0,1)
Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz-2.6.31.2-dgb root=/dev/hda2 ro quiet console=tty0 console =ttyS0,38400n8
[Linux-bzImage, setup=0x3600, size=0x203480]
initrd /boot/initrd.img-2.6.31.2-dgb
[Linux-initrd @ 0x1f983000, 0x65c455 bytes]
Loading, please wait...
WARNING bootdevice may be renamed. Try root=/dev/sda2 Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/hda2 does not exist. Dropping to a shell!
BusyBox v1.10.2 (Debian 1:1.10.2-2) built-in shell (ash) Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs)
Nevertheless with Linux 2.6.26-2-amd64 stock kernel I did not have problems. It would seem to be that at least with 2.6.31.2 the devices cannot be loaded.
Thanks advance for your reply.
Regards,
Daniel
Signature · 2 lines
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Squeeze - Linux user #188.598
Quoted 10 lines · Daniel Bareiro
root (hd0,1)
Filesystem type is ext2fs, partition type0x83
kernel /boot/vmlinuz-2.6.31.2-dgb root=/dev/hda2 ro quiet console=tty0 console =ttyS0,38400n8
[Linux-bzImage, setup=0x3600, size=0x203480]
initrd /boot/initrd.img-2.6.31.2-dgb
[Linux-initrd @0x1f983000,0x65c455bytes]Loading, please wait...
WARNING bootdevice may be renamed. Try root=/dev/sda2
I think if you boot without the "quiet" option you'll see that your guest IDE disk did in fact get installed as /dev/sda and following the advice of the error message above will allow you to boot the guest. You could boot using the uuid of the partition or label the filesystem to avoid device naming issues between your original lenny kernel and the newer kernel.
Alex
Hi, Alex.
Quoted 8 lines · Alex Williamson
Quoted 8 lines
root (hd0,1)
Filesystem type is ext2fs, partition type0x83
kernel /boot/vmlinuz-2.6.31.2-dgb root=/dev/hda2 ro quiet console=tty0 console =ttyS0,38400n8
[Linux-bzImage, setup=0x3600, size=0x203480]
initrd /boot/initrd.img-2.6.31.2-dgb
[Linux-initrd @0x1f983000,0x65c455bytes]
Quoted 6 lines
Quoted 2 lines
Loading, please wait...
WARNING bootdevice may be renamed. Try root=/dev/sda2I think if you boot without the "quiet" option you'll see that your guest IDE disk did in fact get installed as
/dev/sdaand following the advice of the error message above will allow you to boot the guest.
I'm using the option "quiet" with both stock kernel and the kernel compiled by myself.
Quoted 3 lines
You could boot using the uuid of the partition or label the filesystem to avoid device naming issues between your original lenny kernel and the newer kernel.
I was trying changing the not swap devices to the uuid form. Although in this case the swap device was not detected, the guest boots without majors problems. I think that being used the QEMU_HARDDISK names provided by udevinfo would have been solved this problem.
But according to it seems, I could verify that the disks that are passed with -hdX in KVM-88 are mapped in 2.6.31.2 guests like SATA/SCSI devices. With Linux stock 2.6.26 these are mapped like IDE disks. Can it be due to some change in the kernel code related with KVM?
Thanks for your reply.
Regards,
Daniel
Signature · 2 lines
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Squeeze - Linux user #188.598
Quoted 16 lines · Daniel Bareiro
Hi, Alex.
Quoted 10 lines · Alex Williamson
Quoted 10 lines
root (hd0,1)
Filesystem type is ext2fs, partition type0x83
kernel/boot/vmlinuz-2.6.31.2-dgbroot=/dev/hda2 ro quiet console=tty0 console =ttyS0,38400n8
[Linux-bzImage, setup=0x3600, size=0x203480]
initrd/boot/initrd.img-2.6.31.2-dgb
[Linux-initrd @0x1f983000,0x65c455bytes]Loading, please wait...
WARNING bootdevice may be renamed. Try root=/dev/sda2
Quoted 6 lines
Quoted 3 lines
I think if you boot without the "quiet" option you'll see that your guest IDE disk did in fact get installed as
/dev/sdaand following the advice of the error message above will allow you to boot the guest.I'm using the option "quiet" with both stock kernel and the kernel compiled by myself.
It's irrelevant. By using quiet you're hiding the details, that's what it is about -- what's what Alex is saying.
Quoted 9 lines
Quoted 3 lines
You could boot using the uuid of the partition or label the filesystem to avoid device naming issues between your original lenny kernel and the newer kernel.
I was trying changing the not swap devices to the uuid form. Although in this case the swap device was not detected, the guest boots without majors problems. I think that being used the
QEMU_HARDDISKnames provided by udevinfo would have been solved this problem.
Quoted 4 lines
But according to it seems, I could verify that the disks that are passed with -hdX in KVM-88 are mapped in 2.6.31.2 guests like SATA/SCSI devices. With Linux stock 2.6.26 these are mapped like IDE disks. Can it be due to some change in the kernel code related with KVM?
It has nothing to do with kvm. It's different kernel options, all kernels since very early 2.6.x are able to see ide disks as hdX or sdX, depending on the kernel options and modules loaded. There are 2 drivers for each IDE controller - IDE/ATA one, which creates hdX, and PATA one which creates sdX.
/mjt
Hi, Michael.
Quoted 16 lines · Michael Tokarev
Quoted 15 lines
Quoted 15 lines
Quoted 10 lines
root (hd0,1)
Filesystem type is ext2fs, partition type0x83
kernel/boot/vmlinuz-2.6.31.2-dgbroot=/dev/hda2 ro quiet console=tty0 console =ttyS0,38400n8
[Linux-bzImage, setup=0x3600, size=0x203480]
initrd/boot/initrd.img-2.6.31.2-dgb
[Linux-initrd @0x1f983000,0x65c455bytes]Loading, please wait...
WARNING bootdevice may be renamed. Try root=/dev/sda2I think if you boot without the "quiet" option you'll see that your guest IDE disk did in fact get installed as
/dev/sdaand following the advice of the error message above will allow you to boot the guest.
Quoted 5 lines
Quoted 2 lines
I'm using the option "quiet" with both stock kernel and the kernel compiled by myself.
It's irrelevant. By using quiet you're hiding the details, that's what it is about -- what's what Alex is saying.
Yes. Now that I read this paragraph again, I understood what was the idea of the comment of Alex. I must have been something sleepy when I replied to him :-)
Booting without the "quiet" option indeed it can be observed that the disks are detected like sdX:
[ 2.874722] scsi0 : ata_piix [ 2.879423] scsi1 : ata_piix [ 2.882361] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc000 irq 14 [ 2.887637] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc008 irq 15 [ 3.049008] ata1.00: ATA-7: QEMU HARDDISK, 0.10.50, max UDMA/100 [ 3.053725] ata1.00: 10485760 sectors, multi 16: LBA48 [ 3.057987] ata1.01: ATA-7: QEMU HARDDISK, 0.10.50, max UDMA/100 [ 3.062926] ata1.01: 20971520 sectors, multi 16: LBA48 [ 3.068436] ata2.00: ATAPI: QEMU DVD-ROM, 0.10.50, max UDMA/100 [ 3.073701] ata2.00: configured for MWDMA2 [ 3.077614] ata1.00: configured for MWDMA2 [ 3.081563] ata1.01: configured for MWDMA2 [ 3.085219] scsi 0:0:0:0: Direct-Access ATA QEMU HARDDISK 0.10 PQ: 0 ANSI: 5 [ 3.092264] scsi 0:0:1:0: Direct-Access ATA QEMU HARDDISK 0.10 PQ: 0 ANSI: 5 [ 3.099339] scsi 1:0:0:0: CD-ROM QEMU QEMU DVD-ROM 0.10 PQ: 0 ANSI: 5 [ 3.119143] Uniform Multi-Platform E-IDE driver [ 3.163028] sd 0:0:0:0: [sda] 10485760 512-byte logical blocks: (5.36 GB/5.00 GiB) [ 3.169382] sd 0:0:1:0: [sdb] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB) [ 3.175584] sd 0:0:1:0: [sdb] Write Protect is off [ 3.179590] sd 0:0:1:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 3.187178] sd 0:0:0:0: [sda] Write Protect is off [ 3.191050] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 3.198647] sda: [ 3.200566] sdb: sda1 sda2 [ 3.204719] sdb1 [ 3.207129] sd 0:0:1:0: [sdb] Attached SCSI disk [ 3.211340] sd 0:0:0:0: [sda] Attached SCSI disk [ 3.304284] sr0: scsi3-mmc drive: 4x/4x xa/form2 tray [ 3.308449] Uniform CD-ROM driver Revision: 3.20 [ 3.363890] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 3.368353] sd 0:0:1:0: Attached scsi generic sg1 type 0 [ 3.372536] sr 1:0:0:0: Attached scsi generic sg2 type 5
Quoted 15 lines
Quoted 9 lines
Quoted 3 lines
You could boot using the uuid of the partition or label the filesystem to avoid device naming issues between your original lenny kernel and the newer kernel.
I was trying changing the not swap devices to the uuid form. Although in this case the swap device was not detected, the guest boots without majors problems. I think that being used the
QEMU_HARDDISKnames provided by udevinfo would have been solved this problem.Quoted 5 lines
But according to it seems, I could verify that the disks that are passed with -hdX in KVM-88 are mapped in 2.6.31.2 guests like SATA/SCSI devices. With Linux stock 2.6.26 these are mapped like IDE disks. Can it be due to some change in the kernel code related with KVM?
Quoted 5 lines
It has nothing to do with kvm. It's different kernel options, all kernels since very early 2.6.x are able to see ide disks as hdX or sdX, depending on the kernel options and modules loaded. There are 2 drivers for each IDE controller - IDE/ATA one, which creates hdX, and PATA one which creates sdX.
According to I was investigating, I have the impression that the newest kernels delegate this disks denomination to the use of libata. It would be that in 2.6.26 Debian stock kernel not yet was productive to be in experimental phase?
Thanks for your reply.
Regards,
Daniel
Signature · 2 lines
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Squeeze - Linux user #188.598
Daniel Bareiro wrote:
[]
Quoted 12 lines
Quoted 11 lines
Quoted 5 lines
But according to it seems, I could verify that the disks that are passed with -hdX in KVM-88 are mapped in 2.6.31.2 guests like SATA/SCSI devices. With Linux stock 2.6.26 these are mapped like IDE disks. Can it be due to some change in the kernel code related with KVM?
It has nothing to do with kvm. It's different kernel options, all kernels since very early 2.6.x are able to see ide disks as hdX or sdX, depending on the kernel options and modules loaded. There are 2 drivers for each IDE controller - IDE/ATA one, which creates hdX, and PATA one which creates sdX.
Quoted 4 lines
According to I was investigating, I have the impression that the newest kernels delegate this disks denomination to the use of libata. It would be that in 2.6.26 Debian stock kernel not yet was productive to be in experimental phase?
Debian "stock" kernel config does not enable ata devices, only ide ones.
/mjt
Hi Michael.
Quoted 12 lines · Michael Tokarev
Quoted 11 lines
Quoted 11 lines
Quoted 5 lines
But according to it seems, I could verify that the disks that are passed with -hdX in KVM-88 are mapped in 2.6.31.2 guests like SATA/SCSI devices. With Linux stock 2.6.26 these are mapped like IDE disks. Can it be due to some change in the kernel code related with KVM?
It has nothing to do with kvm. It's different kernel options, all kernels since very early 2.6.x are able to see ide disks as hdX or sdX, depending on the kernel options and modules loaded. There are 2 drivers for each IDE controller - IDE/ATA one, which creates hdX, and PATA one which creates sdX.
Quoted 6 lines
Quoted 4 lines
According to I was investigating, I have the impression that the newest kernels delegate this disks denomination to the use of libata. It would be that in 2.6.26 Debian stock kernel not yet was productive to be in experimental phase?
Debian "stock" kernel config does not enable ata devices, only ide ones.
Apparently the Debian GNU/Linux stock kernels has applied a patch [1] which causes that libata only is enabled for SATA controllers.
It draws attention to me that being 2.6.31 the last branch of stable kernel from kernel.org, the Debian developers are applying this patch. I had thought that at the moment libata was sufficiently stable.
Thanks for your reply.
Regards,
Daniel
Signature · 2 lines
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Squeeze - Linux user #188.598