Publish VirtualBox VMs to Amazon

[mhoyman]

Hmm it was dropped from the thread. Here it is.

C:\temp>C:\"Program Files"\Oracle\VirtualBox\Vboxmanage ec2.raw --format --varia
nt Standard --dbfw_1212.vdi

[Perryg]

I'm only going to say this one more time. Use what I posted.

[mhoyman]

Can you please be more clear on what you are expecting of me.

I sourced the documentation you sent me and tried to clone the vm with the syntax that I have provided in this thread. As soon as it fires, my command prompt returns a "Windows returned an unexpected error" and then the command prompt closes all on its own, There is no error message.

Is syntax correct?

I noticed some of my words are being dropped from the thread. Have you posted an alternative syntax other then the URL you provided?

[socratis]

Is syntax correct?

NO!
Please re-read the whole thread. Then read it again. AND AGAIN. C A R E F U L L Y ! ! !

[mhoyman]

I have reread the entire thread and rather then yell at me and post in all caps or different colors can you try to be more clear and specific with what you want me to do.

The closest thing I can tell is you want me to use this URL as a guide.

http://www.virtualbox.org/manual/ch08.h ... e-clonevdi

Which I did and it crashes, which you deny.

I have provided the syntax I used. Can you provide guidance on what I have done wrong.

[Perryg]

Yours that does not work

Code: Select all

Vboxmanage ec2.raw --format --variant Standard --dbfw_1212.vdi

Mine that should work

Code: Select all

VBoxManage clonehd  <uuid|inputfile> <uuid|outputfile>  --format raw

Replace the <uuid|inputfile> with the existing name of the virtualHD
Replace the <uuid|outputfile> with the new name to use

Notice that you do not have the clonehd command in yours which is a must, that has been pointed out to you already and you have the rest of the string all out of whack.

[mhoyman]

Okay thank you. My syntax was not correct. But there is a separate issue in that your parameter list appears to be different then the documentation

Here is what I put in and it is still failing with the command prompt crashing. I have uploaded a screenshot of the error

C:\temp>C:\"Program Files"\Oracle\VirtualBox\vboxmanage clonehd dbfw_1212.vdi ec
2.raw --format raw

I can try Ubuntu if that helps to get a better error message.

[Perryg]

Really. This is a copy of the command syntax and mine is no different. I just don't add useless crap.

Code: Select all

VBoxManage clonehd         <uuid|inutfile> <uuid|outputfile>
                           [--format VDI|VMDK|VHD|RAW|<other>]
                           [--variant Standard,Fixed,Split2G,Stream,ESX]
                           [--existing]

Also you should use the absolute value for the location of the virtualHD. You can add the VirtualBox program folder to the environmental variable and make your life easier.
Remember if you have spaces in the location or file name you must wrap the line in " " quotes.

[mhoyman]

Yes that is correct. The commands I used is exactly what you requested.

And it doesn't work. All my files are local in that directory. I tried it again with full qualified paths and same result

Who do you work for? Oracle?

You are extremely unprofessional. I would appreciate if you stop responding to my thread and someone else who genuinely wants to help respond.

I can not be only one who wants to publish a VirtualBox image to Amazaon EC2

[Perryg]

I just pointed out that the command you used was not the same and I even posted the complete syntax, but so be it.
Your wish is my command.

[mpack]

Your last command syntax seems mostly correct to me, though (as Perry said) you need to wrap the VBoxManage path in quotes as it contains a space. As to the data path, only you can know if that is correct. The syntax you used implies that the source vdi file is in C:\temp, which would be an odd choice. Typically the VDI file would be inside a VM folder.

Can you run VirtualBox VMs on this host? I ask because hanging or crashing gives every appearance of VBox not having been installed properly. Either that or there are problems with at least one of the drives involved in the file copy operation, e.g. one or both is unutterably slow. Raw files will also be very large, so the filesystem must be considered (i.e. not FAT).

[mhoyman]

I moved a copy of my harddisks to temp because this was on windows and all the issues that can happen with non relatives paths and spaces and what not. I also tried to full qualified paths c:\temp\dbfw_1212.vdi and it still failed.

I dont think this works. I move over to vmware.

[mpack]

Well, I'm sure you'll be welcomed with open arms on the VMWare forums. Good luck.