Custom Query (16363 matches)
Results (2515 - 2517 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #19290 | duplicate | Critical Error: Guru Meditation | ||
| Description |
I set up an Ubuntu 18.04 guest on my Macbook Pro 2019 earlier today, and everything was going ok and I was able to use it. I set up port forwarding with VBoxManage modifyvm "vmname" --natpf1 "ssh,tcp,127.0.0.1,3022,10.0.2.15,22" and was able to ssh into my vm. I was also able to use VBoxHeadless successfully. I then opened the VirtualBox GUI, right clicked on my virtual machine name and opened settings, and changed the name of the guest slightly (there was an uppercase by mistake). I then checked to see if my port forwarding rule had been updated and it had. Upon trying to use VBoxHeadless to start the vm it produced a lot of errors in the command line, so I stopped it and tried to open it with the VirtualBox GUI. This was when I receive the Critical Error message and was directed here. I have attached the log file and png from the log folder as requested in the pop up box. |
|||
| #19291 | duplicate | Critical Error: Guru Meditation | ||
| Description |
I set up an Ubuntu 18.04 guest on my Macbook Pro 2019 earlier today, and everything was going ok and I was able to use it. I set up port forwarding with VBoxManage modifyvm "vmname" --natpf1 "ssh,tcp,127.0.0.1,3022,10.0.2.15,22" and was able to ssh into my vm. I was also able to use VBoxHeadless successfully. I then opened the VirtualBox GUI, right clicked on my virtual machine name and opened settings, and changed the name of the guest slightly (there was an uppercase by mistake). I then checked to see if my port forwarding rule had been updated and it had. Upon trying to use VBoxHeadless to start the vm it produced a lot of errors in the command line, so I stopped it and tried to open it with the VirtualBox GUI. This was when I receive the Critical Error message and was directed here. I have attached the log file and png from the log folder as requested in the pop up box. |
|||
| #11784 | obsolete | Critical Windows 8 freeze after start-up since updating to VB 4.2.12 | ||
| Description |
I previously had a perfectly functional Windows 8 guest virtual machine working within Mac OS X Mountain Lion, I believe using VB 4.2.4. I updated to VB 4.2.12 earlier this week and have since been unable to functionally run the virtual machine. On starting the machine, I get as far as the Windows 8 logo screen (i.e. not very far) but the 'loading circles' never appear. VB remains responsive for a short while but the screen never changes and eventually I can only force quit the application. |
|||

