-
Notifications
You must be signed in to change notification settings - Fork 780
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
fusion export fails on VMWareFusion Oracle Linux VM #610
Comments
i suspect it's somewhere a shell escaping issue of the command - or the exitcode is indeed not 0 by default . Could you check the exitcode when you execute the command manually? |
The error is odd. It seems like when veewee runs the command, the ovftool is looking in the wrong directory or something:
But that file is there:
|
Enabled bugging in the export_ova function, and found this: 2013-03-20T14:45:44.409-07:00 [7FFF7535F180 verbose 'Default'] Exception: Failed to open disk: /Users/blysik/Documents/Virtual Machines.localized/seo.vmwarevm/seo.vmdk. Reason: The specified virtual disk needs repair I'm going to go try to repair that with vmware-vdiskmanager. |
[blysik@blysik-imac seo.vmwarevm]$ /Applications/VMware\ Fusion.app/Contents/Library/vmware-vdiskmanager -R seo.vmdk Well that wasn't helpful. |
Okay, I believe I figured it out. In export_ova, it's not waiting long enough after ensure_vm_stopped (or that function should be waiting and it's not). It was trying to run ovftool before the VM was shut down. I added in a sleep 20 after that, and now it's processing. (I see ovftool running in the process table at least.) |
And now I have an ova file! But, I'm confused. What do I do with it? :) |
Aha, I see that in in issue #608 "First pass at building Vagrant 1.x boxes with Veewee", this is being hashed out. |
@blysik this was merged - could you try again? |
I now experienced the same yesterday and today. It fails at the first call, the second call works (veewee 0.3.7) |
we have now nice code to ensure the VM stopped, I assume this issue is fixed with it, closing this ticket, please let me know if that is not the case |
Mac OS X Mountain Lion
VMWare Fusion 5.0.3
fails with this error:
However, if I try that command myself, it works:
Any ideas?
The text was updated successfully, but these errors were encountered: