VirtualBox

Ticket #370 (new defect)

Opened 1 year ago

Last modified 2 months ago

VIA CPUs and newer distros

Reported by: Mito Assigned to:
Priority: critical Component: VMM
Version: VirtualBox 1.3.8 Keywords: via c7 boot install
Cc: mike@isecgroup.com Guest type: other
Host type: other

Description

I almost posted this as a reply to the bug found here: http://www.virtualbox.org/ticket/14

But then I decided that I would create a new bug report since there are multiple things that could be causing my problem.

I have tried to install several different guest machines on a machine that I have built to host my VM's. The only successful install sofar has been using CentOS 4.4, the others all have the same problem.

To start off, I will point out that I am _not_ using an Intel or AMD processor. This system is using a Via C7 1.5GHz CPU, and that could be the cause of my problems, I'm not sure. This machine is running Debian etch, using the .deb provided on the website for 1.3.8.

When I try to install Ubuntu 7.04 Server or Alternate Desktop CD's (all CD's booting directly from ISO, and verified as complete ISO's via md5's) as soon as I choose the install option from the menu it goes to a blank screen with a solid cursor in the top-left corner of the screen, and just sits there (it doesn't matter what install option I used, they all did the same. Even the boot for recovery stop mid-boot, however it did stop at a different place). I then tried to install Ubuntu 7.04 Server into a VM using my Windows box (Pentium 4 system) and it installed properly. After installed however, when booted it goes directly to a system panic. I don't have the log files for that, but I can recreate it if you want/need/would like.

I then installed Ubuntu 7.04 Desktop via the Alternate CD on my windows box, installed it as a command-line system, and the install completed perfectly, and it boots without a problem. I then transfered the .vdi to my Debian box to host it there. The VM boots to the boot menu, and then again hangs at the "Starting up..." screen. I then told it to boot into recovery mode, and it boots up past the "Starting up..." but stops later on after a bit of screen scrolling, here are the last few lines:

NET: Registered protocol family 8 NET: Registered protocol family 20 PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.2 NET: Registered protocol family 2

I've tried discussing this in the forums in this thread: http://forums.virtualbox.org/viewtopic.php?p=682#682 and it appears that other people are having this same problem. I'm not sure if they are using a Via as their processor though, or what they are using as their host OS. Something is definitely messed up though, because both my windows box and linux box are using VB 1.3.8 and the same .vdi file, one boots and the other doesn't.

Attached is the log for the most recent boot, which is when it stops when trying to boot from the fully installed vdi file (the one that was installed using the Windows box) booting to the recovery mode.

Do note that I have also tried installing CentOS 5 and ran into it locking up during the bootup. The last line on the screen then was a "NET: protocol something something something" too. I don't remember the details for that though, as it was over a week ago and I decided to just use a CentOS4.4 install instead.

Attachments

VBox.log (27.6 kB) - added by Mito on 05/28/07 08:42:54.

Change History

05/28/07 08:42:54 changed by Mito

  • attachment VBox.log added.

05/29/07 10:42:22 changed by michael

VirtualBox is currently known to have problems with Via CPUs, so this is probably the reason for the problems you are having.

05/31/07 16:32:54 changed by Mito

I found the problem to be ACPI related.

If I pass the kernel the options:

noacpi noapic nolapic

during boot, my Ubuntu 7.04 Desktop install (command line only) boots perfectly (this is the VM that I installed using my windows box and transfered it to my Debian Etch server to host).

I will continue to try these with my other problematic distros as well. Note though that I didn't have to change anything hardware. All I had to do was pass those options to the kernel during boot and it worked properly.

(follow-up: ↓ 4 ) 06/07/07 21:58:49 changed by Fenix*NBK*

Please change topic from "newer distros" to "VIA CPU".

(in reply to: ↑ 3 ) 06/07/07 22:45:34 changed by Mito

Replying to Fenix*NBK*:

Please change topic from "newer distros" to "VIA CPU".

On the contrary, I think a better change would be:

"VIA CPU: Problems with Newer Distros"

This is because my VM install of CentOS 4.4, and a CentOS 4 offshoot works perfectly without any modifications.

(well the offshoot does tend to lockup my host server sometimes, so I've stopped using it for now...)

06/12/07 09:23:38 changed by frank

  • summary changed from Newer Distros wont boot to VIA CPUs and newer distros.

Mito, could you try again with VirtualBox 1.4.0?

06/17/07 04:27:59 changed by Mito

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.

07/08/07 23:21:01 changed by frank

Please could you try again but remove any kernel parameters, in particular any vga= and quiet= parameters (edit the GRUB command line with 'e'). Which are the last three messages of your guest kernel?

11/17/07 03:09:19 changed by Fenix*NBK*

This bug might be related to bug #774.

-Technologov

07/10/08 08:31:08 changed by frank

  • owner changed.
  • component changed from other to VMM.

© 2008 Sun Microsystems, Inc.
ContactPrivacy policy