Virtualbox guru meditation error

virtualbox.org

End user forums for VirtualBox

• Board index‹General‹VirtualBox on Windows Hosts
• Change font size
• Print view

• FAQ
• Login

[Solved] GURU MEDITATION a critical error occurred while running the virtual machine

[Solved] GURU MEDITATION a critical error occurred while running the virtual machine

by Munim » 11. Apr 2018, 01:46

Hi, i am really stuck with this error right now and been unable to move forward. only way i sorted out to get rid of it is to create a new machine install linux again and then save machine state whenever I want to turn my computer off.
otherwise, if I shut down my Virtual Machine in virtual box, I never get able to run it again and get this Guru meditation error.

I will appreciate if someone can help me in this regard.

Re: GURU MEDITATION a critical error occurred while running the virtual machine and machine executio

by andyp73 » 11. Apr 2018, 10:13

As we aren’t sat in front of your computer or residing in your head then you are going to need to give us much more information than you have to allow us to help you.

Start by posting a log file from the guest that is causing a problem ( zipped of course).

Re: GURU MEDITATION a critical error occurred while running the virtual machine and machine executio

by Munim » 12. Apr 2018, 15:11

Please take a look. I have attached the ZIP file for logs. Basically everytime I run VM I get an error stated in the subject of this post.

Re: GURU MEDITATION a critical error occurred while running the virtual machine and machine executio

by andyp73 » 12. Apr 2018, 16:22

The most likely cause of your problem is going to be:

You will need to enable this in the BIOS as more and more guests (even 32bit ones) seem to need it.

As the log shows VT-x support as being disabled then I guess you don’t get any of the options for 64bit guests. Once you have VT-x enabled, select the «Ubuntu (64bit)» template if you are installing the 64bit version.

Re: GURU MEDITATION a critical error occurred while running the virtual machine and machine executio

by Munim » 12. Apr 2018, 18:30

I am so sorry to bother you but where can i find option to enable VT, i am new to linux.

Re: GURU MEDITATION a critical error occurred while running the virtual machine and machine executio

by mpack » 12. Apr 2018, 18:34

It’s an option in the host BIOS, so it has nothing to do with Linux — or VirtualBox for that matter. Basically, your PC disables VMing for dubious security reasons. You need to enable it. Your PC user manual or support forum can tell you how.

p.s. In future we don’t need 50 different logs and screenshots, since I doubt that anyone will bother to look at all of them. One relevant log is plenty. I have modified your attachment accordingly.

Re: GURU MEDITATION a critical error occurred while running the virtual machine and machine executio

by Munim » 12. Apr 2018, 18:58

Hey thank you very much. I followed your instructions and it worked.

Источник

🛠️ Virtualbox Guru Meditation ошибка на Linux

На этой неделе я тестировал KVM.

Сегодня я узнал, что KVM и Oracle VirtualBox не работают одновременно.

До сегодняшнего дня у меня не было возможности использовать два приложения виртуализации одновременно, поэтому я совершенно не знаю, что KVM и virtualbox не работают одновременно на Linux

Когда был запущен один из экземпляров KVM, я запустил виртуальную машину из VirtualBox, и она не запустилась, а показала окно с ошибкой под названием – Virtualbox Guru Meditation.

Обратите внимание, что KVM и VirtualBox работают бок о бок, фактически никого не удаляя.

Однако я не могу использовать их одновременно.

Эта ошибка является новой, поэтому я решил, что публикация этого руководства поможет кому-то.

KVM и VirtualBox не работают одновременно

Вот полное сообщение об ошибке, когда я пытался запустить ВМ из oracle virtualbox, когда гостевая машина KVM уже запущена:

Затем я остановил гостевую KVM, закрыл приложение KVM и запустил виртуальную машину из virtualbox, все заработало!

Я также попробовал это в обратном порядке.

Я запустил виртуальную машину из virtualbox, а затем запустил гостевую систему KVM, но гостевая система KVM не запускается.

Затем я остановил виртуальную машину, закрыл приложение Virtualbox и запустил экземпляр KVM, все заработало!

Я даже проверил, работают ли модули kvm и vbox, используя команду «lsmod».

Найдем модули KVM с помощью команды lsmod:

Найдем модули virtualbox:

Все модули загружены.

Так как же исправить ошибку «Virtualbox Guru Meditation» на Linux?

На самом деле, нет решения.

Вы должны использовать любой гипервизор за один раз.

Аппаратные расширения виртуализации Intel VT-x / AMD-V нельзя использовать с несколькими разными гипервизорами, работающих одновременно на одном хосте.

Вы должны запускать только один гипервизор на одном хосте.

Если вы хотите использовать другой, закройте работающий в данный момент гипервизор и запустите другой.

Другая причина этой ошибки – это то, что VT-x может быть отключен в BIOS.

Убедитесь, что вы включили его в своем BIOS.

Обратитесь к руководству производителя вашей системы, чтобы включить VT в BIOS.

Я не могу использовать KVM и VirtualBox вместе

У меня нет проблем с KVM и Virtualbox в моей системе Ubuntu 20.04.

Некоторые из вас могут столкнуться с этой ошибкой при запуске KVM и Virtualbox на одном хосте:

Если вы не можете использовать Virtualbox вместе с KVM, вы можете временно отключить модули kvm, а затем включить их, когда захотите.

Выгрузите работающие модули KVM с помощью команды:

Если это система AMD, используйте эту команду:

В качестве альтернативы вы можете использовать следующие команды:

Как в ключить модули KVM

Чтобы включить модули KVM, вы должны сначала найти их, где они находятся на вашем диске.

Для этого запустите:

Вы должны увидеть результат, как показано ниже.

Источник

virtualbox.org

End user forums for VirtualBox

• Board index‹General‹VirtualBox on Windows Hosts
• Change font size
• Print view

• FAQ
• Login

VirtualBox 6.1.16 Guru Meditation Error

VirtualBox 6.1.16 Guru Meditation Error

by zandatzu » 26. Nov 2020, 14:48

I’m running Ubuntu 20.04 on Windows 10 Pro 10.0.19041 Build 19041. Since i installed a Windows Update about a week ago i randomly encounter this guru meditation error. Just now it happened while I clicked out of the VM and back in and it just appeared again. It wont close either, i have to do that via the task manager.

Thanks in advance

Re: VirtualBox 6.1.16 Guru Meditation Error

by mpack » 26. Nov 2020, 18:26

That’s a very unhappy VM you have there.

Trying to use RAM you don’t have:

Likewise, assigning 100% of available cores to the VM. What is the host OS supposed to run on?

Yes, I’m aware that your CPU has 12 threads, but threads are not cores. If they were then none of us would need more than 1 core, and we’d all use the cheaper threads option.

Finally, this particular error seems to be related to upgrading VirtualBox on the host, or upgrading the host OS, while the VM was suspended, invalidating the data in the SAV file. You need to right click the VM in the manager and discard the saved state.

Re: VirtualBox 6.1.16 Guru Meditation Error

by zandatzu » 26. Nov 2020, 19:35

Thank you for your reply.

I changed the ram to 4GB and the cores to 2. If you have better suggestions I would like to hear them. The «Discard Saved State. » button however is greyed out. What can I do about that?

Re: VirtualBox 6.1.16 Guru Meditation Error

by BillG » 27. Nov 2020, 03:06

Re: VirtualBox 6.1.16 Guru Meditation Error

by zandatzu » 27. Nov 2020, 17:44

Re: VirtualBox 6.1.16 Guru Meditation Error

by zandatzu » 29. Nov 2020, 18:49

Re: VirtualBox 6.1.16 Guru Meditation Error

by multiOS » 30. Nov 2020, 00:23

Re: VirtualBox 6.1.16 Guru Meditation Error

by zandatzu » 8. Dec 2020, 14:38

Hello,
I encountered a criritical errror again. The cores are still set to 2 and th VM still uses 4 GB RAM. Between my last post and today I tried to find some good settings that worked, but in the end I still ended up on these settings.
I also put another 8 GB of RAM into my computer, which were from a friend which he had left after he replaced his RAM.

The problem now is that the logfile ist too big to be attached to this post (VBox.log, 438 KB). Did I look up the wrong file?

Thank You for your time

Re: VirtualBox 6.1.16 Guru Meditation Error

by mpack » 8. Dec 2020, 15:23

Re: VirtualBox 6.1.16 Guru Meditation Error

by zandatzu » 8. Dec 2020, 17:13

Re: VirtualBox 6.1.16 Guru Meditation Error

by mpack » 8. Dec 2020, 17:45

Re: VirtualBox 6.1.16 Guru Meditation Error

by zandatzu » 8. Dec 2020, 18:03

Ok, I’ll do that. If I should get this error again anyways I’ll post another reply here.

Thank You very much.

Re: VirtualBox 6.1.16 Guru Meditation Error

by zandatzu » 8. Dec 2020, 18:16

Re: VirtualBox 6.1.16 Guru Meditation Error

by mpack » 8. Dec 2020, 18:50

Re: VirtualBox 6.1.16 Guru Meditation Error

by zandatzu » 8. Dec 2020, 18:59

Источник

I have a penchant for VirtualBox because it gives me a playground for experimentation.

I can intentionally install viruses in the virtual machine (called the guest OS) with little fear of my real computer (the Host OS) getting infected.  I can install entire virtual networks with little trepidation of breaking my real network.  And I can test out different operating system before changing my Host OS to that OS.

It’s great.

But the other day something odd happened after I spun up my VM…

The guest OS launched fine, well for the first 10 seconds, but then it unceremoniously burped up an error about Guru Meditation?

If you’ve ever seen this error, it’s pretty disconcerting and hard to dismiss.  You only have two options:

You can click OK or hit Ignore but both usually return the same result: the application quits.  When you launch it again, it barfs up the same rude error you tried to avoid.

Some crazy spiritual stuff about a meditating guru.

What’s all this about?

Getting spiritual with Guru Meditation

The first time I ever saw this error, I envisioned a Tibetan monk, perched on his aerie ledge in the Himalayas.  His legs are crossed Indian style and his wrists are propped face-up on his knees.  I don’t know why but that’s the first thing that comes to my mind.

I did some research on this and it turns out the phrase “Guru Meditation” finds its origins from one of the first personal computers called the Amiga.  Sold by Commodore in the mid 80’s, these relics of time would sometimes spit up Guru Meditation errors on software failure.

Guru Meditation refers to an error so arcane that you were basically forced to look for a Guru to fix the problem.

Today, you going to help you become a little more Guru when I show you how to fix this positively baffling error.  I promise you my solution doesn’t involve meditation, burning incense or any obscure incantations.  With the alchemy of a little common sense and some patience we can fix this problem in no time.

Instead of being solemn about this recondite message, let’s get a little goofy and have fun finding the answer.

Getting Goofy with Guru Meditation

Nine times out of Ten when you see a “Guru Meditation” error in Virtualbox it’s related to your system memory.  But we don’t have to guess.  VirualBox logs all errors to a little file aptly named Vbox.log.

Let’s check it out.

I’m logged into my computer with user account vhudson and my Virtual Machine is simply named “Windows 8.1” so my log file is located here:

C:UsersvhudsonVirtualBox VMsWindows 8.1Logs

Just replace “vhudson” with your computer username and “Windows 8.1” with the name of that refractory VM that keeps going bonkers.

Let’s take a look in here to see what’s going on.

Open VBox.log in Notepad and press Ctrl + End key on your keyboard to zip down to the last line.  You should see the Guru Meditation stuff in proximity to the last line.  If not, just press Ctrl + f and enter the phrase “Meditation”

There’s a lot of abstruse test in the log but if you look closely you can probably figure out what happened.

I highlighted the last two lines.

It says:

00:03:21.283578 Console: VM runtime error: fatal=false, errorID=HostMemoryLow message="Unable to allocate and lock memory. The virtual machine will be paused. Please close applications to free up memory or close the VM"

and then this:

00:03:21.322610 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'.

The errorID in the first line is telling us the memory on the Host OS is low.

Hmm… so why is that?

Press Ctrl + Shift + Esc to open the Windows Task Manager.

Whoa!

You’ll probably see something similar to the above screenshot.  The memory value is almost at the ceiling.  I’ve got a total of 8GB of RAM on my Host OS and I’m at 7.6GB (which is only 96% full!)

Alright, so now we need to find out what’s specifically causing the problem.

If you click over to the Process tab and sort by Memory you may find the culprit. A bunch of chrome.exe processes are usually near the top of the list busy slurping up memory, but in my case none had the avarice to debilitate my computer.

I can’t blame Chrome today because after closing VirtualBox I noticed an immediate drop in memory usage.  The graph took a veritable nose dive.

Ah, so VirtualBox is killing VirtualBox?

I exonerated Chrome by my new discovery and decided to take a closer look at the VirtualBox settings.

In VirtualBox, select your intractable VM from the left pane and then press Ctrl + s to open the Settings pane.

Click System in the left navigation and check out the Base Memory slider on the right side.

My poor VirtualBox was attempting to allocate half of my physical memory to the VM.

Ultimately, I was apportioning too many resources to VirtualBox.  After changing the value from 4096 MB (4GB) to 2048 (2GB), my Guru Meditations went poof!

The Bottom Line

If you notice VirtualBox is experiencing an accretion of errors lately, check out Vbox.log. A quick look inside will often point you in the right direction.  Even if the error isn’t immediately obvious, you could always copy the error and paste it into Google to see what other people did to fix it.

In the case of Guru Meditation, you’ll usually find that you can fix the problem by managing your memory allocations to the guest OS.  Try decreasing the base memory value by half and see what happens.

I hope this helped you!  If so, please share the goodness in the comments below.  Oh, and if it didn’t help let me know too.  I like bad news just as much as good news.  I really want to make sure VirtualBox works for you.

На этой неделе я тестировал KVM.

Сегодня я узнал, что KVM и Oracle VirtualBox не работают одновременно.

До сегодняшнего дня у меня не было возможности использовать два приложения виртуализации одновременно, поэтому я совершенно не знаю, что KVM и virtualbox не работают одновременно на Linux

Когда был запущен один из экземпляров KVM, я запустил виртуальную машину из VirtualBox, и она не запустилась, а показала окно с ошибкой под названием – Virtualbox Guru Meditation.

Обратите внимание, что KVM и VirtualBox работают бок о бок, фактически никого не удаляя.

Однако я не могу использовать их одновременно.

Эта ошибка является новой, поэтому я решил, что публикация этого руководства поможет кому-то.

Virtualbox Guru Meditation

A critical error has occurred while running the virtual machine and the machine execution has been stopped.

For help, please see the Community section on https://www.virtualbox.org or your support contract. Please provide the contents of the log file VBox.log and the image file VBox.png, which you can find in the /home/sk/VirtualBox VMs/Ubuntu 20.04 Server/Logs directory, as well as a description of what you were doing when this error happened. Note that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window.

Press OK if you want to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special knowledge and tools, so it is recommended to press OK now.

Error starting domain: internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy
2020-07-08T11:28:43.524617Z qemu-system-x86_64: failed to initialize KVM: Device or resource busy

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 66, in newfn
    ret = fn(self, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/object/domain.py", line 1279, in startup
    self._backend.create()
  File "/usr/lib/python3/dist-packages/libvirt.py", line 1234, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirt.libvirtError: internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy
2020-07-08T11:28:43.524617Z qemu-system-x86_64: failed to initialize KVM: Device or resource busy

$ sudo lsmod | grep kvm

kvm_intel             282624  0
kvm                   663552  1 kvm_intel

$ sudo lsmod | grep vbox

vboxnetadp             28672  0
vboxnetflt             28672  0
vboxdrv               487424  2 vboxnetadp,vboxnetflt

VERR_VMX_IN_VMX_ROOT_MODE

$ sudo rmmod kvm-intel

$ sudo rmmod kvm-amd

$ modprobe -r kvm_intel

$ modprobe -r kvm

$ modprobe -r kvm_amd

$ modprobe -r kvm

$ sudo updatedb

$ sudo locate kvm

/lib/modules/5.4.0-39-generic/kernel/arch/x86/kvm
/lib/modules/5.4.0-39-generic/kernel/arch/x86/kvm/kvm-amd.ko
/lib/modules/5.4.0-39-generic/kernel/arch/x86/kvm/kvm-intel.ko
/lib/modules/5.4.0-39-generic/kernel/arch/x86/kvm/kvm.ko
/lib/modules/5.4.0-39-generic/kernel/drivers/gpu/drm/i915/gvt/kvmgt.ko
/lib/modules/5.4.0-39-generic/kernel/drivers/ptp/ptp_kvm.ko
/lib/modules/5.4.0-40-generic/kernel/arch/x86/kvm
/lib/modules/5.4.0-40-generic/kernel/arch/x86/kvm/kvm-amd.ko
/lib/modules/5.4.0-40-generic/kernel/arch/x86/kvm/kvm-intel.ko
[...]

$ sudo insmod /lib/modules/`uname -r`/kernel/arch/x86/kvm/kvm.ko

$ sudo insmod /lib/modules/`uname -r`/kernel/arch/x86/kvm/kvm-intel.ko

Помните, что виртуальные машины Virtualbox не будут запускаться, пока вы не отключите все экземпляры KVM.

Страницы: [1]   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

Страницы: [1]   Вверх