Gnome Boxes stuck when setuping an image

F_oliv · 16 June 2022 09:42

After update I’m trouble with gnome boxes. It stucks when I try to setup an image.

When I do -
journalctl -p 3 -xf
I get -

jun 16 09:38:53 fo-satellitel50c kernel: DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000008d800000-0x000000008fffffff], contact BIOS vendor for fixes
jun 16 09:38:53 fo-satellitel50c systemd[1]: Failed to start Setup Virtual Console.
jun 16 09:38:53 fo-satellitel50c systemd-vconsole-setup[254]: /usr/bin/loadkeys failed with exit status 1.
jun 16 09:39:05 fo-satellitel50c kernel: 
jun 16 09:39:25 fo-satellitel50c gnome-session-binary[875]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
jun 16 09:39:25 fo-satellitel50c gnome-session-binary[875]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
jun 16 09:40:40 fo-satellitel50c gdm-password][1145]: gkr-pam: unable to locate daemon control file
jun 16 09:41:02 fo-satellitel50c gdm-launch-environment][803]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
jun 16 09:41:44 fo-satellitel50c virtqemud[1753]: unsupported configuration: chardev 'spicevmc' not supported without spice graphics
jun 16 09:44:45 fo-satellitel50c kernel: ntfs3: Unknown parameter 'windows_names'
jun 16 09:45:15 fo-satellitel50c virtqemud[1753]: Unable to read from monitor: Connection reset by peer
jun 16 09:45:15 fo-satellitel50c virtqemud[1753]: internal error: qemu unexpectedly closed the monitor: ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy
                                                  2022-06-16T08:45:15.715470Z qemu-system-x86_64: -accel kvm: failed to initialize kvm: Device or resource busy
jun 16 09:45:15 fo-satellitel50c virtqemud[1753]: internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy
                                                  2022-06-16T08:45:15.715470Z qemu-system-x86_64: -accel kvm: failed to initialize kvm: Device or resource busy
jun 16 09:45:39 fo-satellitel50c virtqemud[1753]: End of file while reading data: Input/output error
jun 16 09:46:10 fo-satellitel50c virtqemud[1753]: Unable to read from monitor: Connection reset by peer
jun 16 09:46:10 fo-satellitel50c virtqemud[1753]: internal error: qemu unexpectedly closed the monitor: ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy
                                                  2022-06-16T08:46:10.018888Z qemu-system-x86_64: -accel kvm: failed to initialize kvm: Device or resource busy
jun 16 09:46:10 fo-satellitel50c virtqemud[1753]: internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy
                                                  2022-06-16T08:46:10.018888Z qemu-system-x86_64: -accel kvm: failed to initialize kvm: Device or resource busy
jun 16 09:46:32 fo-satellitel50c virtqemud[1753]: End of file while reading data: Input/output error
jun 16 09:49:14 fo-satellitel50c virtqemud[2975]: Unable to create KVM VM for TSC probing: Device or resource busy
jun 16 09:50:55 fo-satellitel50c virtqemud[2975]: Unable to read from monitor: Connection reset by peer
jun 16 09:50:55 fo-satellitel50c virtqemud[2975]: internal error: qemu unexpectedly closed the monitor: ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy
                                                  2022-06-16T08:50:55.462101Z qemu-system-x86_64: -accel kvm: failed to initialize kvm: Device or resource busy
jun 16 09:50:55 fo-satellitel50c virtqemud[2975]: internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy
                                                  2022-06-16T08:50:55.462101Z qemu-system-x86_64: -accel kvm: failed to initialize kvm: Device or resource busy
jun 16 09:51:26 fo-satellitel50c virtqemud[2975]: End of file while reading data: Input/output error
jun 16 10:09:22 fo-satellitel50c virtlogd[3925]: Unable to open file: /home/fo/.cache/libvirt/qemu/log/manjaro-gnom.log: No such file or directory
jun 16 10:09:22 fo-satellitel50c virtqemud[3879]: Unable to open file: /home/fo/.cache/libvirt/qemu/log/manjaro-gnom.log: No such file or directory
jun 16 10:12:26 fo-satellitel50c virtqemud[3879]: Cannot recv data: Connection reset by peer
jun 16 10:13:14 fo-satellitel50c virtqemud[3879]: argument unsupported: QEMU guest agent is not configured
jun 16 10:13:14 fo-satellitel50c virtqemud[3879]: argument unsupported: QEMU guest agent is not configured
jun 16 10:14:59 fo-satellitel50c virtqemud[3879]: unsupported configuration: chardev 'spicevmc' not supported without spice graphics
jun 16 10:26:41 fo-satellitel50c virtqemud[3879]: unsupported configuration: chardev 'spicevmc' not supported without spice graphics
jun 16 10:27:29 fo-satellitel50c virtqemud[3879]: End of file while reading data: Input/output error
jun 16 10:29:42 fo-satellitel50c virtqemud[3879]: unsupported configuration: chardev 'spicevmc' not supported without spice graphics
jun 16 10:30:39 fo-satellitel50c virtqemud[3879]: End of file while reading data: Input/output error
jun 16 10:37:37 fo-satellitel50c virtqemud[6731]: unsupported configuration: Emulator '/usr/bin/qemu-system-x86_64' does not support virt type 'kvm'
jun 16 10:37:38 fo-satellitel50c virtqemud[6731]: unsupported configuration: Emulator '/usr/bin/qemu-system-x86_64' does not support virt type 'kvm'
jun 16 10:37:46 fo-satellitel50c virtqemud[6731]: Unable to create KVM VM for TSC probing: Device or resource busy
jun 16 10:37:47 fo-satellitel50c virtqemud[6731]: Unable to create KVM VM for TSC probing: Device or resource busy
jun 16 10:37:55 fo-satellitel50c virtqemud[6731]: unsupported configuration: chardev 'spicevmc' not supported without spice graphics
jun 16 10:38:40 fo-satellitel50c systemd[1163]: Failed to start Tracker metadata extractor.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 795 and the job result is failed.
jun 16 10:38:40 fo-satellitel50c systemd[1163]: Failed to start Tracker metadata extractor.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 815 and the job result is failed.
jun 16 10:38:41 fo-satellitel50c systemd[1163]: Failed to start Tracker metadata extractor.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 835 and the job result is failed.
jun 16 10:38:41 fo-satellitel50c systemd[1163]: Failed to start Tracker metadata extractor.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 855 and the job result is failed.
jun 16 10:38:41 fo-satellitel50c systemd[1163]: Failed to start Tracker metadata extractor.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 875 and the job result is failed.
jun 16 10:38:41 fo-satellitel50c systemd[1163]: Failed to start Tracker metadata extractor.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 895 and the job result is failed.

megavolt · 16 June 2022 10:24

Hello @F_oliv

Looks like this issue: box creation gets stuck on Ubuntu 22.04 (#772) · Issues · GNOME / GNOME Boxes · GitLab Still no fix, but the flatpak version works flawless.

worralorrasurfa · 16 June 2022 10:42

Same problem for me as well, but here is a possible solution:

The reason I say “possible” is I can’t downgrade since I only have the current version in cache, so I don’t know if it will work or not.

megavolt · 16 June 2022 11:11

Ah I see… thanks for linking it… I tried it and downgrading works.

pamac install downgrade
sudo downgrade --ala-only libvirt libvirt-python

F_oliv · 16 June 2022 11:56

Thank you, worralorrasurfa!

Thank you, megavolt!

worralorrasurfa · 16 June 2022 13:31

@F_oliv @megavolt

I’m glad that worked out for both of you. I’m sure, in time, there will be an update with a fix for mine.

And, what did I learn from this event?

Number of versions of each package to keep: At least 2.

system · 19 June 2022 03:32

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.