How to Get Boxes to Work?

asked 2015-06-13 06:40:41 -0500

Phx_01 gravatar image

updated 2015-06-23 23:30:28 -0500

mether gravatar image

According to its "advertisement", Boxes should be dead-simple to use. However, none of my virtual machines I try to put in are even starting. All I receive is Failed to start'<virtual_machine_name_here>'. Due to some issues I had in the past, I even reinstalled Fedora from scratch but the issue remains.

Looking at the log (journalctl -f) when trying a Windows 7 box, it provides a decent amount of lines with three of them colored in red:

Jun 13 13:27:28 <computer_name> libvirtd[3169]: unable to set security context 'system_u:object_r:virt_content_t:s0' on '<path_to_iso_file>': Operation not permitted
Jun 13 13:27:28 <computer_name> libvirtd[3169]: Failed to open file '/sys/class/net/tap0/operstate': No such file or directory
Jun 13 13:27:28 <computer_name> libvirtd[3169]: unable to read: /sys/class/net/tap0/operstate: No such file or directory

I also tried with a Fedora 22 and Ubuntu 14 ISO and the output is similar. On the contrary, I can run VirtualBox with the very same ISOs without an issue.

edit retag flag offensive close merge delete



Great... Putting SELinux out of its misery (putting it to permissive for now) solved the issue. However, I hear already all security experts reading this, that this is the wrong approach. Though I must say that, while having a security system is great, having one which so devastatingly interferes with user interactions that it requires an admin to deal with it every time you create a new file (metaphorically speaking), it is very counter-productive as well. I still hope that there is a real solution out there.

Phx_01 gravatar imagePhx_01 ( 2015-06-13 07:04:36 -0500 )edit

The default SELinux settings for Fedora should work with most of the popular apps. If you discover a problem between SELinux and a package, it's a bug and you should submit it for everyone's help. Ideally a workstation is maintained by an administrator who understands SELinux (see man selinux) or the fedora docs. In a personal system, you can disable it if you really want too (it wouldn't be less secure then a non-rbac distro). If you wanted to play around with an alternative, you can recompile a kernel with grsecurity, which has a "learning mode" for RBAC I believe.

bthomas gravatar imagebthomas ( 2015-06-13 21:51:11 -0500 )edit

Coming from Mac OS X, I am still fairly new to the deep mechanisms of Linux. Due to that, I am possibly also spoiled. Though admittedly Mac OS X is quite open concerning local security. However, there you get on-screen warnings, which you can address (even if it means that you need admin privileges). For various issues, I also receive an SELinux warning notification where I get some information and a suggestion of two commands to run to overcome this problem. However, with Boxes nothing shows up (except well hidden in the logs). I will have a look into the man page you mentioned.

Phx_01 gravatar imagePhx_01 ( 2015-06-14 09:24:45 -0500 )edit

In terms of writing bug reports, I would love to, but as asked in one of my other questions, I have no clue where to officially write bug reports. So, I need to take issues as they are and try to work around them on my system as good as possible with my limited knowledge.

Phx_01 gravatar imagePhx_01 ( 2015-06-14 09:39:19 -0500 )edit

Hi @Phx_01 ,

Fedora bugs are tracked at .

Please see to get more info or reporting/tracking bugs in fedora.

Natarajan gravatar imageNatarajan ( 2015-06-14 12:12:03 -0500 )edit