On Wed, Jul 03, 2013 at 04:51:30PM +0200, Sandro Bonazzola wrote:
> Il 03/07/2013 16:40, Sandro Bonazzola ha scritto:
> > Hi,
> > I'm trying to run latest vdsm master on RHEL-6.4.
> > I've built the rpms against livirt-1.10
> >
> > I'm creating a VM using cpu family = 'Intel Westmere Family'
> >
> > <cpu match="exact">
> > <model>qemu64</model>
> > <feature name="svm" policy="disable"/>
> > </cpu>
> >
> > Thread-40::DEBUG::2013-07-03
> > 15:47:47,150::libvirtconnection::136::vds::(wrapper) Unknown
> > libvirterror: ecode: 1 edom: 31 level: 2 message: internal error Cannot
> > find suitable CPU model for given data
> > Thread-40::DEBUG::2013-07-03
> > 15:47:47,150::vm::2003::vm.Vm::(_startUnderlyingVm)
> > vmId=`9deae1fb-e0c5-4362-8f3c-657f39893b8b`::_ongoingCreations released
> > Thread-40::ERROR::2013-07-03
> > 15:47:47,150::vm::2029::vm.Vm::(_startUnderlyingVm)
> > vmId=`9deae1fb-e0c5-4362-8f3c-657f39893b8b`::The vm start process failed
> > Traceback (most recent call last):
> > File "/usr/share/vdsm/vm.py", line 1989, in _startUnderlyingVm
> > self._run()
> > File "/usr/share/vdsm/vm.py", line 2862, in _run
> > self._connection.createXML(domxml, flags),
> > File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py",
> > line 112, in wrapper
> > ret = f(*args, **kwargs)
> > File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2848, in
> > createXML
> > if ret is None:raise libvirtError('virDomainCreateXML() failed',
> > conn=self)
> > libvirtError: internal error Cannot find suitable CPU model for given data
> >
> >
> > Is it required a more updated qemu? Is it a vdsm or a livirt bug?
>
>
> It seems that qemu knows qemu64 as cpu
>
> # /usr/libexec/qemu-kvm --cpu ?
And what does `virsh -r capabilities` report?
Is there something interesting in /var/log/libvirtd.log?
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list