How can I migrate a vm from 1.9 to 2.0 ? I think livemigration is not working, is it possible to qmrestore a 1.9 backup to 2.0 ?
How to migrate a proxmox 1.9 vm to 2.0b3 ?
- Thread starter fpausp
- Start date
Hi,
yes - but you must edit the vm-config after that. The network-line must be changed - take a look on running configs on both nodes and you will see the differences.
BTW. qmrestore use simply tar - so you can do all "by hand".
Udo
Hi udo,
I cannot start from hdd on the qmrestored machine with patched config, it boots up from cd ?
I cannot start from hdd on the qmrestored machine with patched config, it boots up from cd ?
Hi,
any error messages if you start from the console ( qm start 123 )?
Please post your VM-config.
Udo
no errormsg with: qm start 104
config (mac is changed):
config (mac is changed):
Code:
cpu: kvm32
net0: virtio=xx:xx:xx:xx:xx:xx,bridge=vmbr0
ide2: local:iso/smeserver-7.5.1-i386.iso,media=cdrom
name: sme7-242
bootdisk: scsi0
cores: 1
ostype: l26
memory: 512
sockets: 1
scsi0: local:104/vm-104-disk-1.qcow2
keyboard: de
onboot: 1Hi,
scsi0 is the problem i guess. Try with ide0 (or virtio).
On a linux-server it's should run without trouble (if you use UUID/LVM-Path in fstab. oterwise you must edit the fstab inside the VM).
Udo
scsi0 is the problem i guess. Try with ide0 (or virtio).
On a linux-server it's should run without trouble (if you use UUID/LVM-Path in fstab. oterwise you must edit the fstab inside the VM).
Udo
OK the vm (sme7) is booting with ide0.
The config is:
And I had to change to bootorder to ide0.
Thanks for your help, i will do some tests now ...
The config is:
Code:
cpu: kvm32
net0: virtio=XX:XX:XX:XX:XX:XX,bridge=vmbr0
name: sme7-242
bootdisk: ide0
cores: 1
ostype: l26
memory: 512
sockets: 1
ide0: local:104/vm-104-disk-1.qcow2
keyboard: de
onboot: 1
boot: cdnAnd I had to change to bootorder to ide0.
Thanks for your help, i will do some tests now ...
Hi All,
The same result with a qmrestored SME8.
I did a test with iperf to check the (virtual) network-traffic between SME8 and Ubuntu 10.04 on a Fujitsu TX100 S3:
Looks good, I think thats ok
The same result with a qmrestored SME8.
I did a test with iperf to check the (virtual) network-traffic between SME8 and Ubuntu 10.04 on a Fujitsu TX100 S3:
Code:
------------------------------------------------------------
Client connecting to 192.168.111.252, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.111.1 port 50570 connected with 192.168.111.252 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 13.5 GBytes 11.6 Gbits/sec
[ 3] 10.0-20.0 sec 12.4 GBytes 10.6 Gbits/sec
[ 3] 20.0-30.0 sec 12.0 GBytes 10.3 Gbits/sec
[ 3] 30.0-40.0 sec 12.2 GBytes 10.5 Gbits/sec
[ 3] 40.0-50.0 sec 12.1 GBytes 10.4 Gbits/sec
[ 3] 50.0-60.0 sec 12.1 GBytes 10.4 Gbits/sec
[ 3] 0.0-60.0 sec 74.4 GBytes 10.7 Gbits/secLooks good, I think thats ok
Hi,
W2k8R2 is also working, I qmrestored it without any config-modification (just keyboard-layout to german).
The config is:
W2k8R2 is also working, I qmrestored it without any config-modification (just keyboard-layout to german).
The config is:
Code:
name: win2k8r2
net0: virtio=xx:xx:xx:xx:xx:xx,bridge=vmbr0
bootdisk: virtio0
virtio0: local:109/vm-109-disk-1.raw
ostype: w2k8
memory: 8000
sockets: 1
onboot: 0
cores: 1
keyboard: deOh Sh.., after a reboot of the Windows2008R2 I got a ugly bluescreen (DRIVER_IRQL_NOT_LESS_OR_EQUAL) ...
Hi udo,
Thanks, e1000 should work for win7ult and w2k8r2,
the next one is a qmrestored debian 6 (gemeinschaft 3.1 pbx).
I will do some tests ...
Thanks, e1000 should work for win7ult and w2k8r2,
the next one is a qmrestored debian 6 (gemeinschaft 3.1 pbx).
Code:
cpu: qemu64
net0: rtl8139=xx:xx:xx:xx:xx:xx,bridge=vmbr0
virtio1: local:240/vm-240-disk-1.qcow2
name: deb6-gemeinschaft-3-1-225
bootdisk: virtio1
cores: 1
ostype: l26
memory: 1000
sockets: 1
keyboard: de
vga: cirrus
boot: cdnI will do some tests ...
Hi,
for linux-guest I preferr virtio-net (very stable - not comparable with the windows version).
Udo
OK, thanks for the hint. Is it possible to extract the given-name from a backup for example vzdump-qemu-114-2012_01_26-06_58_42.tgz ?
Hi,
you can extract the config alone:
Code:
tar xvzf vzdump-qemu-114-2012_01_26-06_58_42.tgz qemu-server.conf
grep name qemu-server.conf