We have a CentOS machine running on DigitalOcean. And now we would like to create a vmdk image of that machine which should be supported on VirtualBox.
Please see the below commands which we used to create vmdk image
1) created a raw image from the entire system using dd command
dd if=/dev/vda of=disk.img , where vda is the volume.
2) then converted the raw image using vboxmanage command
VBoxManage convertfromraw disk.img disk.vmdk --format VMDK
Then we downloaded the vmdk image, and tried to create a new VM on VirtualBox. But we were getting an error message as follows :
FATAL: no bootable medium found! System Halted.
It would be great if anyone help us to create a bootable vmdk image from running centos machine.
Related
I have a running vm in vmware environment and need to migrate that vm to openstack environment(qcow2).
I exported my virtual machine and it created 3 vmdks files, now how can I install this 3 vmdk files in to openstack environment. I have converted these 3 vmdks files to qcow2 format but how can I handle 3 qcow2 image to install my vm.
Could someone guide please?
You could try create server with --block-device-mapping, check from "Block Device Mapping in Nova".
Like this:
openstack server create --flavor FLAVOR.NAME --image qcow2.first.vmdk \
--block-device-mapping vdb=qcow2.second_1.vmdk:image \
--block-device-mapping vdc=qcow2.third_2.vmdk:image \
--nic port-id=the_port_with_same_ip_as_in_vmware \
qcow2_image_server_name
In my situation, we use ceph to provide the shared storage, so I use volume instead of the image in above command line, it works for me. I think it's similar with local disk storage like your scenario.
Another thing, I had test that ceph shared storage could transform to local disk storage with replace the disk's file by qemu-img convert, vice versa.
How can I export a gce Image to use it in a local Virtualbox?
I get the error:
error: No such device
gce-image-export.vmdk
gce-image-export.qcow2
gce-image-export.vdi
I use the command:
qemu-img convert -O vdi gce-image-export.qcow2 gce-image-export.vdi
I get by *.vmdk, *.qcow2, *.vdi all the the same error.
Did you have input for me?
Thanks
kivitendo
You can export the image using the gcloud command. You can see in the following documentation all the use of the command and the flags.
gcloud compute images export \
--destination-uri <destination-uri> \
--image <image-name> \
--export-format <format>
The --export-format flag exports the image to a format supported by QEMU using qemu-img. Valid formats include 'vmdk', 'vhdx', 'vpc', 'vdi', and 'qcow2'.
You can send it to a Bucket and later you can download it.
thanks, i only can export from Google Cloud Platform (gce) to
*.VMDK
*.VHDX
*.VPC
*.qcow2
formats.
I must Virtualbox 6.1 change Virtualbox Machine to EFI Support.
If i use than rEFInd 0.12 as boothelper i can start my vce *.vmdk machine.
I get many errormessage and i don't can log in, in my vce *.vmdk machine. to repair the errormessage and install grub-efi to my vce *.vmdk machine.
My installed NextCloud server is starting.
How can i log in, to my machine?
root doesn't work.
I don't find any tutorial.
kivitendo
I have a number of windows VMs running on my hyper-v instance I want to turn into vagrant boxes. Its there a tool out there that can do this for me or a clear guide on what needs to be enabled on the machine and how to create the config files that go into the box?
The documentation for windows VMs coming from hyper-v seem to be lacking with most guides focusing on virtual box.
TIA
There is no direct approach to achieve what you want.
NOTE: remove the hyper-v integration tools (agent, PV drivers etc...).
First, you need to convert VHD to VMDK or VDI format using VBoxManage, for example from VHD to VDI -> VBoxManage clonehd source.vhd target.vdi --format VDI
Once done, create a VM in VirtualBox with a proper spec (# of vCPUs, Memory, etc.), use the existing converted .vdi file as its virtual disk.
Try to boot the VM and see if everything works as expected. Install the VirtualBox Guest Additions (recommended).
Configure the VM as per Vagrant Documentation (e.g. NAT port forwarding rules, disabling UAC etc., refer to Creating a Base Box)
Package it as Vagrant box vagrant package --base vbox_vm_name --output /file/to/name.box
I am trying to set up a Windows 7 instance on Openstack. This instance requires at least 50 GB of free disk space to run an application. When I create my windows 7 image and upload it everything works fine, except for one problem - The disk space is already 80% used when I start.
For example a windows 7 instance with a 100GB hard drive has only 18.3GB of free space.
What I tried:
I have been trying to create a windows 7 image with a 100GB hard drive. I created a QCOW2 file with a windows 7 ISO and the Virt-IO drivers ISO using the below commands:
create the empty qcow2 file:
qemu-img create -f qcow2 win_64bit_SP1_100GB.qcow2 100G
Combine the two ISOs:
sudo virt-install --connect qemu:///system --name
PS4Agent_win7_64bit_SP1_100GB --ram 2048 --vcpus 2 --network
network=default,model=virtio --disk
path=win_64bit_SP1_100GB.qcow2,format=qcow2,device=disk,bus=virtio
--cdrom /home/khennessy/win7_win8_iso_creation/SW_DVD5_Win_Pro_7w_SP1_64BIT_English_-2_MLF_X17-59279.ISO
--disk path=/home/khennessy/win7_win8_iso_creation/virtio-win-0.1-100.iso,device=cdrom
--vnc --os-type windows --os-variant win2k8 --force
I then uploaded these to Openstack using a 'minimum disk space' of 90GB, making the minimum flavor xl. (Currently trying a lower value, the images are so large it takes a long time to test anything.)
I then create an instance using this image and log into it using the 'console' view. It all works fine but when I go into 'my computer' it tells me I have only 18GB free space? I have tried 'resizing' the images but it just seems to bring them into an error state?
Can anyone help me? Thanks very much.
Before you upload your windows 7 image onto glance, you need to download CloudbaseInitSetup_x64.msi
or CloudbaseInitSetup_x86.msi] and install it on your windows7 image first. Also, don't forget to add "plugins=cloudbaseinit.plugins.windows.extendvolumes.ExtendVolumesPlugin" to the configuration file of Cloudbase-init.
You can visit and http://cloud-ninja.org/2014/05/14/running-windows-7-guests-on-openstack-icehouse/ for more information.
Although vmdk disk format is supported by ec2-import-instance tool, every time I try to run the command on a vmdk file, I get the following error:
ERROR: File uses unsupported compression algorithm 0
I invoke the tool in the following format:
ec2-import-instance -f vmdk -o <ACCESS KEY> -w <SECRET KEY> <VMDK file>
I am using ec2 tools version 1.6.6.1.
Looks like it's got nothing to do with "compression algorithm" but instead more to do with supported vmdk formats as documented in http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/VMImportPrerequisites.html
ERROR: File uses unsupported compression algorithm 0.
The VMDK was created using OVA format instead of OVF format.
Resolution
Create the VMDK in OVF format.
I fixed this for myself by exporting my VM from VirtualBox(where I created it). This exported its into OVF format(I had to change the default exention from OVA to OVF). Then ec2-import-instance worked.
This put me on the right track when converting to RAW using qemu-img did not work.
This ec2 migration tool works with both VMware workstation and ESX
http://cloudscraper.migrate2iaas.com/
Just run it from your running server.
I have experienced the same issue. My solution: the StarWind V2V converter to convert VMDK to RAW (-f RAW) or VHD (-f VHD).