#918 closed defect (fixed)
CD with kernel 2.6.23 does not boot
Reported by: | Helmut Auer | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 1.5.2 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | other |
Description (last modified by )
Hello,
The boot CD of my Gen2VDR Distri does not boot with VB 1.5.2 on a Win2K Host. With vmware and "normal" PC's this iso boots as usual. The behaviour is very strange. VB starts booting from the iso image, but then it tries to boot from root /dev/hda ( which is not available ).
The bootable part is here: http://www.htpc-forum.de/gen2vdr/2.0/files/tst.iso
The bootup log is attached, tthe strange part is:
00:00:10.090 PIIX3 ATA: LUN#0: no unit 00:00:10.090 PIIX3 ATA: LUN#1: no unit 00:00:10.093 PIIX3 ATA: LUN#2: CD/DVD, total number of sectors 3500, passthrough enabled 00:00:10.093 PIIX3 ATA: LUN#3: no unit ... 00:00:15.704 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0) 00:00:15.704 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0x00 (-1 usec ago) CmdIf1=0x00 (-1 usec ago) 00:00:15.705 PIIX3 ATA: Ctl#1: finished processing RESET 00:00:16.013 Guest Log: BIOS: Booting from Hard Disk... 00:00:22.377 Guest Log: BIOS: KBD: unsupported int 16h function 03
Attachments (4)
Change History (23)
by , 17 years ago
Attachment: | g2v2-2007-11-23-10-37-20.log added |
---|
comment:2 by , 17 years ago
Hello, Absolutely great bugtracking system - I do net get an Email when someone answers my post - I do not find my bugs when search for bugs reported by me. Looks like wasted time to report here :( Anyway it happanes with all kernel parameters i tried. All of these are working fine when I boot from harddisk instead of a DVD image. You can take test it with the iso in the link shown above. And please send me an email, when you answer ( helmut attt helmutauer dotttt de ) Bye
comment:3 by , 17 years ago
P.S. Sorry for the hard words, but it made me sad to see that such a good software product like virtualbox is using a bad bugtracking system ...
comment:4 by , 17 years ago
Description: | modified (diff) |
---|
comment:5 by , 17 years ago
I don't agree that the part of the log you quote separately is any special. The config you have should boot from DVD/CD. But the log also clearly shows that you pressed "F12" followed by "2" (selecting a hard disk boot). So in fact the log shows that YOU told the BIOS in the VM not to boot from CD as it would have normally done but from the non-existent hard disk.
So either the log you provided is just accidentally the wrong one which has nothing to do with the problem you have, or you're wasting our time.
comment:6 by , 17 years ago
Just as a side note to the bugtracking system complaint above: I just double-checked that my response was successfully sent out by our mailserver. If it doesn't reach you we can't do much about it.
comment:7 by , 17 years ago
Hello,
I do not get any mails from virtualbox about changes in this Bug ( maybe there is a typo in my emailadress, but I do not see any profile page where I can check my settings ).
Also when I look for bugs reported by me, I do not find this bug (and I'm sure that I'm logged on) :)
You're right, the log above is the wriong one - sorry for that, please download the iso noticed in my first post( 6 MB ), try to boot from it with virtualbox 1.5.2 Win and you see the problem ( hopefully ;)
Vmware and every PC I tried til now can boot with it - Virtualbox can't.
Here is a screenshot: http://www.htpc-forum.de/download/vb.gif
And now I attached the correct log :)
Thanks for your assistance.
comment:8 by , 17 years ago
P.S: After booting the CD Image you have to press enter once ( or wait for 30 seconds ).
comment:9 by , 17 years ago
P.P.S. Instead of enter You can try different kernel parameters with selecting 1-9:
LABEL 1 KERNEL /isolinux/vmlinuz.2623 APPEND initrd=instrd.gz video=uvesafb:off root=/dev/ram0 rw ramdisk_size=32000 LABEL 2 KERNEL /isolinux/vmlinuz.2623 APPEND initrd=instrd.gz ide=nodma video=uvesafb:off root=/dev/ram0 rw devfs=nomount ramdisk_size=32000 acpi=off apm=off nomce noapic LABEL 3 KERNEL /isolinux/vmlinuz.2623 APPEND initrd=instrd.gz video=uvesafb:off root=/dev/ram0 rw ramdisk_size=32000 acpi=off apm=off LABEL 4 KERNEL /isolinux/vmlinuz.2623 APPEND initrd=instrd.gz video=uvesafb:off root=/dev/ram0 rw ramdisk_size=32000 nomce noapic LABEL 5 KERNEL /isolinux/vmlinuz.2623 APPEND initrd=instrd.gz video=uvesafb:off root=/dev/ram0 rw ramdisk_size=32000 nomce noapic devfs=nomount LABEL 6 KERNEL /isolinux/vmlinuz.2623 APPEND initrd=instrd.gz video=uvesafb:off root=/dev/ram0 rw ramdisk_size=32000 acpi=off apm=off devfs=nomount LABEL 7 KERNEL /isolinux/vmlinuz.2623 APPEND initrd=instrd.gz video=uvesafb:off root=/dev/ram0 rw ide=nodma ramdisk_size=32000 nomce noapic LABEL 8 KERNEL /isolinux/vmlinuz.2623 APPEND initrd=instrd.gz video=uvesafb:off root=/dev/ram0 rw ide=nodma ramdisk_size=32000 nomce noapic devfs=nomount LABEL 9 KERNEL /isolinux/vmlinuz.2623 APPEND initrd=instrd.gz video=uvesafb:off root=/dev/ram0 rw ide=nodma ramdisk_size=32000 acpi=off apm=off devfs=nomount
comment:10 by , 17 years ago
Any news on this subject ? Could you reproduce the problem ? I have good news - with kernel 2.6.24 it works fine :) Anyway it would be interesting to know why VirtualBox fails when booting kernel 2.6.23 from CD.
comment:12 by , 17 years ago
Guest type: | other → Linux |
---|
comment:13 by , 17 years ago
Hi.
i get essentially the exact same error "unsupported int 16h function 03" trying to boot the kubuntu 8.10 alpha 1 CD in virtualbox 1.6.2. the host OS is windows XP. ill attach both a creenshot and the VBox.log file
by , 17 years ago
Attachment: | virtualBox crash.PNG added |
---|
kubuntu 8.10a1 boot crashing in virtualbox 1.6.2
comment:14 by , 17 years ago
oh, and one more thing: here's a link to what i think is the relevant bug in the ubuntu launchpad : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/246067
comment:16 by , 16 years ago
Is this bug still relevant?
Sure its relevant - I am not able to boot from a linux boot CD with kernel 2.6.23
comment:18 by , 16 years ago
Hi,
You're right 2.0.0 fixed this problem. I saw nothing in the Changelog so I didn't give it a try. Thanks for your support !
comment:19 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
VirtualBox LogFile