Custom Query (16363 matches)
Results (1720 - 1722 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3054 | fixed | no way to limit outgoing IP traffic from a VM | ||
| Description |
It appears that VirtualBox does not provide a way to limit the outgoing access from an app inside a VM. This means that other mechanisms must be found to (say) keep an app from spamming the host OS. If so, this is an unfortunate deficiency. On OSX, the "sandbox" facility can be used to limit the IP access of an app, so I'll try to run VB under it. On Linux, however, the best answer I've found is to run iptables on the guest OS. This seems wrong, philosophically, because it is conceivable that the guest OS could be compromised by a malicious app. Please consider putting in some configuration features that will allow a VM to be held to a sharply limited set of outgoing IP addresses and ports. BTW, although my need is related to the use of Debian Linux and iptables, the problem is not specific to the guest OS. |
|||
| #3056 | fixed | Sent packets come back when using Host Interface on Linux host => Fixed in SVN | ||
| Description |
On a linux host (Debian, tested on 2.6.27 and 2.6.28 kernels but should also apply to previous ones), when using Host Interface mode for guest's interfaces, all(*) the packets sent by the guest come back to it. This has very bad side effects: Among others, this behavior prevents IPv6 stateless address autoconfiguration using Neighbor Discovery: the guest's stack receives its own Neighbor Solicitation packets and consider that the address on which it was performing DAD is duplicate. The host's interface used for the tests were physical ones in all cases (tried with an e1000e and a ASIX AX8817x), not vlan interfaces. Changing the guest interface (PCnet-Fast III or Intel PR0/1000 MT Desktop) does not change the behavior. 2 easy ways to reproduce it:
(*) the packets sent by the guest are not duplicated when sent to the host itself, it only happens when the packet are sent on the wire. ps: I opened a separate ticket because I am not sure it is the exact same issue as the one described in #2713 |
|||
| #3057 | fixed | Windows XP Sp3 MSDN cd fail to install (recompiler triple fault) | ||
| Description |
Can't install Windows xp service pack 3 (from MSDN CD). Setup started loading drivers and finally after trying to start windows (load kernel?) VirtualBox crashed. Faulting application virtualbox.exe, version 0.0.0.0, faulting module vboxrem32.dll, version 0.0.0.0, fault address 0x00005541. |
|||

