Page 1 of 1
Installing Virtualbox on Windows Vista 64 bit
Posted: 7. Sep 2008, 04:44
by lierre
I have been trying to install virtualbox v.2.0 (64 bit) on my vista machine
(64 bit).
After creating the virtual hard drive I get the message "Virtualbox.exe has stopped working." I also get the following program details:
Code: Select all
Problem signature:
Problem Event Name: APPCRASH
Application Name: VirtualBox.exe
Application Version: 0.0.0.0
Application Timestamp: 48bedc51
Fault Module Name: VBoxQtCore4.dll
Fault Module Version: 4.3.3.0
Fault Module Timestamp: 4868db25
Exception Code: c0000005
Exception Offset: 00000000000641cb
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033
Additional Information 1: d286
Additional Information 2: 8bbc1bb1a58a2d7918336e1211b7adee
Additional Information 3: cf6f
Additional Information 4: 000aeea9b5b50c4527a6c5b0a34ed964
My processor is the T5750. It is not listed on the Intel processor list, so I do not know if it has "VT". In addition how do I access Guest settings and the Advanced Tab?
Thank you.
Posted: 7. Sep 2008, 06:12
by dtanderson
You have gotten farther than me. I cannot even get it to install on my Vista 64, just like with all the previous version it just will not install. It starts the install and then gets to one point then starts to rollback with "Sun xVM VirtualBox Setup Wizard ended prematurely".
Installing Virtualbox on Windows Vista
Posted: 7. Sep 2008, 15:03
by lierre
Somehow I have managed to get as far as trying to install Windows in the VM. However whenever I click on auto install I get the message:
" FATAL: Could not read from the host medium? System halted.
What does this mean? What should I do?
Posted: 8. Sep 2008, 09:09
by vifani
I got the same BSOD installing Vista x64 guest on Vista x64 host, during the first boot time. Analyzing the DUMP file with Windbg I found the driver that catches the exception: ATI Display Driver.
Posted: 8. Sep 2008, 17:58
by pentagonik
@lierre: Which size did you use for your newly create hard disk? If the number is odd (like 25 GB), the 2.0 GUI will crash. This bug will be fixed in the next maintenance release. As a workaround please use an even number (22 or 24 GB for example) for it.
Posted: 8. Sep 2008, 20:02
by lierre
Hello,
The set up suggested 1024 MB, so that is what I did.
I have now moved on (somehow) from that problem and hae now encountered these. First, the settings and delete boxes are greyed out.
Second, I get a black screen that says "Virtualbox Temporary boot device selection"; it then lists the following:
Detected Hard Disks:
IDE Controller:
1) Primary Master
Other boot devices:
f)Floppy
c) CD-Rom
l)LAN
b)Continue booting
How do I move on from here?
Thanks.
Posted: 8. Sep 2008, 21:28
by Sasquatch
Check with
CPU-z what your processor is capable of. IIRC, the 5750 doesn't have VT-x support.
Btw, Google "intel t5750", first hit Intel CPU list:
http://processorfinder.intel.com/detail ... Spec=SLA4D
NO VT-x support mentioned. Too bad.
Posted: 8. Sep 2008, 23:40
by lierre
Sasquatch,
On the "details" screen it says: VT-x/AMD-V Enabled.
Doesn't this mean that the cpu supports VT-x?
Posted: 8. Sep 2008, 23:54
by Sasquatch
No, that only means that VB is in support mode. If the processor has it, it will use it.
Posted: 9. Sep 2008, 08:07
by ppgrainbow
My processor has the Intel Core 2 Duo Mobile T7250 processor. The processor that I use has Intel Virtualisation Technology.
When I upgraded VB from 1.6.4 to version 2, uninstalling VB v1.6.4 went okay with the exception of getting this message:
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2803.
But when the installation of VB v2 took place, everything went flawlessly for me. None of the hard disk images were affected by the upgrade at all.
Now, I just need to create another hard disk image to see if everything is going okay without problems. I'll probably do that when I install another Linux-based guest operating system. =p
Posted: 9. Sep 2008, 08:10
by ppgrainbow
pentagonik wrote:@lierre: Which size did you use for your newly create hard disk? If the number is odd (like 25 GB), the 2.0 GUI will crash. This bug will be fixed in the next maintenance release. As a workaround please use an even number (22 or 24 GB for example) for it.
Okay...if you created a new hard disk image that includes a decimal number like 1.2 GB or 1.6 GB or images as small as 85 MB or 540 MB, will the Virtual Box 2.0 GUI crash as well?
I just want to play things safe until the next maintenance release...
Posted: 9. Sep 2008, 19:41
by Sasquatch
If you want to be safe, use 1.6.6 or an older version to create the VDI files. You can install VB inside your Guest VM, but it won't allow you to run any VMs you create. Move the created VDI to the host using Shared Folders or network shares and use it in 2.0.
We do suggest that unless you really need the extra features of 2.0, to stick to 1.6.6.
Posted: 9. Sep 2008, 21:40
by ppgrainbow
Sasquatch wrote:If you want to be safe, use 1.6.6 or an older version to create the VDI files. You can install VB inside your Guest VM, but it won't allow you to run any VMs you create. Move the created VDI to the host using Shared Folders or network shares and use it in 2.0.
We do suggest that unless you really need the extra features of 2.0, to stick to 1.6.6.
I have a feeling that Sun needs to made a maintenance release to fix a bug that will not allow the virtual machines to be run off of another storage device such as a USB hard drive or USB memory stick. Because the VDI images were created under v1.6.4 and v1.6.6 is the last stable release for the time being.
The internal hard drive is riddled with 280 reallocated sectors that could attempt to corrupt the data on the VDI file if moved in the near future.