VM's from old version V 1.1 dont start in V1.3 ?

ictdude

Active Member
May 18, 2008
88
0
26
VM's from old version dont start in V1.3 ?

i made some backups of linux and Windows machines.
Dit test backup and restore in V 1.1 after reinstall server to
version 1.3. i restore the machines but they dont start up any more ?
How to troble shoot this ? :rolleyes: :confused:
 
VM's from old version dont start in V1.3 ?

i made some backups of linux and Windows machines.
Dit test backup and restore in V 1.1 after reinstall server to
version 1.3. i restore the machines but they dont start up any more ?
How to troble shoot this ? :rolleyes: :confused:

KVM or OpenVZ? Error messages, logs?
 
KVM or OpenVZ? Error messages, logs?

I use KVM. I did try to restart my Windows 2003 server.
here the log of the tasks. i did hide my IP adres with some *
cause i dont gonna put all ip info on this forum.

/usr/bin/ssh -t -t -n -o BatchMode=yes *.*.70.135 /usr/sbin/qm start 001
tcgetattr: Inappropriate ioctl for device
load_defaults - unable to parse value of 'keyboard'
Use of uninitialized value $path in concatenation (.) or string at /usr/share/perl5/PVE/QemuServer.pm line 639.
Invalid ID
start failed: command '/usr/bin/kvm -monitor unix:/var/run/qemu-server/001.mon,server,nowait -vnc unix:/var/run/qemu-server/001.vnc,password -pidfile /var/run/qemu-server/001.pid -daemonize -usbdevice tablet -name MS_2003_x64_Server -smp 2 -id 001 -cpuunits 2000 -boot cad -vga cirrus -tdf -localtime -drive file=/var/lib/vz/images/001/vm-120-disk-1.qcow2,if=ide,index=1 -drive file=/var/lib/vz/images/001/vm-120-disk.qcow2,if=ide,index=0,boot=on -drive file=,if=ide,index=2,media=cdrom -m 512 -net tap,vlan=0,ifname=vmtab001i0,script=/var/lib/qemu-server/bridge-vlan0 -net nic,vlan=0,model=rtl8139,macaddr=B2:C0:3F:0B:6E:62' failed with exit code 1 at /usr/share/perl5/PVE/QemuServer.pm line 314.
Connection to *.*.70.135 closed.
VM 001 start failed -
 
You use illegal VM IDs - they should be integer numbers.

"001" is inavlid - should be a integer > 100.

Earlier version allowed to create such illegal VM ids, but it is fixed on 1.2.

Only thing you can do is to rename everything manually.
 
You use illegal VM IDs - they should be integer numbers.

"001" is inavlid - should be a integer > 100.

Earlier version allowed to create such illegal VM ids, but it is fixed on 1.2.

Only thing you can do is to rename everything manually.

Thnx for reply. How to rename this manully ? Its not possible in the gui.
Are this the files in /etc/qemu-server ? So they must be renamed ? :rolleyes:
 
You use illegal VM IDs - they should be integer numbers.

"001" is inavlid - should be a integer > 100.

Earlier version allowed to create such illegal VM ids, but it is fixed on 1.2.

Only thing you can do is to rename everything manually.

I did restore to VM 150 but cant start. See log:

/usr/bin/ssh -t -t -n -o BatchMode=yes *.*.70.135 /usr/sbin/qm start 150
tcgetattr: Inappropriate ioctl for device
load_defaults - unable to parse value of 'keyboard'
qemu: could not open disk image /var/lib/vz/template/iso/en_win_srv_2003_r2_enterprise_x64_with_sp2_vl_cd1_X13-48614.iso
start failed: command '/usr/bin/kvm -monitor unix:/var/run/qemu-server/150.mon,server,nowait -vnc unix:/var/run/qemu-server/150.vnc,password -pidfile /var/run/qemu-server/150.pid -daemonize -usbdevice tablet -name MS_2003_x64_Server_02 -smp 2 -id 150 -cpuunits 2000 -boot cad -vga cirrus -tdf -localtime -drive file=/var/lib/vz/images/150/vm-120-disk-1.qcow2,if=ide,index=1 -drive file=/var/lib/vz/images/150/vm-120-disk.qcow2,if=ide,index=0,boot=on -drive file=/var/lib/vz/template/iso/en_win_srv_2003_r2_enterprise_x64_with_sp2_vl_cd1_X13-48614.iso,if=ide,index=2,media=cdrom -m 512 -net tap,vlan=0,ifname=vmtab150i0,script=/var/lib/qemu-server/bridge-vlan0 -net nic,vlan=0,model=rtl8139,macaddr=2A:0F:0D:FC:69:7E' failed with exit code 1 at /usr/share/perl5/PVE/QemuServer.pm line 314.
Connection to *.*.70.135 closed.
VM 150 start failed -
 
could not open disk image /var/lib/vz/template/iso/en_win_srv_2003_r2_enterprise_x64_with_sp2_vl_cd1_ X13-48614.iso

the ISO file is not on the new system so you cannot start - remove it on the option tab before you start.
 
the ISO file is not on the new system so you cannot start - remove it on the option tab before you start.

Thnx guys !!! I did not know that i was this critical. Just a simple cd rom not there and VM machine number not correct and then problems.
But now all ok :D Many thnx !!! Is there a book are stuff i can buy from Proxmox so those basic things i can lookup ?
 
Thnx guys !!! I did not know that i was this critical. Just a simple cd rom not there and VM machine number not correct and then problems.
But now all ok :D Many thnx !!! Is there a book are stuff i can buy from Proxmox so those basic things i can lookup ?

perfect. the VMID issue is solved already and the restore problem is also known and should be fixed some time.

documentation is on the wiki and after release of 2.x we will start a new attempt to make it more complete.
 
perfect. the VMID issue is solved already and the restore problem is also known and should be fixed some time.

documentation is on the wiki and after release of 2.x we will start a new attempt to make it more complete.

Perfect !!! Proxmox is a great product. I did use Vmware products. But Proxmox and hardware virtualisation like intel -VT have a great performance !!
better then Vmware ESX. Keep up the good job !!! :cool:
 

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!