Opened 14 years ago
Closed 14 years ago
#7511 closed bug (fixed)
[kernel] doesn't boot in VirtualBox with io-apics enabled
| Reported by: | diver | Owned by: | mmlr |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | System/Kernel | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Attachments (3)
Change History (14)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 14 years ago
Replying to diver:
hrev41527 grep routing /var/log/syslog KERN: using io-apics for interrups routing
Interesting, that's the first revision with IO-APIC default on (which definitely worked fine on my end as well). So implementing source overrides in hrev41528 seems to be the cause.
I broke IO-APICs due to non-initialized NMI sources in hrev41530 and fixed that again in hrev41535, so that explains that range.
I will try to reproduce this later, but right now I don't have the time. If you could attach a serial log from such a hanging boot (you need to configure VirtualBox to write that into a file), that'd be most appreciated.
by , 14 years ago
| Attachment: | syslog_r41536.txt added |
|---|
comment:4 by , 14 years ago
That's really strange. I'm running VirtualBox 4.0.8 (r 71778) here and I tried replicating your exact setup (device configuration according to the PCI config in your log).
But when I run that I get two extra mappings in the IRQ routing table and two source overrides that aren't shown in your log. On the other hand your log seems to be missing some lines of the PCI dump as well, so maybe something got lost? In any case I was unable to replicate a hang with any combination of settings I tried. Can you tell me in detail what your configuration looks like? It is a pretty elaborate configuration BTW, nowhere near a "default" VirtualBox config I've seen so far.
Is it possible that you migrated those settings over a couple of VirtualBox versions maybe? Does it still happen if you set up a new VM with the same Haiku disk?
follow-up: 6 comment:5 by , 14 years ago
This is hrev41551 in VirtualBox 3.0.12.
It still happens after creating new VM. It hangs at the 3rd icon (card) unless I disable USB support in the VM. Without USB support it hangs at the 4th (disk) icon.
by , 14 years ago
| Attachment: | syslog_without_usb_r41551.txt added |
|---|
by , 14 years ago
| Attachment: | syslog_with_usb_r41551.txt added |
|---|
comment:6 by , 14 years ago
Replying to diver:
This is hrev41551 in VirtualBox 3.0.12.
I've now rechecked with my older install (at work) that is 3.2.12 (r 68302) and I still can't reproduce it in any way. I'm therefore inclined to say this is a VirtualBox bug that got fixed in newer versions. As the IO-APIC isn't really necessary in VirtualBox (it even tells that it'll degrade performance slightly) and since it isn't enabled by default, I would like to close this as invalid. What do you say diver?
comment:8 by , 14 years ago
| Resolution: | → invalid |
|---|---|
| Status: | assigned → closed |
Closing as a bug in earlier VirtualBox versions in that case.
comment:10 by , 14 years ago
| Resolution: | invalid |
|---|---|
| Status: | closed → reopened |
did you try with vmware vmplayer free?? ? I have always had problems with virtualbox ?