Open kamidon opened 4 years ago
Thank you for your contributions.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:
Haven't looked into this but I now boxes isn't in a good shape on nixos
I marked this as stale due to inactivity. → More info
Describe the bug When
gnome-boxes
attempts to connect to a QEMU system VM after starting it, the connection fails. I can connect to the started VM usingvirt-viewer -c qemu:///system -a
and selecting the started VM from the dialog that appears.To Reproduce Steps to reproduce the behavior:
virsh -c qemu:///system ...
)gnome-boxes
and click on the VM to start it and attempt to connect to the display using spice.Connection to "<vm name>" failed.
NOTE: this only happens with system VMs. User VMs work fine.
Expected behavior The display of the VM is shown in the
gnome-boxes
window.Additional context
Running
gnome-boxes
asgnome-boxes --spice-debug
while following the reproduction procedure produces the following output:From this log, it appears that
gnome-boxes
is concluding that it must connect over an IP connection but that it does not have the required ports to connect to for either an unencrypted or encrypted connection.When I start
virt-viewer
withvirt-viewer --spice-debug -c qemu:///system -a
the log looks the same up until the line:Neither that line nor the following one about not attempting an encrypted connection show up in the
virt-viewer
log and it seems to continue without a problem. It's as if gnome-boxes is failing to use a connection method thatvirt-viewer
is able to use, but I'm not sure what that is or how to check if there is possibly a build problem withgnome-boxes
that is causing that.Metadata Output of
nix run nixpkgs.nix-info -c nix-info -m
: