// Solved: Solution at the end of the post

I want to test Hyprland with NixOS in a VM using Virt-Manager (https://virt-manager.org/) on Arch Linux host before installing it on my machine.

Unfortunately, I'm encountering an issue. Here's the error I get when I run Hyprland; this is what appears in the logs:

[LOG] Disabling stdout logs! Check the log for further details.
[CRITICAL] m_sWLRRenderer was NULL!

And here's the output:

[libseat] [libseat/backend/seatd.c:64] Could not connect to socket /run/seatd.sock: no such file or directory

I read somewhere that I need to pass through the internal GPU of my host, but I couldn't find any settings for this. I'm using an x1 Carbon Gen 5, which I want to install NixOS on, assuming it works.

Can someone help me get the ball rolling? If I can get through some installations, I would like to install NixOS as my main OS on the x1. Any general help is also most welcome vm siplay spice

<graphics type="spice" port="5900" autoport="yes" listen="127.0.0.1">
  <listen type="address" address="127.0.0.1"/>
  <image compression="off"/>
  <gl enable="no"/>
</graphics>

enabling the 3d accelatation gives me

Error starting domain: internal error: process exited while connecting to monitor: 2023-08-12T23:07:22.162711Z qemu-system-x86_64: SPICE GL support is local-only for now and incompatible with -spice port/tls-port

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn
    ret = fn(self, *args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/share/virt-manager/virtManager/object/domain.py", line 1402, in startup
    self._backend.create()
  File "/usr/lib/python3.11/site-packages/libvirt.py", line 1373, in create
    raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: internal error: process exited while connecting to monitor: 2023-08-12T23:07:22.162711Z qemu-system-x86_64: SPICE GL support is local-only for now and incompatible with -spice port/tls-port

Here's my current configuration:

{ config, pkgs, ... }:
{
  imports =
      /etc/nixos/hardware-configuration.nix
    ];
  boot.loader.grub.enable = true;
  boot.loader.grub.device = "/dev/vda";
  networking.hostName = "nixos";
  time.timeZone = "Europe/Amsterdam";

  users.defaultUserShell = pkgs.zsh;
  users.users.user = {
     isNormalUser = true;
     packages = with pkgs; [
        chromium
     ];
   };
  environment.systemPackages = with pkgs; [
     neovim
     wget
     zsh
     fzf
     git
     tmux
     busybox
     seatd
   ];
  programs.zsh.enable = true;
  programs.hyprland.enable = true;
  security.polkit.enable = true;
  security.rtkit.enable = true;
  services.dbus.enable = true;
}

Update

thanks to u/510Threaded the key was to enable 3d acceleration in virtmanger here are my settings

<graphics type="spice">
  <listen type="none"/>
  <image compression="off"/>
  <gl enable="yes" rendernode="/dev/dri/renderD128"/>
</graphics>


<video>
  <model type="virtio" heads="1" primary="yes">
    <acceleration accel3d="yes"/>
  </model>
  <alias name="video0"/>
  <address type="pci" domain="0x0000" bus="0x00" slot="0x01" function="0x0"/>
</video>

I am using NVIDIA with the proprietary drivers and have been running this on NixOS on the stable branch with no trouble at all. It was my Hyprland on Arch that suddenly ate it. I am running hyprland-nvidia-git, and it's been working just fine up until this morning. I remember doing an update last night and this morning I tried to boot Hyprland from TTY as I normally do (I don't use a login manager), and it just ate it and core dumped, telling me there was no /run/seatd.sock to be found. I'm not sure what could have changed this or why. I tried reinstalling seatd and also hyprland-nvidia-git and also tried using regular hyprland-nvidia and then standard hyprland and it still didn't work. I am new to Arch, so this could be an artifact of me not understanding Arch very well yet. If anyone can point me in the right direction or has had a similar experience and knows what I could do to start troubleshooting this, I would be very grateful. Thank you.