Created attachment 914452 [details] screenshot of warning Description of problem: Can gnome-boxes to run a virtual machine on the processor does not support VT extensions? $ rpm -q gnome-boxes gnome-boxes-3.12.2-1.fc20.i686 # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz stepping : 13 microcode : 0xa4 cpu MHz : 1200.000 cache size : 1024 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fdiv_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes 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 nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm bogomips : 3990.24 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz stepping : 13 microcode : 0xa4 cpu MHz : 1200.000 cache size : 1024 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fdiv_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes 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 nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm bogomips : 3990.24 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management:
Created attachment 914453 [details] screenshot of problem
(In reply to Mikhail from comment #1) > Created attachment 914453 [details] > screenshot of problem That screenshot doesn't say anything about VT. If you created the VM when VT were available and then trying to launch it when they are not, its likely going to fail. If not, there could be many reasons for this failue. For starts could you provide output of `gnome-boxes --checks` and console log when you reproduce the issue while enabling debug `G_MESSAGES_DEBUG=Boxes gnome-boxes` ?
$ gnome-boxes --checks • The CPU is capable of virtualization: no • The KVM module is loaded: no • Libvirt KVM guest available: no • Boxes storage pool available: yes • The SELinux context is default: yes Report bugs to <https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-boxes>. Boxes home page: <http://live.gnome.org/Boxes>. [mikhail@localhost ~]$ G_MESSAGES_DEBUG=Boxes gnome-boxes (gnome-boxes:3291): Boxes-DEBUG: libvirt-system-importer.vala:45: Connected to system libvirt, now fetching domains.. (gnome-boxes:3291): Boxes-DEBUG: libvirt-system-importer.vala:49: Fetched 0 domains from system libvirt. (gnome-boxes:3291): Boxes-DEBUG: wizard-source.vala:250: No boxes to import (gnome-boxes:3291): Boxes-DEBUG: util-app.vala:256: check_cpu_vt_capability: no (gnome-boxes:3291): Boxes-DEBUG: util-app.vala:276: check_module_kvm_loaded: no (gnome-boxes:3291): Boxes-DEBUG: libvirt-machine.vala:111: new libvirt machine: boxes-unknown (gnome-boxes:3291): Boxes-DEBUG: machine.vala:61: State of 'Windows 7 Ultim x86 Ru nBook IE11 by OVGorskiy 11' changed to BOXES_MACHINE_MACHINE_STATE_STOPPED (gnome-boxes:3291): Boxes-DEBUG: machine.vala:579: connect display failed: Unable to start domain: unsupported configuration: CPU mode 'host-passthrough' is only supported with kvm
Ouch, taking this upstream: https://bugzilla.gnome.org/show_bug.cgi?id=732680
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.