Jump to content

Rockikone

Members
 View Profile  See their activity

  • Posts

    150

  • Joined

  • Last visited

 Content Type 

Report Comments posted by Rockikone

    (6.11.3) iGPU kick off

    in Stable Releases

    Posted

    @JorgeB

    @SimonF

     

    Error could be found and fixed in the German subforum now. The disks were previously installed in a Coffee Lake Xeon system. There I used the plugin gvt-g. When changing the server to AlderLake, the plugin was uninstalled beforehand, but apparently there were still config remnants in the file /etc/libvirt/hooks/qemu.
    I have now deleted the libvirt file and recreated the VM's. Error is gone. I would never have thought of that.

    I wish you all a great 2023

     

    Greetings from Bavaria

     

    Thomas

     

    • Like 1

    (6.11.3) iGPU kick off

    in Stable Releases

    Posted

    @JorgeB

    @SimonF

     

    Unfortunately, I have to open this error message again.
    In the meantime, the iGPU has gone bye-bye twice again.
    Yesterday for the last time. Since the server was already running for 6 days without problems.
    I can narrow down the error pretty well in the meantime.
    Yesterday I had to work on a Windows VM, which runs on the Unraid server.
    At 15:37 I was done with the work and shut down the VM (in the VM). I was connected with RDP.

    As you can see in the log, the iGPU flew out of the system at 15:37. So the story is related to the VM environment.
    The iGPU is only used for Docker and Unraid. It is not mounted in any VM. There is no dGPU installed in the system anymore, only the iGPU.
    I don't know now if the problem is with Unraid or the bios. But the error is unfortunately still there and is related to the VM environment!

     

    Greetings

      

    Nov 29 15:37:46 Homeserver  avahi-daemon[7715]: Interface vnet2.IPv6 no longer relevant for mDNS.
Nov 29 15:37:46 Homeserver  avahi-daemon[7715]: Leaving mDNS multicast group on interface vnet2.IPv6 with address fe80::fc54:ff:fe0e:bc60.
Nov 29 15:37:46 Homeserver kernel: br0.25: port 4(vnet2) entered disabled state
Nov 29 15:37:46 Homeserver kernel: device vnet2 left promiscuous mode
Nov 29 15:37:46 Homeserver kernel: br0.25: port 4(vnet2) entered disabled state
Nov 29 15:37:46 Homeserver kernel: sdc: sdc1 sdc2 sdc3 sdc4
Nov 29 15:37:46 Homeserver  avahi-daemon[7715]: Withdrawing address record for fe80::fc54:ff:fe0e:bc60 on vnet2.
Nov 29 15:37:46 Homeserver unassigned.devices: Disk with serial 'Samsung_SSD_850_EVO_250GB_S2R6NB0J531111V', mountpoint 'Samsung_SSD_850_EVO_250GB_S2R6NB0J531111V-part2' is set as passed through.
Nov 29 15:37:46 Homeserver unassigned.devices: Disk with serial 'Samsung_SSD_850_EVO_250GB_S2R6NB0J531111V', mountpoint 'Samsung_SSD_850_EVO_250GB_S2R6NB0J531111V-part1' is set as passed through.
Nov 29 15:37:46 Homeserver unassigned.devices: Disk with serial 'Samsung_SSD_850_EVO_250GB_S2R6NB0J531111V', mountpoint 'S2R6NB0J531111V-part4' is set as passed through.
Nov 29 15:37:46 Homeserver unassigned.devices: Disk with serial 'Samsung_SSD_850_EVO_250GB_S2R6NB0J531111V', mountpoint 'S2R6NB0J531111V-part3' is set as passed through.
Nov 29 15:37:49 Homeserver kernel: sdc: sdc1 sdc2 sdc3 sdc4
Nov 29 15:37:49 Homeserver kernel: sdc: sdc1 sdc2 sdc3 sdc4
Nov 29 15:37:49 Homeserver  acpid: input device has been disconnected, fd 8
Nov 29 15:37:49 Homeserver unassigned.devices: Disk with serial 'Samsung_SSD_850_EVO_250GB_S2R6NB0J531111V', mountpoint 'Samsung_SSD_850_EVO_250GB_S2R6NB0J531111V-part2' is set as passed through.
Nov 29 15:37:49 Homeserver unassigned.devices: Disk with serial 'Samsung_SSD_850_EVO_250GB_S2R6NB0J531111V', mountpoint 'S2R6NB0J531111V-part3' is set as passed through.
Nov 29 15:37:49 Homeserver unassigned.devices: Disk with serial 'Samsung_SSD_850_EVO_250GB_S2R6NB0J531111V', mountpoint 'S2R6NB0J531111V-part4' is set as passed through.
Nov 29 15:37:49 Homeserver unassigned.devices: Disk with serial 'Samsung_SSD_850_EVO_250GB_S2R6NB0J531111V', mountpoint 'Samsung_SSD_850_EVO_250GB_S2R6NB0J531111V-part1' is set as passed through.
Nov 29 15:37:49 Homeserver unassigned.devices: Disk with serial 'Samsung_SSD_850_EVO_250GB_S2R6NB0J531111V', mountpoint 'S2R6NB0J531111V-part4' is set as passed through.
Nov 29 15:37:49 Homeserver unassigned.devices: Disk with serial 'Samsung_SSD_850_EVO_250GB_S2R6NB0J531111V', mountpoint 'Samsung_SSD_850_EVO_250GB_S2R6NB0J531111V-part1' is set as passed through.
Nov 29 15:37:49 Homeserver unassigned.devices: Disk with serial 'Samsung_SSD_850_EVO_250GB_S2R6NB0J531111V', mountpoint 'S2R6NB0J531111V-part3' is set as passed through.
Nov 29 15:37:49 Homeserver unassigned.devices: Disk with serial 'Samsung_SSD_850_EVO_250GB_S2R6NB0J531111V', mountpoint 'Samsung_SSD_850_EVO_250GB_S2R6NB0J531111V-part2' is set as passed through.
Nov 29 15:37:49 Homeserver kernel: pci 0000:00:02.0: Removing from iommu group 3
Nov 29 15:51:29 Homeserver kernel: hrtimer: interrupt took 12313 ns

     

    homeserver-diagnostics-20221130-0727.zip

    • Like 1

    (6.11.3) iGPU kick off

    in Stable Releases

    Posted

    @SimonF

    Okay, the reason the iGPU was kicked was because of the Guacamole Docker. This was running without special rights.

    I have been using this for several years. I don't know now if it's the new hardware environment or Unraid 6.11.

    I have now uninstalled Guacamole and the iGPU remains in the system.

    Greetings

    • Like 2

    (6.11.3) iGPU kick off

    in Stable Releases

    Posted

    @SimonF

    You write that a Docker with the guacd identifier is possibly responsible for ejecting the iGPU.
    I have now found out that guacd stands for the container Guacamole. This was with me on Autstart at boot. I have now deactivated this once and restarted.
    Let's see if it was the problem.
    Greetings

    6.11.1 system crash after shutting down Windows 11 VM

    in Stable Releases

    Posted

    @SimonF

    Crash happens with audio and video passthrough.

    I have other problems too. igpu kick off by kernel etc.

    Maybe it's a motherboard bios problem. I've a very new board Gigabyte MW34-SP0 (W680)

     

    Just now i was vpn on a windows vm and after i did a shutdown the whole server is down. even the remote console of the board. but what i notice is that the crashes mostly have to do with virtual machines. the windows machine has no graphics card associated with it, only vnc.

×
×
  • Create New...