Search results

My mistake. You can use X2go in LXC containers. There must be a bug in my X2go client. If I try the same configuration using an older version it works.

How did you get X2go working? I can't manage it in a container. It looks like X2go executes /usr/bin/x2gomountdirs on log in, and that fails in a container.

I can confirm that spiceproxy is not listening on IPv6 by default. However, if I change the IP address of the pvelocalhost entry in /etc/hosts to the IPv6 address and restart pveproxy, pveproxy will listen on IPv6 too.

For me, running that 4.10 kernel is the only solution with proven stability. Achieved a week uptime now, instead of 2 or 3 blue screens every day.

Crashes here too. Fresh install of Poxmox 5.1. Windows 2008 R2 (mostly freeze, but today I got a DRIVER_IRQL_NOT_LESS_OR_EQUAL blue screen) Windows 10, always blue screen. All drivers are virtio 0.1.141. I changed NIC driver on Windows 2008 R2 to Intel, and the blue screen is since then...