Custom Query (16363 matches)
Results (2002 - 2004 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3595 | fixed | xVM and VBoxManage report virtual machine as aborted when it is running correctly | ||
| Description |
OK. The host is a Centos 5.2 machine. We have several Centos 5.2 (text-only) guest machines cloned from one original. All works fine unless you change the settings (in this case, the network configuration) of one of the switched off guests (keira). The xVM GUI then crashes. When it runs again, it reports one of the running machines as "aborted", even though it is running correctly (see "reese"). The offline guest whose configuration was being edited ("keira") is reported as "Powered Off", but the "settings" button is now no longer available. A reboot of the host usually solves the problem, but this means downtime for all of the guests. Another headache is that the guest that is marked as "aborted" can be started by clicking on the green arrow, even though it is already running! This isn't good. An |
|||
| #3597 | fixed | VBox 2.1.4 Freezes on shutdown of Windows Server 2008 | ||
| Description |
Host: Windows Server 2008 64-bit Guest(s): Windows Server 2008 32-bit and Windows XP 32-bit The process is as follows:
This occurs quite frequently. |
|||
| #3598 | fixed | please improve VERR_ACCESS_DENIED error text | ||
| Description |
I setup 3 vms: Haiku Mer w7 I was able to run Haiku, Mer and w7 simultaneously. Then I enabled VT-x for w7. Started Mer, and tried to run w7.
This error message, while technically correct is poorly written (bad grammar, and confusing). Could you possibly replace the message with this: "This machine is configured to use VT-x which requires all running instances use VT-x. There is an instance <name here> currently using software virtualization." |
|||

