You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the current commit, the Qemu VM of a PI3 is not booting after having done a sudo apt-get upgrade
Presume there is something in the upgrade that breaks the VM but do not know where to start finding a fix
this is a snippet of the vm startup
........
Extracting /fixup4x.dat to /fat/fixup4x.dat
Extracting /LICENCE.broadcom to /fat/LICENCE.broadcom
Searching for kernel='kernel8.img'
Searching for dtb='bcm2710-rpi-3-b-plus.dtb'
Booting QEMU machine "raspi3b" with kernel=/fat/kernel8.img dtb=/fat/bcm2710-rpi-3-b-plus.dtb
qemu-system-aarch64: Slirp: Failed to send packet, ret: -1
qemu-system-aarch64: Slirp: Failed to send packet, ret: -1
qemu-system-aarch64: Slirp: Failed to send packet, ret: -1
qemu-system-aarch64: Slirp: Failed to send packet, ret: -1
qemu-system-aarch64: Slirp: Failed to send packet, ret: -1
the Slirp: Failed ... messages repeat with long intervals between 5+min and the docker VM is using 50% plus of CPU resources of HOST
The following while not the same as an upgrade prove to me that updates are persistant across reboots.
Using the current commit, the Qemu VM of a PI3 is not booting after having done a
sudo apt-get upgrade
Presume there is something in the upgrade that breaks the VM but do not know where to start finding a fix
this is a snippet of the vm startup
the
Slirp: Failed ...
messages repeat with long intervals between 5+min and the docker VM is using 50% plus of CPU resources of HOSTThe following while not the same as an upgrade prove to me that updates are persistant across reboots.
sudo apt-get update
requires the argument--allow-releaseinfo-change
sudo apt-get install git
Host is DockerDesktop , windows 10
The text was updated successfully, but these errors were encountered: