Use of .qcow2 as "image"

[EpicFrench]

Hello !

Thanks in advance for your future help,

Now here's come the "problem"

I'm actually on an company which used to use VMWare ESXi 5.1 and now for some reasons want to use ProxMox VE 3.0.

So what I actually did was to copy and convert some files I needed to restore the VM which I did. (Thanks to http://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE)

Now that I have my .qcow2 file I don't know how to make it understand " Use this .qcow2 extension to boot ".

Thanks,

Best regards.

 

[mmenaz]

I would create a VM from proxmox web interface, hd type qcow2, etc. then replace the generated empty file with the one you want to use for that vm.
i.e. for VM 105 something like that:
# cp myhd.qcow2 vm-105-disk-2.qcow2 /var/lib/vz/images/105/vm-105-disk-1.qcow2

 

[EpicFrench]

Thanks a lot, apparently same error occured, so I think it's my copy from VMWare VM which actually fail. Which file should i convert, the .vmdk one or the flat.vmdk ?

Thanks,

Best regards.

 

[mir]

Does your VmWare keep the "disks" in one vmdk or is it scattered over a number of vmdk's size 2G? If the disks are scattered over a number of vmdk's you need to get VmWare to assemble all the peaces to one vmdk before you convert. (AFAIK Qemu does not support disks scattered over many small vmdk's)

See: http://www.mahmoudthoughts.com/2009/07/merge-2gb-vmdk-files-to-one-single-vmdk.html

 

[EpicFrench]

Hi,

No, my tree looks like this

 

[spirit]

maybe this can help:
http://blog.rah.org/2008/12/converting-split-vmdk-files-to-qcow2.html

 

[EpicFrench]

Unfortunately I've already done this

Thanks.

Best regards

 

[udo]

Thanks a lot, apparently same error occured, ...

Hi,
what do you mean with "same error occured"??
If you start the VM, do you see anything?
Do you get any error messages?
What is the output if you start the VM from the console?

qm start VMID

Please post also the VM-config

cat /etc/pve/qemu-server/VMID.conf

Which system is inside the VM (Linux, Windows, Version?) and which kind of disk was defined in ESX - I assume scsi?

Udo

 

[EpicFrench]

Hi, thanks a lot for your answer !

I'll give you all of theses informations tomorrow @ work.

Thanks.

Best regards

 

[EpicFrench]

Hi,
what do you mean with "same error occured"??
If you start the VM, do you see anything?
Do you get any error messages?
What is the output if you start the VM from the console?

qm start VMID

Please post also the VM-config

cat /etc/pve/qemu-server/VMID.conf

Which system is inside the VM (Linux, Windows, Version?) and which kind of disk was defined in ESX - I assume scsi?

Udo

Actually I would, use a Windows Server 2008 R2 inside, and yes, it's a SCSCI one.

Here's the VMID.conf

"
boot : c
bootdisk : scsi0
cores : 2
ide2: none, media=cdrom
memory: 2048
name: SRV-WEB
net0: e1000=9E:9E:30:66:C5:17, bridge=vmbr0
ostype: win7/2008r2
scsci0 : local:102/vm-102-disk-1.qcow2, format=qcow2, size 8G
sockets: 1

Thanks a lot,

Best regards
P.S : Here is my error message

 

[udo]

Hi,
it's looks that somethings goes wrong during the convertion.

But your *-flat.vmdk is one huge big file, right?
In this case it's allready an raw-image of an hdd. Simply copy the file to the pve-host, named /var/lib/vz/images/102/vm-102-disk-1.raw and select this as disk0 (start with ide. because the right scsi-driver is normaly not installed in windows).
With file you should get an answer like this (in this case it's an non bootable hdd)

file /var/lib/vz/images/102/vm-102-disk-1.raw
/var/lib/vz/images/102/vm-102-disk-1.raw: x86 boot sector; partition 1: ID=0x83, starthead 0, startsector 2048, 207667 sectors, extended partition table (last)\011, code offset 0x0

So you VM.conf should look like

boot : c
bootdisk : ide0
cores : 2
ide2: none, media=cdrom
memory: 2048
name: SRV-WEB
net0: e1000=9E:9E:30:66:C5:17, bridge=vmbr0
ostype: win7/2008r2
ide0 : local:102/vm-102-disk-1.raw, size 8G
sockets: 1

Udo

 

[EpicFrench]

Hi,

Thanks for your reply i'll give it a try ASAP
But as it looks i don't have any .raw extension, strange.

Thanks,

Best regards

 

[EpicFrench]

Ok seems, we can access the Start Windows or use back up system like rescue tools (something like that I have french version ).
And now we have Blue screen with 0x0000007B and can't do anything.

Thanks.

Best regards

 

[mir]

If the vmdk is created on a VmWare 5.x it might be worth a try first to convert this image to a VmWare 4.x vmdk before converting to qcow2.

 

[EpicFrench]

Seems we get through this problem, actually we have the BSOD 0x000007B issue

 

[EpicFrench]

BUMP, Does anyone have any idea about this BSOD 0x00007B Error ?

I tried so many things, I'm running out of ideas.

Thanks,

Best Regards

 

[m.ardito]

hi!

the wiki article you cited on the first post explains how to get around those errors... look for "inaccessible boot device" just at the top...
in my experience, all the times it was that. Check also the boot.ini is loading the right partition

Marco

 

[EpicFrench]

Hello,

Thanks a lot we passed through all of these problems

Thanks,

Best regards