Adam,
So I have been using version 23.10.1, built as per the download page, and have gotten a couple
VMs to ping eachother and give me a login prompt. I finally realized I was missing the virtio_switch
package and grabbed it from github and put it where it is supposed to go. Of course, being a version mismatch now,
it did not compile. I decide to bite the bullet and do an upgrade (always a mistake) and use the new build
process given with the new website. That went smoothly! I install ham, run it, etc, everything builds,
I update my local scripts and links to use the new environment variables instead of being hardcoded,
and it all builds and looks good. Except that it doesn't run. The VMs get a memory exception and kick
into jdb.
I have not changed any of my .cfg or .list files. The VMs and ramdisks are untouched.
My local (L4 native) processes start and appear to run. But the VMs crash for some reason.
Even the device tree is unchanged. I also tried a newly built linux (as opposed to a prebuilt) and that failed as well.
Is there some reason for this new crash between version 23.10.1 and the latest version from github?
I've attached the VM startup output from both the old and new runs so you can take a look.
I'm so close... I see the IP configuration parameter and how to set up lwip and virtio_switch....
Then my natives should be able to talk directly to my linuxes.
Your help is greatly appreciated!
Richard