[Plugin] Intel-GVT-g

[Megumi]

i retry boot ubuntu with gvt-g at 20:03

unraid sys.log

Sep  4 20:02:42 MARIO kernel: pcieport 0000:00:1d.2: Intel SPT PCH root port ACS workaround enabled
Sep  4 20:03:09 MARIO kernel: br0: port 3(vnet2) entered disabled state
Sep  4 20:03:09 MARIO kernel: vnet2 (unregistering): left allmulticast mode
Sep  4 20:03:09 MARIO kernel: vnet2 (unregistering): left promiscuous mode
Sep  4 20:03:09 MARIO kernel: br0: port 3(vnet2) entered disabled state
Sep  4 20:03:22 MARIO kernel: pcieport 0000:00:1d.2: Intel SPT PCH root port ACS workaround enabled
Sep  4 20:03:23 MARIO kernel: pcieport 0000:00:1d.2: Intel SPT PCH root port ACS workaround enabled
Sep  4 20:03:28 MARIO kernel: pcieport 0000:00:1d.2: Intel SPT PCH root port ACS workaround enabled
Sep  4 20:03:33 MARIO kernel: pcieport 0000:00:1d.2: Intel SPT PCH root port ACS workaround enabled
Sep  4 20:03:34 MARIO kernel: pcieport 0000:00:1d.2: Intel SPT PCH root port ACS workaround enabled
Sep  4 20:03:37 MARIO kernel: pcieport 0000:00:1d.2: Intel SPT PCH root port ACS workaround enabled
Sep  4 20:03:37 MARIO kernel: pcieport 0000:00:1d.2: Intel SPT PCH root port ACS workaround enabled
Sep  4 20:03:43 MARIO kernel: intel_vgpu_mdev 68af120f-0815-411f-8a18-28c0811b924c: Adding to iommu group 13
Sep  4 20:03:45 MARIO kernel: br0: port 3(vnet3) entered blocking state
Sep  4 20:03:45 MARIO kernel: br0: port 3(vnet3) entered disabled state
Sep  4 20:03:45 MARIO kernel: vnet3: entered allmulticast mode
Sep  4 20:03:45 MARIO kernel: vnet3: entered promiscuous mode
Sep  4 20:03:45 MARIO kernel: br0: port 3(vnet3) entered blocking state
Sep  4 20:03:45 MARIO kernel: br0: port 3(vnet3) entered forwarding state
Sep  4 20:03:50 MARIO kernel: pcieport 0000:00:1d.2: Intel SPT PCH root port ACS workaround enabled
Sep  4 20:04:31 MARIO flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update

 

but just find some syslog in ubuntu at this time, hope this is useful. and i just had the same problem in debain🙁

Sep  4 20:03:05 ubuntu22s systemd[1]: unattended-upgrades.service: Deactivated successfully.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopping Session 1 of User megumi...
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopping Session 3 of User megumi...
Sep  4 20:03:05 ubuntu22s systemd[1]: Removed slice Slice /system/modprobe.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped target Cloud-init target.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped target Graphical Interface.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped target Host and Network Name Lookups.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped target Timer Units.
Sep  4 20:03:05 ubuntu22s systemd[1]: apt-daily-upgrade.timer: Deactivated successfully.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped Daily apt upgrade and clean activities.
Sep  4 20:03:05 ubuntu22s systemd[1]: apt-daily.timer: Deactivated successfully.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped Daily apt download activities.
Sep  4 20:03:05 ubuntu22s systemd[1]: dpkg-db-backup.timer: Deactivated successfully.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped Daily dpkg database backup timer.
Sep  4 20:03:05 ubuntu22s systemd[1]: e2scrub_all.timer: Deactivated successfully.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped Periodic ext4 Online Metadata Check for All Filesystems.
Sep  4 20:03:05 ubuntu22s systemd[1]: fstrim.timer: Deactivated successfully.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped Discard unused blocks once a week.
Sep  4 20:03:05 ubuntu22s systemd[1]: fwupd-refresh.timer: Deactivated successfully.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped Refresh fwupd metadata regularly.
Sep  4 20:03:05 ubuntu22s systemd[1]: logrotate.timer: Deactivated successfully.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped Daily rotation of log files.
Sep  4 20:03:05 ubuntu22s systemd[1]: man-db.timer: Deactivated successfully.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped Daily man-db regeneration.
Sep  4 20:03:05 ubuntu22s systemd[1]: motd-news.timer: Deactivated successfully.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped Message of the Day.
Sep  4 20:03:05 ubuntu22s systemd[1]: systemd-tmpfiles-clean.timer: Deactivated successfully.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Sep  4 20:03:05 ubuntu22s systemd[1]: update-notifier-download.timer: Deactivated successfully.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped Download data for packages that failed at package install time.
Sep  4 20:03:05 ubuntu22s systemd[1]: update-notifier-motd.timer: Deactivated successfully.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped Check to see whether there is a new version of Ubuntu available.
Sep  4 20:03:05 ubuntu22s systemd[1]: lvm2-lvmpolld.socket: Deactivated successfully.
Sep  4 20:03:05 ubuntu22s systemd[1]: Closed LVM2 poll daemon socket.
Sep  4 20:03:05 ubuntu22s systemd[1]: systemd-rfkill.socket: Deactivated successfully.
Sep  4 20:03:05 ubuntu22s systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopping Availability of block devices...
Sep  4 20:03:05 ubuntu22s systemd[1]: cloud-final.service: Deactivated successfully.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped Execute cloud user/final scripts.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped target Multi-User System.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped target Login Prompts.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopping Modem Manager...
Sep  4 20:03:05 ubuntu22s ModemManager[779]: <info>  caught signal, shutting down...
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopping LSB: automatic crash report generation...
Sep  4 20:03:05 ubuntu22s dockerd[1006]: time="2024-09-04T20:03:05.482724141+08:00" level=info msg="Processing signal 'terminated'"
Sep  4 20:03:05 ubuntu22s systemd[1]: cloud-config.service: Deactivated successfully.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped Apply the settings specified in cloud-config.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped target Cloud-config availability.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopping Regular background program processing daemon...
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopping Docker Application Container Engine...
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopping Create final runtime dir for shutdown pivot root...
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopping Getty on tty1...
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopping irqbalance daemon...
Sep  4 20:03:05 ubuntu22s ModemManager[779]: <info>  ModemManager is shut down
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopping LVM event activation on device 252:3...
Sep  4 20:03:05 ubuntu22s dockerd[1006]: time="2024-09-04T20:03:05.487896793+08:00" level=info msg="Daemon shutdown complete"
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopping Dispatcher daemon for systemd-networkd...
Sep  4 20:03:05 ubuntu22s systemd[1]: plymouth-quit.service: Deactivated successfully.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopped Terminate Plymouth Boot Screen.
Sep  4 20:03:05 ubuntu22s systemd[1]: Stopping System Logging Service...

 

[Megumi]

On 9/4/2024 at 2:15 PM, ich777 said:

Oh sorry this was a typo…

It‘s meant to say „xe“ driver.

after I changed the vgpu pci address on the vm xml to the physical address, the vm finally worked properly.

[sdballer]

I am using modprobe i915 in the go file for Plex acceleration.

Since GVT-g is asking for a blacklist, I assume I can't use both... Docker Plex + VM Windows? (Images below)

 

I currently have all 3 plugins installed.

• Intel GVT-g
• Intel GPU TOP
• GPU Statistics

With the following CPU:

• Intel® Xeon® E-2126G Processor with integrated Intel® UHD Graphics P630

 

Edited September 16 by sdballer

[ich777]

2 hours ago, sdballer said:

 

I am using modprobe i915 in the go file for Plex acceleration.

 

Please post your Diagnostics.

I don‘t know whats going on on your system.

 

BTW please remove that few lines from the go file and reboot, that is not necessary anymore, the plugins will handle all on it‘s own.

[solidrago]

il y aurait un tutoriel pour linux ubuntu ou debian peu importe sur windows tout fonctionne sous linux il détecte bien l'igpu mais continue d'utiliser le qxl comme affichage principal donc je n'ai pas d'accélération 3D, je suis sur mint 22 mate, avec xrdp, j'aimerais avoir l'accélération 3D en rdp puis par la suite installer parsec.

Edited September 20 by solidrago

[ich777]

13 hours ago, solidrago said:

 

il y aurait un tutoriel pour linux ubuntu ou debian peu importe sur windows tout fonctionne sous linux il détecte bien l'igpu mais continue d'utiliser le qxl comme affichage principal donc je n'ai pas d'accélération 3D, je suis sur mint 22 mate, avec xrdp, j'aimerais avoir l'accélération 3D en rdp puis par la suite installer parsec.

 

First of all to make our lifes easier, please only use english in the main forums (use google translate or your prefered translator, english isn‘t my main language too).

 

I never played around with Linux and GVT-g however AFAIK you actually have to have the same Kernel version as on the host to be able to use GVT-g properly.

Sorry but I can‘t help with that request.

However some of the last posts in the tread where from a user who had GVT-g running with Linux, granted I‘m not 100% sure what Distribution he was running.

[Patty92]

Hey @ich777,

 

ich habe mal eine kleine Verständnisfrage.
Soll es mit dem Plugin möglich sein mehrere VM's gleichzeit damit laufen lassen zu können oder funktioniert das so nicht?

 

Ich habe bei mir folgende Konstellation.

 

VM1: Läuft mit Intel GVT-g - funktioniert
VM2: Start mit Intel GVT-g - funktioniert nicht

 

VM2: Läuft mit Intel GVT-g - funktioniert
VM1: Start mit Intel GVT-g - funktioniert nicht

 

Ich kann also beide Maschinen mit der iGPU "ausstatten" aber dann nur eine zur gleichen Zeit laufen lassen.
Ist das so korrekt oder passt da was bei mir nicht?

 

Danke im Voraus.

 

Grüße Patty

 

 

(Translate vom deepl.com)

 

Hey,

I have a small comprehension question.
Should it be possible to run several VMs at the same time with the plugin or does it not work that way?

 

I have the following constellation.

 

VM1: Runs with Intel GVT-g - works
VM2: Start with Intel GVT-g - does not work

 

VM2: Runs with Intel GVT-g - works
VM1: Start with Intel GVT-g - does not work

 

So I can “equip” both machines with the iGPU but then only run one at a time.
Is this correct or is there something wrong?

 

Thanks in advance.

 

Regards Patty

[ich777]

5 hours ago, Patty92 said:

So I can “equip” both machines with the iGPU but then only run one at a time.
Is this correct or is there something wrong?

Depends on your hardware and also the vGPU that you've created in the plugin which you've assigned to the VM.

You should get warnings in your syslog when your hardware isn't capable starting a second VM that you are running out of memory on your iGPU IIRC.

 

However some users where able to run two or even three VMs (and the iGPU on the Host for Docker) with GVT-g but on most Motherboards only one or maybe two simultaneous VMs will work with GVT-g.

 

Maybe @alturismo can add something here.

[alturismo]

20 hours ago, Patty92 said:

Ist das so korrekt oder passt da was bei mir nicht?

Nope, not correct 

 

I always had 2++ simultaneously running, even my Mainboard only allowed 256mb vram, even BIOS is set to 1024mb.

 

may look at your VM configs in XML view that the passed vgpu's have unique uid's.

 

or look at your logs (syslog and/or VM log) if there are any decent errors when starting the 2nd VM.

[Patty92]

I had already checked that there are different id's in the XML, which is fine.

I haven't looked at the logs yet, when starting the 2nd vm I already get a pop up error during startup. 
Should I perhaps open a separate thread here?

Greetings Patty

[ich777]

8 minutes ago, Patty92 said:

Should I perhaps open a separate thread here?

No just post here.
However just to make it clear, not every hardware supports multiple vGPUs, that always depends how it's implemented in the Firmware (BIOS) and since GVT-g is almost abonded from Intel most manufacturers don't bother to implement it correctly, one user in this thread did even a deep dive and said that some settings in the BIOS even doesn't take effect for GVT-g which the usually should.