Vms no auto start and no more live migration after 1.5 upgrade

V

vitor costa

Renowned Member
Oct 28, 2009
142
2
83
i update from pvetest repo to pve version 1.5

Now i have 2 problens:

1)

When the host boot none kvm vms start automaticaly.

If in host term/console i start /etc/init.d/qemu-server start - the vms go up.

try 2.6.32 kernel and test to 2.6.24 too. same efect.

2)

My environment is a 2 node cluster with drbd. The live migration worked with 1 cpu only. Its before.... now when i start a live migration i have this:

/usr/bin/ssh -t -t -n -o BatchMode=yes 192.168.1.201 /usr/sbin/qmigrate --online 192.168.1.200 102
Jan 26 20:19:53 starting migration of VM 102 to host '192.168.1.200'
Jan 26 20:19:54 copying disk images
Jan 26 20:19:54 starting VM on remote host '192.168.1.200'
Jan 26 20:19:54 starting migration tunnel
Jan 26 20:19:55 starting online/live migration
Jan 26 20:19:57 migration status: active (transferred 9320KB, remaining 531676KB), total 540928KB)


the normal progression not go. I abort and then vm apear in destination node running , but dead.

Any ideas or sugestions ?
 
Here output:

# pveversion -v:

pve-manager: 1.5-5 (pve-manager/1.5/4627)
running kernel: 2.6.24-9-pve
proxmox-ve-2.6.18: 1.5-4
pve-kernel-2.6.32-1-pve: 2.6.32-4
pve-kernel-2.6.24-9-pve: 2.6.24-18
pve-kernel-2.6.24-8-pve: 2.6.24-16
pve-kernel-2.6.18-1-pve: 2.6.18-4
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-7
vncterm: 0.9-2
vzctl: 3.0.23-1pve5
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-4



About logs:

I examine the logs in period from last boot (last night 19:22):

- Nothing about qemu in syslog
- Nothing about qemu in messages

Any other log ?
 
You simply run wrong versions!

> running kernel: 2.6.24-9-pve

but you installed:

> proxmox-ve-2.6.18: 1.5-4

Please install proxmox-ve-2.6.24 if you run kernel 2.6.24.
 
Originaly i have pvetest with 2.6.24 i uptate to pve production repository and update. After that i install the 2.6.32 and 2.618 kernels. I think all kernsl can live in the same host only selecti the kennel in boot time....

If not i need remove all kernnels but one ?
 
vitor costa said:
Originaly i have pvetest with 2.6.24 i uptate to pve production repository and update. After that i install the 2.6.32 and 2.618 kernels. I think all kernsl can live in the same host
only selecti the kennel in boot time....
Click to expand...

No, you also need the appropriate userspace tools.

vitor costa said:
If not i need remove all kernnels but one ?
Click to expand...

No, simply install the correct usepspace tools. For example, if you want to use 2.6.24 do:

# apt-get install proxmox-ve-2.6.24

That should install everything you need for that kernel.
 
vitor costa said:
Originaly i have pvetest with 2.6.24 i uptate to pve production repository and update. After that i install the 2.6.32 and 2.618 kernels. I think all kernsl can live in the same host only selecti the kennel in boot time....

If not i need remove all kernnels but one ?
Click to expand...

no, pls see http://pve.proxmox.com/wiki/Proxmox_VE_Kernel

I will explain:
you need to install one of the new virtual packages (2.6.18,2.6.24,2.6.32).
by doing this, the virtual packages install all needed packages suitable for the kernel. you are running 2.6.24 now, but using pve-qemu-kvm-2.6.18 which is only for 2.6.18 - therefore you have problems.

based on you posting, you are running 2.6.24.
therefore, install:

Code: 
apt-get install proxmox-ve-2.6.24
this will install the latest 2.6.24 kernel and the pve-qemu-kvm for this kernel.

finally your pveversion -v should look like this (running kernel and kvm in red):

Code: 
pveversion -v

pve-manager: 1.5-5 (pve-manager/1.5/4627)
[COLOR=Red]running kernel: 2.6.24-10-pve[/COLOR]
proxmox-ve-2.6.24: 1.5-21
pve-kernel-2.6.24-10-pve: 2.6.24-21
pve-kernel-2.6.18-1-pve: 2.6.18-4
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-8
vncterm: 0.9-2
vzctl: 3.0.23-1pve7
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
[COLOR=Red]pve-qemu-kvm: 0.11.1-2[/COLOR]
 
I do that.

pm-1:~# pveversion -v
pve-manager: 1.5-5 (pve-manager/1.5/4627)
running kernel: 2.6.24-10-pve
proxmox-ve-2.6.24: 1.5-21
pve-kernel-2.6.32-1-pve: 2.6.32-4
pve-kernel-2.6.24-10-pve: 2.6.24-21
pve-kernel-2.6.24-9-pve: 2.6.24-18
pve-kernel-2.6.24-8-pve: 2.6.24-16
pve-kernel-2.6.18-1-pve: 2.6.18-4
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-7
vncterm: 0.9-2
vzctl: 3.0.23-1pve5
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-1


Results:

1) Auto boot vms: Same problem (none start at boot)

2) Migration: The memory transfer now progress ok (no need abort) but 2 of my 3 vms not apear live in th destination host.:
Vm with Pfsense/freebsd 1 cpu - sucess migration
Vm with Windows Xp 1 cpu - dead (with 102% cpu utilization)
Vm with OpenSuse 11.2 with 2 cpu - Dead (with 102% cpu utilization -its a old problem)
 
vitor costa said:
I do that.

pm-1:~# pveversion -v
pve-manager: 1.5-5 (pve-manager/1.5/4627)
running kernel: 2.6.24-10-pve
proxmox-ve-2.6.24: 1.5-21
pve-kernel-2.6.32-1-pve: 2.6.32-4
pve-kernel-2.6.24-10-pve: 2.6.24-21
pve-kernel-2.6.24-9-pve: 2.6.24-18
pve-kernel-2.6.24-8-pve: 2.6.24-16
pve-kernel-2.6.18-1-pve: 2.6.18-4
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-7
vncterm: 0.9-2
vzctl: 3.0.23-1pve5
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-1


Results:

1) Auto boot vms: Same problem (none start at boot)

2) Migration: The memory transfer now progress ok (no need abort) but 2 of my 3 vms not apear live in th destination host.:
Vm with Pfsense/freebsd 1 cpu - sucess migration
Vm with Windows Xp 1 cpu - dead (with 102% cpu utilization)
Vm with OpenSuse 11.2 with 2 cpu - Dead (with 102% cpu utilization -its a old problem)
Click to expand...

Hello vitor,

Where is your images located?
I had a similar problem with online migration when I tryed to use one of two host servers as NFS server for images.

Stas
 
I do that.

pm-1:~# pveversion -v
pve-manager: 1.5-5 (pve-manager/1.5/4627)
running kernel: 2.6.24-10-pve
proxmox-ve-2.6.24: 1.5-21
pve-kernel-2.6.32-1-pve: 2.6.32-4
pve-kernel-2.6.24-10-pve: 2.6.24-21
pve-kernel-2.6.24-9-pve: 2.6.24-18
pve-kernel-2.6.24-8-pve: 2.6.24-16
pve-kernel-2.6.18-1-pve: 2.6.18-4
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-7
vncterm: 0.9-2
vzctl: 3.0.23-1pve5
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-1


Results:

1) Auto boot vms: Same problem (none start at boot)

2) Migration: The memory transfer now progress ok (no need abort) but 2 of my 3 vms not apear live in th destination host.:
Vm with Pfsense/freebsd 1 cpu - sucess migration
Vm with Windows Xp 1 cpu - dead (with 102% cpu utilization)
Vm with OpenSuse 11.2 with 2 cpu - Dead (with 102% cpu utilization -its a old problem)
 
vitor costa said:
I examine the logs in period from last boot (last night 19:22):

- Nothing about qemu in syslog
- Nothing about qemu in messages

Any other log ?
Click to expand...

Is there any message on the console screen when you boot that host?
 
You must log in or register to reply here.
Top Bottom