Timeline for How to set video memory with KVM/QEMU virtualization?
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 7, 2019 at 12:39 | history | edited | Stephen Kitt | CC BY-SA 4.0 |
Typo, thanks Jean-Michaël!
|
| Aug 17, 2018 at 11:42 | comment | added | Stephen Kitt |
Looking at the contents of the VMware Tools ISO, it looks like it doesn’t install a graphics driver anyway — it might be worth trying Windows as-is with -vga vmware, perhaps the driver is built-in nowadays. (I’m following the QEMU documentation and source code; I don’t have a Windows VM to test with. Linux VMs report the correct amount of video memory with -vga std and -vga vmware.)
|
|
| Aug 16, 2018 at 19:22 | comment | added | Josh Pinto | I tried installing it but it said I needed to run it in a VM. Apparently it doesn't recognize KVM/QEMU as a valid means of virtualization. | |
| Aug 16, 2018 at 18:47 | comment | added | Stephen Kitt | See here. | |
| Aug 16, 2018 at 17:42 | comment | added | Josh Pinto | Where do I get VMWare Tools? I DuckDuckGo searched it and found its docs and they only mentioned if I started Windows in VMWare, not in QEMU. No download link given, only how to get it from within VMWare itself. | |
| Aug 16, 2018 at 17:14 | comment | added | Stephen Kitt | Not on the command line, in the QEMU console (connect to QEMU, then Ctrl-Alt-2). | |
| Aug 16, 2018 at 17:14 | comment | added | Josh Pinto |
For me info ramblock returns: info: No menu item 'ramblock' in node '(dir)Top'.
|
|
| Aug 16, 2018 at 17:10 | comment | added | Stephen Kitt |
Right, so it should work; perhaps Windows 10 only uses 32 MiB on a VESA device (which is the default in QEMU 2.2 and later). In the QEMU console, info ramblock will show the amounts of memory allocated to the various memory blocks, including video memory; for me it correctly reflects the vgamem_mb property. If you install VMware Tools in Windows you could try -vga vmware instead.
|
|
| Aug 16, 2018 at 16:30 | comment | added | Josh Pinto | QEMU: 2.12.0. Kernel: 4.17.13. OS: openSUSE Tumbleweed. | |
| Aug 16, 2018 at 16:28 | comment | added | Stephen Kitt | OK, and what version of QEMU are you using? | |
| Aug 16, 2018 at 16:25 | comment | added | Josh Pinto |
I used the above -device specification, although I combined it with the qemu-kvm command I was using, namely: qemu-kvm -boot d /data/VMs/win10.img -m 8192 -smp 3 -soundhw hda -device VGA,vgamem_mb=128. There's an error mentioned relating to the audio (audio: Unknown audio driver pa'`), but as that's not graphics related I didn't think it counted.
|
|
| Aug 16, 2018 at 16:21 | comment | added | Stephen Kitt | What driver are you using? | |
| Aug 16, 2018 at 16:20 | comment | added | Josh Pinto | I tried this with a Windows 10 VM and it's still saying there's only 32 MB video memory available to it, even though I allocated 128 MB and there's no error at the command-line. | |
| Aug 16, 2018 at 16:19 | vote | accept | Josh Pinto | ||
| Aug 16, 2018 at 16:19 | |||||
| Aug 16, 2018 at 16:18 | comment | added | Stephen Kitt | I have no idea, sorry... | |
| Aug 16, 2018 at 16:00 | comment | added | Josh Pinto | Thanks, one side question. Which driver would be best for a Windows 10 VM? | |
| Aug 16, 2018 at 15:38 | history | answered | Stephen Kitt | CC BY-SA 4.0 |