On Fri, Feb 16, 2018 at 04:28:05PM +0100, Jiri Denemark wrote: > On Fri, Feb 16, 2018 at 09:39:17 -0500, John Ferlan wrote: > ... > > Here's the command it uses: > > > > /usr/bin/virt-install --hvm --accelerate --name 'avocado-vt-vm1' \ > > --memory=1024 --vcpu=2 --import --vnc --os-variant fedora25 \ > > --serial pty --memballoon model=virtio --disk \ > > path=/var/lib/avocado/data/avocado-vt/images/jeos-25-64.qcow2,bus=virtio,size=10,format=qcow2 > > \ > > --network=bridge=virbr0,model=virtio,mac=52:54:00:f9:fa:fb \ > > --noautoconsole > > > > Adding the --cpu host-model does allow the creation to complete. > > Yeah, virt-install/virt-manager defaults for guest CPU configuration are > completely wrong (and some other CPU options too). I discussed it with > Pavel Hrdina. He knew about the issue and said he'd work on fixing it. > Is there a bugzilla for this, Pavel? There is a bugzilla to track the CPU issue: <https://bugzilla.redhat.com/show_bug.cgi?id=1055002>. Pavel
Attachment:
signature.asc
Description: PGP signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
