#1721 closed defect (fixed)
Unable to start Kubuntu VM with AMD-V
回報者: | riker | 負責人: | |
---|---|---|---|
元件: | VMM/HWACCM | 版本: | VirtualBox 1.6.4 |
關鍵字: | 副本: | ||
Guest type: | other | Host type: | other |
描述
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
附加檔案 (4)
更動歷史 (16)
16 年 前 由 編輯
附檔: | 新增 VBox_failure01.log |
---|
16 年 前 由 編輯
附檔: | 新增 VBox_failure02.log |
---|
16 年 前 由 編輯
附檔: | 新增 VBox_failure03.log |
---|
16 年 前 由 編輯
附檔: | 新增 VBox_success.log |
---|
comment:2 16 年 前 由 編輯
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:4 16 年 前 由 編輯
摘要: | 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 16 年 前 由 編輯
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 16 年 前 由 編輯
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 16 年 前 由 編輯
摘要: | AMD-V is not stable in the Virtualbox v1.6.2 -> fixed in SVN → Unable to start Kubuntu VM with AMD-V |
---|---|
版本: | VirtualBox 1.6.2 → VirtualBox 1.6.4 |
comment:10 16 年 前 由 編輯
元件: | VMM → VMM/HWACCM |
---|
comment:11 16 年 前 由 編輯
狀態: | new → closed |
---|---|
處理結果: | → fixed |
Please try again with a later version and reopen if necessary. AMD-V should be fine with 2.0.2.
comment:12 16 年 前 由 編輯
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?