Opened 14 years ago
Closed 14 years ago
#5486 closed defect (fixed)
Linux guest and host, guest can't boot with IO-APIC after update to 3.0.12
Reported by: | Brian Prodoehl | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 3.0.12 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Linux |
Description (last modified by )
I've been running a CentOS 5.4 64-bit guest (kernel 2.6.18-164.6.1.el5) under a Fedora 11 64-bit host (kernel 2.6.30.9-96.fc11.x86_64), with VirtualBox 3.0.10 and ACPI, IO-APIC and AMD-V enabled. After the update to 3.0.12, the guest would no longer boot (it got a kernel panic immediately). I disabled IO-APIC in the configuration, and the guest boots again.
CPU info (same for second core):
processor : 0 vendor_id : AuthenticAMD cpu family : 17 model : 3 model name : AMD Turion(tm) X2 Dual-Core Mobile RM-70 stepping : 1 cpu MHz : 500.000 cache size : 512 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch osvw skinit bogomips : 4000.11 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate
Change History (7)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
Please add the kernel parameter nmi_watchdog=0 to the guest kernel command line.
comment:3 by , 14 years ago
Description: | modified (diff) |
---|---|
Guest type: | other → Linux |
Host type: | other → Linux |
comment:4 by , 14 years ago
Adding nmi_watchdog=0 to the guest kernel command line lets it boot. So, thank you, but the regression was a surprise and it isn't obvious to me why that's necessary.
comment:5 by , 14 years ago
We are aware of this problem and there will be an FAQ entry for this. Some more explanations will follow soon.
comment:7 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Actually adding this parameter isn't necessary anymore as of VBox 3.1.2.
Sorry, I failed to set the guest and host types, both are Linux.