Opened 15 years ago
Closed 8 years ago
#4048 closed defect (obsolete)
Long delay booting between bios and grub (canima linux, software virtualization only)
Reported by: | higuita | Owned by: | |
---|---|---|---|
Component: | VMM/RAW | Version: | VirtualBox 3.0.6 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Windows |
Description (last modified by )
After installing virtualbox 2.2.2 on a windows vista host, i downloaded the canaima ISO - http://canaima.softwarelibre.gob.ve:8080/canaima_cms/descargas/canaima-i386/releases (i used the 2.0 version, since then there is a 2.0.1, that i didnt test yet)
i created a new debian 32bit VM and loaded the install ISO the system boot from the ISO and the install went to the end without errors and ask for reboot...
after the virtualbox starts the VM and show the BIOS screen, it takes about 15 min showing to show the grub menu, during this time i can only see a black screen and the host CPU on 100%
after the long delay, the system seens to work fine (after installing the vboxguestadditions i have lost the keyboard in X, but i will open a new bug)
Attachments (6)
Change History (20)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
i found the 2.0 ISO:
http://190.9.128.108/imagenes/canaima-2.0-DVD-i386.iso
i will attach the log next
comment:3 by , 15 years ago
i forgot... yes, the problem persist on every boot... i have to wait a long period for the machine to boot (7mim from the log on this machine)... on a faster machine it takes less time, but still a long period (about 5 minutes)
comment:4 by , 15 years ago
just installed the 2.0.1 version and have the same problem
i also tested in a linux host (debian) and it also takes a long time to boot (but the machine is faster, so the delay is about 2 minutes). Here the relevant part of the log for the linux machine and the canaima 2.0.1:
00:28:42.783 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0) 00:28:42.785 Guest Log: BIOS: CDROM boot failure code : 0003 00:28:42.785 Guest Log: BIOS: Boot from CD-ROM failed 00:28:42.787 Guest Log: BIOS: Booting from Hard Disk... 00:28:42.790 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0x20 (-1 usec ago) CmdIf1=0x00 (-1 usec ago) 00:28:42.790 PIIX3 ATA: Ctl#0: finished processing RESET 00:28:42.793 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 00:28:43.203 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=00007f3929ed8000 w=640 h=480 bpp=32 cbLine=0xA00 00:28:53.611 VMMDev::SetVideoModeHint: got a video mode hint (660x498x0) at 0 00:28:56.275 VMMDev::SetVideoModeHint: got a video mode hint (723x549x0) at 0 00:29:21.331 VMMDev::SetVideoModeHint: got a video mode hint (744x571x0) at 0 00:30:58.543 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 00:30:58.549 Guest Log: BIOS: KBD: unsupported int 16h function 03 00:30:58.554 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001! 00:30:58.554 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001! 00:30:58.554 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001! 00:30:58.554 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001! 00:30:58.554 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001! 00:30:58.554 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001! 00:30:58.555 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001! 00:30:58.555 Guest Log: BIOS: int13_harddisk: function 41, ELDL out of range 89 00:30:58.555 Guest Log: BIOS: int13_harddisk: function 02, ELDL out of range 89 00:30:58.555 Guest Log: BIOS: int13_harddisk: function 41, ELDL out of range 8A
comment:5 by , 15 years ago
Please reopen if this still applies to a recent release of VirtualBox (3.0.4 or 3.0.6 Beta 1).
comment:6 by , 15 years ago
I just tested with 3.06 r52128 and canaima stills takes a long time to just reach the grub menu, so reopenning
comment:7 by , 15 years ago
Version: | VirtualBox 2.2.2 → VirtualBox 3.0.6 |
---|
by , 15 years ago
3.06 vbox startup log, started with "VirtualBox --debug --debug-statistics --debug-command-line"
comment:8 by , 15 years ago
Please could you update the guest additions from 2.1.4 to 3.0.6, does that make any difference?
comment:9 by , 15 years ago
i will do that, but as it doesnt even reach the grub (stage 2 at least) during this delay... i dont really believe it will make a difference. i suspect something related with the bios and the MBR or grub stage 1
tomorrow i will check... i will also try to run with strace and check what its trying to do during the delay... i will also try gdb and see what reports (probably need to rebuild with debug enable)
comment:11 by , 15 years ago
its a plain linux distro, with few things of ours, there is no big problem... but i also prefer to not post here the url (any private way, like email? my email is higuita@…)
its 6GB uncompressed, i assume compressed will be at least 2GB.
i will compress it and send you the url
comment:12 by , 15 years ago
Component: | other → VMM/RAW |
---|---|
Summary: | Long delay booting between bios and grub (canima linux) → Long delay booting between bios and grub (canima linux, software virtualization only) |
I've got your .vdi image and started it locally on a 64-bit Linux host. Using an Intel Core 2 Duo with 2.66GHz here. Assigned 1GB guest memory (as you did). VT-x enabled.
It takes about 4 seconds from starting the VM until the GRUB boot menu appears. Waiting 90 more seconds and the login screen is visible. Looks to me quite normal (well, Ubuntu Jaunty boots faster but I assume that your Linux distribution starts some more services during boot). Also, don't enable the I/O-APIC as you use only one guest CPU.
The picture is completely different when disabling VT-x. I now see the big delay as well. So if VT-x/AMD-V is available, use it. We will have a look at the software emulation mode but this will take time.
comment:13 by , 15 years ago
priority: | critical → major |
---|
Decreasing priority because it works as expected with VT-x/AMD-V.
comment:14 by , 8 years ago
Description: | modified (diff) |
---|---|
Resolution: | → obsolete |
Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
So the long delay is still persistent? Please attach a VBox.log of a VM session with such a long delay before the GRUB menu is shown.