Open wpence opened 2 years ago
We have run into this same issue but the fix still has some race conditions: https://github.com/panda-re/panda/pull/1232
Not sure if your issue is arriving at the race condition in the same way, but one workaround we had was to add an lpj=
kernel argument. Just observed boot without the network tap to grab a sane value from the console.
We have run into this same issue but the fix still has some race conditions: #1232
Not sure if your issue is arriving at the race condition in the same way, but one workaround we had was to add an
lpj=
kernel argument. Just observed boot without the network tap to grab a sane value from the console.
Interesting, this is probably a duplicate of your issue then. If I boot with lpj=2912256
it seems to boot reliably.
I have been running into an issue where it appears that QEMU/PANDA hangs after issuing the command to start my VM where there is no output and nothing happens. This may be some sort of race condition as it only happens sometimes. I have narrowed the issue down to using a network tap with the vexpress-a9 ARM board. I am attaching a sample VM and script where this behavior can be reproduced.
To reproduce this issue with vm_sample.tar.gz:
I've crafted a simple bash script (run.sh) to attempt to start the VM over and over again and then exit when it fails to start. Using gdb to attach to the PANDA pid when it hangs, I've gotten the following backtrace:
For reference the PANDA command being used is:
I'm getting the same behavior in both my local PANDA build as well as the latest pandare/panda:latest docker container image. I have found that this issue only happens when using the vexpress-a9 QEMU ARM machine. If I switch to
-M virt
or-M versatilepb
it seems to boot fine every time. It only happens with the tap network device. For example, if I change the net config to-net nic -net user
it boots fine every time. Using either-netdev tap
or-net tap
seems to trigger this behavior on the vexpress-a9 board. It happens whether the filesystem is an initramfs or-drive
device. I have reproduced this with several different versions of Linux targeting vexpress-a9.