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
Expected behavior
I expect ping 127.0.0.1 to indicate that it's connected. For example, if I boot the puipui kernel (same kernel as above) with its associated initrd,
~ # ping 127.0.0.1
127.0.0.1 is alive!
So: ping from busy box works as expected while u-root ping does not where kernel, vm and vm launch configuration are held constant.
Conclusion: there is something not-right happening with my u-root to setup the network. Any helpful comments would be appreciated. Otherwise, I will continue to explore this and update the bug.
The text was updated successfully, but these errors were encountered:
Yeah, this is a problem with u-root ping, this can be reproduced on any machine, you don't need a VM. To make it work on localhost is more tricky. It will work with -c=1 but no more.
I should probably note in passing that I discovered this bug while trying to make the network work in my vm and stopped at "if I can't even get ping to localhost to work, then there's no hope for more general networking"
Describe the bug
I create a Linux vm using
vfkit
on an Apple Silicon Mac. I booted such a vm using the testpuipui
kernel from Code-Hex/vz: Create virtual machines and run Linux-based operating systems in Go using Apple Virtualization.framework. and aninitrd
build withu-root
.To Reproduce
Boot the vm.
ping 127.0.0.1
. Note the following unexpected outputExpected behavior
I expect
ping 127.0.0.1
to indicate that it's connected. For example, if I boot thepuipui
kernel (same kernel as above) with its associatedinitrd
,So:
ping
from busy box works as expected whileu-root
ping does not where kernel, vm and vm launch configuration are held constant.Conclusion: there is something not-right happening with my
u-root
to setup the network. Any helpful comments would be appreciated. Otherwise, I will continue to explore this and update the bug.The text was updated successfully, but these errors were encountered: