[PVE-User] VM windows 2008 issue.

Alain Péan alain.pean at lpp.polytechnique.fr
Fri Jul 1 16:34:10 CEST 2011


Hi Holger,

Thanks for the clarification. That is indeed not what I understood. I am 
not sure that it is the fastest way to do the migration. I myself had to 
migrate Microsoft Virtual Server VMs to Proxmox, and here is what I did :
1) remove 'Virtual additions' (the same as vmware tools),
2) apply ide.reg patch in order the system recognizes IDE drives,
3) Create a new VM in Proxmox with the same HD size (raw, IDE) as the 
windows VM ones (I had fixed size .vhd files)
4) replace these new raw files, by the .vhd ones, renaming them to .raw.
5) boot the VM.

Fixed size .vhd files, the same for .vmdk, are in fact .raw files. For 
ordinary NTFS files, you can mount them using :
# mount -o loop,offset=32256 /path/to/image.vhd /mnt/mountpoint

You can replace .vhd by .raw, it is the same, and see the files inside 
inside the image file.

I agree that your method could deal better with some driver issues. I 
saw for example a problem with a 'processor' driver, for ACPI, but it 
appears to be harmless....

Alain

Le 01/07/2011 16:05, Holger Ernst a écrit :
> Hi Alain, hi Muhammad,
> Alain, you got something wrong here. I appologize for having been 
> short and unprecise.
> What I did: Do a Backup from within the windows Server with Microsoft 
> built in  Backup program to an available cifs share (not VMware, not nfs).
> Create the appropriate vm in proxmox with a Windows2008 ISO mounted as 
> boot cd.
> Then do a restore from within the windows rescue system from the cifs 
> share mentioned above.
> If you need additional drivers (like virtio disk drivers for example) 
> add another cd and attach an ISO with the drivers.
> I would not try to convert the disk images itself. You might run into 
> trouble with windows handling disk drivers very unflexible. Win2008 is 
> far better than Win2003 but still not flexible enough sometimes.
> Regards. Holger
>
> ------------------------------------------------------------------------
> *Von:* pve-user-bounces at pve.proxmox.com 
> [mailto:pve-user-bounces at pve.proxmox.com] *Im Auftrag von *Alain Péan
> *Gesendet:* Freitag, 1. Juli 2011 14:06
> *An:* pve-user at pve.proxmox.com
> *Betreff:* Re: [PVE-User] VM windows 2008 issue.
>
> Hi Muhammad,
>
> See a recent thread on this list 'Vmware to Proxmox migration" and 
> especially the answer from Ernst Holger. He meant to use the backup 
> program from Vmware, to store the backup to a network share (NFS...), 
> then use the backup program from proxmox, and the function 'restore', 
> to restore the VM on Proxmox. Martin Maurer tested it and agreed it 
> was the easiest solution.
>
> For the growable image file, it seems it is possible to convert it 
> with vmware vdisk-manager. See for example this thread :
> http://communities.vmware.com/thread/155051
>
> Alain
>
> Le 01/07/2011 13:42, Muhammad Yousuf Khan a écrit :
>> ok, thats sounds interesting and new. can you please tell me what do 
>> u mean by exporting with VMWARE stuff ? unfortunately i am using 
>> VMware harddisk which increase the size when data inserted. :(. and i 
>> think we can not convert that type of harddisk with Qemu converter. 
>> make me right if mis-concept.
>>
>> Thank you,
>>
>>
>>
>>
>> On Fri, Jul 1, 2011 at 4:26 PM, Laurent CARON 
>> <lcaron at unix-scripts.info <mailto:lcaron at unix-scripts.info>> wrote:
>>
>>     On 01/07/2011 13:15, Muhammad Yousuf Khan wrote:
>>     > here is the status.
>>     >
>>     > VMware to KVM (migration)= not working (with 30 GB HD and 2 GB RAM)
>>     >
>>     > Fresh installation = worked (with 20gb HD and 1GB RAM with same DVD
>>     > image deployed on VMWARE)
>>     >
>>     > now problem is i am stuck in migration from VMware to KVM
>>     haven't tried
>>     > migration from real machine
>>
>>
>>     Hi,
>>
>>     I would suggest the following:
>>
>>     - Export the image of the VMWare VM using VMWare stuff
>>     - Convert it with qemu-img
>>            - qemu-img convert -O raw input_disk output_disk
>>     - d the output_disk file onto the device
>>
>>     I had to do this on some VMs which were exhibiting the same black
>>     screen
>>     you're getting.
>>
>>     Hope this helps.
>>     _______________________________________________
>>     pve-user mailing list
>>     pve-user at pve.proxmox.com <mailto:pve-user at pve.proxmox.com>
>>     http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>
>>
>>
>> _______________________________________________
>> pve-user mailing list
>> pve-user at pve.proxmox.com
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>
> -- 
> ==========================================================
> Alain Péan - LPP/CNRS
> Administrateur Système/Réseau
> Laboratoire de Physique des Plasmas - UMR 7648
> Observatoire de Saint-Maur
> 4, av de Neptune, Bat. A
> 94100 Saint-Maur des Fossés
> Tel : 01-45-11-42-39 - Fax : 01-48-89-44-33
> ==========================================================
>
>
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user


-- 
==========================================================
Alain Péan - LPP/CNRS
Administrateur Système/Réseau
Laboratoire de Physique des Plasmas - UMR 7648
Observatoire de Saint-Maur
4, av de Neptune, Bat. A
94100 Saint-Maur des Fossés
Tel : 01-45-11-42-39 - Fax : 01-48-89-44-33
==========================================================

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pve.proxmox.com/pipermail/pve-user/attachments/20110701/74d77238/attachment-0014.html>


More information about the pve-user mailing list