virtualbox.org

Symptom - When the VM reboots after zerotouch cancel or after a reload command the VM crashes.

Please let me know if I can provide any additional information.

Hardware and Software:

Mac Book Pro
Mac OS 10.13.6
8 GB RAM
VirtualBox 6.0.0
Arista VEOS - vEOS-lab-4.21.1.1F.vmdk
Guest Settings - 64bit Fedora, 2 GB RAM

Following instructions
Search for "Building a Virtual Lab with Arista vEOS and VirtualBox" - I can't post URLs yet

Link to my VBoxLog File - It was too large for the forum upload, I also can't post URLS. Please message me for a dropbox link to the log file.

Thank you for your assistance.

PacketsAreUs wrote:Search for "Building a Virtual Lab with Arista vEOS and VirtualBox" - I can't post URLs yet

The first link that I found was from 2012... Can you obfuscate the URL and I can fix it? Or add it to a text file and attach the text file?

PacketsAreUs wrote:Link to my VBoxLog File - It was too large for the forum upload

Even if you ZIP it? Which BTW is the preferred way to upload a VBox.log?

Hello here is the link I used to configure Virtual Box.
http://www.gad.net/Blog/2012/10/27/buil ... irtualbox/

Hello. I have attached the zip copies of the VBox logs during a crash. This is now on a Windows host system, but the symptoms are the same.

00:01:32.213210 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:01:32.213514 Console: Machine state changed to 'GuruMeditation'
00:01:32.213911 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:01:32.213912 !!
00:01:32.213912 !! VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
00:01:32.214639 !!
00:01:32.214650 !! Skipping ring-0 registers and stack, rcErr=VINF_EM_TRIPLE_FAULT

Here is a snip from the log where the vm crashes.

Thanks for your help,
Justin Morse

PacketsAreUs wrote:00:01:32.213912 !! VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)

That is the symptom of your problem - the guest has done something really bad that can't be recovered and the only thing VirtualBox has been able to do it crash. These are notoriously difficult to diagnose.

Looking at what was in the log prior to that then it looks like the guest has woken up from being suspended and then tried to re-initialise the four network adapters. Does the problem occur if you reduce the number of enabled guest network adapters to 1 or if you change them from the PCnet-FAST III (Am79C973) adapter emulation to the Intel PRO/1000 MT Desktop?

-Andy.

Hello Andy.

The propblem does occur if I only use one network adapter.

Thanks for taking a look.

Justin