(solved) Kvm virt-manager vm run error

I’ve tried installing virt-manager on 2 machines.

machine 1 worked fine using these instructions:
https://wiki.manjaro.org/index.php?title=Virt-manager

machine 2, I had first tried the below instructions

that didnt work so I tried the instructions for machine 1 (found those instructions later).

Following the same process as per instructions, but now I get the following error when I try to run the machine.

Perhaps it was one of the commands from the first howto?

Please advise

Thanks

------ error below on vm run ------

Unable to complete install: ‘internal error: qemu unexpectedly closed the monitor: .0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -spice port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on
2018-02-09T17:46:37.230962Z qemu-system-x86_64: can’t apply global Broadwell-noTSX-x86_64-cpu.spec-ctrl=on: Property ‘.spec-ctrl’ not found’

Traceback (most recent call last):
File “/usr/share/virt-manager/virtManager/asyncjob.py”, line 89, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File “/usr/share/virt-manager/virtManager/create.py”, line 2545, in _do_async_install
guest.start_install(meter=meter)
File “/usr/share/virt-manager/virtinst/guest.py”, line 498, in start_install
doboot, transient)
File “/usr/share/virt-manager/virtinst/guest.py”, line 434, in _create_guest
domain = self.conn.createXML(install_xml or final_xml, 0)
File “/usr/lib/python2.7/site-packages/libvirt.py”, line 3659, in createXML
if ret is None:raise libvirtError(‘virDomainCreateXML() failed’, conn=self)
libvirtError: internal error: qemu unexpectedly closed the monitor: .0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -spice port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on
2018-02-09T17:46:37.230962Z qemu-system-x86_64: can’t apply global Broadwell-noTSX-x86_64-cpu.spec-ctrl=on: Property ‘.spec-ctrl’ not found

Which kernel are you running?
I’m on 4.15 and also wasn’t able to run a vm with the updated guest microcode.

[adminuser@adminuser-pc ~]$ uname -r
4.14.16-1-MANJARO

solution i found was to do the following:

  1. add groups to user. kvm and libvirt
  2. on cpu of vm, change this to ‘copy host configuration’.

I don’t think (1) was the solution although I had done this.

It all started working when I did (2).

1 Like

Good it’s working, but I thought you wanted the patched ibrs cpu’s running. I still didn’t get those working.

Thanks,
I’m no Manjaro user (arch), but I’d like to report I have fixed this issue setting CPU default to “Hypervisor default” and adding my user to both the groups “kvm” and "libvirt"
Thanks again, bye!
-------
ceres-c

what does that do and why is it needed?

my system seems to be working fine now.

also got file shares working between host/win guest by adding thunar shares.

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by Bytemark