Ask Your Question

knel's profile - activity

2019-04-01 21:15:46 -0600 received badge  Famous Question (source)
2019-04-01 21:15:46 -0600 received badge  Notable Question (source)
2019-04-01 21:15:46 -0600 received badge  Popular Question (source)
2018-11-30 07:30:27 -0600 received badge  Famous Question (source)
2018-11-30 07:30:27 -0600 received badge  Notable Question (source)
2018-11-30 07:30:27 -0600 received badge  Popular Question (source)
2018-10-04 08:26:41 -0600 received badge  Famous Question (source)
2018-07-10 10:16:37 -0600 received badge  Popular Question (source)
2018-05-18 16:49:38 -0600 received badge  Notable Question (source)
2017-06-26 20:01:23 -0600 received badge  Popular Question (source)
2016-06-09 16:00:23 -0600 commented answer Move gnome-boxes images to external usb drive?

Ok, seems this will work. Will try when I get the external.

2016-06-06 14:19:10 -0600 received badge  Nice Question (source)
2016-06-04 18:45:28 -0600 asked a question Move gnome-boxes images to external usb drive?

I don't have much space left on my home partition, yet want to create more virtual partitions via gnome-boxes, each of which requires about 20 gb hard drive space as a minimum, I believe. One solution that comes to mind is to move my images to an external drive. However, I don't know what this would entail exactly. I know the images are stored under the .local directory, so how could I move the images, config, and xml files to an external usb in a way that the gnome-boxes app would recognize?

I see this link is similar, but it concerns moving a boxes virtual image to another computer and basically copying everything setting for setting, directory for directory, on the other computer. How do I move a boxes image within the directory space of one computer?

2016-04-08 16:16:21 -0600 received badge  Scholar (source)
2016-04-07 19:35:45 -0600 commented answer virbr0 interface up and disappeared

so if libvirtd is enabled, it starts on boot, but if libvirtd.socket is enabled, i have to start libvirtd on demand?

2016-04-07 17:46:17 -0600 commented answer virbr0 interface up and disappeared

what is libvirtd.socket exactly? should i enable that as well?

2016-04-07 17:13:15 -0600 commented answer virbr0 interface up and disappeared

libvirtd.socket is inactive (dead)

2016-04-06 17:21:49 -0600 commented answer virbr0 interface up and disappeared

I see. Why didn't I need to do this before? I was using Boxes for some time without incident, without configuring anything in particular (aside from the install, of course).

2016-04-05 15:52:51 -0600 commented question virbr0 interface up and disappeared

I had to install libvirt during my initial amateur fiddling. I had gnome boxes working previously so I was confused that wouldn't be installed. How could that be?

On reboot, libvirtd.service is inactive. I have to systemctl restart it to get the virbr0 working. What do I change to get it auto initialized?

2016-04-05 02:25:08 -0600 asked a question virbr0 interface up and disappeared

Everything associated with a virtual machine, including the virtual network interface, came packaged with my install, and I was able to get something up and running in Gnome Boxes fairly easily. All of a sudden, I cannot start up my install. All of the usual ways to list network interfaces show no bridge interface, not virbr0, br0, etc.

Looking through the journal logs, the most relevant bit I find is this: internal error: /usr/libexec/qemu-bridge-helper --br=virbr0 --fd=22: failed to communicate with bridge helper: Transport endpoint is not connected stderr=failed to get mtu of bridge `virbr0': No such device

I have tried a few simple things via a google search, but nothing that has helped. What do I do here?

2016-03-22 09:35:50 -0600 received badge  Good Question (source)
2016-03-22 01:27:11 -0600 received badge  Nice Question (source)
2016-03-21 19:14:55 -0600 received badge  Editor (source)
2016-03-19 21:14:31 -0600 received badge  Supporter (source)
2016-03-15 18:41:24 -0600 commented question Created signing key in order to run VirtualBox on an UEFI machine, any security risks?

thanks, I used the same instructions in the guide at the eguilor domain in the ask.fedora question you linked. I just wondered, is there anything more I need to know about creating my own keys and signing a kernel module? It just seems like an advanced action requiring some caution.

2016-03-15 13:03:53 -0600 commented question Created signing key in order to run VirtualBox on an UEFI machine, any security risks?

yeah, I have secure boot activated. Why would the default option be that I don't?

2016-03-15 09:08:43 -0600 received badge  Student (source)
2016-03-15 03:04:43 -0600 commented answer Created signing key in order to run VirtualBox on an UEFI machine, any security risks?

eh, I'd installed several of the peripheral virtualbox packages, to no avail. This worked, it just seemed like something I'd want to understand better instead of doing the usual parroting of command line instructions. Ummm. Are you saying I should disable UEFI? Your comment is hard to decipher somewhat, sorry.

2016-03-15 01:04:45 -0600 asked a question Optical drive access in Gnome Boxes

I have a Windows 10 installation in Gnome Boxes and I want to install software from a dvd. How do I give gnome boxes access to the optical drive? Under the devices tab in system properties, the cd/dvd option seems to want an .iso file. When I first opened the contextual menu for the cd/dvd option, the .iso file I used to install windows was selected. Once I de-selected it and tried to choose the cd/dvd containing software, I was not able to. Instead, the contextual menu keeps pushing me into sub-menus, as if only an .iso file works for the "cd/dvd" selection.

edit (Mar 21 2016): I still have not been able to get access to the optical drive (nor can I get usb passthru to work for that matter), but the solution that worked for now was to burn the dvd contents to an .iso file, and use that.

2016-03-14 20:25:24 -0600 asked a question Created signing key in order to run VirtualBox on an UEFI machine, any security risks?

I followed this tutorial to create my own signing key so I could run VirtualBox on a computer with a UEFI boot. Are there any security risks associated with creating my own signing key? I don't have an expert-level understanding of security concepts but it seems like creating my own key is something that could have consequences, so forgive me if this is a silly question.