Convert from physical server to virtual Proxmox

B@ktery

New Member
Feb 16, 2019
18
0
1
35
Hello!

I'm trying to convert from a physical server to a virtual. Created a server image server.vhdx, uploaded it to the server Proxmox. I convert command
qemu-img convert -O qcow2 server.vhdx /dev/pve/vm-104-disk-0
Created a virtual machine with ID 104, run it, the message is as in the picture.
What I do wrong?
 

Attachments

  • 1.png
    1.png
    12.3 KB · Views: 120
Right this is LVM
It is possible to convert LVM to ZFS? And if the data is lost after conversion?
 
It is possible to convert LVM to ZFS? And if the data is lost after conversion?

No and yes. You have reinstall everything, so please backup all you VMs, store them on an external disk, reinstall PVE with ZFS and restore the VMs. This is the easiest and fastest way to do this.
 
I converted the server to /dev/pve/vm-104-disk-0
What are my next steps in the interface, I have to create VM, how do i point the way to the existing drive?
 
LVM volume created automatically when installing Proxmox 5.3 from ISO

root@company:~# ls -l /dev/pve
total 0
lrwxrwxrwx 1 root root 7 Feb 27 13:52 base-100-disk-0 -> ../dm-6
lrwxrwxrwx 1 root root 7 Feb 27 13:49 root -> ../dm-1
lrwxrwxrwx 1 root root 7 Feb 27 13:49 swap -> ../dm-0
lrwxrwxrwx 1 root root 7 Feb 27 14:01 vm-101-disk-0 -> ../dm-7
lrwxrwxrwx 1 root root 7 Feb 27 14:03 vm-102-disk-0 -> ../dm-8
lrwxrwxrwx 1 root root 7 Feb 27 14:03 vm-103-disk-0 -> ../dm-9
 
LVM volume created automatically when installing Proxmox 5.3 from ISO

No, the volume group was created automatically, not the volume. The volume is created if you create a VM.

root@company:~# ls -l /dev/pve
total 0
lrwxrwxrwx 1 root root 7 Feb 27 13:52 base-100-disk-0 -> ../dm-6
lrwxrwxrwx 1 root root 7 Feb 27 13:49 root -> ../dm-1
lrwxrwxrwx 1 root root 7 Feb 27 13:49 swap -> ../dm-0
lrwxrwxrwx 1 root root 7 Feb 27 14:01 vm-101-disk-0 -> ../dm-7
lrwxrwxrwx 1 root root 7 Feb 27 14:03 vm-102-disk-0 -> ../dm-8
lrwxrwxrwx 1 root root 7 Feb 27 14:03 vm-103-disk-0 -> ../dm-9

As I suspected, the file you wrote to does not exist.

In order to get the VM migration, you have to follow the guide:

https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE

In short:
- Create a new VM with the desired specs including the disk with the same or higher capacity as your source VM
- then get the ID and check if the block device exists: ls -lL /dev/pve/vm-<ID>-disk-0
- do the neccessary pre-migration tasks according to the wiki article
- run your copy-command again to write in RAW format to the device
- bootup your VM and do all the necessary post-migration tasks according to the wiki
 
I deleted vm-104-disk-0
I understand correctly that after I converted server.vhdx in vm-104-disk-0, I just need to replace it instead of the disk that was created in /dev/pve/vm-104-disk-0 while creating VM?
 
I understand correctly that after I converted server.vhdx in vm-104-disk-0, I just need to replace it instead of the disk that was created in /dev/pve/vm-104-disk-0 while creating VM?

Yes and No. As I wrote: You need to create the disk beforehand and overwrite the disk contents. It's the same command, but block device needs to be there first.
 
Finally, I managed to run VM, but for this I additionally had to change the interface SATA to IDE.
At boot time a blue screen appears, how do I get it to work VM on SATA? In this case IDE severely affects disk performance?
 
Finally, I managed to run VM, but for this I additionally had to change the interface SATA to IDE.
At boot time a blue screen appears, how do I get it to work VM on SATA? In this case IDE severely affects disk performance?

Have you read the link i posted earlier?

https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE

There is everything explained like bluescreen stuff and also how to use scsi with virtio, which is far superior than using sata.
 
Yes, I did what is written. Loaded from windows disk, connected virtio-win-0.1.164.iso. No suitable driver found.
I also tried to add an additional disk SCSI, and install drivers with Windows connecting virtio-win-0.1.164.iso. The drivers were installed, with an exclamation mark (compatibility warning), after that Windows stopped loading, when I try to boot, I get into the recovery menu Windows.
 
I also tried to add an additional disk SCSI, and install drivers with Windows connecting virtio-win-0.1.164.iso. The drivers were installed, with an exclamation mark (compatibility warning), after that Windows stopped loading, when I try to boot, I get into the recovery menu Windows.

That is the right way to do and I did this at least 50 times without any problem. What is this for type of windows, what edition and what language. I used german and english and never had a problem.
 
Hello!

I'm trying to convert from a physical server to a virtual. Created a server image server.vhdx, uploaded it to the server Proxmox. I convert command
qemu-img convert -O qcow2 server.vhdx /dev/pve/vm-104-disk-0
Created a virtual machine with ID 104, run it, the message is as in the picture.
What I do wrong?
Hi, how did you move your physical server or backed it up on usb or where? I am trying the same thing but I am lost as this is new to me and online are not many things explaining this.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!