Custom Query (16363 matches)
Results (1864 - 1866 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4524 | duplicate | UDP Port forwarding broken in version 3.0.2 | ||
| Description |
I had VirtualBox 2.2.4r47978 running on Windows XP 32bit with xubuntu 9.04 as the guest (with additions). With a few port forwardings: VirtualBox Command Line Management Interface Version 2.2.4 (C) 2005-2009 Sun Microsystems, Inc. All rights reserved. Key: GUI/SaveMountedAtRuntime, Value: yes Key: GUI/LastWindowPostion, Value: 132,73,720,444 Key: GUI/Fullscreen, Value: off Key: GUI/Seamless, Value: off Key: GUI/AutoresizeGuest, Value: on Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/ASSS/Protocol, Value: TCP Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/ASSS/GuestPort, Value: 5000 Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/ASSS/HostPort, Value: 5000 Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/ASSS2/Protocol, Value: TCP Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/ASSS2/GuestPort, Value: 5001 Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/ASSS2/HostPort, Value: 5001 Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/ASSS_UDP/Protocol, Value: UDP Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/ASSS_UDP/GuestPort, Value: 5000 Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/ASSS_UDP/HostPort, Value: 5000 Key: GUI/InfoDlgState, Value: 400,450,normal Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/ASSS2_UDP/Protocol, Value: UDP Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/ASSS2_UDP/GuestPort, Value: 5001 Key: VBoxInternal/Devices/pcnet/0/LUN#0/Config/ASSS2_UDP/HostPort, Value: 5001 Key: GUI/LastCloseAction, Value: shutdown Key: GUI/MiniToolBarAutoHide, Value: on In other words TCP & UDP forwarding on port 5000 and 5001 This worked fine for weeks, until I upgraded today to VirtualBox 3.0.2. I noticed that while the TCP forwarding worked, the UDP forwarding did not. (nothing has changed on the guest OS). I then downgraded back again to VirtualBox 2.2.4 and the port forwarding is working properly again. |
|||
| #15106 | fixed | on MacOS X, Windows seven VM crashes when logging in in dual screen seamless mode | ||
| Description |
the VM occasionally crashes when restoring and systematically when booting up and then logging in. the VM is configured to use the two screens of the computer and is in seamless mode. if the VM is not in seamless mode when restoring / logging in then it never crashes. attached is the log of a crash after booting up and then logging in (at 00:03:04) |
|||
| #7032 | obsolete | possible regression in 3.2.4: blank (white) window when restoring from saved state | ||
| Description |
This has been discussed on http://forums.virtualbox.org/viewtopic.php?f=6&t=31941 Please see that thread for detailed information including log files. After upgrading from 3.2.2 to 3.2.4 saved machine states can not be successfully restored. They come up with a blank (white) window in the top left corner of the screen with the titlebar off the screen. This is a Windows 7 64bit host with Gentoo Linux guest, but other combinations have shown the same symptoms (see the forum thread). When you resize the machine window Windows 7 automatically recenters such that you now see the titlebar, however, the window is still completely blank and does also not show the menu bar. Forcing a machine power off (using the close button in the top right window corner) and restarting the powered off machine works as expected, no problems there. This is 100% reproducible, in 3.2.4 restoring saved states doesn't work, powering off and powering on again works just fine. Reverting to 3.2.2 solves the problem for me. With 3.2.2 saved states can be restored just fine. This might help as well: after reverting back to 3.2.2, when I first restarted the (forcefully) powered off machine I got the same symptoms(!). The system did appear to be starting fine though (disk activity etc.), although nothing was shown in the machine window. When the boot up sequence reached the X Windows start, the machine window was repainted and now the menu bar and everything appeared. From then on, everything has been working fine again, including several save/restore and power off/power on cycles. Not sure how to make sense of this. In 3.2.2 it only occurred for the machine that was forcefully powered off using 3.2.4, while in 3.2.4 it only occurred for save/restore cycles, not for forced power off/power on cycles. Weird, isn't it? |
|||

