Custom Query (16363 matches)
Results (1342 - 1344 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10063 | fixed | Bridged Linux guest does not detect link changes with host resuming from ram | ||
| Description |
When host is resuming from ram on a different network than where it was suspended while guests were running, guests still thinks they're on the old network. I have to manually restart the network to make it renew DHCP on the new network. I believe that if the host could cycle link state on resume, or do a link down on suspend and link up on resume, this problem would disappear. |
|||
| #6155 | fixed | Bridged Network problem | ||
| Description |
Hello,
host ip: 192.168.1.4 lan ip: 192.168.1.1 (one printer in lan) ping from my host: 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.382 ms 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.399 ms 64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.346 ms 64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=0.376 ms 64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=0.332 ms 64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=411 ms <--- here begin a simple download from internet in a guest. 64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=4606 ms 64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=3604 ms 64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=2604 ms 64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=4300 ms 64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=3301 ms 64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=4126 ms 64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=3117 ms 64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=3959 ms I had before a bridge (br0) that i used for the bridge interface (like old versions of virtualbox needed) but after search how to fix this problem i read in the forum that in the last versions it is not recommended so i deleted the bridge and used eth0 for the interface in the guests configuration, this does not helped though. The linux kernel in the guest vm it is 2.6.30-1-686 (debian) but i have tried too with 2.6.24 and have the same problem. If i disable the guest interface and enable other time i have a small time of working better (normal) but in less that 2 minutes i have the same problem. Host uses a intel 1000 desktop network interface (i have tried disabling tso) and in the guest i have tried three different cards with the same result. This post in the forum seems to be related too http://forums.virtualbox.org/viewtopic.php?f=6&t=25543&p=123376#p123376. I have attached the log of a session with the problem but i think this problem does not log anything. |
|||
| #5210 | obsolete | Bridged Network to WLAN not working | ||
| Description |
VB currently 3.0.8 Host: WinXP SP3 32-bit Guests: multiple 64-bit OS: Win 7 RC1, Fedora 11, Ubuntu 9.04 desktop & server Bridged network when associated with wireless host interface (Intel(R) Wireless WiFi Link 4965AGN) has intermittent network connectivity (tested by continuous pings on Win 7 and Fedora 11; on Win7 every 11-12 pings are followed by requests timed outs, overall up to 40% packet loss; on Fedora11 up to 80% packet loss. Bridged network when associated with wired host interface (Intel(R) 82566MM Gigabit Network Connection) working properly, no packet loss. NAT interface working properly for both hosts interfaces, wireless and wired. This issue started to occur before VB v3.0.4 and continues in v3.0.8. Originally, on VB 2.2.2 & 2.2.4 this behavior was not observed, no issues observed. Guests do not report or log any errors for Nics. So, I am not sure how and where additionally track this issue. I tried wireshark, but I was not able to find anything. Dmesg or linux logs--nothing either. Other VMs on the same host machine, on VMWare server, Microsoft PC 2007 or server 2005 do not have issues with bridged networking attached to the same WiFi. Host machine by itself has no issues with WiFi either. |
|||

