[CentOS] qemu-kvm failed after update from CR repo

Mon Nov 28 23:44:58 UTC 2011
Emmett Culley <emmett at webengineer.com>

On 11/28/2011 02:48 PM, Akemi Yagi wrote:
> On Mon, Nov 28, 2011 at 10:38 AM, Emmett Culley<emmett at webengineer.com>  wrote:
>> I finally decided to install the CR repo on one of my CentOS 6 machines that I use as a host for some VMs (also running CentOS 6).
>> Before updating the host I updated a VM that was not critical to test the process and was able to boot that VM, so I went ahead with updating the host and the two VMs that were in use.
>> When I rebooted the host none of the VM would start.
>> Once I figured out that it had to be the host I started downgrading the virtual packages.  I was finally able to get the VMs to boot after dwongrading qemu-kvm.
>> Has anyone else seen this?
> You might want to provide more detailed info. What is the version of
> qemu-kvm that worked/failed ? What is the kernel version? When the VM
> guests failed to start, did you see any error message?
> Also, VM-related questions may be better discussed on the cent-virt
> mailing list.
> Akemi
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos
kernel-2.6.32-131.17.1.el6.x86_64 (after update and currently)

After update:


After downgrade:


Prior to installing the CR repo the host was up to date with the CentOS base and updates repos (not many packages different from the release ISO).  After, it was up to date with the CR repo and the VM would not start.  The host is now up to date with the CR repo except that libvirt* pyton-libvirt and qemu-kvm have all been downgraded to what was up to date for the CentOS base and updates repos.

By "won't boot" I mean that "running" a VM via virt-manager showed only a black screen with the CPU usage graphic in virt-manager at a steady state.  No error messages, only a black screen.

If no one else has seen this I will look to the cent-virt mailing list as suggested.  I am assuming however, that this is a CR repo issue.