Debian Lenny Won't Boot in VBox 4.0.0

[Commifreak]

I've also tried the graphical installer - but this nice window doesn't appear for me.

[fixedwheel]

that means it hangs before you can see it?

this was "advanced graphic install" some steps already done ...

[fixedwheel]

installation has rebooted and is ready (no "Desktop" installed)

[Commifreak]

I can select the Install-methode (Install, Graphical Install etc..)

I doesnt tried the advanced graphical install, yet.

It hangs, after a selection, at:

Booting the kernel...

I'll try Debian with advanced graphical install later.

[magicbus]

Tried everything suggested earlier...still nothing. Disabled VT-x and nested paging. I still can't boot the CD at all. Plain install freezes on kernel boot; on graphical install the screen just goes dark.

My disc is older; I'm installing 5.0.6 i386 on a 64-bit machine. I was going to try out 5.0.7 64-bit instead of upgrading (I didn't figure that it would make a difference, though) but of course now I don't really need to.

[fixedwheel]

don't care: 5.0.6 or 5.0.7 should make no difference IMHO.

Tried everything suggested earlier...still nothing.

what else you could try is: move to the wanted install option like Graphical install and hit the tab key to edit the kernel parms (see attached picture)
remove the quiet parm to see what happens and add your own after the "--" (don't remove).
Lists and explanations can be found by google "kernel parameter" or take this short reference: http://www.kernel.org/doc/Documentation ... meters.txt (look for label: X86, X86-32 or X86-64, BUGS=X86-32 ...)
i suggest you try one of: nopat noapic nolapic nosmp noexec=off nohz=off

-edit- reference reading
i386 => http://www.debian.org/releases/lenny/i386/ch05s03.html
amd64 => http://www.debian.org/releases/lenny/amd64/ch05s03.html

[magicbus]

I tried all of the parameters you suggested and each time I got this result: the boot hangs at parport_pc 00:04 : reported by Plug and Play ACPI.

[fixedwheel]

I tried all of the parameters you suggested and each time I got this result: the boot hangs at parport_pc 00:04 : reported by Plug and Play ACPI.

lp=0 to rule out the parallel port

i guess next would be accessing CD drive, see attached screenshot of dmesg output
could be some timeout issue, try ide-core.nodma=1.0 or ide_core.cdrom=1.0 (=1.0 equals hdc from my screenshot, my VBox storage setting is IDE Secondary Master for CD drive)
reference => http://www.kernel.org/doc/Documentation/ide/ide.txt and http://www.kernel.org/doc/Documentation ... meters.txt

[Commifreak]

I tried all of the parameters you suggested and each time I got this result: the boot hangs at parport_pc 00:04 : reported by Plug and Play ACPI.

EXACTLY the same with my 5.0.7 netinst 32bit.

I've tried lp=0 and the other params - no change.

It hangs on exacly this point...

Eene no change with "Install", "Graphical Install" and the extended version of them..

[fixedwheel]

I've tried lp=0 (...)

so i think it gets some timeout thing detecting CD drive, did you try ide-core.nodma=1.0 or ide_core.cdrom=1.0 ...and what are the VBox settings for CD drive?

[fixedwheel]

hmm, something in your logs:

Code: Select all

00:00:04.765 PIT: mode=2 count=0x12a5 (4773) - 249.98 Hz (ch=0)
00:00:05.582 PIT: mode=4 count=0x121b (4635) - 257.42 Hz (ch=0)
00:00:05.582 PIT: mode=4 count=0x1204 (4612) - 258.71 Hz (ch=0)
00:00:05.586 PIT: mode=4 count=0x1285 (4741) - 251.67 Hz (ch=0)
00:00:05.590 PIT: mode=4 count=0x1291 (4753) - 251.03 Hz (ch=0)
00:00:05.594 PIT: mode=4 count=0x117f (4479) - 266.39 Hz (ch=0)
00:00:05.597 PIT: mode=4 count=0x11f8 (4600) - 259.38 Hz (ch=0)
00:00:05.601 PIT: mode=4 count=0x127f (4735) - 251.99 Hz (ch=0)
00:00:05.605 PIT: mode=4 count=0x120c (4620) - 258.26 Hz (ch=0)
00:00:05.609 PIT: mode=4 count=0x26 (38) - 31399.52 Hz (ch=0)
00:00:05.609 PIT: mode=4 count=0x25 (37) - 32248.16 Hz (ch=0)
00:00:05.609 PIT: mode=4 count=0x25 (37) - 32248.16 Hz (ch=0)
00:00:05.610 PIT: mode=4 count=0x1199 (4505) - 264.85 Hz (ch=0)
00:00:05.614 PIT: mode=4 count=0x11de (4574) - 260.86 Hz (ch=0)
00:00:05.618 PIT: mode=4 count=0x1281 (4737) - 251.88 Hz (ch=0)
00:00:05.622 PIT: mode=4 count=0x11f5 (4597) - 259.55 Hz (ch=0)
00:00:05.625 PIT: mode=4 count=0x1261 (4705) - 253.59 Hz (ch=0)
00:00:05.629 PIT: mode=4 count=0x1291 (4753) - 251.03 Hz (ch=0)
00:00:05.633 PIT: mode=4 count=0x1278 (4728) - 252.36 Hz (ch=0)
00:00:05.637 PIT: mode=4 count=0x1287 (4743) - 251.56 Hz (ch=0)
00:00:05.641 PIT: mode=4 count=0x126f (4719) - 252.84 Hz (ch=0)
00:00:05.647 PIT: mode=4 count=0xe (14) - 85227.28 Hz (ch=0)
00:00:05.647 PIT: mode=4 count=0xe3d (3645) - 327.34 Hz (ch=0)
00:00:05.649 PIT: mode=4 count=0x122a (4650) - 256.59 Hz (ch=0)
00:00:05.659 PIT: mode=4 count=0x2a0 (672) - 1775.56 Hz (ch=0)
00:00:05.660 PIT: mode=4 count=0xc11 (3089) - 386.26 Hz (ch=0)
00:00:05.661 PIT: mode=4 count=0x11ec (4588) - 260.06 Hz (ch=0)
00:00:05.665 PIT: mode=4 count=0x128e (4750) - 251.19 Hz (ch=0)

Code: Select all

00:00:16.614 PIT: mode=2 count=0x12a5 (4773) - 249.98 Hz (ch=0)
00:00:17.422 PIT: mode=4 count=0x10 (16) - 74573.87 Hz (ch=0)
00:00:17.422 PIT: mode=4 count=0xe (14) - 85227.28 Hz (ch=0)
00:00:17.674 PIT: mode=4 count=0xe (14) - 85227.28 Hz (ch=0)
00:00:18.002 PIT: mode=4 count=0xe (14) - 85227.28 Hz (ch=0)
00:04:43.100 Changing the VM state from 'RUNNING' to 'SUSPENDING'.

try with clock parms... another clocksource? clocksource=acpi_pm

i remember a fedora guest freeze while doing I/O => http://forums.virtualbox.org/viewtopic. ... 6&start=30
64 bit: noapictimer nohz=off highres=off
32bit: nolapic_timer nohz=off highres=off

[Narp]

try with clock parms... another clocksource? clocksource=acpi_pm

i remember a fedora guest freeze while doing I/O => http://forums.virtualbox.org/viewtopic. ... 6&start=30
64 bit: noapictimer nohz=off highres=off
32bit: nolapic_timer nohz=off highres=off

Thank you! This worked for me. I haven't narrowed it down to which options are required, but I added all of them for my Debian Lenny 5.08 Netinst CD (i386) and it booted and installed successfully.

[frank]

This is actually bug #8033 and will be fixed in the next maintenance release.