On Wed, Jul 11, 2018 at 03:26:45PM +0000, Javier Uruen Val wrote:
Vmware fusion allows you to configure a network interface
as "hostonly". This uses a private network that is not
normally accessible from the physical networks on the
Mac/PC.
So this is just for guest <-> host communication and the guest cannot
communicate with the world?
We map "hostonly" in the vmx configuration to
"network"
in the domain configuration. Some comments in vmx.c
seem to point towards using this mapping and not other
such as "internal" or something else.
Which comments?
If you cannot use a network defined in libvirt's network driver with the
interface, I don't think type='network' is the right match.
Sadly, we don't seem to have documentation for type='internal'.
Added tests and configuration files from actual vmx
machines configured with "hostonly".
Signed-off-by: Javier Uruen Val <javi.uruen(a)gmail.com>
---
src/vmx/vmx.c | 19 ++-
.../vmx2xml-fusion-in-the-wild-2.vmx | 115 ++++++++++++++++++
.../vmx2xml-fusion-in-the-wild-2.xml | 34 ++++++
tests/vmx2xmltest.c | 1 +
.../xml2vmx-fusion-in-the-wild-2.vmx | 36 ++++++
.../xml2vmx-fusion-in-the-wild-2.xml | 31 +++++
tests/xml2vmxtest.c | 1 +
7 files changed, 231 insertions(+), 6 deletions(-)
create mode 100644 tests/vmx2xmldata/vmx2xml-fusion-in-the-wild-2.vmx
create mode 100644 tests/vmx2xmldata/vmx2xml-fusion-in-the-wild-2.xml
create mode 100755 tests/xml2vmxdata/xml2vmx-fusion-in-the-wild-2.vmx
create mode 100644 tests/xml2vmxdata/xml2vmx-fusion-in-the-wild-2.xml
And some changes to docs/formatdomain.html.in to tell people how to use
it would be beneficial.
Jano