Dear Matthew,
Oh! That’s a very-very useful logs.
It looks like this somehow related to the network boot or something.
See (last entries from the log):
npAddFreeTxBuf: Add TxBufWrap 7D852698, TxBuf 7D8526C1
MnpAddFreeTxBuf: Add TxBufWrap 7D851018, TxBuf 7D851041
MnpAddFreeTxBuf: Add TxBufWrap 7D851698, TxBuf 7D8516C1
MnpAddFreeTxBuf: Add TxBufWrap 7D850018, TxBuf 7D850041
MnpAddFreeTxBuf: Add TxBufWrap 7D850698, TxBuf 7D8506C1
MnpAddFreeTxBuf: Add TxBufWrap 7D84F018, TxBuf 7D84F041
MnpAddFreeTxBuf: Add TxBufWrap 7D84F698, TxBuf 7D84F6C1
MnpAddFreeTxBuf: Add TxBufWrap 7D84E018, TxBuf 7D84E041
MnpAddFreeTxBuf: Add TxBufWrap 7D84E698, TxBuf 7D84E6C1
MnpAddFreeTxBuf: Add TxBufWrap 7D84D018, TxBuf 7D84D041
MnpAddFreeTxBuf: Add TxBufWrap 7D84D698, TxBuf 7D84D6C1
MnpAddFreeTxBuf: Add TxBufWrap 7D84C018, TxBuf 7D84C041
MnpAddFreeTxBuf: Add TxBufWrap 7D84C698, TxBuf 7D84C6C1
MnpAddFreeTxBuf: Add TxBufWrap 7D84B018, TxBuf 7D84B041
MnpAddFreeTxBuf: Add TxBufWrap 7D84B698, TxBuf 7D84B6C1
MnpAddFreeTxBuf: Add TxBufWrap 7D84A018, TxBuf 7D84A041
Now let’s analyze the callstack from which MnpAddFreeTxBuf
is called:
MnpAddFreeTxBuf
MnpAllocTxBuf
MnpBuildTxPacket
MnpTransmit
...
MNP stands for “Managed Network Protocol” in the edk2. It is used in the PXE/TFTP/HTTP boot stuff as far as I understand.
Since you are using Multipass (which I don’t now little about), I can guess that network boot stuff is configured in your case and probably something goes terribly wrong because of that.
To prove (or disprove) this hypothesis, I would suggest to play with the problematic instance a bit. You can make a copy of it, then try to reproduce the same problem with the copy. After you do that, you can disable (remove) network device from the instance and try to reproduce the issue again. If you see that problem is completely disappeared then we are on the right way to surround it.
After that we can share our findings with the EDKII developers or even try to create a minimal reproducer for it.
P.S. Just to be 100% sure. Do I understand correctly that visible behavior with this bug is that a VM just stuck on boot with the black screen?
Kind regards,
Alex