In Memory Panic VNC #80

@sickcodes commented on GitHub (Oct 18, 2020):

I can't replicate it as the OS won't download lol, will try again later without VPN

@sickcodes commented on GitHub (Oct 18, 2020): I can't replicate it as the OS won't download lol, will try again later without VPN

adam commented

@UliPrantz commented on GitHub (Nov 10, 2020):

Got the same problem but also only got qemu 2.11.1, which is considered the newest version by apt. Is there any easy way to install qemu v5.0.1 under ubuntu? I only found this guide but building it manually seems a little bit too much

@UliPrantz commented on GitHub (Nov 10, 2020): Got the same problem but also only got qemu 2.11.1, which is considered the newest version by apt. Is there any easy way to install qemu v5.0.1 under ubuntu? I only found [this guide](https://www.reddit.com/r/VFIO/comments/hkezeq/how_to_set_up_qemu_500_on_ubuntu_1804/) but building it manually seems a little bit too much

adam commented

@UliPrantz commented on GitHub (Nov 10, 2020):

Tried with new qemu version and still got the same error:

Output of virsh -c qemu:///system version --daemon is:

Compiled against library: libvirt 4.0.0
Using library: libvirt 4.0.0
Using API: QEMU 4.0.0
Running hypervisor: QEMU 5.1.0
Running against daemon: 4.0.0

@UliPrantz commented on GitHub (Nov 10, 2020): Tried with new qemu version and still got the same error: Output of `virsh -c qemu:///system version --daemon` is: ``` Compiled against library: libvirt 4.0.0 Using library: libvirt 4.0.0 Using API: QEMU 4.0.0 Running hypervisor: QEMU 5.1.0 Running against daemon: 4.0.0 ```

adam commented

2025-12-29 05:21:43 +01:00

@sickcodes commented on GitHub (Dec 4, 2020):

@UliPrantz You should install qemu latest from the ubuntu repo. If you don't have qemu 5 in ubuntu, consider upgrading the distro ti latest.

Virsh and qemu are inside the Docker image btw

@sickcodes commented on GitHub (Dec 4, 2020): @UliPrantz You should install qemu latest from the ubuntu repo. If you don't have qemu 5 in ubuntu, consider upgrading the distro ti latest. Virsh and qemu are inside the Docker image btw

adam commented

@jamestalbot3 commented on GitHub (Dec 10, 2020):

Was running into this problem today. Crapped out at the exact same point. Using the alternate run command solved it for me. Not sure which command did it, but just use trial and error.

@jamestalbot3 commented on GitHub (Dec 10, 2020): Was running into this problem today. Crapped out at the exact same point. Using the alternate run command solved it for me. Not sure which command did it, but just use trial and error.

adam commented

2025-12-29 05:21:43 +01:00

@emsi commented on GitHub (Mar 11, 2021):

Same here though on regular images:

Both big sur and catalina images stared as:

docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY:-:0.0}" sickcodes/docker-osx:big-sur

My workstation has 2 CPUs with 8 cores (16 threads each). Usually it's not OK to use more than 16 vCPUs for virtualization in my setup. Virtualization is enabled:

egrep -c '(svm|vmx)' /proc/cpuinfo
32

@emsi commented on GitHub (Mar 11, 2021): Same here though on regular images: ![image](https://user-images.githubusercontent.com/433383/110834917-68d27a00-829e-11eb-8e92-4395814fa4b5.png) Both big sur and catalina images stared as: `docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY:-:0.0}" sickcodes/docker-osx:big-sur` My workstation has 2 CPUs with 8 cores (16 threads each). Usually it's not OK to use more than 16 vCPUs for virtualization in my setup. Virtualization is enabled: ``` egrep -c '(svm|vmx)' /proc/cpuinfo 32 ```

adam commented

2025-12-29 05:21:43 +01:00

@emsi commented on GitHub (Mar 11, 2021):

m'kay... seems my virtualization beast despite having 128GB of ram and 32 threads does not sport avx2:

emsi@ubu:~$ egrep -c 'avx' /proc/cpuinfo
32
emsi@ubu:~$ egrep -c 'avx2' /proc/cpuinfo
0

As per https://github.com/kholia/OSX-KVM

A CPU with SSE4.1 support is required for >= macOS Sierra
A CPU with AVX2 support is required for >= macOS Mojave

It might be worth to add CPU checks to container startup.

@emsi commented on GitHub (Mar 11, 2021): m'kay... seems my virtualization beast despite having 128GB of ram and 32 threads does not sport avx2: ``` emsi@ubu:~$ egrep -c 'avx' /proc/cpuinfo 32 emsi@ubu:~$ egrep -c 'avx2' /proc/cpuinfo 0 ``` As per https://github.com/kholia/OSX-KVM > A CPU with SSE4.1 support is required for >= macOS Sierra > A CPU with AVX2 support is required for >= macOS Mojave It might be worth to add CPU checks to container startup.

adam commented

@sickcodes commented on GitHub (Mar 13, 2021):

Never seen that error before @emsi thank you for pointing that out! I'll check it shortly using digital ocean

@sickcodes commented on GitHub (Mar 13, 2021): Never seen that error before @emsi thank you for pointing that out! I'll check it shortly using digital ocean

adam commented

@fcastilloec commented on GitHub (Mar 18, 2021):

I'm seeing the exact same error with both Big Sur and Catalina and my CPU does have AVX2:

$ egrep -c 'avx2' /proc/cpuinfo
4
$ egrep -c '(svm|vmx)' /proc/cpuinfo
8

@fcastilloec commented on GitHub (Mar 18, 2021): I'm seeing the exact same error with both Big Sur and Catalina and my CPU does have AVX2: ``` $ egrep -c 'avx2' /proc/cpuinfo 4 $ egrep -c '(svm|vmx)' /proc/cpuinfo 8 ```

adam commented

@sickcodes commented on GitHub (Mar 19, 2021):

I'm seeing the exact same error with both Big Sur and Catalina and my CPU does have AVX2:
$ egrep -c 'avx2' /proc/cpuinfo

4

$ egrep -c '(svm|vmx)' /proc/cpuinfo

8

Can you post the output of https://github.com/sickcodes/Docker-OSX/blob/master/.github/ISSUE_TEMPLATE/issue-running-docker-osx.md

@sickcodes commented on GitHub (Mar 19, 2021): > I'm seeing the exact same error with both Big Sur and Catalina and my CPU does have AVX2: > > ``` > > $ egrep -c 'avx2' /proc/cpuinfo > > 4 > > $ egrep -c '(svm|vmx)' /proc/cpuinfo > > 8 > > ``` > > > > Can you post the output of https://github.com/sickcodes/Docker-OSX/blob/master/.github/ISSUE_TEMPLATE/issue-running-docker-osx.md

adam commented

@fcastilloec commented on GitHub (Mar 19, 2021):

Can you post the output of https://github.com/sickcodes/Docker-OSX/blob/master/.github/ISSUE_TEMPLATE/issue-running-docker-osx.md

Here it is, in the same order as the template:

Linux felipe-desktop 5.8.0-45-generic #51~20.04.1-Ubuntu SMP Tue Feb 23 13:46:31 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
:1
1
NAME="Ubuntu"
PRETTY_NAME="Ubuntu 20.04.2 LTS"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
Filesystem      Size  Used Avail Use% Mounted on
/dev/nvme0n1p2  228G  114G  103G  53% /
QEMU emulator version 4.2.1 (Debian 1:4.2-3ubuntu6.14)
Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers
libvirtd (libvirt) 6.0.0
              total        used        free      shared  buff/cache   available
Mem:           31Gi       6.8Gi       2.3Gi       560Mi        22Gi        23Gi
Swap:         8.0Gi          0B       8.0Gi
4
8
crw-rw----+ 1 root kvm 10, 232 Mar 18 13:22 /dev/kvm
total 16K
drwxrwxrwt  2 root root 4.0K Mar 18 13:24 .
drwxrwxrwt 32 root root  12K Mar 19 10:43 ..
srwxrwxrwx  1 root root    0 Mar 18 13:22 X0
srwxrwxrwx  1 root root    0 Mar 18 13:24 X1
root        1264  0.1  0.3 1316432 122248 ?      Ssl  Mar18   1:35 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

The output of df might be useless since I've set docker with data-root in a different drive, here's the output of the other drive:

Filesystem                    Size  Used Avail Use% Mounted on
/dev/mapper/home_vg-home_ext  963G  556G  359G  61% /mnt/Docker

I've also used this repository ppa:jacob/virtualisation to update QEMU and libvirtd to these values and the issue still happens:

QEMU emulator version 5.0.0 (Debian 1:5.0-5ubuntu6~ppa0)
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
libvirtd (libvirt) 6.6.0

@fcastilloec commented on GitHub (Mar 19, 2021): > Can you post the output of https://github.com/sickcodes/Docker-OSX/blob/master/.github/ISSUE_TEMPLATE/issue-running-docker-osx.md Here it is, in the same order as the template: ``` Linux felipe-desktop 5.8.0-45-generic #51~20.04.1-Ubuntu SMP Tue Feb 23 13:46:31 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux :1 1 NAME="Ubuntu" PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_CODENAME=focal UBUNTU_CODENAME=focal Filesystem Size Used Avail Use% Mounted on /dev/nvme0n1p2 228G 114G 103G 53% / QEMU emulator version 4.2.1 (Debian 1:4.2-3ubuntu6.14) Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers libvirtd (libvirt) 6.0.0 total used free shared buff/cache available Mem: 31Gi 6.8Gi 2.3Gi 560Mi 22Gi 23Gi Swap: 8.0Gi 0B 8.0Gi 4 8 crw-rw----+ 1 root kvm 10, 232 Mar 18 13:22 /dev/kvm total 16K drwxrwxrwt 2 root root 4.0K Mar 18 13:24 . drwxrwxrwt 32 root root 12K Mar 19 10:43 .. srwxrwxrwx 1 root root 0 Mar 18 13:22 X0 srwxrwxrwx 1 root root 0 Mar 18 13:24 X1 root 1264 0.1 0.3 1316432 122248 ? Ssl Mar18 1:35 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock ``` The output of `df` might be useless since I've set docker with `data-root` in a different drive, here's the output of the other drive: ``` Filesystem Size Used Avail Use% Mounted on /dev/mapper/home_vg-home_ext 963G 556G 359G 61% /mnt/Docker ``` I've also used this repository [ppa:jacob/virtualisation](https://launchpad.net/~jacob/+archive/ubuntu/virtualisation?field.series_filter=focal) to update QEMU and `libvirtd` to these values and the issue still happens: ``` QEMU emulator version 5.0.0 (Debian 1:5.0-5ubuntu6~ppa0) Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers libvirtd (libvirt) 6.6.0 ```

adam commented

@sickcodes commented on GitHub (Mar 24, 2021):

chmod 666 /dev/kvm

You also did not post grep "docker\|kvm\|virt" /etc/group

@sickcodes commented on GitHub (Mar 24, 2021): `chmod 666 /dev/kvm` You also did not post `grep "docker\|kvm\|virt" /etc/group`

adam commented

@fcastilloec commented on GitHub (Mar 25, 2021):

Sorry, I guess I didn't select the last line when copy/pasting. Here it is:

$ grep "docker\|kvm\|virt" /etc/group
kvm:x:108:felipe
docker:x:137:felipe
libvirt-dnsmasq:x:140:

Also, I don't think it's necessary to do chmod 666 /dev/kvm because I'm part of the kvm group, so I should be able to read/write. No need to give access to other users.

@fcastilloec commented on GitHub (Mar 25, 2021): Sorry, I guess I didn't select the last line when copy/pasting. Here it is: ``` sh $ grep "docker\|kvm\|virt" /etc/group kvm:x:108:felipe docker:x:137:felipe libvirt-dnsmasq:x:140: ``` Also, I don't think it's necessary to do `chmod 666 /dev/kvm` because I'm part of the `kvm` group, so I should be able to read/write. No need to give access to other users.

adam commented

@redfive2012 commented on GitHub (Jun 28, 2021):

I've used the Ubuntu Focal Backports PPA repo to update QEMU and libvirt, and I'm also getting this crash when trying to start the Big Sur install process. Ubuntu server 20.04.2 LTS 64-bit, dual 6-core Intel CPUs w/Hyperthread (total 24 logical), 32GB RAM. I can give any further details if requested. AVX is supported, but apparently AVX2 is not.

@redfive2012 commented on GitHub (Jun 28, 2021): I've used the Ubuntu Focal Backports PPA repo to update QEMU and libvirt, and I'm also getting this crash when trying to start the Big Sur install process. Ubuntu server 20.04.2 LTS 64-bit, dual 6-core Intel CPUs w/Hyperthread (total 24 logical), 32GB RAM. I can give any further details if requested. AVX is supported, but apparently AVX2 is not.

adam commented

@sickcodes commented on GitHub (Jun 28, 2021):

Have you docker pulled the latest image?

@sickcodes commented on GitHub (Jun 28, 2021): Have you docker pulled the latest image?

adam commented

@redfive2012 commented on GitHub (Jun 30, 2021):

Yes, I've only been trying this in the last couple of days.

On Mon, Jun 28, 2021 at 1:38 PM sickcodes @.***> wrote:

Have you docker pulled the latest image?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sickcodes/Docker-OSX/issues/96#issuecomment-869880497,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKMNTUNU7EPESSOUI3V7Z3TVCXPZANCNFSM4SR4FSCA
.

@redfive2012 commented on GitHub (Jun 30, 2021): Yes, I've only been trying this in the last couple of days. On Mon, Jun 28, 2021 at 1:38 PM sickcodes ***@***.***> wrote: > Have you docker pulled the latest image? > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/sickcodes/Docker-OSX/issues/96#issuecomment-869880497>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAKMNTUNU7EPESSOUI3V7Z3TVCXPZANCNFSM4SR4FSCA> > . >

adam commented

@sickcodes commented on GitHub (Jul 1, 2021):

@redfive2012

# 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

@sickcodes commented on GitHub (Jul 1, 2021): @redfive2012 ``` # 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 ```

adam commented