mirror of
https://github.com/sickcodes/Docker-OSX.git
synced 2026-01-11 21:10:25 +01:00
In Memory Panic VNC #79
Reference in New Issue
Block a user
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?
Originally created by @gruaig on GitHub (Oct 15, 2020).
Hey base OS Centos 8
Docker version 19.03.5, build 633a0ea
QEMU emulator version 1.5.3 (qemu-kvm-1.5.3-173.el7_8.3), Copyright (c) 2003-2008 Fabrice Bellard
jenkins-osx ~]# lscpu | grep Virtualization
Virtualization type: full
lsmod | grep -i kvm
kvm 636931 0
irqbypass 13503 1 kvm
docker command ' docker run -e RAM=4 --name docker-osx-vnc -p 8888:5999 -p 50922:10022 -d --privileged docker-osx-vnc
'
While installing over VNC it hits the above error message and freezes let me know if you need any more information
@sickcodes commented on GitHub (Oct 18, 2020):
Testing now
@sickcodes commented on GitHub (Oct 18, 2020):
Try rebuilding it with no cache
I'm running
https://rpmfind.net/linux/RPM/centos/updates/7.8.2003/x86_64/Packages/qemu-kvm-1.5.3-173.el7_8.3.x86_64.html
Package says it has qemu-kvm-5.1.0-7.1.x86_64.rpm which looks good
Were you able to install?
If it didn't boot at all, then hardware nested virt might be off
@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
@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):
Tried with new qemu version and still got the same error:
Output of
virsh -c qemu:///system version --daemonis:@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
@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.
@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-surMy 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:
@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:
As per https://github.com/kholia/OSX-KVM
It might be worth to add CPU checks to container startup.
@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
@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:
@sickcodes 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
@fcastilloec commented on GitHub (Mar 19, 2021):
Here it is, in the same order as the template:
The output of
dfmight be useless since I've set docker withdata-rootin a different drive, here's the output of the other drive:I've also used this repository ppa:jacob/virtualisation to update QEMU and
libvirtdto these values and the issue still happens:@sickcodes commented on GitHub (Mar 24, 2021):
chmod 666 /dev/kvmYou also did not post
grep "docker\|kvm\|virt" /etc/group@fcastilloec commented on GitHub (Mar 25, 2021):
Sorry, I guess I didn't select the last line when copy/pasting. Here it is:
Also, I don't think it's necessary to do
chmod 666 /dev/kvmbecause I'm part of thekvmgroup, so I should be able to read/write. No need to give access to other users.@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.
@sickcodes commented on GitHub (Jun 28, 2021):
Have you docker pulled the latest image?
@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:
@sickcodes commented on GitHub (Jul 1, 2021):
@redfive2012
@redfive2012 commented on GitHub (Jul 5, 2021):
Nelson Butterworth
On Thu, Jul 1, 2021 at 4:06 AM sickcodes @.***> wrote:
@sangdrax8 commented on GitHub (Nov 5, 2021):
Ubunt 20.04, I was running big-sir image a month ago. I tried to boot it up in the last week and couldn't get it to boot. I removed all images and tried pulling clean, but resulted in this same crash.