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

Unable to start kvm virtual machines after re-install of "testing"



Hi,

After a fresh reinstall of Debian "testing" today, I am unable to start
my virtual machines. I lost the configuration during the reinstall, but
have the disk images. I'm not sure if it is a bug or something wrong on
my machine. The images worked on Debian "testing" after an upgrade two
days ago).


Trying to import any of the VM's with "virt-manager", I get the the
error below.

Please advice it I should file a bug-report or steps to resolve the problem.


>From "Virtual Machine Manager":
Unable to complete install: 'internal error: Cannot find suitable CPU
model for given data'

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in
cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/create.py", line 1787, in
do_install
    guest.start_install(meter=meter)
  File "/usr/share/virt-manager/virtinst/guest.py", line 403, in
start_install
    noboot)
  File "/usr/share/virt-manager/virtinst/guest.py", line 467, in
_create_guest
    dom = self.conn.createLinux(start_xml or final_xml, 0)
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3440, in
createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: internal error: Cannot find suitable CPU model for given data


In /var/log/kern.log I observe:
Nov 11 11:28:13 revenger libvirtd[1081]: libvirt version: 1.2.9,
package: 3 (root 2014-10-14-16:53:26 bogon)
Nov 11 11:28:13 revenger libvirtd[1081]: Preferred CPU model SandyBridge
not allowed by hypervisor; closest supported model will be used
Nov 11 11:28:13 revenger libvirtd[1081]: internal error: Cannot find
suitable CPU model for given data


# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 42
model name      : Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz
stepping        : 7
microcode       : 0x28
cpu MHz         : 809.789
cache size      : 6144 KB
physical id     : 0
siblings        : 8
core id         : 0
cpu cores       : 4
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx
est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt
tsc_deadline_timer aes xsave avx lahf_lm ida arat epb xsaveopt pln pts
dtherm tpr_shadow vnmi flexpriority ept vpid
bogomips        : 4385.36
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:



-- 
Jarle Aase                      email: jarle@jgaa.com
Author of Free Software.        http://www.jgaa.com

War FTP Daemon:                 http://www.warftp.org
Other free software:            http://products.jgaa.com

NB: If you reply to this message, please include all relevant
information from the conversation in your reply. Thanks.
<<< no need to argue - just kill'em all! >>>


Reply to: