Opened 17 years ago
Closed 15 years ago
#1700 closed defect (fixed)
importing win2000 vmdk failed
Reported by: | jcottier | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 1.6.2 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | other |
Description
Hello, I have several vmware workstation vmdk's and I am trying to import a windows 2000 one to virtualbox as a test. Windows boots until the boot bar-graph reaches the end but then locks. I have tried renaming the agp440 file, the merge_ide mods, but neither made any apparent change. I have also tried to boot from the windows 2000 install CD, but after loading in its files and getting to "starting windows 2000" it locks again. I have also tried safe mode, vga mode, but it just locks. VMworkstation can load it fine, but the migration mods made it fail, so I have restored the original vmdk and started over, but with no success.
Attachments (2)
Change History (6)
by , 17 years ago
Attachment: | VBox.log.3 added |
---|
comment:1 by , 17 years ago
by , 17 years ago
Attachment: | W2000 boot failure added |
---|
comment:2 by , 17 years ago
Guest type: | other → Windows |
---|
comment:3 by , 15 years ago
Please Close this bug.
This is known Windows behavior, not a VBox bug.
See: http://www.virtualbox.org/wiki/Migrate_Windows
-Technologov
comment:4 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I disabled IO APIC again and got the W2000 CD to work. Entered repair mode and repaired W2000, it replaced the kernel and some other stuff. No change after reboot.
Then I applied the merge IDE patch again using VMware, using google to check the German text. It was applied successfully. VMware could then no longer boot W2000 (see attached screen dump). Used the W2000 CD to repair again. VMware can now boot, Virtualbox still cant load.
Used the W2000 CD repair again, checked and disabled agp440 service. No change after reboot. VMware can still boot fine, but Virtualbox still locks after the initial screen. Are there any files you need to track this problem?