Custom Query (16363 matches)
Results (1057 - 1059 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1821 | fixed | NAT malfunction under Windows host | ||
| Description |
Guest (Fedora 9) does not get access to network (NAT is configured for the guest) when host (Windows XP) is connected using WiFi. The guest OS acquires IP address from DHCP yet no packets go through to the outside network. NAT was working fine for several weeks before failing. During the time the host was connected either using Ethernet or WiFi. Eventually only Ethernet was working. The problem was solved by uninstalling VirtualBox, removing '.VirtualBox' folder, and reinstalling the application. |
|||
| #1822 | fixed | XP Guest Additions issue | ||
| Description |
I am running 5 Ubuntu boxes 4 are Hardy and 1 is gutsy all with XP SP2 Guests. When I install or updated to virtualbox 1.6.2 I had to install guest additions several times to get network shares working. For example: I had my Documents folder shared in 1.5.6 on a gutsy box and a net use script that mounted upon login. As soon as I upgraded to 1.6.2 and installed guest additions the net use script wouldn't work. I knew this problem existed from my other boxes and installed them again, no worky, again, no worky, and finally the 4TH TIME my net use script mounted it automatically. Thank you for your product. |
|||
| #1829 | fixed | Kernel Bug "Scheduling with irqs disabled" | ||
| Description |
My Host: -
My Guests:
I get this constantly in the hosts 'dmesg': - ----------------------------- [293528.625941] BUG: scheduling with irqs disabled: softirq-timer/2/0x00000000/32 [293528.625950] caller is rt_spin_lock_slowlock+0xae/0x1c0 [293528.625954] Pid: 32, comm: softirq-timer/2 Tainted: P 2.6.24-19-rt #1 [293528.625956] [293528.625957] Call Trace: [293528.625978] [<ffffffff80478b00>] schedule+0xe0/0x110 [293528.625983] [<ffffffff804793de>] rt_spin_lock_slowlock+0xae/0x1c0 [293528.626001] [<ffffffff80249294>] lock_timer_base+0x34/0x70 [293528.626008] [<ffffffff80249c77>] __mod_timer+0x37/0xe0 [293528.626021] [<ffffffff88a3c7e0>] :vboxdrv:VBoxDrvLinuxGipTimer+0x0/0xf0 [293528.626028] [<ffffffff88a3c859>] :vboxdrv:VBoxDrvLinuxGipTimer+0x79/0xf0 [293528.626035] [<ffffffff80249616>] run_timer_softirq+0x296/0x520 [293528.626050] [<ffffffff80245491>] ksoftirqd+0x121/0x2a0 [293528.626057] [<ffffffff80245370>] ksoftirqd+0x0/0x2a0 [293528.626062] [<ffffffff80245370>] ksoftirqd+0x0/0x2a0 [293528.626068] [<ffffffff8025579b>] kthread+0x4b/0x80 [293528.626074] [<ffffffff8020d308>] child_rip+0xa/0x12 [293528.626087] [<ffffffff80255750>] kthread+0x0/0x80 [293528.626091] [<ffffffff8020d2fe>] child_rip+0x0/0x12 ----------------------------------- Kernel is tainted with the NVidia Module. The host is running a real-time kernel, which may be the reason its coming up. I'm sure I remember reading somewhere that the warning comes up when the calling program is doing something that _could_ be done a different (and thus more real-time) friendly way. Unfortunately I just can't find that link at the moment. It doesn't break Virtualbox, and apart from dmesg being constantly filled with this, I havn't noticed any speed difference between a non-realtime and a realtime kernel so its really a FYI.
|
|||

