Vagrant VMDK file broken?
therealmarv at gmail.com
Wed Jan 21 10:02:15 UTC 2015
I do not have another Vagrant VM running.
To keep sure it is not my OS config (using OS X) I've done today a vagrant
inception setup and installed a new Precise 32 vagrant machine inside a
Trusty 64 vagrant successfully!
When I tried to to setup Ubuntu Core on top of Trusty64 I cannot even reach
the boot process. Similar issue. I'm sure this error is reproducable when
doing it on a new machine (like a VM or other PC).
Here my console output:
2015-01-20 22:07 GMT+01:00 Ben Howard <ben.howard at canonical.com>:
> I saw this earlier as well, but was unable to reproduce after digging
> in. Do you have another Vagrant running?
> On 01/20/2015 09:07 AM, Marvin Reimer wrote:
> > Hi,
> > I recently had time to spin up the Vagrant box for Ubuntu Core.
> > However I've got errors and the VMDK seems corrupted.
> > Details: https://gist.github.com/therealmarv/effdae09bfa5fc0f7ca8
> > I have no problem creating other Vagrant (1.6.5) machines with my
> > Virtualbox (4.3.20r96996).
> > Does a fresh installation of Ubuntu Core work for anybody?
> > Commands for a fresh Ubuntu Core installation:
> > vagrant box remove ubuntu/ubuntu-core-devel-amd64
> > vagrant init ubuntu/ubuntu-core-devel-amd64
> > vagrant up
> > Cheers,
> > Marvin Reimer
> Ben Howard
> ben.howard at canonical.com
> GPG ID 0x5406A866
> snappy-devel mailing list
> snappy-devel at lists.ubuntu.com
> Modify settings or unsubscribe at:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the snappy-devel