Custom Query (16363 matches)
Results (1462 - 1464 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8334 | obsolete | AVM FRITZ!Fernanschluss crashes every time since installing VirtualBox 4.0.2/4.0.3 Guest Additions | ||
| Description |
AVM FRITZ!Fernanschluss is a virtual USB port that allows the use of Fritz!Box connected printer on multiple PCs over network. The AVM Support says that it is not supported in virtual environments. It would be nice if it would work again. Thanks for your help. Best regards Steffen Lorenz |
|||
| #8339 | obsolete | Mac OS X Host: Fullscreen is always on main monitor, regardless of vm screen position | ||
| Description |
Hi, starting with 4.0.0 if I have a vm window on the secondary monitor and then switch it to fullscreen, it always goes full screen on the main monitor. In 3.x it went fullscreen on the exact monitor the windows was beforehand. Now I have to make the external (projector) screen the main one, fullscreen the vm and then take the main screen back, so the host programs open new windows on the laptop screen. This makes VirtualBox almost unusable since this is a real hassle not only when setting up the projector the first time. Now, when the vm reboots (still in fullscreen) and the vm additions kick in to change resolution, they take the resolution from the main screen, which is different from the projector.. Sorry: absolutely unusable. Furthermore if the fullscreen vm has focus, menubar and dock on main screen get hidden, which, too, has not been the case with 3.x. Please change this back. ;-) Please do not hesitate to ask for further information. VB is a great product, I'd really like to help. :) |
|||
| #8346 | obsolete | Snapshot of new machine under 4.0.2 dissappeared | ||
| Description |
I upgraded from the latest version 3 release to 4.0.2 on Mac OS X Snow Leopard, and my existing VM worked fine. I created a new VM (Ubuntu x64 server 10.04) and loaded the OS and installed updates. I then created a snapshot. When I went to start the VM again, there was no sign of any snapshot; all that appeared in the list was "Current State." The VM was the same as the state of the VM when I made the snapshot. I think I checked the Snapshots directory and did not find any. Since this was a fresh install with only updates applied, I just reinstalled Ubuntu using the same VDI file, as I did not want to take any chances with snapshot problems. The VM has been working as expected since then (I sometimes get a kernel panic because of an IO-APIC timer issue, but don't expect that's related). |
|||

