Migration from Ubuntu KVM

[Xmindaugas]

Hello,
I couldn't find information, about MIGRATION from Ubuntu KVM to ProxMox.
Above systems using *.qcow2 type files for VM machines, but my VM's on Ubuntu KVM has Machine ID on *.xml,
as you know *.xml file has all "mechanical" configuration for VM (core numbers, RAM and etc.)
I have founded in ProxMox something same, but files is not identical to each other.
I cant lost or change VM's machines ID, because all licenses of MS will be reset, also it will be with CRM Software, so is not good.
So what to do

 

[MarvinE]

Hello,

I think you search the following:

https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines#_vm_generation_id

Edit: on Configuration:

You can also find a hv-vendor-id
https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines#qm_configuration

hv-vendor-id=<vendor-id> The Hyper-V vendor ID. Some drivers or programs inside Windows guests need a specific ID.

Optional / not supported kvm options can be added over args:
args: <string> Arbitrary arguments passed to kvm, for example:

 

[Xmindaugas]

Hello,

I think you search the following:

https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines#_vm_generation_id

Edit: on Configuration:

You can also find a hv-vendor-id
https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines#qm_configuration

hv-vendor-id=<vendor-id> The Hyper-V vendor ID. Some drivers or programs inside Windows guests need a specific ID.

Optional / not supported kvm options can be added over args:
args: <string> Arbitrary arguments passed to kvm, for example:

Thank you for reaplay, who made that in real ?

 

[MarvinE]

Did you mean where you can set this configurations?

This is described in the first line:
https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines#qm_configuration
Configuration VM configuration files are stored inside the Proxmox cluster file system, and can be accessed at /etc/pve/qemu-server/<VMID>.conf. Like other files stored inside /etc/pve/, they get automatically replicated to all other cluster nodes.

 

[Xmindaugas]

can I do thiese steps:
1, copying vm1.qcow2 from Linux KVM to ProxMox machine, then
2. then making the same configuration as previous VM
3. going to ( in proxmox) /etc/pve/qemu-server/<VMID>.conf
4. copying machine ID from Linux kvm *.xml file to *.conf file in Proxmox?

 

[MarvinE]

Can you post some example XML ? You can replace some critical informations with XXXXX or something.

 

[Xmindaugas]

<domain type='kvm'>
<name>Server2012-Std</name>
<uuid>97c5e5b4-e098-4d4a-91ae-5fdd60965088</uuid>
<memory unit='KiB'>8192000</memory>
<currentMemory unit='KiB'>8192000</currentMemory>
<vcpu placement='static' current='12'>144</vcpu>
<os>
<type arch='x86_64' machine='pc-i440fx-bionic'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<vmport state='off'/>
</features>
<cpu mode='custom' match='exact' check='partial'>
<model fallback='allow'>Haswell-noTSX-IBRS</model>
<topology sockets='2' cores='6' threads='12'/>
</cpu>
<clock offset='utc'>
<timer name='rtc' tickpolicy='catchup'/>
<timer name='pit' tickpolicy='delay'/>
<timer name='hpet' present='no'/>
</clock>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
half of file of xml, everything else about pci devices and etc..

so of xml file string:
<uuid>97c5e5b4-e098-4d4a-91ae-5fdd60965088</uuid>
very similar to machiene id of
smbios1:
uuid=542c7a29-1115-4dd3-a52e-597a896228bf

 

[MarvinE]

https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines#_vm_generation_id

I think you can set it with:
qm set <VMID> -vmgenid 00000000-0000-0000-0000-000000000000

Here I found your smbios1 setting:
https://forum.proxmox.com/threads/setting-uuid-for-kvm-vm.45880/post-217958
qm set <VMID> -smbio1 uuid=<uuid>

The following I would do:

1. Create a new VM with qcow2 in Proxmox (note the VMID) (Use a folder as Storage)
2. Set all your hardware configurations in Proxmox gui
3. Set on command line vmgenid/uuid
4. Replace the Proxmox .qcow2 with your vm1.qcow2

But I don't now if your software license will work. Every software producer uses different ways to detect hardware changes.