Custom Query (16363 matches)
Results (1306 - 1308 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1333 | fixed | Share file invisible -> Fixed in 1.6 | ||
| Description |
I installed a Win XP Pro guest on Mac OS X host. I shared a folder via VirtualBox after installing the additional guests addons. When I connect on my guest, I can't see any share folder. When I look the network places, there's nothing. I tried also to create a link with this command line : net x: \vboxsrv\shared but the vboxsrv was not found... So I don't know how to find my share folder... |
|||
| #1334 | fixed | Network connection blinking when not connected | ||
| Description |
Host: Windows Vista Home Premium When I disconnect the guest's network cable, the network connection is "blinking" (i.e. connected - not connected - connected...). It doesn't matter if I start disconnected or if I disconnect the cable while the vm is running. The session log is attached (cable disconnected all the time). |
|||
| #1335 | duplicate | Very low speed on outgoing traffic with NAT | ||
| Description |
Description The NAT mode guest interface is truely a great feature, but there are some optimization/scheduling problems on outbound traffic to remote hosts. I have tried this on several hosts (linux and windows) each with different hardware configurations, the result is the same - a throughput less than 500 kbyte/s (on windows hosts less than less than 100 kbyte/s). There is no problem when sending data from the guest to it's host. I have spent days debugging and profiling, but the problem is not a part of my expertees so at last I had to give up. I have communicated quite a lot with the vbox developers via IRC passing on debug and profiling information - they say the problem is due to low prioritized scheduling on the host side. Reproduce
Odd observations
My opinion I think there is a great potential in NAT with port forwarding, because it enables you (in conjunction with VBoxHeadless.exe) to distrubute a virtual machine and run it as a normal service (ie. Windows Service) the only thing missing is outgoing traffic speed :-) Best regards Jakob Simon-Gaarde btw: vmware's NAT has the same defect. So this could be a place where VirtualBox can offer a little more :-) |
|||

