Custom Query (16611 matches)
Results (25 - 27 of 16611)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #6425 | worksforme | "CPU stuck" in 3.1.6 Linux 2.6.32-3 => Fixed in SVN | ||
| Description |
After updating my debian unstable guest to 2.6.32-3, I found that the system did not boot. I saw a lockup during kernel output at roughly 4 seconds. 61 seconds later I would see a stack trace that ran off the screen.
Adding 'quiet', I could see:
This happens every 61 seconds. I found a strange post here about a workaround: http://crunchbanglinux.org/forums/topic/6463/problem-running-debian-inside-virtualbox/ Interestingly, as he said, lowering my RAM allocation from 1024MB to 512MB worked. I tried:
Attached are my VBox.log files, though I didn't see anything too helpful - I really don't know what I'm looking at. |
|||
| #3421 | fixed | "Cable Connected" setting ignored (Intel NIC only) => Fixed in SVN | ||
| Description |
"Cable Connected" setting is ignored. host (uname -a): Linux vmhost 2.6.28.6.etg #1 SMP Wed Feb 18 07:30:55 EET 2009 x86_64 Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz GenuineIntel GNU/Linux guest: linux x86_32 3 eth interfaces: NIC 1: MAC: 080027CAB5B0, Attachment: Host Interface 'vlan4000', Cable connected: off, Trace: off (file: none), Type: 82543GC, Reported speed: 0 Mbps NIC 2: MAC: 08002756E015, Attachment: Host Interface 'vlan4000', Cable connected: off, Trace: off (file: none), Type: 82543GC, Reported speed: 0 Mbps NIC 3: MAC: 080027E54698, Attachment: Host Interface 'eth0', Cable connected: on, Trace: off (file: none), Type: 82543GC, Reported speed: 0 Mbps On guest machine mii-tool reports "no link", ethtool reports "Link detected: Yes", ip reports "LOWER_UP" And yes, the link is up, and machine has access to the net. The Host Interface above is vlan due to conflict with the real machine on the lan (vm is a clone of real running host), using eth instead of vlan doesn't make difference, problem persists |
|||
| #9740 | fixed | "Cable connected" option is not persisted with "Paravirtualized Network" | ||
| Description |
Before starting the VM, set "Adapter 1" to NAT, set adapter type to "Paravirtualized Network", and untick "Cable connected". Start the VM, when logged on, while the VM is running, tick "Cable connected" in Network settings. Restart the VM - the cable is reported as unplugged in the OS, despite the new settings showing that "Cable connected" option is ticked. The only solution is to shutdown the VM, then start it (there's no need to change the settings, just a shutdown and start again). The same problem will occur if you start with "Cable connected" ticked", and when the VM starts, untick "Cable connected", and when you restart the VM, the OS reported that the cable is still plugged in. Guest: XP, host Windows 7 x64. |
|||
