After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 784573 - Switch to host-model as default CPU with libvirt 3.2+
Switch to host-model as default CPU with libvirt 3.2+
Status: RESOLVED OBSOLETE
Product: gnome-boxes
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-07-05 19:26 UTC by Adam Williamson
Modified: 2018-01-11 10:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Adam Williamson 2017-07-05 19:26:12 UTC 
src/vm-configurator.vala has this note:

        // Ideally we should be using 'host-model' but there is currently issues with that:
        // https://bugzilla.redhat.com/show_bug.cgi?id=870071

#870071 was closed in March, with libvirt 3.2:

https://bugzilla.redhat.com/show_bug.cgi?id=870071#c36

So should Boxes now be changed to use host-model, at least when running on libvirt 3.2 or higher? Note that I have filed a corresponding bug for virt-manager / virt-install: https://bugzilla.redhat.com/show_bug.cgi?id=1468016
Comment 1 Eduardo Habkost 2017-07-05 21:01:55 UTC 
I assume live-migrating a VM created by GNOME Boxes is not a common use case.  When no live-migration is required I recommend using "host-passthrough" as the default.
Comment 2 GNOME Infrastructure Team 2018-01-11 10:55:15 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-boxes/issues/150.