I know, there's a similar question with the problem manifesting in a similar way but using virsh didn't work for me, it refused to delete the problematic VM. I tried deleting all the configs to stop gnome-boxes from trying to load a faulty VM list but it didn't work. I deleted everything named gnome-boxes* in my home directory and apt purgeing it then reinstalling, the problem persisted.

I recently followed the steps outlined in [this answer](https://unix.stackexchange.com/a/649326/646494) to enable SSH port forwarding in GNOME Boxes. However, after applying the modifications, I encountered an issue when trying to SSH into the guest. Here's a detailed breakdown of what I did: **Steps I Followed:** 1. I edited the XML configuration of the VM using virsh edit boxes-unknown to modify the networking and add port forwarding for SSH. - I changed the root element of the domain XML to:

- I removed the existing `` section:

- Then, I added the following QEMU command to forward port 2222 on the host to port 22 on the guest:

2. After making these changes, I rebooted the guest using the following command:

virsh reboot boxes-unknown

3. I then attempted to SSH into the guest with:

ssh -vvv -p 2222 user@localhost

**Problem:** When trying to SSH, I receive the following output:

OpenSSH_9.2p1 Debian-2+deb12u3, OpenSSL 3.0.14 4 Jun 2024
debug1: Reading configuration data /home/xxx/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/xxx/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/xxx/.ssh/known_hosts2'
debug2: resolving "localhost" port 2222
debug3: resolve_host: lookup localhost:2222
debug3: ssh_connect_direct: entering
debug1: Connecting to localhost [::1] port 2222.
debug3: set_sock_tos: set socket 3 IPV6_TCLASS 0x10
debug1: connect to address ::1 port 2222: Connection refused
debug1: Connecting to localhost [127.0.0.1] port 2222.
debug3: set_sock_tos: set socket 3 IP_TOS 0x10
debug1: Connection established.
debug1: identity file /home/xxx/.ssh/id_rsa type 0
debug1: identity file /home/xxx/.ssh/id_rsa-cert type -1
debug1: identity file /home/xxx/.ssh/id_ecdsa type -1
debug1: identity file /home/xxx/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/xxx/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/xxx/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/xxx/.ssh/id_ed25519 type -1
debug1: identity file /home/xxx/.ssh/id_ed25519-cert type -1
debug1: identity file /home/xxx/.ssh/id_ed25519_sk type -1
debug1: identity file /home/xxx/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/xxx/.ssh/id_xmss type -1
debug1: identity file /home/xxx/.ssh/id_xmss-cert type -1
debug1: identity file /home/xxx/.ssh/id_dsa type -1
debug1: identity file /home/xxx/.ssh/id_dsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_9.2p1 Debian-2+deb12u3
kex_exchange_identification: read: Connection reset by peer
Connection reset by 127.0.0.1 port 2222

The guest is no longer accessible through GNOME Boxes, and SSH fails with the "Connection reset by peer" error. **Additional Information:** - Port 2222 is not in use by any other service on the host (I verified this with sudo lsof -i:2222). - The guest's SSH service is running, and it's configured to listen on port 22. - I've reviewed the "Troubleshooting Log" under the "System" tab in the guest "Properties" in GNOME Boxes. Following is the last line on the log:

2024-09-16T08:56:02.478433Z qemu-system-x86_64: Slirp: Failed to send packet, ret: -1

**Question:** Has anyone encountered similar issues with SSH port forwarding in GNOME Boxes or using QEMU’s hostfwd option? Any advice on how to resolve this issue or recover access to the guest would be greatly appreciated. Thanks in advance for your help!

I am a long time linux user (ubuntu-budgie 24.04) trying out VMs recently. I followed this recipe to create a QEMU vm running GhostBSD 24.04.2. It works great from the command line using qemu-system-x86_64. How do I get this vm to show up in gnome-boxes?

I am trying to make my laptop camera accessible by a guest system on it. With the guest system not running, I open it in virt-manager, go to "Show virtual hardware details" → "Add Hardware" → "USB Host Device". Here I choose my camera (001:002 Chicony Electronics Co., Ltd HD User Facing) and click "Finish". The procedure seems to be the same as described in the KVM documentation . This results in the following stanza added to the XML config of the guest machine.

-xml

This looks correct according to the Red Hat's manual on attaching and updating a device with virsh . However, I cannot run the guest with it because qemu is denied permission.

Error starting domain: internal error: qemu unexpectedly closed the monitor: 2022-03-13T05:27:57.240470Z qemu-system-x86_64: -device {"driver":"usb-host","hostdevice":"/dev/bus/usb/001/002","id":"hostdev0","bus":"usb.0","port":"6"}: failed to open /dev/bus/usb/001/002: Permission denied

Traceback (most recent call last):
  File "/gnu/store/r9jxh3pv020qa05pza3jiky2vppn68mx-virt-manager-3.2.0/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/gnu/store/r9jxh3pv020qa05pza3jiky2vppn68mx-virt-manager-3.2.0/share/virt-manager/virtManager/asyncjob.py", line 101, in tmpcb
    callback(*args, **kwargs)
  File "/gnu/store/r9jxh3pv020qa05pza3jiky2vppn68mx-virt-manager-3.2.0/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn
    ret = fn(self, *args, **kwargs)
  File "/gnu/store/r9jxh3pv020qa05pza3jiky2vppn68mx-virt-manager-3.2.0/share/virt-manager/virtManager/object/domain.py", line 1329, in startup
    self._backend.create()
  File "/gnu/store/7c16ipd35j0fdl6mrjbg3v9zsn8iivi0-python-libvirt-7.9.0/lib/python3.9/site-packages/libvirt.py", line 1353, in create
    raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor: 2022-03-13T05:27:57.240470Z qemu-system-x86_64: -device {"driver":"usb-host","hostdevice":"/dev/bus/usb/001/002","id":"hostdev0","bus":"usb.0","port":"6"}: failed to open /dev/bus/usb/001/002: Permission denied

The device that it is trying to access is correct:

$ lsusb -s 001:002
Bus 001 Device 002: ID 04f2:b6dd Chicony Electronics Co., Ltd HD User Facing

The device is owned by root. It seems that read access is not enough for qemu.

$ LC_ALL=C ls -l /dev/bus/usb/001/002
crw-rw-r-- 1 root root 189, 1 Mar 13 06:15 /dev/bus/usb/001/002

My guess is that the device is owned by root for a good security reason. Similarly, virt-manager does not prompt me to run qemu as root. How do I safely manage permissions to allow the guest access the camera? ---------- Another approach, which I initially tried, was to use GNOME Boxes to enable access to the camera device in the respective guest settings. It tries to use SPICE USB redirection, which is similar to what is described in the SPICE user manual , but uses qemu-xhci host adapter instead of ich9-ehci1. However, when I try to flip the switch in the guest settings for the camera device, it just notifies that its redirection failed. Here are the relevant parts in my guest machine configuration, which seem to be OK:

-xml

-xml

---------- So, how can I make the camera available to the guest?

Most desktop environments and distros use various alert sounds, can be distracting when you have a high-end sound system connected to the computer and some ~0 dBFS bell jingle or a generic error sound plays. At the time **I don't need any audio in my virtual machines** — it's preferred to entirely disable the sound processing, if possible. I'd appreciate not having to ever configure the audio setting in a fresh VM (be it alsamixer, pactl for Pulseaudio or DE settings). The Gnome volume mixer (settings → sound → volume levels) doesn't appear to save the muted state even for one VM.

I am moving GNOME Boxes virtual machines from Fedora to Guix following [the guide on Fedora wiki](https://fedoraproject.org/wiki/Move_boxes_virtual_machines) . On the Fedora workstation:

$ virsh list --all
 Id   Name           State
-------------------------------
 -    win10          shut off
$ cd ~
$ virsh dumpxml win10 >win10.xml
$ mv .local/share/gnome-boxes/images/win10 win10

Then, I moved win10 and win10.xml to the home directory at the new machine. On that Guix system:

$ guix install gnome-boxes
$ cd ~
$ mv win10 .local/share/gnome-boxes/images/win10
$ guix install libvirt
$ virsh create win10.xml
error: Failed to create domain from win10.xml
error: Cannot check QEMU binary /usr/bin/qemu-system-x86_64: No such file or directory

qemu-system-x84_64 is located in a different place:

$ type qemu-system-x86_64
qemu-system-x86_64 is /run/current-system/profile/bin/qemu-system-x86_64

So, how do I complete importing the virtual machine?

I tried to run Gnome OS, Fedora Silverblue and endeavourOS with Gnome Boxes (Flathub install) on Fedora 37. However, regardless of system, booting into the virtual machine immediately stops with: The steps I took were pretty default: 1. Install Gnome Boxes via Flathub 2. Open Gnome Boxes and choose 'Create Virtual Machine' 3. Install GnomeOS Nightly (2nd time Fedora Silverblue) from pre-configured source 4. Start Virtual Machine If I check my virtualization capabilities, everything looks fine:

$ gnome-boxes --checks
• The CPU is capable of virtualization: yes
• The KVM module is loaded: yes
• Libvirt KVM guest available: yes
• Boxes storage pool available: yes
• The SELinux context is default: yes

The image are at the right place and accessible to libvirt: $ virsh list ; virsh vol-list gnome-boxes Id Name Status ------------------------------ 1 gnomenightly laufend Name Pfad -------------------------------------------------------------------------------- gnomenightly /home/firestarter/.local/share/gnome-boxes/images/gnomenightly The QEMU logs show some warnings of qemu-system-x86_64: warning: This family of AMD CPU doesn't support hyperthreading(2) (I have a AMD Ryzen 5 5500U). However, this should not be a problem here as far as my research have told me. UPDATE: So it appears, that it relates to the default uefi boot modus of Gnome OS and Fedora Silverblue. Trying another image, Manjaro, which offers me the option to boot in BIOS the virtual machine boots. Using UEFI option for the same image, the boot fails as before; although edk2-ovmf is installed.

*in short:* **My virtual machine named CONAN01 is not starting up in gnome-boxes, I receive/see different errors and do not know what the real issues behind them are:** **Error 1:** When starting gnome-boxes from the Gnome desktop environment and clicking on my virtual machine CONAN01 to start it up, I receive a pop-up message with the option to open the error log and in this error log I can see the last lines, which state: 2022-06-15 09:39:22.707+0000: Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2022-06-15T09:39:22.800582Z qemu-system-x86_64: warning: This family of AMD CPU doesn't support hyperthreading(2) Please configure -smp options properly or try enabling topoext feature. 2022-06-15T10:30:56.757942Z qemu-system-x86_64: terminating on signal 15 from pid 3544 (/lib/systemd/systemd) **Error 2:** When using the terminal to start gnome-boxes and then using the mouse to click and run my virtual machine CONAN01, I receive following error: > gnome-boxes error output at gnome-boxes startup: (gnome-boxes:709111): Gtk-WARNING **: 22:02:27.216: GtkFlowBox with a model will ignore sort and filter functions (gnome-boxes:709111): Gtk-WARNING **: 22:02:27.217: GtkListBox with a model will ignore sort and filter functions (gnome-boxes:709111): GLib-GObject-WARNING **: 22:02:28.067: ../../../gobject/gsignal.c:2715: handler '2888' of instance '0x562fb55b44e0' is not blocked error output at virtual machine CONAN01 startup: (gnome-boxes:709111): Boxes-WARNING **: 22:02:32.045: machine.vala:605: Failed to start CONAN01: Unable to start domain: internal error: /usr/lib/qemu/qemu-bridge-helper --use-vnet --br=virbr0 --fd=31: failed to communicate with bridge helper: Transport endpoint is not connected stderr=failed to create tun device: Operation not permitted **Error 3:** When executing the gnome-boxes – CLI checks by performing the necessary command, I receive following information: > gnome-boxes --checks information output: (gnome-boxes:717997): Boxes-WARNING **: 22:50:30.599: util-app.vala:376: Failed to execute child process ?restorecon? (No such file or directory) • The CPU is capable of virtualization: yes • The KVM module is loaded: yes • Libvirt KVM guest available: yes • Boxes storage pool available: no /root/.local/share/gnome-boxes/images is known to libvirt as GNOME Boxes’s storage pool but this directory does not exist • The SELinux context is default: no Report bugs to . Boxes home page: . Despite changing the location of the storage pool by using the necessary commands, but the output showing the XML – configuration has not changed, virsh and gnome-boxes still think the old location is valid, my intend was to change “/home/myusername/.local/share/gnome-boxes/images”: > virsh pool-info gnome-boxes Name: gnome-boxes UUID: edb0bf37-df0f-4295-a3cf-0ced96970de0 State: running Persistent: yes Autostart: yes Capacity: 907,44 GiB Allocation: 531,49 GiB Available: 375,95 GiB > virsh pool-dumpxml gnome-boxes gnome-boxes edb0bf37-df0f-4295-a3cf-0ced96970de0 974357393408 570679726080 403677667328 /root/.local/share/gnome-boxes/images 0744 0 0 > sudo virsh pool-edit gnome-boxes > virsh pool-dumpxml gnome-boxes gnome-boxes edb0bf37-df0f-4295-a3cf-0ced96970de0 974357393408 570679726080 403677667328 /root/.local/share/gnome-boxes/images 0744 0 0

VMWare Workstation 16 allows me to choose how many processors the VM may use. Does Gnome Boxes have this same option? I am unable to find it.

I have received a virtual machine for my CS assignment. I have opened it in Gnome Boxes (just by double-clicking on the VM image), but I do not want to write code there, but on my local machine and then compile trough ssh on the virtual machine. The virtual machine has an .ova extension and in Boxes Preferences it says Broker QEMU Session, Display Protocol SPICE. What should I use as remote IP for ssh? Are there any additional configurations of the VM to be made and how should I add them?

I'm not too familiar with SSH things, and I'm trying to do a remote connection to a virtual machine on my other PC which has Gnome Boxes installed on it. **Might be a simple question, but are there any commands to run to see my SSH status, and how can I connect to my remote Gnome Box?** I'm essentially trying to find a way to obtain the address of my other box (the ssh://xxxx address) in order to connect remotely to my Gnome box of another device. Help would be much appreciated!

I'm running windows 10 inside gnome boxes (on fedora) which, while kinda slow, works well enough. However, after closing and reopening boxes, it appears that windows just continues where I left off. Now, of course that's what it should do, but it also keeps the time and date from where I left it and when I'm not connected to the internet, it can't grab the correct time from network. Now, I can either set the correct time by hand, or always "correctly" shutdown and boot windows to fix it, but I was wondering if there's a way to provide a time server for windows/boxes guests inside the virtual network that boxes is running. *Reason I'm asking: I need windows for some software to read data from meteorological stations, so I'm in the sticks, not connected to the internet and this software apparently depends on correct system time to be able to download data. If my windows thinks it's one week ago, I can only download data from one week ago.*

I have a webserver running on my host OS and I want to access it from a windows VM running in gnome boxes. The VM has internet access but it does not seem to be able to access anything on the local network by local IP address. There seems to be no UI for changing network settings. Is there any way to change the network configuration to allow accessing local devices on the network?

Yesterday I duplicated my Windows 10 machine in Gnome boxes to upgrade to Win 11. After realising that it would need 64 GB of space on my harddrive, which I do not have currently, I deleted the image. Now Gnome boxes crashes with the following error: (gnome-boxes:59538): Boxes-CRITICAL **: 09:44:24.321: boxes_vm_importer_get_source_media: assertion 'self != NULL' failed To me this sounds like a missing image (source_media). I would like to simply delete the machine that is referring to that image, but googling didn’t provide me with anything useful. Thanks for help

I installed Windows 10 Education (Win10E) in Gnome Boxes on elementary OS 6 (Odin). As far as I can tell, it installs fine, and I can use Win10E with my university account. However, if I restart my computer or Gnome Boxes, the Win10E login screen will not accept my password, and I cannot log back into Win10E. Win10E acts as though my password is wrong, but it is not. Gnome Boxes also offers the option to install Win10E with a local account. I can add a local account, which allows me to log back into Win10E. However, there is a warning in the lower-right corner of the screen that I am in “test mode”. It seems that test mode means that I have an unsigned driver. I found [this guidance](https://windowsloop.com/disable-test-mode-windows-10/) on how to remove the test-mode warning. However, I prefer to not blindly silence warnings if I can fix the underlying situation. What is the correct way to run a Windows 10 *Education* virtual machine on Linux? I am open to other virtual machines, and all I really need is full access to Office 365 (i.e., not the web version).

I use GNOME Boxes on Fedora 32 to virtualize a Fedora Silverblue installation. I did not setup a sophisticated/smart partitioning for my virtual Fedora and have run out of disk space on my virtual root partition. My objective is to be able to continue using my virtual Fedora machine as efficient and soon as possible without recreating the virtualization and without adding another partition. Therefore, how can I increase the root partition of my QEMU-based virtualization? Similar question: https://unix.stackexchange.com/questions/349586/resize-qcow2-root-parition

I was running Kali Linux in gnome boxes just like virtualbox and I was running out of space so I used gnome boxes to increase the hd capacity. Now when attempt to login the screen goes blank for a fraction of a second and asks for the user name and password again and will not log me in. I don't think that it is because of boxes, it's because I changed the hd size and Kali crapped out. I can alt shift f1 and log in. How could I fix? It? Please thx

I am trying to connect to a remote machine using boxes on centos7. I enter ssh://ip:port which brings me to some usage: ssh screen with a blinking cursor that I am unable to exit out of. Likely because I don't know the [code bro] Do I have the syntax wrong?

To build a virtual machine with GNOME Boxes, I have this problem: "virtualization extensions are unavailable on your system. Check your bios settings to enable them." what's the solution?

I use GNOME Boxes on a laptop. The guest machines get the Internet connection automatically with default settings whenever the laptop moves between networks (Ethernet, Wi-Fi in different locations, or a cellular phone as a USB modem). The guest machines are not bridged with the host and are not visible on the host's LAN implying that [the MAC addresses of the guests are overwritten](https://superuser.com/a/1510360/1203531) before passing the frames to the host's LAN. > By default QEMU will create a > [SLiRP](https://en.wikipedia.org/wiki/Slirp#Influence_on_other_projects) > user network backend and an appropriate virtual network device for the > guest… > > [User Networking](https://wiki.qemu.org/Documentation/Networking#User_Networking_.28SLIRP.29) is implemented using "slirp", which provides a full > TCP/IP stack within QEMU and uses that stack to implement a virtual > NAT'd network. > QEMU's final, and most bizarre, networking option is also its default option. What this does is connect a "[usermode network stack](https://people.gnome.org/~markmc/qemu-networking.html) " to a vlan. This network stack is a standalone implementation of the ip, tcp, udp, dhcp and tftp (etc.) protocols. It can handle frames from the vlan by e.g. responding to dhcp requests with a valid address, responding to tftp requests with a file from the host filesystem or by creating udp/tcp sockets over which packet data can be forwarded. > >Note that this network stack is running within the qemu process itself. So, for example there is no separate dhcp or tftp process handling those requests. Also, the stack is effectively acting as a proxy by unpacking application data from udp/tcp packets and forwarding them over a socket connecting the qemu process and the destination process. Note, in the above context, "vlan" stands for "emulated" LAN, [it doesn't mean IEEE 802.1Q VLAN ID](https://wiki.qemu.org/Documentation/Networking#The_legacy_-net_option) . By default, the guest has 10.0.2.15 IP address on 10.0.2.0/24 network. The gateway is 10.0.2.2. The DNS server is 10.0.2.3. The guest can access the host by connecting on 10.0.2.2 gateway IP. At a particular Wi-Fi network, all guest machines lose Internet access. I found [another question about lack of Internet](https://unix.stackexchange.com/q/593838/423679) in the guest under QEMU, which discovered that DNS may not work out-of-the-box under certain setup. So, I checked mine. I can access websites by their IP from the guest. Also, if I configure an IPv4 connection manually, resolving gets restored if I add another known resolver, such as 8.8.8.8, as a backup in addition to the default 10.0.2.3. According to the local administrator, this Wi-Fi network has VLAN tagging enabled to separate local computers from visitors' computers. Apparently, if VLAN were an issue, it would cause complete loss of Internet access, not just resolving. Another particularity of that network is that the first DNS resolver is configured to refuse most request. The second resolver 8.8.8.8 is provided, but, apparently, not used by QEMU. The issue persists across devices. I tried on two completely different laptops with Intel wireless. The issue is found in Debian "Buster" at least since 10.4, "Bullseye" and "Sid".