On 2018-05-30 14:44, Andrei Borzenkov wrote:
On Wed, May 30, 2018 at 3:34 PM, Carlos E. R. <> wrote:
Hi,
I can't ping my virtual box VM machines, but I can from VM to host.
cer@Telcontar:~> ping 10.0.2.15
This is user LAN address which is not visible on host at all. Traffic from VM ends up in virtualbox process which then sends it further on its behalf. You may consider virtualbox process as NAT router; you cannot connect from outside to systems inside of NATed network. It may be possible to forward individual ports inside VM, just like in normal NAT case, I do not remember whether VB supports it (qemu does).
I'm using NAT, the same as with vmware. Connection from host to guest worked fine: ethernet0.present = "TRUE" ethernet0.connectionType = "nat" ethernet0.virtualDev = "e1000"
...
How should I best handle this issue?
You may start with reading virtualbox documentation which describes possible network types and their restrictions and then decide which one suits better in your use case.
Ok :-) -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)