virtualbox.org

Hello guys,

I've been having this problems for quite a while on one of our servers, although cannot pin down why. I've installed VirtualBox on four other hosts and they run happy, although I'm having real problems with my last and final server.

I've used this guide for all five (Here), which as menationed above, works perfectly on four of them.

The host servers are all very old Dell PowerEdge servers, different models I must add, although the one I'm having problems with is a 6850.

In terms of specs and OS:

OS: Fedora 23 64-bit
CPU: 2 x Intel Xeon Processor 7020 2.66 GHz (Virtualation is enabled in BIOS)
RAM: 12 GB
Disk Space: 250 GB (Will upgrade at a later date)

In terms of guest OS's I've tried CentOS 7, CentOS 6.8, Fedora 24, Fedora 23 and Windows Server 2008 R2 - all with the server error message (Guru Meditation).

Not a clue what is at fault, hopefully someone can help. Logs will be attached.

Did you try a guest with less then four CPUs?
You shouldn't assign all available physical host cores to a single VM.

Thanks for your reply, just tried now. New log attached if that can help.

Still no luck sadly.

You said:

Jamie_Lambertstock wrote:CPU: 2 x Intel Xeon Processor 7020 2.66 GHz (Virtualation is enabled in BIOS)

On the other hand, the log says:

00:00:01.405544 CPUM: Matched host CPU INTEL 0xf/0x4/0x8 Intel_NB_Prescott2M with CPU DB entry 'Intel Pentium 4 3.00GHz' (INTEL 0xf/0x4/0x3 Intel_NB_Prescott2M)

You can see the minute difference, right? The problem is that at some later point the processor is identified as:

00:00:01.623546 Full Name: "Intel(R) Xeon(TM) CPU 2.66GHz"

One thing you might want to try, is to change the Paravirtualization option to "None". VM Settings, System, Acceleration, Paravirtualization Interface.

Just to clarify a bit on an issue that is confusing to say the least.
Actually the first line says Pentium to match MSR but the real definition is given later and does match the actual CPU.

Now to some issues. Running from the /root folder is never a good idea and can cause a lot of issues like permission and others.
This is the actual error and is very hard to track down. Usually a host driver issue or what ever but I would first try to *NOT* run as root. I also do not support running as root and can not help anyone do so but this needed to be pointed out.

Thanks for all your help guys, sadly still having problems.

socratis wrote:One thing you might want to try, is to change the Paravirtualization option to "None". VM Settings, System, Acceleration, Paravirtualization Interface.

Just tried - sadly still not happy. Please see log attached.

Perryg wrote:Just to clarify a bit on an issue that is confusing to say the least.

Code: Select all

00:00:01.405544 CPUM: Matched host CPU INTEL 0xf/0x4/0x8 Intel_NB_Prescott2M with CPU DB entry 'Intel Pentium 4 3.00GHz' (INTEL 0xf/0x4/0x3 Intel_NB_Prescott2M)

00:00:01.623546 Full Name:                       "                  Intel(R) Xeon(TM) CPU 2.66GHz"

Actually the first line says Pentium to match MSR but the real definition is given later and does match the actual CPU.

I see what you mean, very odd. Looks like I might be down to four servers at this rate - cannot get my head around what's at fault.

Perryg wrote:

Code: Select all

00:00:01.646064 AIOMgr:     /root/VirtualBox VMs/Test Server (1 CPU)/Test Server (1 CPU).vdi

Running from the /root folder is never a good idea and can cause a lot of issues like permission and others.

Code: Select all

00:00:21.310178 !!                 Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)

This is the actual error and is very hard to track down. Usually a host driver issue or what ever but I would first try to *NOT* run as root. I also do not support running as root and can not help anyone do so but this needed to be pointed out.

Thanks for that, I was planning on creating standard users once I know everything is up and running. The servers in question are simply for development work, nothing that will be visible to the public, although that being said, I've now created a new user which was used in the following log.

The new log does not so a real problem as far as I can tell. The triple fault can be anything that will stop the guest from booting. It mean that three tries have failed and stops the load. Very hard to find especially remotely. I would try disabling features and see if the guest boots and then we can see what might be the reason, but other than that you would need to raise a ticket at bugtracker for the DEVs to take a look.