virtualbox.org

Dear all,
I'm using 2 different setups:
Host: Mac OS , VirtualBox 5
Host: CentOS 7, VirtualBox 5

However using the same OVA image (CentOS 6.6 as VM image), importing with default same settings I have quite different results:

Host: Mac OS - works perfectly
Host: CentOS 7 - kernel panic or Guru error, and it cannot boot at all

I wonder how it is possible can someone explains and if there is a fix?

vebaev wrote:I wonder how it is possible can someone explains and if there is a fix?

Not unless we have some more information. Just going with a generic host description and a generic guest description is not enough. Not even for a start.

For each of your hosts:

1. Start the VM. Not from a saved or paused state. Clean start.
2. Take the steps required to generate/observe the error. Record the error message. EXACTLY. Post a screenshot if you have to.
3. Shut down the VM (if it hasn't aborted by itself). Not saved, not paused. Completely shut down. If you can't shut it down by normal means, close the VM window and select "Power off".
4. Right-click on the VM in the VirtualBox Manager. Select "Show Log..."
5. Save it (just the first log), ZIP it and attach it in your response (see the "Upload attachment" at the bottom of the form).

I would also like to see the "recipe" of the VM, the ".vbox" file:

1. Right-click on the VM in the VirtualBox Manager. Select "Show in Finder/Explorer/Whatever".
2. ZIP the selected ".vbox" file and attach it in your response.

And finally, if the OVA is public, point us to it so we can check it out.

Thanks for your detailed reply,

here is the info attached.

And here is the public OVA - download pitagora-galaxy org data/release/Pitagora-Galaxy-0.2.3.ova


Vesko

PS
I have replaced the dots with spaces in the address since the forum do not allows me to post adresses as a newbie
Also zipped the 2 files since max was 128kb and the log is 197kb

Zipping is acceptable and encouraged.
The Mac OS .vbox and log are garbled & unrecognizable. Try it again?

The guest is set to 16 virtual CPUs, and the CentOS host log reports an 'AMD FX-8150 Eight-Core' physical processor, which may count as 8 or 4 cores to Virtualbox depending on how one reads AMD's marketing info. Sounds like a heavily-overprovisioned guest. Try reducing to a couple processors in the guest.

Ram size, 12GB available, 40GB (!) wanted for the guest. Squeeeeezzzeeee!!!

My host (the CentOS one ) have 48 cores with 128GB ram , so my point is to use at least half of these to the guest OS as it should be used as research computational instance.....decreasing the cpu/ram will ruined the idea

You're right, I missed that in the log.

In fact I misread the memory available in the log, too, that's not 12373MB available, it's 123734MB available. (walking in hard shoes in an empty warehouse noise...)

Never mind my restricted host thoughts.

But we don't have comparison with the Mac guest, can you get that info?

On the Mac is working should I run it and shut it down, then attach the log?


PS
I have tried to reduce the CPU and RAM on the server CentOS but it gives me again Guru meditation error (attached)

Since this is hard to troubleshoot, you'll have to send me your 128GB RAM, 24 real/48 hyperthreaded CPU system for a close inspection. I'll send you my address via PM. It's a PO Box, I hope you don't mind...
</joke>


Man, that's a difficult system to compare with. So, we'll have to try our best blind guess. Here are some things that stand out:

• You're using a rather exotic system. The AMD processors give me thoughts, because they have had their share of problems in the past.
• It's rather troubling that by changing the number of CPUs and/or the amount of RAM causes different reactions. In fact I don't remember seeing it before.
• Not only that, but you get a "Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)" which is the most difficult for us users to troubleshoot.
• LSILogic? Do you have to or is it the default of the OVA? (still downloading it)
• The link that you gave me doesn't work, there is an alternative one, actually two. I managed to find it (although my only Japanese is "Arigato"), the one is Windows and the other is Mac and it's at version 0.2.4. I really don't know why they bothered to have two, since OVA is OS-agnostic:
  • http://download.pitagora-galaxy.org/dat ... .4-Win.ova
  • http://download.pitagora-galaxy.org/dat ... .4-Mac.ova

If you can upload the Mac VBox.log (ZIPPED) it would be great, but I don't think it would be enlightening...

Here is the Mac (host) Log and vbox attached of the image Pitagora-Galaxy-0.2.3.ova which is working fine on my Mac.

Yes these images you linked are in the same folder/path as the one I'm using Pitagora-Galaxy-0.2.3.ova and also making problems on the Centos server. I also was wondering why whey are Win and Mac version

PS
Here is attaching also an image PNG of the 0.2.4-Mac.ova from your link again making guru error, so all these ova make same errors I suppose on the CentOS server host.
PS2
I do not knoq why is so exoting as it should be a regular CentOS VM

First thing, right off the bat, you're running 5.0.20 on your Linux and 5.1.12 on your Mac. Please upgrade your CentOS installation from the official download site https://www.virtualbox.org/wiki/Downloads and use the same settings to get us going. Later on, if it works you can modify them.

Do not worry about your VMs, they will be fine through the upgrade process...

It took me ages uninstalling the old version but now I installed 5.1.12 same version as on the Mac.

Unfortunately the result is the same - attaching the log and vbox file.

Almost everytime it gives error when I see on the screen "Odd, counter constraints enabled but no core perfctrs detected!"

Fine, at least you're on the same page in terms of VirtualBox version. You're still not on the same page as far as settings is concerned, but if you still get the same results with 2 CPUs and 4 GB of RAM, you should head to the bugtracker and either search for an appropriate bug, or open a new bug report where you'll attach your logs and other vital information. Unless someone else has any other ideas.

Generally speaking, when comparing two systems, make sure that ALL the settings are as close as possible. And if you're importing an OVA, just import it. Do not start modifications without understanding the ramifications. You were testing a VM which not a lot of people could do. 22 CPUs with 40 GB RAM, doesn't come easy. Start with 2 CPUs and 4 GB of RAM, just as the OVA creator intended, and if it works, you start modifying it.

Yes I have tryied also that - importing with default settings and no modifications - same result. Unfortunatelly I will go for a searching new image rather debuging this one as it will take me too much time I do not have I''m afraid. In summary I was not excpecting ran into such problem in first place at all

vebaev wrote:I was not excpecting ran into such problem in first place at all

Murphy is ubiquitous. Prepare for him ubiquitously.

Hope you can get things going!

The guru meditation is a Triple Fault, meaning the guest OS tried something really unexpected.

Strangely, the OVA links are downloading .MAN files over here. I'm taking both Windows & Mac versions and plan a FC to see if they're really the same, if I can unpack them. Slow download link, though....

Let me know if you found something, all 0.2.4 and 0.2.3 give same inconsistancy in running on my centOS server regardless of cpu and ram settings. I got maybe 1 of 10 run times the VM image load the full guest OS, which is quiteunstable for me.

Yes probably the dl is slow since the source is in Japan