Marko Weber | 8000
2017-Jul-19 09:45 UTC
[libvirt-users] creating new vm with virt-manager, existing disk failure
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?
lscpu:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 12
On-line CPU(s) list: 0-11
Thread(s) per core: 2
Core(s) per socket: 6
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 79
Model name: Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz
Stepping: 1
CPU MHz: 2974.658
CPU max MHz: 4000.0000
CPU min MHz: 1200.0000
BogoMIPS: 7191.87
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 15360K
NUMA node0 CPU(s): 0-11
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 pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good
nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor
ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1
sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand
lahf_lm abm 3dnowprefetch epb cat_l3 cdp_l3 intel_pt tpr_shadow vnmi
flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms
invpcid rtm cqm rdt_a rdseed adx smap xsaveopt cqm_llc cqm_occup_llc
cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts
kind regards
marko
--
zbfmail - Mittendrin statt nur Datei!
Pavel Hrdina
2017-Jul-19 12:01 UTC
Re: [libvirt-users] creating new vm with virt-manager, existing disk failure
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
Marko Weber | 8000
2017-Jul-19 16:07 UTC
Re: [libvirt-users] creating new vm with virt-manager, existing disk failure
Am 2017-07-19 14:01, schrieb Pavel Hrdina:> 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.Yes, i think its a great idea. Can u do this? kind regards marko> > Pavel
Marko Weber
2017-Aug-03 11:08 UTC
Re: [libvirt-users] creating new vm with virt-manager, existing disk failure
Hi pavel, Am 2017-07-19 14:01, schrieb Pavel Hrdina:> 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. > > Pavelcan you tell me if this problem is solved in the time? We need this way to migrate machines. Or is it not planned to fix this bug? kind regards marko
Possibly Parallel Threads
- creating new vm with virt-manager, existing disk failure
- Re: error: internal error: missing backend for pool type 11 (zfs)
- libvirt and virt-manager - Unable to complete install: 'internal error: unsupported input bus usb'
- Libvirt 3.0 machine start fails on LVM
- Re: Fedora 19/20 new install :Unable to create vcpu cgroup