Opened 11 years ago
Last modified 8 years ago
#11651 closed defect
Failure to create new virtual machine — at Version 4
| Reported by: | vman315 | Owned by: | |
|---|---|---|---|
| Component: | installer | Version: | VirtualBox 4.2.10 |
| Keywords: | Cc: | ||
| Guest type: | all | Host type: | Windows |
Description (last modified by )
Host
Windows 7 Home Premium x64
MSI MotherBoard
320 GB, 1.5 TB, 2 TB, 3 TB, 3 TB
AMD A6-3670 APU with Radeon HD Graphics 2.7 Ghz Quad Core
24 GB Ram
I have uninstalled, rebooted, reintstalled, and repeated 3 times. I am unable to create a virtual machine, upon trying I receive the following message.
Failed to open a session for the virtual machine a.
Failed to assign the machine to the session (Unknown Status 0x80004005).
Result Code: VBOX_E_VM_ERROR (0x80BB0003)
Component: Machine
Interface: IMachine {22781af3-1c96-4126-9edf-67a020e0e858}
Callee RC: E_FAIL (0x80004005)
I run a in house storage center, & RDC. I had 16 Windows XP Pro x64 with 10 GB primary with 1 GB of RAM, & Windows Server 2008 with 25 GB primary 1 TB slave with 2 GB of RAM. All of which was stored on the 2 TB. The problem all started when the 2 TB drive, when a large section of the drive became corrupted, and I was forced to reformate the drive. I would greatly appreciate being able to have m
Change History (4)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
I am having the same problem. Windows 7 Pro. Trying to create a Linux VM on a secondary drive (E: Drive)
Windows 7 Pro 64 bit SP1 8 GB Ram
AMD Athlon(tm) II X2 250 Processor 3.00 GHZ Mainboard Micro-Star International 790XT-G45 (MS-7388) BIOS American Megatrends Inc V2.4 05/21/2010
comment:3 by , 11 years ago
Oh BTW mine is a second VM. The first VM was moved from another machine and works fine.
Thanx
Bodger
comment:4 by , 11 years ago
| Description: | modified (diff) |
|---|


Seems I messed up in posting.
EDIT:
I run a in house storage center, & RDC. I had 16 Windows XP Pro x64 with 10 GB primary with 1 GB of RAM, & Windows Server 2008 with 25 GB primary 1 TB slave with 2 GB of RAM. All of which was stored on the 2 TB. The problem all started when the 2 TB drive, when a large section of the drive became corrupted, and I was forced to reformate the drive. I would greatly appreciate being able to have the ability to continue to use this wonderful program.