lundi 23 janvier 2012

Unpacking Boxes...

For the impatient people running Fedora 16 but who still want to get an aperçu of Boxes, today's your lucky day! I set up a preview repository with all the needed package to install Boxes on Fedora 16.
If you want to try it, download this file to /etc/yum.repos.d and then run  
yum install gnome-boxes && yum update



To go back to your previous setup, you can either use the convenient yum history, or remove /etc/yum.repos.d/gnome-boxes-preview.repo and use
yum remove libvirt-glib && yum distro-sync

Keep in mind that this is a new application still in heavy development, so you're likely to find bugs and missing features. But I'm sure you will enjoy it nonetheless :)

Feel free to join us in #boxes on irc.gnome.org if you have any issues, or if you just want to chat with us.


6 commentaires:

Anonyme a dit…

Fedora 16 x86_64:

Error: PRotected multilib versions: glib2-2.31.10-1.fc16.teuf.x86_64 != glib2-2.30.2-1.fc16.i686

Anonyme a dit…

Are you seriously using the "Mio" unit for RAM and disk? I suspect that is tech speak that alienates users. MiB/GiB would be a far better choice if you want something that will be actually understood by users...

Christophe a dit…

Anonymous #1, this is a known issue, this happens because on 64 bit machines, only the 64 bit repo is accessible (not sure why yet...), so yum cannot update the 32 bit version of glib, and having 2 different glib version in 32 and 64 bit is forbidden.

Anonymous #2, Mio is the French translation for MiB, so all will be good if you use an English locale :)

Christophe a dit…

The multilib error should now be fixed, hardlinks to the 32 bit versions were missing from the x86_64 directory.

Jeff Fortin a dit…

When trying to analyze an ISO image:


Boxes-WARNING **: wizard.vala:136: Failed to create domain: internal error Process exited while reading console log output: qemu-system-x86_64: -spice port=5901,addr=127.0.0.1,disable-ticketing: there is no option group "spice"
spice is not supported by this qemu build.

Christophe a dit…

Jeff, maybe the kvm_intel module isn't loaded on your system.