VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (964 - 966 of 16363)

Ticket Resolution Summary Owner Reporter
#6499 obsolete VBox causes packet processing delays on the host network interface when using bridged interface. OpenSolaris 2009.06 Clemens Fruhwirth
Description

The moment I turn on bridging for a guest installed on an Opensolaris host, the physical interface of the OpenSolaris host the guest is bridged to, becomes sluggish to the outside world.

192.168.1.5 is my host, which I ping from another box on the same physical LAN (192.168.1.2). You can see clearly that the ping response time jumps when bridging is active (sometimes even to almost half a second).

PING 192.168.1.5 (192.168.1.5) 56(84) bytes of data.
64 bytes from 192.168.1.5: icmp_seq=1 ttl=255 time=0.122 ms
64 bytes from 192.168.1.5: icmp_seq=2 ttl=255 time=0.152 ms
64 bytes from 192.168.1.5: icmp_seq=3 ttl=255 time=0.141 ms
64 bytes from 192.168.1.5: icmp_seq=4 ttl=255 time=0.154 ms
64 bytes from 192.168.1.5: icmp_seq=5 ttl=255 time=0.168 ms
64 bytes from 192.168.1.5: icmp_seq=6 ttl=255 time=0.150 ms
64 bytes from 192.168.1.5: icmp_seq=7 ttl=255 time=0.165 ms
64 bytes from 192.168.1.5: icmp_seq=8 ttl=255 time=0.161 ms
64 bytes from 192.168.1.5: icmp_seq=9 ttl=255 time=0.191 ms
64 bytes from 192.168.1.5: icmp_seq=10 ttl=255 time=0.139 ms
64 bytes from 192.168.1.5: icmp_seq=11 ttl=255 time=0.147 ms
64 bytes from 192.168.1.5: icmp_seq=12 ttl=255 time=0.173 ms
64 bytes from 192.168.1.5: icmp_seq=13 ttl=255 time=0.156 ms
64 bytes from 192.168.1.5: icmp_seq=14 ttl=255 time=0.192 ms
64 bytes from 192.168.1.5: icmp_seq=15 ttl=255 time=0.137 ms
64 bytes from 192.168.1.5: icmp_seq=16 ttl=255 time=0.272 ms
64 bytes from 192.168.1.5: icmp_seq=17 ttl=255 time=0.176 ms
64 bytes from 192.168.1.5: icmp_seq=18 ttl=255 time=0.188 ms
64 bytes from 192.168.1.5: icmp_seq=19 ttl=255 time=0.147 ms
64 bytes from 192.168.1.5: icmp_seq=20 ttl=255 time=0.174 ms
64 bytes from 192.168.1.5: icmp_seq=21 ttl=255 time=0.160 ms
64 bytes from 192.168.1.5: icmp_seq=22 ttl=255 time=0.156 ms
VirtualBox switched to bridged interface
64 bytes from 192.168.1.5: icmp_seq=23 ttl=255 time=0.593 ms
64 bytes from 192.168.1.5: icmp_seq=24 ttl=255 time=0.210 ms
64 bytes from 192.168.1.5: icmp_seq=25 ttl=255 time=0.208 ms
64 bytes from 192.168.1.5: icmp_seq=26 ttl=255 time=0.430 ms
64 bytes from 192.168.1.5: icmp_seq=27 ttl=255 time=404 ms
64 bytes from 192.168.1.5: icmp_seq=28 ttl=255 time=413 ms
64 bytes from 192.168.1.5: icmp_seq=29 ttl=255 time=421 ms
64 bytes from 192.168.1.5: icmp_seq=30 ttl=255 time=249 ms
64 bytes from 192.168.1.5: icmp_seq=31 ttl=255 time=427 ms
64 bytes from 192.168.1.5: icmp_seq=32 ttl=255 time=0.465 ms
64 bytes from 192.168.1.5: icmp_seq=33 ttl=255 time=0.446 ms
64 bytes from 192.168.1.5: icmp_seq=34 ttl=255 time=0.354 ms
64 bytes from 192.168.1.5: icmp_seq=35 ttl=255 time=0.254 ms
64 bytes from 192.168.1.5: icmp_seq=36 ttl=255 time=0.248 ms
64 bytes from 192.168.1.5: icmp_seq=37 ttl=255 time=0.254 ms
64 bytes from 192.168.1.5: icmp_seq=38 ttl=255 time=0.625 ms
64 bytes from 192.168.1.5: icmp_seq=39 ttl=255 time=0.248 ms
64 bytes from 192.168.1.5: icmp_seq=40 ttl=255 time=0.249 ms
64 bytes from 192.168.1.5: icmp_seq=41 ttl=255 time=0.265 ms
64 bytes from 192.168.1.5: icmp_seq=42 ttl=255 time=0.227 ms
64 bytes from 192.168.1.5: icmp_seq=43 ttl=255 time=0.235 ms
64 bytes from 192.168.1.5: icmp_seq=44 ttl=255 time=0.180 ms
64 bytes from 192.168.1.5: icmp_seq=45 ttl=255 time=0.253 ms
64 bytes from 192.168.1.5: icmp_seq=46 ttl=255 time=0.256 ms
64 bytes from 192.168.1.5: icmp_seq=47 ttl=255 time=0.231 ms
64 bytes from 192.168.1.5: icmp_seq=48 ttl=255 time=0.600 ms
64 bytes from 192.168.1.5: icmp_seq=49 ttl=255 time=0.227 ms
64 bytes from 192.168.1.5: icmp_seq=50 ttl=255 time=0.195 ms
64 bytes from 192.168.1.5: icmp_seq=51 ttl=255 time=0.791 ms
64 bytes from 192.168.1.5: icmp_seq=52 ttl=255 time=624 ms
64 bytes from 192.168.1.5: icmp_seq=53 ttl=255 time=570 ms
64 bytes from 192.168.1.5: icmp_seq=54 ttl=255 time=0.524 ms
VirtualBox switched to Not Attached interface
64 bytes from 192.168.1.5: icmp_seq=55 ttl=255 time=0.146 ms
64 bytes from 192.168.1.5: icmp_seq=56 ttl=255 time=0.416 ms
64 bytes from 192.168.1.5: icmp_seq=57 ttl=255 time=0.262 ms
64 bytes from 192.168.1.5: icmp_seq=58 ttl=255 time=0.127 ms
64 bytes from 192.168.1.5: icmp_seq=59 ttl=255 time=0.156 ms
64 bytes from 192.168.1.5: icmp_seq=60 ttl=255 time=0.138 ms
64 bytes from 192.168.1.5: icmp_seq=61 ttl=255 time=0.140 ms
64 bytes from 192.168.1.5: icmp_seq=62 ttl=255 time=0.132 ms
64 bytes from 192.168.1.5: icmp_seq=63 ttl=255 time=0.132 ms
64 bytes from 192.168.1.5: icmp_seq=64 ttl=255 time=0.119 ms
64 bytes from 192.168.1.5: icmp_seq=65 ttl=255 time=0.149 ms
64 bytes from 192.168.1.5: icmp_seq=66 ttl=255 time=1.97 ms
64 bytes from 192.168.1.5: icmp_seq=67 ttl=255 time=0.148 ms
64 bytes from 192.168.1.5: icmp_seq=68 ttl=255 time=0.119 ms
64 bytes from 192.168.1.5: icmp_seq=69 ttl=255 time=0.135 ms
64 bytes from 192.168.1.5: icmp_seq=70 ttl=255 time=0.135 ms
64 bytes from 192.168.1.5: icmp_seq=71 ttl=255 time=0.173 ms
64 bytes from 192.168.1.5: icmp_seq=72 ttl=255 time=0.133 ms
64 bytes from 192.168.1.5: icmp_seq=73 ttl=255 time=0.186 ms
64 bytes from 192.168.1.5: icmp_seq=74 ttl=255 time=0.125 ms
64 bytes from 192.168.1.5: icmp_seq=75 ttl=255 time=0.108 ms
64 bytes from 192.168.1.5: icmp_seq=76 ttl=255 time=0.124 ms

I attached a libpcap dump from another ping session. Reinstalled from 3.1.4 to 3.1.6 to see if this problem persists (yes it does). So I'm confident that you should see this problem even with fresh installations.

One side note: my opensolaris host is serving a lot of data as NFS server, so that might play into this.

OpenSolaris Version is 2009.06.

The guest doesn't play a role here. The problem becomes apparent right at the boot loader.

#6501 obsolete host keyboard function unnormal Bill William
Description

installed virtualbox under MacOSX10.6.3 32-bit, guest Linux/wINDOWs also 32-bit, everything good.

but, when I reboot snow leopard to 64-bit version, start any guest VM , the host keyboard function unnormal.

like CTRL+<arrow> , CTRL+SPACE, COMMAND+SPACE are all corrupt.

hope this fixed soon

appreciations & thx

#6503 obsolete Windows Home Server (Win 2003) - Win 7 guest does not see sound, network or system device Mike
Description

After installing VB on Windows Home Server (Windows Server 2003) and building a Windows 7 guest, the guest does not recognize the network, sound or a system device (undetermined). The guest installed and starts/runs fine except for the fact that it does not detect the drivers for network, sound or on system device (not sure which one). They show up in the control panel as yellow !.

The system is running and Intel quad core Q9550 on an Intel DP945SG motherboard with 4GB DDR3-1333 memory and an HP P400 Smart Array hardware RAID controller with 512MB cache.

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