Issue running maps

[adieyal]

This issue might be completely unrelated to virtualization but I wanted to rule it out. Big Sur works perfectly, except that Maps and Find My don't show any maps (see screenshot)

Is there any chance that it could be related to the container?

OS related issued, please help us identify the issue by posting the output of this

uname -a
; echo "${DISPLAY}"
; echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs
; grep NAME /etc/os-release
; df -h .
; qemu-system-x86_64 --version
; libvirtd --version
; free -mh
; nproc
; egrep -c '(svm|vmx)' /proc/cpuinfo
; ls -lha /dev/kvm
; ls -lha /tmp/.X11-unix/
; ps aux | grep dockerd
; docker ps | grep osx
; grep "docker|kvm|virt" /etc/group
Linux blackbox 5.10.70-1-MANJARO #1 SMP PREEMPT Thu Sep 30 15:29:01 UTC 2021 x86_64 GNU/Linux
:1
1
NAME="Manjaro Linux"
PRETTY_NAME="Manjaro Linux"
Filesystem Size Used Avail Use% Mounted on
tmpfs 32G 203M 32G 1% /tmp
QEMU emulator version 6.1.0
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers
libvirtd (libvirt) 7.8.0
total used free shared buff/cache available
Mem: 62Gi 17Gi 16Gi 443Mi 28Gi 44Gi
Swap: 69Gi 4.8Gi 64Gi
24
24
crw-rw-rw- 1 root kvm 10, 232 Nov 18 10:24 /dev/kvm
total 0
drwxrwxrwt 2 root root 60 Nov 12 10:34 .
drwxrwxrwt 26 root root 700 Nov 18 10:30 ..
srwxrwxrwx 1 root xyz 0 Nov 12 10:33 X1
root 1228 0.0 0.0 6735696 40440 ? Ssl Nov12 5:00 /usr/bin/dockerd -H fd://
xyz 587271 0.0 0.0 6496 2312 pts/4 S+ 10:30 0:00 grep dockerd
6c38ef8b1756 sickcodes/docker-osx:big-sur "/bin/bash -c 'sudo …" 2 days ago Up 6 minutes 0.0.0.0:50922->10022/tcp, :::50922->10022/tcp happy_proskuriakova
kvm:x:992:xyz
docker:x:963:xyz
libvirt:x:961:xyz

[sickcodes]

There are no GPS devices that I know of that the container could access to locate itself other than IP based and neighboring wifi networks.

Have you tried zooming out? Might not work unfortunately

[adieyal]

The problem isn't the GPS, just that the maps aren't displaying. It could be a million things, just wanted to rule out the container being the cause.

[sickcodes]

Android apparently has is in their hard fork of QEMU https://android.googlesource.com/platform/sdk/+/ics-mr0/emulator/gps/gps_qemu.c

There may be an App Store app that lets you fake the location or some other HID

Does google maps work?

A simple solution for local setups would be a dongle passed thru to the container:

https://forums.ybw.com/index.php?threads/ive-found-a-cheap-usb-gps-dongle-which-works-with-opencpn-on-mac-os-x.455598/

There may be some emulator or Realtek style testing dummy GPS card.

I personally haven't opened maps ever in the container, so I can't rule out host issues on your side.

However this is interesting, perhaps there is a kext available

[prusswan]

likely related to 3d/gpu hardware acceleration: https://communities.vmware.com/t5/VMware-Fusion-Discussions/Translucent-displays-sluggish-Maps-is-dark/td-p/2832898

@sickcodes Do you know the current 3d capabilities of docker-osx? Is Maps working for anybody or any configuration at all?

[ExpensivePerson]

Same issue here.

Maps and Find My don't show any maps. Tried to use github.com/seemoo-lab/openhaystack. Big Sur is needed. This app comes with an native app, which also has apple maps included. Here, too, the map is gray.

• apple maps isn't working
• openhaystack (using apple maps also) doesn't work.
• google maps on safari is working fine.

maybe @prusswan is right and it has to do something with the hw acc.

System info:

• Ubuntu 23.10 x86_64
• Docker version 25.0.3, build 4debf41
• QEMU emulator version 8.0.4

but thx for this great project @sickcodes

[aptalca]

It's likely an issue with the virtual graphics driver not supporting whatever 3d/hw acceleration the maps and find my apps need.

I have the same issue when I run a hackintosh QEMU VM (Big Sur) with the qemu virtio graphics adapter. Maps and Find My show blank maps. Also in Safari, many web pages display the info for a brief second and then most of the contents become invisible. In that case, if you open another app in the foreground, the contents become visible again.

I believe if you do a gpu passthrough, those issues are resolved, suggesting the culprit is likely the virtual display drivers.

[prusswan]

I believe if you do a gpu passthrough, those issues are resolved, suggesting the culprit is likely the virtual display drivers.

That's probable. Could someone using gpu passthrough confirm? I suppose the list of supported gpus mentioned here is still applicable.