VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (379 - 381 of 16363)

Ticket Resolution Summary Owner Reporter
#3850 obsolete dolphin and systemsettings lose window title menu shadow after running vm with 3d acceleration Yao Ziyuan
Description

in a kde4 host environment, enable window effect "Shadow" so windows and menus will have shadows. then enable a vbox virtual machine's "3D Acceleration" property and then run the vm.

now open a dolphin or systemsettings and right-click its window title. you will find the menu without shadow.

#3851 obsolete DNS suffix not working when VirtualBox Host-Only Ethernet Adapter is active Rainer Meier
Description

I noticed that the VirtualBox Host-Only Ethernet Adapter is somehow screwing up correct DNS resolution on my hosts.

First I show you what happens before installing VirtualBox:

ipconfig /all shows the following for my Local Area Connection: ...

Connection-specific DNS Suffix . : mydomain.local

...

nslookup shows the following for a local server: C:\>nslookup server Server: server.mydomain.local Address: 10.0.1.6

Name: server.mydomain.local Addresses: xxxx:xxxx:xxxx:x::x

10.0.1.6

A ping to the host looks as follows: C:\>ping server

Pinging server.mydomain.local [xxxx:xxxx:xxxx:x::x] from xxxx:xxxx:xxxx:x:xxxx:xxxx:xxxx:xxxx with 32 bytes of data: Reply from xxxx:xxxx:xxxx:x::x: time<1ms ...

So the ping to the local server succeeds and uses the IPv6 address.

Now I install VirtualBox. As soon as the VirtualBox Host-Only Ethernet Adapter is installed the output of nslookup changes immediately:

C:\>nslookup server Server: server.mydomain.local Address: 10.0.1.6

Non-authoritative answer: Name: server Address: 67.215.65.132

The address returned corresponds to 67.215.65.132 which is the re-direct page for non-existent domains used by my DNS provider (OpenDNS).

So it looks like the DNS suffix is not attached to the request any more and therefore DNS resolving fails locally. Manually adding the DNS suffix still works as expected (same output as without the VirtualBox Host-Only Ethernet Adapter).

But when I try to ping 'server' it gets a little strange: C:\>ping server

Pinging server [10.0.1.6] with 32 bytes of data: Reply from 10.0.1.6: bytes=32 time<1ms TTL=64 ...

So somehow it does not try to ping the IP resolved by OpenDNS (67.215.65.132) but the local IP instead (which is not resolved by nslookup). The IPv6 address however is not used any more at all.

When I try to ping the full host name (server.mydomain.local) then it works perfectly. Also when I disable the VirtualBox Host-Only Ethernet Adapter within the network connections or the device manager and then either reboot or disable and re-enable my local Ethernet interface the problem disappears immediately and re-appears if I re-enable the Host-Only adapter. So there seems to be some problem with the DNS suffix when the VirtualBox Host-Only Ethernet Adapter is active.

I am running

  • Microsoft Windows Vista x64 Business
  • VirtualBox 2.2.0
#3862 obsolete Switching off seamless mode makes VB window disappear dimitris
Description

Host is Kubuntu 9.04, guest is XP SP3 with 2.2.2 guest additions.

Steps to reproduce:

  • Start guest; it was last not in seamless mode, so it starts in its own window.
  • Host-L to go to seamless mode.
  • Host-L to go back to its own window.
  • Guest window doesn't appear, and neither do any programs' windows that were displaying on the guest's desktop.
  • VB is still sort-of responding: If I "explicitly" switch to the VB window using the KDE taskbar, and then press Host-L, VB switches back to seamless mode.
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy