Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Virtual box created without HostOnlyInterface name. #6

Open
Infiniverse opened this issue Apr 8, 2015 · 3 comments
Open

Virtual box created without HostOnlyInterface name. #6

Infiniverse opened this issue Apr 8, 2015 · 3 comments

Comments

@Infiniverse
Copy link

A virtual box machine is being created with no HostOnlyInterface named in the config, which is preventing the virtual box provisioning process from being completed.

Host: MacOs Yosemite.
Ploy fron git today.

Using the default test config:

[vb-instance:ploy-demo]
vm-nic2 = nat
vm-natpf2 = ssh,tcp,,44003,,22
storage =
    --medium vb-disk:defaultdisk
    --type dvddrive --medium http://mfsbsd.vx.sk/files/iso/10/amd64/mfsbsd-se-10.1-RELEASE-amd64.iso --medium_sha1 03af247c1058a78a251c46ad5a13dc7b84a7ee7d

Running: ploy start ploy-demo

The virtual box configuration file generated contains:

    <Adapter slot="0" enabled="true" MACAddress="080027323DF0" cable="true" speed="0" type="Am79C973">
      <DisabledModes>
        <NAT>
          <DNS pass-domain="true" use-proxy="false" use-host-resolver="false"/>
          <Alias logging="false" proxy-only="false" use-same-ports="false"/>
        </NAT>
        <InternalNetwork name="intnet"/>
        <NATNetwork name="NatNetwork"/>
      </DisabledModes>
      <HostOnlyInterface name=""/>
    </Adapter>

Note that the should be

How do I resolve this please?

@tomster
Copy link
Contributor

tomster commented Apr 8, 2015

this is a longstanding PITA... it crops up every now and again but we're not sure how to resolve this.

what seems to help is to remove all host-only networks (i.e. via the VirtualBox GUI) and then re-run ploy start ploy-demo

if you can confirm that this helps i'll add it as a caveat to the documentation
screen shot 2015-04-08 at 09 33 12

@tomster
Copy link
Contributor

tomster commented Apr 8, 2015

or you could try referencing any existing host-only interfaces explicitly:

vm-hostonlyadapter1 = vboxnet1

in my experience, the problem does rather seem that the existing vboxnet0 somehow lacks some required attribute (its name or id).

at least that's my guess since deleting and re-creating an existing vboxnet0 interface seems to do the trick...

@Infiniverse
Copy link
Author

Yes, deleting the vboxnet interfaces first fixed the problem:

(bsdploy)unnamed-72:ploy-quickstart joe$ ploy start ploy-demo
INFO: Creating instance 'ploy-demo'
INFO: Created host only interface 'vboxnet0'.
INFO: Added dhcpserver 'vboxnet0'.
INFO: Adding default 'sata' controller.
INFO: Starting instance 'vb-instance:ploy-demo'
INFO: Instance started

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants