Does "console -t vga" work on macos?

lxc console -t vga -v fedora-33

(spicy:56956): GSpice-WARNING **: 19:54:32.166: main-1:0: could not set sockopt TCP_NODELAY: Operation not supported on socket
** Message: 19:54:32.253: main channel: opened

(spicy:56956): GSpice-WARNING **: 19:54:32.284: display-2:0: could not set sockopt TCP_NODELAY: Operation not supported on socket

(spicy:56956): GSpice-WARNING **: 19:54:32.284: usbredir-9:2: could not set sockopt TCP_NODELAY: Operation not supported on socket

(spicy:56956): GSpice-WARNING **: 19:54:32.284: usbredir-9:1: could not set sockopt TCP_NODELAY: Operation not supported on socket

(spicy:56956): GSpice-WARNING **: 19:54:32.284: usbredir-9:0: could not set sockopt TCP_NODELAY: Operation not supported on socket
spicy(56956,0x16c08f000) malloc: *** error for object 0x1287c2130: pointer being freed was not allocated
spicy(56956,0x16c08f000) malloc: *** set a breakpoint in malloc_error_break to debug

is that spicy error ?
or never work on macos

Hmm, looks like it. I remember having it working on macOS but that may have been with virt-viewer?

I believe I used this one: GitHub - jeffreywildman/homebrew-virt-manager: A set of homebrew formulae to install virt-manager and virt-viewer on MAC OSX

no luck with virt-viewer, fails with:

◰³ venv39  ~/W/theater-pi  lxc console -t vga fedora-33                                                                                                                                                            二  6/15 23:16:51 2021

(remote-viewer:79553): GSpice-WARNING **: 23:16:55.821: main-1:0: could not set sockopt TCP_NODELAY: Operation not supported on socket

(remote-viewer:79553): GSpice-WARNING **: 23:16:55.995: display-2:0: could not set sockopt TCP_NODELAY: Operation not supported on socket

(remote-viewer:79553): GSpice-WARNING **: 23:16:55.995: usbredir-9:2: could not set sockopt TCP_NODELAY: Operation not supported on socket

(remote-viewer:79553): GSpice-WARNING **: 23:16:55.995: usbredir-9:1: could not set sockopt TCP_NODELAY: Operation not supported on socket

(remote-viewer:79553): GSpice-WARNING **: 23:16:55.995: usbredir-9:0: could not set sockopt TCP_NODELAY: Operation not supported on socket
remote-viewer(79553,0x16d6d7000) malloc: *** error for object 0x11d7f8dc0: pointer being freed was not allocated
remote-viewer(79553,0x16d6d7000) malloc: *** set a breakpoint in malloc_error_break to debug

my device is macbook with M1

Could be something wrong with the build of GTK on those machines…
Can you try running remote-viewer on its own see if that crashes too?

try to connect kvm with “virt-viewer -c”:

and open the window:
截屏2021-06-16 上午12.41.59

click my vm and breaked

virt-viewer -c 'qemu+ssh://tongchia@192.168.123.191/system?socket=/var/run/libvirt/libvirt-sock'                                                                               2553ms  三  6/16 00:38:51 2021

(virt-viewer:86177): GSpice-WARNING **: 00:38:58.073: main-1:0: could not set sockopt TCP_NODELAY: Operation not supported on socket

(virt-viewer:86177): GSpice-WARNING **: 00:38:58.405: usbredir-9:1: could not set sockopt TCP_NODELAY: Operation not supported on socket

(virt-viewer:86177): GSpice-WARNING **: 00:38:58.405: usbredir-9:0: could not set sockopt TCP_NODELAY: Operation not supported on socket

(virt-viewer:86177): GSpice-WARNING **: 00:38:58.405: playback-5:0: could not set sockopt TCP_NODELAY: Operation not supported on socket

(virt-viewer:86177): GSpice-WARNING **: 00:38:58.405: record-6:0: could not set sockopt TCP_NODELAY: Operation not supported on socket

(virt-viewer:86177): GSpice-WARNING **: 00:38:58.405: display-2:0: could not set sockopt TCP_NODELAY: Operation not supported on socket
virt-viewer(86177,0x17042b000) malloc: *** error for object 0x116f047e0: pointer being freed was not allocated
virt-viewer(86177,0x17042b000) malloc: *** set a breakpoint in malloc_error_break to debug

Ok, so that definitely suggests a bug, most likely with gtk on the M1 Mac platform.
I’m not sure who the best contact point for such an issue would be though,

Issues · GNOME / gtk · GitLab maybe?