Description of problem: sudo virt-install --connect qemu:///system \ --name=swanfedora26base \ --os-variant fedora26 \ --vcpus=1 \ --memory 1024 \ --nographics \ --disk size=8,cache=writeback,path=/home/libreswan/pool/swanfedora26base.qcow2 \ --network=network:swandefault,model=virtio \ --rng type=random,device=/dev/random \ --location=/home/libreswan/pool/Fedora-Server-dvd-x86_64-26-1.5.iso \ --initrd-inject=testing/libvirt/fedora26.ks \ --extra-args="swanname=swanfedora26base ks=file:/fedora26.ks console=tty0 console=ttyS0,115200" \ --noreboot Starting install... Retrieving file .treeinfo... | 1.6 kB 00:00:00 Retrieving file vmlinuz... | 7.0 MB 00:00:00 Retrieving file initrd.img... | 57 MB 00:00:00 Allocating 'swanfedora26base.qcow2' | 8.0 GB 00:00:00 ERROR internal error: process exited while connecting to monitor: 2018-02-14T17:48:28.610786Z qemu-system-x86_64: can't apply global Broadwell-noTSX-x86_64-cpu.spec-ctrl=on: Property '.spec-ctrl' not found Version-Release number of selected component (if applicable): $ rpm -q virt-install qemu-system-x86 virt-install-1.5.0-1.fc27.noarch qemu-system-x86-2.11.0-4.fc27.x86_64 How reproducible: 100% Also happens when f27 is the image
Thanks for the report. Can you provide your libvirt-daemon version, and virt-install --debug output when reproducing? You might be able to work around it by adding --cpu host-passthrough or maybe --cpu qemu64 but it's just a guess
$ rpm -qa libvirt-daemon virt-install libvirt-daemon-4.0.0-2.fc27.x86_64 virt-install-1.5.0-1.fc27.noarch
Created attachment 1396552 [details] Log from virt-install --debug ...
--cpu host-passthrough gets past the problem; I'll see if it has any visible affect on crypto et.al. http://blog.wikichoon.com/2016/01/using-cpu-host-passthrough-with-virt.html --cpu qemu64 trips up with 'the CPU is incompatible with host CPU: Host CPU does not provide required features: svm'; according to the internet this is because my host is an Intel(R) Core(TM) i5-6400T CPU @ 2.20GHz
Bizarrely, this then fails: virsh --connect qemu:///system define /home/libreswan/pool/ad.east.xml.tmp where the disk was copied from the vm above. The resulting VM has not network interfaces. I've attached the xml, should I suspect it is because an option needs to be added to that?
Created attachment 1396781 [details] xml used to create a domain that should have, but is missing, 3 networks
(In reply to cagney from comment #5) This is unrelated, please ignore. With the workaround, I've got things working. > Bizarrely, this then fails: > virsh --connect qemu:///system define /home/libreswan/pool/ad.east.xml.tmp > where the disk was copied from the vm above. > > The resulting VM has not network interfaces. > > I've attached the xml, should I suspect it is because an option needs to be > added to that?
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.