#3970 closed defect (wontfix)
VirtualBox 2.2.2
Reported by: | Jon Camilleri | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 2.2.2 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
Having tried VirtualBox 2.2.2, I noted that
- 64 bit operating systems cannot be installed as virtual machines, even, though the host machine runs Windows Server 2008 (64 bit).
The following OSs could not be tested successfully as virtual machines (include 64 bit and 32 bit OSs: Win Server 2008 64 bit Ubuntu Server 9.04 64 bit Ubuntu Server 9.04 32-bit CentOS 5.2 64-bit Slackware 12.2 (linux-based) - after an 8 hour installation an error was displayed indicating that the installation on the virtual hard disk was not bootable.
Related threads at
http://cid-b712073b3513eb8e.skydrive.live.com/self.aspx/.Public/slackware|_3.png
- Error displayed after booting on Slackware
- virtual machines have evident performance issues when compared to other products. I previously used Virtual Server 2005 R2 and VMWare Server 2.0, running on WinXP SP2 64 bit edition.
NOTE 1: Host machine
Windows Server 2008 64 bit (v6.0.6001) with Hyper-V AMD Athlon 64x2 4600+ 2.40Ghz 4Gb RAM
NOTE 1.1: I have an issue with Hyper-V since the network interface, so I tried VirtualBox as an alternative)
Attachments (1)
Change History (10)
comment:1 by , 16 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
comment:2 by , 16 years ago
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
Thanks, I'll try to keep one ticket per issue. I started the slackware installation again and the same error message appeared, with the OS not loading.
comment:4 by , 16 years ago
It would be great if I could upload the log file as attachments, because I suspect they are barely readable :)
comment:5 by , 16 years ago
See the 'Attach File' button. I'll delete your copy/paste comment as I can't read it.
by , 16 years ago
comment:8 by , 16 years ago
Resolution: | → wontfix |
---|---|
Status: | reopened → closed |
Actually your CPU doesn't support AMD-V. VirtualBox requires this for 64 bits guests, sorry.
comment:9 by , 16 years ago
I'm not sure on 2nd thought. Anyway, look at your BIOS for a setting called AMD-V or SVM.
It would be more useful if: a) you restrict a defect to a single issue b) give a proper title to the defect c) include VBox.log of a failing session. d) fill in the correct guest and host OS fields
My guess (since you fail to provide VBox.log) is that Hyper-V has locked AMD-V for itself. When VBox can't use VT-x or AMD-V, you can't run 64 bits guests. This is explained in the manual.
Please turn off Hyper-V and try again. If it still fails, attach the VBox.log to the defect.