Custom Query (16363 matches)
Results (1618 - 1620 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16922 | duplicate | vboxnetX interfaces are not brought automatically up after upgrade from 5.1.22 to 5.1.24 | ||
| Description |
Just like title says: after upgrade to 5.1.24 host-only network does not work. I found that I need to invoke manually on the host sudo ifconfig vboxnet1 up to bring network interface up and than it works. It wasn't so on previous versions. Host: Linux Mint 18.2, 4.8.0-58-generic #63~16.04.1-Ubuntu SMP Mon Jun 26 18:08:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux VirtualBox installed from deb http://download.virtualbox.org/virtualbox/debian xenial contrib |
|||
| #10597 | obsolete | Seamless windows managed by host window manager | ||
| Description |
Disadvantages of the current seamless module are that you can't have different windows at different strata. One window can't be covered while the other isn't. A native window is either above all the host windows or none of them. Not being able to take advantages of window manager feature like snapping windows, virtual desktops or always on top is annoying as well. To say nothing about how broken seamless mode is on a tiling window manager. Seamless RDP fixes this by spawning each windows as it's own xserver window, instead of just one window with transparency. I'd like to see something like that on virtualbox, as seamless RDP is not very efficient and can be difficult for users to set up. |
|||
| #8870 | obsolete | VBox 4.0.6r71344 with Win2008 PDC Server crashes due to memory leak | ||
| Description |
System chrashs while using Windows 2008 Guest with 8GB RAM - 10GB available. 4 CPUs avail, 1 used. Using Headless Version. Virtualbox works 24 hours and then crashes. I attach the vbox.log and a dmesg output. |
|||

