VirtualBox

Ticket #5423 (closed defect: fixed)

Opened 4 years ago

Last modified 22 months ago

CentOS 5.x and nolapic (Enable IO APIC)

Reported by: zigi Owned by:
Priority: major Component: other
Version: VirtualBox 3.0.10 Keywords:
Cc: Guest type: Linux
Host type: Linux

Description (last modified by frank) (diff)

Host: Kubuntu 9.10 (Linux 2.6.31-14-generic 48-Ubuntu SMP x86_64)

Guest: CentOS 5.x

In VBox 3.0.10 I must append kernel boot parameter nolapic or enable IO APIC in the settings of the guest. Without that guest hangs during boot at NET: Registered protocol 2.

Attachments

VBox.log Download (42.0 KB) - added by zigi 4 years ago.
log up to hang
VBox.log.1 Download (164.0 KB) - added by korn 3 years ago.

Change History

comment:1 Changed 4 years ago by zigi

It seems, that the problem is older than I thought. I find this on CentOS websites  http://www.centos.org/modules/newbb/viewtopic.php?viewmode=thread&topic_id=19274&forum=45, this note is for VirtualBox 2.1.4.

Some notes:
The guest setting parameter Enable IO APIC is checked by default for new guest.
May be I had IO APIC enabled when I was be installing CentOS guest and later I disabled it.
Fedora 11 and Kubuntu 9.x guests boot without any problems with IO APIC disabled.

comment:2 Changed 4 years ago by sandervl73

Without the VBox.log of that session we can't help you.

comment:3 follow-up: ↓ 4 Changed 4 years ago by Technologov

hmmm...

Host: Windows 7, 64-bit, VBox 3.0.10, Core 2 Q6600, VT-x = on.

RHEL 5.3 guest works fine here. Both 32 and 64-bit VMs. Both UP and SMP. Audio + network work too.

-Technologov, 9.nov.2009.

Changed 4 years ago by zigi

log up to hang

comment:4 in reply to: ↑ 3 Changed 4 years ago by zigi

Replying to Technologov:

hmmm...

Host: Windows 7, 64-bit, VBox 3.0.10, Core 2 Q6600, VT-x = on.

RHEL 5.3 guest works fine here. Both 32 and 64-bit VMs. Both UP and SMP. Audio + network work too.

-Technologov, 9.nov.2009.

Did you disable IO APIC in the settings of the guest?

comment:5 follow-up: ↓ 6 Changed 4 years ago by Technologov

IO APIC *must* be enabled for SMP guests. VirtualBox automatically enables it.

-Technologov

comment:6 in reply to: ↑ 5 Changed 4 years ago by zigi

Replying to Technologov:

IO APIC *must* be enabled for SMP guests. VirtualBox automatically enables it.

-Technologov

From VirtualBox manual:

"Enabling the I/O APIC is required for 64-bit guest operating systems, especially Windows Vista; it is also required if you want to use more than one virtual CPU in a virtual machine."

But why Fedora and (K)ubuntu boots without problem with IO APIC disabled. All they are SMP a 1 virtual CPU guests.

comment:7 follow-up: ↓ 8 Changed 4 years ago by Technologov

SMP means >= 2 CPUs UP means = 1 CPU

There is no such thing as "SMP a 1 virtual CPU guest".

-Technologov

comment:8 in reply to: ↑ 7 Changed 4 years ago by zigi

Replying to Technologov:

SMP means >= 2 CPUs UP means = 1 CPU

There is no such thing as "SMP a 1 virtual CPU guest".

-Technologov

OK, I thought Linux kernels with SMP..

comment:9 Changed 4 years ago by zigi

In VB 3.0.12 is a new bug related to CentOS, you must add kernel boot parameter nmi_watchdog=0
viz.  http://forums.virtualbox.org/viewtopic.php?f=7&t=24804

comment:10 Changed 4 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to fixed

That's fixed in 3.1.2.

comment:11 Changed 3 years ago by brettalton

  • Status changed from closed to reopened
  • Resolution fixed deleted

I would like to state that using VirtualBox 3.2.12 and CentOS 5.5, this bug still exists. The boot seemed to be stuck as NET: Registered protocol 2. as reported and CentOS couldn't fully boot until Settings > System > Enable IO APIC was enabled.

comment:12 Changed 3 years ago by daledouglas

I would like to add that I am having the problem intermittently with VB 3.2.12 and CentOS 5.5; MacBook Snow Leopard host. EVEN THOUGH "Enable IO APIC" is Enabled!!! After having the problem four times in a row, I finally got a successful boot, so I am not willing to reboot to report exact error message, but it hangs in a different place than above.

comment:13 Changed 3 years ago by frank

Could you retry with VBox 4.0.4? There were several PIT fixes in VBox 4.0.2 and 4.0.4.

comment:14 Changed 3 years ago by korn

I have same issue with 4.0.4 on WinXP SP3 host machine, enabling APIC and nmi_watchdog=0 didn't do the trick.

Changed 3 years ago by korn

comment:15 Changed 3 years ago by korn

with enabled APIC and disabled virtualization in CentOS guest system boots ok

comment:16 Changed 2 years ago by frank

What do you mean by "disabled virtualization in CentOS guest system"? Is that a setting in the CentOS guest or do you mean the VT-x/AMD-V VM setting?

comment:17 Changed 22 months ago by frank

  • Status changed from reopened to closed
  • Resolution set to fixed
  • Description modified (diff)

No response, closing.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use