[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [rhelv6-list] KVM issues post RHEL6-1->6.2 update



On Fri, Jan 6, 2012 at 9:29 PM, Robin Price II  wrote:
> Ben and rhelv6-list,
>
> Updated KVM host from RHEL 6.1 to RHEL 6.2, migrated guests fail to start
> https://access.redhat.com/kb/docs/DOC-68326


It seems I have a similar problem but in the opposite direction of migration
I have 3 nodes, two with 6.1 version + some updates (but below 6.2)
and one with 6.2.

I have a vm on 6.1 hypervisor and I'm able to live migrate it to the
6.2 host, but then I am not able to migrate from 6.2 to either one of
the 6.1....

relevant components:

6.1 hosts
qemu-kvm-0.12.1.2-2.160.el6_1.8.x86_64
libvirt-0.8.7-18.el6_1.1.x86_64
kernel-2.6.32-131.17.1.el6.x86_64

6.2 hosts
qemu-kvm-0.12.1.2-2.209.el6_2.1.x86_64
libvirt-0.9.4-23.el6_2.1.x86_64
kernel-2.6.32-220.2.1.el6.x86_64

guest is named dacsmaster and it is rh el 5.4
the migration from 6.2 to 6.1 fails with

# clusvcadm -M vm:dacsmaster -m intrarhev2
Trying to migrate vm:dacsmaster to intrarhev2...Failed; service
running on original owner

/var/log/messages information:
on source hypervisor:
Jan 12 15:45:17 rhev1 rgmanager[9267]: Migrating vm:dacsmaster to intrarhev2
Jan 12 15:45:18 rhev1 rgmanager[22193]: [vm] Migrate dacsmaster to
intrarhev2 failed:
Jan 12 15:45:18 rhev1 rgmanager[22215]: [vm] error: internal error
missing hostuuid element in migration data
Jan 12 15:45:18 rhev1 rgmanager[9267]: migrate on vm "dacsmaster"
returned 150 (unspecified)
Jan 12 15:45:18 rhev1 rgmanager[9267]: Migration of vm:dacsmaster to
intrarhev2 failed; return code 150

on target hypervisor:
Jan 12 15:45:18 rhev2 kernel: device vnet4 entered promiscuous mode
Jan 12 15:45:18 rhev2 kernel: brvlan65: topology change detected, propagating
Jan 12 15:45:18 rhev2 kernel: brvlan65: port 3(vnet4) entering forwarding state
Jan 12 15:45:18 rhev2 libvirtd: 15:45:18.113: 31182: warning :
qemudStartVMDaemon:3336 : Executing /usr/libexec/qemu-kvm
Jan 12 15:45:18 rhev2 libvirtd: 15:45:18.119: 31182: warning :
qemudStartVMDaemon:3346 : Executing done /usr/libexec/qemu-kvm
Jan 12 15:45:18 rhev2 qemu-kvm: Could not find keytab file:
/etc/qemu/krb5.tab: No such file or directory
Jan 12 15:45:18 rhev2 libvirtd: 15:45:18.332: 8787: error :
virCgroupRemoveRecursively:679 : Unable to remove
/cgroup/cpu/libvirt/qemu/dacsmaster/ (16)
Jan 12 15:45:18 rhev2 libvirtd: 15:45:18.332: 8787: error :
virCgroupRemoveRecursively:679 : Unable to remove
/cgroup/cpuacct/libvirt/qemu/dacsmaster/ (16)
Jan 12 15:45:18 rhev2 libvirtd: 15:45:18.332: 8787: error :
virCgroupRemoveRecursively:679 : Unable to remove
/cgroup/cpuset/libvirt/qemu/dacsmaster/ (16)
Jan 12 15:45:18 rhev2 libvirtd: 15:45:18.332: 8787: error :
virCgroupRemoveRecursively:679 : Unable to remove
/cgroup/memory/libvirt/qemu/dacsmaster/ (16)
Jan 12 15:45:18 rhev2 libvirtd: 15:45:18.332: 8787: error :
virCgroupRemoveRecursively:679 : Unable to remove
/cgroup/devices/libvirt/qemu/dacsmaster/ (16)
Jan 12 15:45:18 rhev2 libvirtd: 15:45:18.332: 8787: error :
virCgroupRemoveRecursively:679 : Unable to remove
/cgroup/freezer/libvirt/qemu/dacsmaster/ (16)
Jan 12 15:45:18 rhev2 libvirtd: 15:45:18.332: 8787: error :
virCgroupRemoveRecursively:679 : Unable to remove
/cgroup/blkio/libvirt/qemu/dacsmaster/ (16)
Jan 12 15:45:18 rhev2 kernel: brvlan65: port 3(vnet4) entering disabled state
Jan 12 15:45:18 rhev2 kernel: device vnet4 left promiscuous mode
Jan 12 15:45:18 rhev2 kernel: brvlan65: port 3(vnet4) entering disabled state

powering off the guest (through "disable" action of the related rhcs
service) and powering it on on 6.1 host, I'm able to live migrate it
either to the other 6.1 host and to the 6.2 one...

/etc/libvirt/libvirtd.conf doesn't contain anything for the host_uuid
part as I find in messages of source 6.2 hypervisor.....
and dmidecode command succeeds on all the three systems.

they are identical servers and for example output on one of them gives:
# dmidecode -s system-uuid
34353439-3036-435A-4A38-303330393332

BTW: the contents of the KB referred seem quite limitating in
flexibility during upgrade between minor versions....

Thanks in advance,
Gianluca


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]