GNOME Bugzilla – Bug 679238
Unable to create a VM with any ISO file on Fedora 17
Last modified: 2016-03-31 14:00:28 UTC
I wish I could actually try out your neat piece of software. jeff@krom:~$ gnome-boxes --checks The CPU is capable of virtualization: yes The KVM module is loaded: yes jeff@krom:~$ uname -r 3.4.4-3.fc17.i686.PAE [root@krom jeff]# lsmod |grep kvm kvm_intel 126459 0 kvm 352546 1 kvm_intel jeff@krom:~$ gnome-boxes (gnome-boxes:8396): Boxes-WARNING **: wizard.vala:154: Unable to start domain: internal error Process exited while reading console log output: char device redirected to /dev/pts/2 No accelerator found! KVM not supported for this target ---------- The host is Fedora 17 32-bits PAE. This error occurs when trying to open /home/jeff/Téléchargements/ubuntu-12.04-desktop-i386.iso I also tried with /home/jeff/Fedora-17-i686-Live-XFCE.iso "libvirtd" was not running before this. Doing a killall libvirtd as root and trying again does not work either.
What version of the various packages? The output of rpm -qa 'libvirt*' gnome-boxes would be helpful. Is selinux enabled? Does it report any failure?
SELinux is disabled, I'm not a masoschist ;) jeff@krom:~$ rpm -qa 'libvirt*' gnome-boxes libvirt-daemon-config-nwfilter-0.9.11.4-3.fc17.i686 libvirt-daemon-0.9.11.4-3.fc17.i686 libvirt-docs-0.9.11.4-3.fc17.i686 libvirt-gobject-devel-0.0.8-1.fc17.i686 libvirt-python-0.9.11.4-3.fc17.i686 libvirt-glib-0.0.8-1.fc17.i686 libvirt-daemon-config-network-0.9.11.4-3.fc17.i686 libvirt-gobject-0.0.8-1.fc17.i686 libvirt-daemon-kvm-0.9.11.4-3.fc17.i686 libvirt-glib-devel-0.0.8-1.fc17.i686 libvirt-gconfig-devel-0.0.8-1.fc17.i686 libvirt-devel-0.9.11.4-3.fc17.i686 libvirt-gconfig-0.0.8-1.fc17.i686 gnome-boxes-3.4.3-1.fc17.i686 libvirt-client-0.9.11.4-3.fc17.i686
I also tried with the "libvirt" package installed, no luck.
VM creation in 3.4.x requires x86_64 with KVM (Will be fixed in 3.6: bug#674209). BTW, I didn't know of 32-bit systems out there with VT supported. Perhaps you installed 32-bit Fedora on 64-bit machine?
I always run 32 bit versions of distros even though I have a modern processor (Intel Core i7-2640M), for a couple of reasons: - I don't truly see the point of 64 bits for casual use, and I can run a 32-bits PAE kernel to address my entire RAM - dogfooding for 32 bits users. I find bugs that developers don't always experience. For virtualization... If VirtualBox runs fine on this (or even on older CPUs like a Pentium 4), why couldn't gnome-boxes?
(In reply to comment #5) > For virtualization... If VirtualBox runs fine on this (or even on older CPUs > like a Pentium 4), why couldn't gnome-boxes? Because of a bug which Zeeshan mentioned in comment #4 ... There are indeed few testers of x86 builds these days.
Yes, what I mean is, in theory nothing prevents it (except bugs, which is fine), right?
(In reply to comment #5) > > For virtualization... If VirtualBox runs fine on this (or even on older CPUs > like a Pentium 4), why couldn't gnome-boxes? Depends on your definition of 'runs fine'. Seeing that modern OSs have performance issues on my kvm-enabled multicore/multithreaded machine with many GIGs of RAM, I seriously doubt VirtualBox can do a very good job on a Pentium 4 host without any KVM. Besides your usecase seems pretty different from actually using a very old machine. You will be able to create and run VMs on your machine in 3.6, just not in 3.4 unfortunately. *** This bug has been marked as a duplicate of bug 674209 ***