Possible issue with Virtualbox 4.1.16 #316

Closed
scflode opened this Issue Jun 8, 2012 · 4 comments

Comments

Projects
None yet
4 participants
@scflode

scflode commented Jun 8, 2012

I don't know if this is an issue with veewee or vagrant.

If I try to do a vagrant basebox build with 4.1.16 in VBoxSVC.log there is a message that no storage device attached. The install process then hangs with no disk drive found.

In the .vbox file is no entry for HardDisks.

Downgrading to 4.1.14 resolved the issue.

Host OS: OSX 10.6.8
Guest OS: Debian 6

@ksteffensen

This comment has been minimized.

Show comment Hide comment
@ksteffensen

ksteffensen Aug 30, 2012

I'm having the same issue with Virtualbox 4.1.20. The vdi has been created, but it's showing as not attached to a VM.

Host OS: Ubuntu 12.04
Guest OS: Ubuntu 12.04

Update: I was able to overcome the error by upgrading from 12.04 to 12.04.1 (with corresponding changes to the box definitions, etc.)

I'm having the same issue with Virtualbox 4.1.20. The vdi has been created, but it's showing as not attached to a VM.

Host OS: Ubuntu 12.04
Guest OS: Ubuntu 12.04

Update: I was able to overcome the error by upgrading from 12.04 to 12.04.1 (with corresponding changes to the box definitions, etc.)

@jedi4ever

This comment has been minimized.

Show comment Hide comment
@jedi4ever

jedi4ever Sep 4, 2012

Owner

@staticsirupflo @ksteffensen can you run this while providing the --debug flag? This will give me more insight in the problem. thanks

Owner

jedi4ever commented Sep 4, 2012

@staticsirupflo @ksteffensen can you run this while providing the --debug flag? This will give me more insight in the problem. thanks

@ksteffensen

This comment has been minimized.

Show comment Hide comment
@ksteffensen

ksteffensen Sep 4, 2012

@jedi4ever Unfortunately, I haven't been able to reproduce this since I had the problem. If it happens again (or any other issues), I'll use the --debug flag.

Thanks,
Kirk

@jedi4ever Unfortunately, I haven't been able to reproduce this since I had the problem. If it happens again (or any other issues), I'll use the --debug flag.

Thanks,
Kirk

@mpapis

This comment has been minimized.

Show comment Hide comment
@mpapis

mpapis Oct 4, 2014

Collaborator

thanks for reporting - closing as it could not be reproduced anymore (with newer version)

Collaborator

mpapis commented Oct 4, 2014

thanks for reporting - closing as it could not be reproduced anymore (with newer version)

@mpapis mpapis closed this Oct 4, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment