Bug#731815: virsh: Unable to start any VM with custom cpu model

2015-01-23 Thread Jörg Esser
Hi, I had exactly the same problem with latest testing from today. Just delete the old /var/cache/libvirt/qemu/capabilities and do /etc/init.d/libvirtd restart solves all problems. Thx to Ariel Malves hf, Joerg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a

Bug#731815: [Pkg-libvirt-maintainers] Bug#731815: virsh: Unable to start any VM with custom cpu model

2014-10-29 Thread Thomas Rechberger
I did a fresh install from beta2 iso: http://cdimage.debian.org/cdimage/jessie_di_beta_2/amd64/iso-cd/debian-jessie-DI-b2-amd64-lxde-CD-1.iso Following steps to reproduce: After fresh install the /var/cache/libvirt/qemu/capabilities folder does not exist. Installed libvirt-bin and virtinst pack

Bug#731815: [Pkg-libvirt-maintainers] Bug#731815: virsh: Unable to start any VM with custom cpu model

2014-10-28 Thread Guido Günther
On Tue, Oct 28, 2014 at 07:36:40PM +0100, Thomas Rechberger wrote: > That is totally working for me, thank you so much for the find. That points to libvit no refreshing capabilities properly during the upgrade from wheezy to jessie. It should detect the changed qemu and do so. Can you add the in

Bug#731815: virsh: Unable to start any VM with custom cpu model

2014-10-28 Thread Thomas Rechberger
That is totally working for me, thank you so much for the find. Am 28.10.2014 18:33, schrieb Ariel Malves: Hi, I faced a similar problem when upgrading libvirt/qemu packages from wheezy to wheezy-backports. Try to delete /var/cache/libvirt/qemu/capabilities and restart libvirt-bin. []'s Ariel

Bug#731815: virsh: Unable to start any VM with custom cpu model

2014-10-28 Thread Ariel Malves
Hi, I faced a similar problem when upgrading libvirt/qemu packages from wheezy to wheezy-backports. Try to delete /var/cache/libvirt/qemu/capabilities and restart libvirt-bin. []'s Ariel On 10/27/2014 02:38 PM, Thomas Rechberger wrote: Same problem after changing from wheezy to jessie. vi

Bug#731815: virsh: Unable to start any VM with custom cpu model

2014-10-27 Thread Thomas Rechberger
Same problem after changing from wheezy to jessie. virt-install --name test --memory 1024 --nodisk --pxe --cpu host ERRORinternal error: Cannot find suitable CPU model for given data libvirtd log: Preferred CPU model Opteron_G3 not allowed by hypervisor; closest supported model will be used

Bug#731815: virsh: Unable to start any VM with custom cpu model

2014-04-25 Thread Ariel Malves
Dear Maintainer, Just to confirm the bug: I'm running Debian stable, with libvirt, qemu and kvm from wheezy-backports (libvirt 1.2.1, API QEMU 1.2.1, hypervisor QEMU 1.7.1), in a HP ProLiant G7 server, with Xeon E5649 processor. I can't start a domain, through virsh start, with any type of c