[2022-07-09T16:35:57+0200] [ALPM] installed libxvmc (1.0.13-1)
[2022-07-09T16:35:57+0200] [ALPM] installed xf86-video-intel (1:2.99.917+916+g31486f40-2)
The output of "sudo dmesg | grep drm" did not change in the VM.
]]>> qemu-system-x86_64 -cdrom $cdr -boot order=a -drive file=$hdf,format=raw -m 4G -enable-kvm -machine q35 -device intel-iommu -cpu host -device virtio-vga-gl -display sdl,gl=on -device intel-hda -device hda-duplex
The problem really seems to be Virt-Manager.
Thank you very much!!!!!
Edit: The problem is not virt-manager but SPICE.
]]>edit: BTW. did you try to change the offset for the audio channel?
I wont guarantee it does 'anything' for you but it's worth a try I think
That is also the case with me. Already from the beginning in Virt-manager. But according to Wiki should be:
[drm] virgl 3d acceleration enabled
It could be the message is old and the one you see now is the current(new)?
I like the terminal output... very interesting. I have to think over the options. smile
'man qemu' is your biggest friend here, everything is in there and there is a lot of info on other distro fora & wiki's - like Gentoo or RedHat F.I.
I still like it. Just add USB devices (Webcam/ USB-Stick) to do video chats for work in M$ Teams or something. Add network cards... It's very quick and easy for me.
I wish there was the easy option to export the Qemu commando line from a Virt-Manager VM.
(And I have(!) to use Windows because the driver for my Logitech vf0770 webcam quite stupidly no longer works with new kernels. I used it many years with ubuntu and at least some months with arch. In a win10VM the webcam works)
All these can be run (easily) with CLI options just start reading man pages and wiki's and you'll get there + it gives enormous insight!
edit: I remember this thread about running Windows10-Qemu-CLI, there is a lot of extra info too:
https://bbs.archlinux.org/viewtopic.php?id=274354
What I mean is if you start the VM does X start?
Yes X starts.
There is no 'nedev' in my line, there is 'netdev'
Works flawless for me.
Btw: if you execute 'glxinfo' in the guest you should see something similar to the next output:
direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Mesa/X.org (0x1af4) Device: virgl (0x1010) Version: 22.1.2 Accelerated: yes Video memory: 0MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 4.3 Max compat profile version: 3.1 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Mesa/X.org OpenGL renderer string: virgl
To me that indicates 'virgl' is doing it's job, maybe someone can confirm that?
edit: use 'glxinfo -B' to get the above output immediately (see) man glxinfo
That is also the case with me. Already from the beginning in Virt-manager. But according to Wiki should be:
[drm] virgl 3d acceleration enabled
@ Lone_Wolf does this work for you?
>the correct line:
I like the terminal output... very interesting. I have to think over the options.
I don't like using virt-manager at all sad I very much dislike it kudos to anyone who is able to use that (in my eyes) POS...
CLI is the way to go;)
I still like it. Just add USB devices (Webcam/ USB-Stick) to do video chats for work in M$ Teams or something. Add network cards... It's very quick and easy for me.
I wish there was the easy option to export the Qemu commando line from a Virt-Manager VM.
(And I have(!) to use Windows because the driver for my Logitech vf0770 webcam quite stupidly no longer works with new kernels. I used it many years with ubuntu and at least some months with arch. In a win10VM the webcam works)
But what this topic is about: Is the picture and sound of a Youtube video in sync in your VM?
And: Thank you for trying to help me.
]]>qemu-system-x86_64 -boot order=a,menu=on,reboot-timeout=5000 -m size=3072,slots=0,maxmem=3221225472 -k en-us -name archlinux-lightdm-2022.06.22-x86_64.iso,process=archlinux-lightdm-2022.06.22-x86_64.iso_0 -device virtio-scsi-pci,id=scsi0 -device virtio-vga-gl -display sdl,gl=on -audiodev pa,id=snd0 -device ich9-intel-hda -device hda-output,audiodev=snd0 -device virtio-net-pci,romfile=,netdev=net0 -netdev user,id=net0,hostfwd=tcp::-:22 -machine type=q35,accel=kvm,usb=on,pcspk-audiodev=snd0 -global ICH9-LPC.disable_s3=1 -enable-kvm -device scsi-cd,bus=scsi0.0,drive=cdrom0 -drive id=cdrom0,if=none,format=raw,media=cdrom,read-only=on,file=/home/mark/archiso/iso-and-img/iso-img/archlinux-lightdm-2022.06.22-x86_64.iso -serial stdio -no-reboot
How do you mean that? "not try to enable "virtio 3d acceleration"?" If I use:
> qemu-system-x86_64 -cdrom $cdr -boot order=a -drive file=$hdf,format=raw -m 8G -enable-kvm -machine q35 -device intel-iommu -cpu host
The vm starts fine.
What I mean is if you start the VM does X start?
I can not start your commado,
>qemu-system-x86_64: -nedev: invalid optionI cannot find this option (-nedev) in the qemu manpage.
There is no 'nedev' in my line, there is 'netdev'
But by the way, I like qemu from the command line. It seems to start faster than via virt-manager.
I don't like using virt-manager at all I very much dislike it kudos to anyone who is able to use that (in my eyes) POS...
CLI is the way to go;)
Btw: if you execute 'glxinfo' in the guest you should see something similar to the next output:
...
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Mesa/X.org (0x1af4)
Device: virgl (0x1010)
Version: 22.1.2
Accelerated: yes
Video memory: 0MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.3
Max compat profile version: 3.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL vendor string: Mesa/X.org
OpenGL renderer string: virgl
...
To me that indicates 'virgl' is doing it's job, maybe someone can confirm that?
edit: use 'glxinfo -B' to get the above output immediately (see) man glxinfo
Yeah I made a mistake with that line 'nedev' I will paste the result in a few minutes!
]]>[drm] pci: virtio-vga detected
[drm] features: +virgl +edid
...
gl_version 46 - core profile enabled
GLSL feature level 460
This is what happens to me. But Virgl does not seem to be active.
> Question/s: does X start on the guest if you do not try to enable 'virtio 3d acceleration'?
How do you mean that? "not try to enable "virtio 3d acceleration"?" If I use:
> qemu-system-x86_64 -cdrom $cdr -boot order=a -drive file=$hdf,format=raw -m 8G -enable-kvm -machine q35 -device intel-iommu -cpu host
The vm starts fine.
I'll show you the command I used to start my guest, but, it runs from ISO not an HD-image!
I can not start your commado, I do not even know how to build a custom ISO. Someday I will learn. I am a noob. But I tried it with another ISO file:
>sh vmscript.sh D
>qemu-system-x86_64: -nedev: invalid option
I cannot find this option (-nedev) in the qemu manpage.
But by the way, I like qemu from the command line. It seems to start faster than via virt-manager.
]]>-device virtio-vga-gl -display gtk,gl=on
After that calling dmesg for drm
[drm] pci: virtio-vga detected
[drm] features: +virgl +edid
But I don't get that specific message: 'virgl 3d acceleration enabled' ...
Loading the guest also provides this message(host)
gl_version 46 - core profile enabled
GLSL feature level 460
edit: my line is based on variables, changed that..;)
Question/s: does X start on the guest if you do not try to enable 'virtio 3d acceleration'?
I'll show you the command I used to start my guest, but, it runs from ISO not an HD-image!
qemu-system-x86_64 -boot order=d,menu=on,reboot-timeout=5000 -m size=3072,slots=0,maxmem=3221225472 -k en-us -name archlinux-lightdm-2022.06.21-x86_64.iso,process=archlinux-lightdm-2022.06.21-x86_64.iso_0 -device virtio-scsi-pci,id=scsi0 -device virtio-vga-gl -display gtk,gl=on -audiodev pa,id=snd0 -device ich9-intel-hda -device hda-output,audiodev=snd0 -device virtio-net-pci,romfile=,netdev=net0 -nedev user,id=net0,hostfwd=tcp::60032-:22 -machine type=q35,accel=kvm,usb=on,pcspk-audiodev=snd0 -global ICH9-LPC.disable_s3=1 -enable-kvm -device scsi-cd,bus=scsi0.0,drive=cdrom0 -drive id=cdrom0,if=none,format=raw,media=cdrom,read-only=on,file=/home/mark/archiso/iso-and-img/iso-img/archlinux-lightdm-2022.06.21-x86_64.iso -serial stdio -no-reboot
You can use your own tweaked 'run_archiso.sh' - that's what I do...
(see)https://gitlab.archlinux.org/archlinux/ … archiso.sh - why invent a new wheel if only the tires need air...;)
Lone_Wolf and qinohe: Does "virtio 3d acceleration" works for you?
> Currently a work in progress, supporting only very recent (>= 4.4) Linux guests with mesa (>=11.2) compiled with the option gallium-drivers=virgl
Does it work on a arch guest? Mesa is compiled with gallium-drivers=virgl
https://github.com/archlinux/svntogit-p … k/PKGBUILD
qemu-system-x86_64 -cdrom $cdr -boot order=a -drive file=$hdf,format=raw -m 8G -enable-kvm -machine q35 -device intel-iommu -cpu host -device virtio-vga-gl -display sdl,gl=on
console output:
> gl_version 46 - core profile enabled
> GLSL feature level 460
If I start with -vga vmware:
qemu-system-x86_64 -cdrom $cdr -boot order=a -drive file=$hdf,format=raw -m 8G -enable-kvm -machine q35 -device intel-iommu -cpu host -vga vmware
X won't start.
]]>[ 2.878462] [drm] pci: virtio-vga detected at 0000:00:01.0
basic functionality of virtio is active, but there's no sign of a line with [drm] virgl 3d acceleration enabled so that part probably doesn't work .
Apart from the special setup, check virglrenderer is installed on the host.
]]>By the way, I use a Windows 10VM to play "The Settlers 4". The picture and sound are synchronous.
]]>