[libvirt-users] creating new vm with virt-manager, existing disk failure

Pavel Hrdina phrdina at redhat.com
Wed Jul 19 12:01:11 UTC 2017


On Wed, Jul 19, 2017 at 11:45:36AM +0200, Marko Weber | 8000 wrote:
> 
> hello,
> i rsynced a kvm vm from one host to another.
> i start virt-manager and tell virt-manager to use an existing disk.
> i set cpu to haswell that is on the host.
> 
> configure before start is set, and i start "begin installation".
> I get this output by virt-manager:
> 
> Unable to complete install: 'internal error: process exited while 
> connecting to monitor: 2017-07-19T09:27:10.861928Z qemu-system-x86_64: 
> can't apply global Haswell-x86_64-cpu.cmt=on: Property '.cmt' not found'
> 
> Traceback (most recent call last):
>    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 88, in 
> cb_wrapper
>      callback(asyncjob, *args, **kwargs)
>    File "/usr/share/virt-manager/virtManager/create.py", line 2288, in 
> _do_async_install
>      guest.start_install(meter=meter)
>    File "/usr/share/virt-manager/virtinst/guest.py", line 477, in 
> start_install
>      doboot, transient)
>    File "/usr/share/virt-manager/virtinst/guest.py", line 405, in 
> _create_guest
>      self.domain.create()
>    File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1062, in 
> create
>      if ret == -1: raise libvirtError ('virDomainCreate() failed', 
> dom=self)
> libvirtError: internal error: process exited while connecting to 
> monitor: 2017-07-19T09:27:10.861928Z qemu-system-x86_64: can't apply 
> global Haswell-x86_64-cpu.cmt=on: Property '.cmt' not found
> 
> 
> 
> 
> try to set it to another cpu and clicking start, i get this:
> 
> Unable to complete install: 'Domain has already been started!'
> 
> Traceback (most recent call last):
>    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 88, in 
> cb_wrapper
>      callback(asyncjob, *args, **kwargs)
>    File "/usr/share/virt-manager/virtManager/create.py", line 2288, in 
> _do_async_install
>      guest.start_install(meter=meter)
>    File "/usr/share/virt-manager/virtinst/guest.py", line 455, in 
> start_install
>      raise RuntimeError(_("Domain has already been started!"))
> RuntimeError: Domain has already been started!
> 
> 
> 
> how do i stop the already runing vm? virsh list dont show the vm
> and why do i get the error on haswell?

Hi, this is actually a bug in virt-manager which was fixed in upstream
by these commits:

    2099a1946e22b62d31b954dc3e7b813404c2d019
    93085d2b9d4a3dd6cbb9edfeae9b6cefee9419c1
    8181e8609867fe6ed101e48212d42a1c38373539

To work-around this issue cancel the installation and start it again.
There is no official release of virt-manager with that fix included, we
should probably make the release.

Pavel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20170719/bf6d54c6/attachment.sig>


More information about the libvirt-users mailing list