starred/Docker-OSX-sickcodes
1
0
Fork 0
mirror of https://github.com/sickcodes/Docker-OSX.git synced 2026-01-14 07:33:30 +01:00
Code Issues 411 Packages Projects Releases Wiki Activity

Define display memory (VRAM) #11

New Issue
Closed
opened 2025-12-29 05:19:37 +01:00 by adam · 11 comments
adam commented 2025-12-29 05:19:37 +01:00
Owner
Copy Link

Originally created by @antoineraulin on GitHub (Jun 5, 2020).

Hi,
I noticed that macos runs with 7~9 MB of vram on this project, which doesn't seem like much even if the system works properly anyway. I looked up how to increase the vram of a virtualized system with qemu-kvm, but most of the answers say to add a vga device with the desired vram size as an option, but this creates a conflict with the vga vmware option of qemu. Does anyone have an idea how to increase the vram for the current configuration?

Originally created by @antoineraulin on GitHub (Jun 5, 2020). Hi, I noticed that macos runs with 7~9 MB of vram on this project, which doesn't seem like much even if the system works properly anyway. I looked up how to increase the vram of a virtualized system with qemu-kvm, but most of the answers say to add a vga device with the desired vram size as an option, but this creates a conflict with the vga vmware option of qemu. Does anyone have an idea how to increase the vram for the current configuration?
adam closed this issue 2025-12-29 05:19:37 +01:00
adam commented 2025-12-29 05:19:38 +01:00
Author
Owner
Copy Link

@sickcodes commented on GitHub (Jun 5, 2020):

Some notes here:
037a3edc8d/notes.md

If you can figure it out, write the additional qemu options here and I (or anyone who wants to contribute) can submit a pull request

@sickcodes commented on GitHub (Jun 5, 2020): Some notes here: https://github.com/kholia/OSX-KVM/blob/037a3edc8ddffb28940e59a54553ab5408276383/notes.md If you can figure it out, write the additional qemu options here and I (or anyone who wants to contribute) can submit a pull request
adam commented 2025-12-29 05:19:38 +01:00
Author
Owner
Copy Link

@antoineraulin commented on GitHub (Jun 5, 2020):

It seems to be related to the "Accelerated Graphics" paragraph of the file you're talking about, the document only mentions the Clover bootloader which is not used here. But I'll look into it more tomorrow, thank you !

@antoineraulin commented on GitHub (Jun 5, 2020): It seems to be related to the "Accelerated Graphics" paragraph of the file you're talking about, the document only mentions the Clover bootloader which is not used here. But I'll look into it more tomorrow, thank you !
adam commented 2025-12-29 05:19:38 +01:00
Author
Owner
Copy Link

@sickcodes commented on GitHub (Jun 5, 2020):

You can use the clover boot loader actually it’s in directory /home/arch/OSX-KVM

docker run --privileged v /tmp/.X11-unix:/tmp/.X11-unix -it sickcodes/docker-osx /bin/bash

Run the Perl script to change the networking from tap to user mode on boot-macOS-NG.sh

Also change the ./backup to ./ on the ovmf line

I used to use the clover method but the new open boot one launches 1920x1080

@sickcodes commented on GitHub (Jun 5, 2020): You can use the clover boot loader actually it’s in directory /home/arch/OSX-KVM docker run --privileged v /tmp/.X11-unix:/tmp/.X11-unix -it sickcodes/docker-osx /bin/bash Run the Perl script to change the networking from tap to user mode on boot-macOS-NG.sh Also change the ./backup to ./ on the ovmf line I used to use the clover method but the new open boot one launches 1920x1080
adam commented 2025-12-29 05:19:39 +01:00
Author
Owner
Copy Link

@antoineraulin commented on GitHub (Jun 5, 2020):

I'm having trouble getting clover to work, whether I'm using the clover from the Mojave folder or the Catalina folder (knowing that I upgraded from Mojave to Catalina my main disk) I always have this message appearing there
osx

@antoineraulin commented on GitHub (Jun 5, 2020): I'm having trouble getting clover to work, whether I'm using the clover from the Mojave folder or the Catalina folder (knowing that I upgraded from Mojave to Catalina my main disk) I always have this message appearing there ![osx](https://user-images.githubusercontent.com/25278917/83918095-55770900-a778-11ea-9fa1-995000e2868e.png)
adam commented 2025-12-29 05:19:39 +01:00
Author
Owner
Copy Link

@sickcodes commented on GitHub (Jun 6, 2020):

Download OSX-KVM from the upstream source https://github.com/kholia/OSX-KVM,

Import the Catalina xml into virt-manager and change the networking to user mode (see the Perl line in my Dockerfile)

Replace the .img with the one you have made in your container (stored in /var/lib/docker/....). Instructions regarding how to find the img in the readme.

Let me know if that helps

@sickcodes commented on GitHub (Jun 6, 2020): Download OSX-KVM from the upstream source https://github.com/kholia/OSX-KVM, Import the Catalina xml into virt-manager and change the networking to user mode (see the Perl line in my Dockerfile) Replace the .img with the one you have made in your container (stored in /var/lib/docker/....). Instructions regarding how to find the img in the readme. Let me know if that helps
adam commented 2025-12-29 05:19:40 +01:00
Author
Owner
Copy Link

@sickcodes commented on GitHub (Jun 6, 2020):

I’ll upload my virt manager xml shortly so anyone who wants to undockerize it can. They would have to install the packages, however.

@sickcodes commented on GitHub (Jun 6, 2020): I’ll upload my virt manager xml shortly so anyone who wants to undockerize it can. They would have to install the packages, however.
adam commented 2025-12-29 05:19:40 +01:00
Author
Owner
Copy Link

@antoineraulin commented on GitHub (Jun 6, 2020):

I've tried several things to try to increase the vram:

  • since qemu uses vga vmware I thought that VMware’s tools could help me. Well without suspense it didn't do anything except adding screen configurations and thus more possible resolutions in the macOS settings.

  • I also tried to change the device that handles the display, I managed to set the vram in the qemu command, but like for the VMware extension it didn't do much.

I still couldn't get clover to work. And with the virt-manager my keyboard and mouse aren't transmitted.

When your libvirt config file will be available I’ll try again.

@antoineraulin commented on GitHub (Jun 6, 2020): I've tried several things to try to increase the vram: - since qemu uses vga vmware I thought that VMware’s tools could help me. Well without suspense it didn't do anything except adding screen configurations and thus more possible resolutions in the macOS settings. - I also tried to change the device that handles the display, I managed to set the vram in the qemu command, but like for the VMware extension it didn't do much. I still couldn't get clover to work. And with the virt-manager my keyboard and mouse aren't transmitted. When your libvirt config file will be available I’ll try again.
adam commented 2025-12-29 05:19:41 +01:00
Author
Owner
Copy Link

@sickcodes commented on GitHub (Jun 7, 2020):

My libvirt one was OpenCore-Boot actually but here's the one I used to boot, first thing you'll notice is it starts in 1000x1000

MY_OPTIONS="+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check"

OVMF="./"

qemu-system-x86_64 -enable-kvm -m 5500 -cpu Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,$MY_OPTIONS\
-machine q35 \
-smp 4,cores=4 \
-usb -device usb-kbd -device usb-tablet \
-device isa-applesmc,osk="ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" \
-drive if=pflash,format=raw,file=$OVMF/OVMF_CODE.fd \
-drive if=pflash,format=raw,file=$OVMF/OVMF_VARS-1024x768.fd \
-smbios type=2 \
-device ich9-intel-hda -device hda-duplex \
-device ich9-ahci,id=sata \
-drive id=Clover,if=none,snapshot=on,format=qcow2,file=./'Mojave/CloverNG.qcow2' \
-device ide-hd,bus=sata.2,drive=Clover \
-device ide-hd,bus=sata.3,drive=InstallMedia \
-drive id=InstallMedia,if=none,file=BaseSystem.img,format=raw \
-drive id=MacHDD,if=none,file=./mac_hdd_ng.img,format=qcow2 \
-device ide-hd,bus=sata.4,drive=MacHDD \
-netdev user,id=net0 -device vmxnet3,netdev=net0,id=net0,mac=52:54:00:09:49:17 \
-monitor stdio \
-vga vmware
@sickcodes commented on GitHub (Jun 7, 2020): My libvirt one was OpenCore-Boot actually but here's the one I used to boot, first thing you'll notice is it starts in 1000x1000 `MY_OPTIONS="+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check"` `OVMF="./"` ``` qemu-system-x86_64 -enable-kvm -m 5500 -cpu Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,$MY_OPTIONS\ -machine q35 \ -smp 4,cores=4 \ -usb -device usb-kbd -device usb-tablet \ -device isa-applesmc,osk="ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" \ -drive if=pflash,format=raw,file=$OVMF/OVMF_CODE.fd \ -drive if=pflash,format=raw,file=$OVMF/OVMF_VARS-1024x768.fd \ -smbios type=2 \ -device ich9-intel-hda -device hda-duplex \ -device ich9-ahci,id=sata \ -drive id=Clover,if=none,snapshot=on,format=qcow2,file=./'Mojave/CloverNG.qcow2' \ -device ide-hd,bus=sata.2,drive=Clover \ -device ide-hd,bus=sata.3,drive=InstallMedia \ -drive id=InstallMedia,if=none,file=BaseSystem.img,format=raw \ -drive id=MacHDD,if=none,file=./mac_hdd_ng.img,format=qcow2 \ -device ide-hd,bus=sata.4,drive=MacHDD \ -netdev user,id=net0 -device vmxnet3,netdev=net0,id=net0,mac=52:54:00:09:49:17 \ -monitor stdio \ -vga vmware ```
adam commented 2025-12-29 05:19:41 +01:00
Author
Owner
Copy Link

@antoineraulin commented on GitHub (Jun 8, 2020):

thanks for your config, actually it looks pretty much like the one I came up with after multiple small adjustments, I feel like one of the only ways to get more vram would be to do a gpu-passthrought. Anyway, thanks for the effort you put into this project, it's wonderful.
Feel free to close this issue if you want.

@antoineraulin commented on GitHub (Jun 8, 2020): thanks for your config, actually it looks pretty much like the one I came up with after multiple small adjustments, I feel like one of the only ways to get more vram would be to do a gpu-passthrought. Anyway, thanks for the effort you put into this project, it's wonderful. Feel free to close this issue if you want.
adam commented 2025-12-29 05:19:42 +01:00
Author
Owner
Copy Link

@sickcodes commented on GitHub (Jun 8, 2020):

Thanks dude! Will be following upstream developments and make appropriate changes if they come through.

@sickcodes commented on GitHub (Jun 8, 2020): Thanks dude! Will be following upstream developments and make appropriate changes if they come through.
adam commented 2025-12-29 05:19:42 +01:00
Author
Owner
Copy Link

@uniquekey-coder commented on GitHub (Nov 30, 2024):

hi，Is there any new progress？

@uniquekey-coder commented on GitHub (Nov 30, 2024): hi，Is there any new progress？
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
following upstream developments
good first issue
help wanted
invalid
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Docker-OSX-sickcodes#11
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?