Custom Query (16363 matches)
Results (1519 - 1521 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #7833 | duplicate | Guru Meditation on WinXP host, Kubuntu Guest | ||
| Description |
I was running VirtualBox 3.2.12, compiling Linux code on a Kubuntu Guest while doing other things on the host. Kubuntu was in seamless mode and the console was minimized (only the Kubuntu taskbar was visible). I got a Guru Meditation alert. The VBox.log is attached. |
|||
| #7834 | duplicate | How do I get VirtualBox to run with more than one CPU core on my Dell Desktop PC | ||
| Description |
I'm trying to use Sun VirtualBox on my Dell Optiplex 755 Desktop PC running Windows XP SP3 on an Intel Core 2 Duo E8400 3.00GHz processor and the latest version of VirtualBox (3.2.12) to run a Linux Kubunto Guest OS. This works very well as long as I only use only one of the two processor cores. If I try to enable the second core, I must also enable VT-X virtualization. However, in this case I always get an error Unknown error creating VM (VERR_VMX_MSR_LOCKED_OR_DISABLED) Result Code E_FAIL (0x0004005) Comonent: Console Interface: IConsole {6375231a-c17c-464b-92cb-ae9e128d71c3} I checked the system BIOS and virtualization as well as all other processor features are enabled, and there are no supervisor password locks. I successfully updated the BIOS from version A11 to the latest version A17 using a tool that I downloaded from the DELL website specifically for the Optiplex 755, but this did not help. I checked other websites regarding the VERR_VMX_MSR_LOCKED_OR_DISABLED message and I only get vague mentions of BIOS bugs on Dell computers. The same procedure works well on my Lenovo Laptop. I'm sending this same support request to DELL as well. |
|||
| #9413 | invalid | VERR_VD_IMAGE_READ_ONLY error | ||
| Description |
Today, I upgraded to VirtualBox 4.1.0 under Windows 7 Pro SP1. I created a virtual image from an existing WinXP hard disk using the SysInternals disk2vhd 1.63 utility runninbg on the Win7 machine. I created a new Windows XP VM around the new VHD file. However, whenever I launch the new VM, I get Failed to open a session for the virtual machine xxxxxx Failed to open image c:\xxxxxx.VHD for writing do to wrong permission (VERR_VD_IMAGE_READ_ONLY) Result Code: E_FAIL (0x80004005) Component: Console Interface: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} However, the image is NOT read only and I have full permissions for it. |
|||

