Opened 18 years ago
Closed 17 years ago
#141 closed defect (fixed)
Ubuntu 7.04 Herd 4 (Feisty Fawn) Kernel Loading Failure
Reported by: | lrose | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 1.4.0 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
Ubuntu 704 Guest does not move past "Starting up ..." when booting.
System: AMD64 X2, WinXP SP2 Host, Ubuntu 7.04 Herd/Alpha 4 Guest, and Slax 6 pre10 Guest
A work-around is to add "clock=pit" to the kernel. Setting CPU affinity to one CPU does not correct this.
Problem consistent with Ticket 35, http://www.virtualbox.org/ticket/35, but is experienced with VirtualBox 1.3.6 and Ubuntu 704.
Problem is not seen with Ubuntu 610 Guest or Slax 5.1.8.1 Guest
Change History (13)
comment:1 by , 18 years ago
follow-up: 4 comment:3 by , 18 years ago
I've seen this also with the Ubuntu Feisty (7.04) beta. In my case, the live-CD from the final Feisty version booted correctly and I was able to install. So it seems to be a problem with the beta version.
comment:4 by , 18 years ago
Replying to markba:
I've seen this also with the Ubuntu Feisty (7.04) beta. In my case, the live-CD from the final Feisty version booted correctly and I was able to install. So it seems to be a problem with the beta version.
I'm still experiencing this problem with the final version, of both the Desktop Alternate CD and the Server CD.
comment:6 by , 18 years ago
Sorry for the delay, but I just tested an install with the Ubuntu Fiesty 7.04 Alternate CD, and I am getting the same results. As soon as the installation method is chosen, it locks up after loading the kernel, before the "Starting up..." is even displayed, it just has a non-blinking cursor in the top-left corner.
This is on a Debian host that had VB upgraded via apt from 1.3.8 to 1.4.0.
comment:7 by , 18 years ago
Same problem here on a AMD X2 4600+, Ubuntu Feisty Host and Ubuntu Feisty as Guest on VirtualBox 1.4.0.
After I chose "Start or install ubuntu" VirtualBox just hangs and does nothing more. There are no error messages in the log file.
comment:8 by , 18 years ago
I forgot to add that everything works fine with Ubuntu Edgy as guest OS.
Since the bug is reproduced on VB 1.4.0 wouldn't it be a good idea to tag it as 1.4.0 bug so everyone can see that it is still not fixed?
comment:9 by , 18 years ago
Version: | VirtualBox 1.3.6 → VirtualBox 1.4.0 |
---|
comment:10 by , 18 years ago
The same (?) problem with Feisty guest on Intel proccesors (Core Sole / Pentium D).
VB 1.4.0, Feisty 7.04 guest/host (2.6.20).
Details: http://forums.virtualbox.org/viewtopic.php?t=592
And I already got three installation attempts that just hangs in progress too.
comment:11 by , 18 years ago
I'm just compiled open source edition and use it instead of precompiled one from repo. Feisty guest now boots just fine! Maybe my problem is not in this ticket, I'm sorry :(
comment:12 by , 18 years ago
It could be this bug, but the fact that the bug is in the compiled package, or is in the closed source portions of the program.
I'll try to bring up another host system and recreate this bug, and then reinstall it with the open source version and see what happens. Not sure when I'll get time to do that though :|
comment:13 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Reopen if this is still relevant.
VirtualBox currently has some problems on AMD X2 systems due to inconsistencies in time counting between the CPUs. This should soon be fixed in the SVN repository.