Custom Query (16363 matches)
Results (1690 - 1692 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #14364 | fixed | Can't start any virtual machines in windows 10 due to kernel mode not bieng ready | ||
| Description |
I have recently upgraded to windows 10 from windows 7 and i cannot start any virtual machines. I have attached the log file Hopefully this will be fixed soon as i use virtual box frequently for my projects |
|||
| #6886 | obsolete | Can't start guest after enabling nictrace with VBoxManage | ||
| Description |
From the command line, I attempt to enable nictrace by typing the following:
When trying this on OS X Leopard with VBox 3.1.6, I am able to run "VBoxManage startvm" but after I get "Remote session has been successfully opened" and the VM window appears, an error dialog immediately appears indicating "Failed to start the virtual machine vmname." and "Unknown error creating VM (VERR_PDM_DRVINS_UNKNOWN_CFG_VALUES)." Expanding the Details section shows Result Code: NS_ERROR_FAILURE (0x80004005), Component: Console, Interface: IConsole {6375231a-c17c-464b-92cb-ae9e128d71c3}." When trying this on OS X Snow Leopard with VBox 3.2, I get the following output in the console:
VBoxManage showvminfo "vmname" | grep -i nic returns the following, so it is able to parse the options: NIC 1: MAC: 0800274FE239, Attachment: NAT, Cable connected: on, Trace: on (file: /Users/me/nictrace1.pcap), Type: Am79C973, Reported speed: 0 Mbps Once I disable nictrace the vm is once again able to start just fine. Is nictrace broken or am I somehow configuring it wrong? |
|||
| #10931 | fixed | Can't start windows 8 virtual machine | ||
| Description |
Failed to open a session for the virtual machine Windows 8 vbox. No error info. Result Code: E_FAIL (0x80004005) Component: ProgressProxy Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913} |
|||

