#1721 closed defect (fixed)
Unable to start Kubuntu VM with AMD-V
Reported by: | riker | Owned by: | |
---|---|---|---|
Component: | VMM/HWACCM | Version: | VirtualBox 1.6.4 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
I upgraded the Virtualbox from v1.6.0 to v1.6.2, and tried to enable the AMD-V to test a issue which I reported as the ID#1510. I found the AMD-V feature is not stable. I active the VM 4 times and only one time is success. The system environment I used aer sumarized as below.
Host System : Windows XP SP3. Virtualbox : v1.6.2 Guest System: Kubuntu v7.10
Attachments (4)
Change History (16)
by , 17 years ago
Attachment: | VBox_failure01.log added |
---|
by , 17 years ago
Attachment: | VBox_failure02.log added |
---|
by , 17 years ago
Attachment: | VBox_failure03.log added |
---|
by , 17 years ago
Attachment: | VBox_success.log added |
---|
comment:1 by , 17 years ago
comment:2 by , 17 years ago
Thanks very much for your reponse. I only start one VM. The sytem would become no response and the screen is blank for a long time. After 3~5 minutes, I close the window to terminated the VM. If you need more tests, I will help do it.
comment:3 by , 17 years ago
Component: | other → VMM |
---|
comment:4 by , 17 years ago
Summary: | AMD-V is not stable in the Virtualbox v1.6.2 → AMD-V is not stable in the Virtualbox v1.6.2 -> fixed in SVN |
---|
Fixed in SVN. I can give you a test build if you're interested, but it will have to wait until next week.
comment:5 by , 17 years ago
If I can give any help, I would like to do it. Virtualbox is a good software. Its support and response is pretty good. It is better than other open source project I had joined. Thanks!
comment:6 by , 17 years ago
Is the update included in the Virtualbox 1.6.4? I had run the same test in the Virtualbox 1.6.4 and update the results in issue #1934.
comment:7 by , 17 years ago
Summary: | AMD-V is not stable in the Virtualbox v1.6.2 -> fixed in SVN → Unable to start Kubuntu VM with AMD-V |
---|---|
Version: | VirtualBox 1.6.2 → VirtualBox 1.6.4 |
comment:9 by , 17 years ago
comment:10 by , 17 years ago
Component: | VMM → VMM/HWACCM |
---|
comment:11 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please try again with a later version and reopen if necessary. AMD-V should be fine with 2.0.2.
comment:12 by , 17 years ago
I upgrade Virtualbox to 2.0.2 and test the original issue 10 times. All are okay. This issue is fixed. Thank you very much.
Did you start all VM's in parallel? What exactly happened? VM state changed to 'aborted' or some error dialog?