VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1777 - 1779 of 16363)

Ticket Resolution Summary Owner Reporter
#4175 invalid createrawvmdk with Vista x64 --> vmdk size calculation is wrong sven.gamasin
Description

Hi, the following scenario:

1. list partitions C:\Program Files\Sun\xVM VirtualBox>VBoxManage.exe internalcommands listpartitio ns -rawdisk \.\PhysicalDrive0 VirtualBox Command Line Management Interface Version 2.2.4 (C) 2005-2009 Sun Microsystems, Inc. All rights reserved.

Number Type StartCHS EndCHS Size (MiB) Start (Sect) 1 0x07 0 /32 /33 1023/239/63 65536 2048 2 0x07 1023/254/63 1023/254/63 150107 134223075 3 0x0c 1023/239/63 1023/239/63 22827 441643008

2. create raw partition access with "createrwavmdk" C:\Program Files\Sun\xVM VirtualBox>VBoxManage.exe internalcommands createrawvmd k -filename r:\virtuals\extldata.vmdk -rawdisk \.\PhysicalDrive1 -partitions 3 -register VirtualBox Command Line Management Interface Version 2.2.4 (C) 2005-2009 Sun Microsystems, Inc. All rights reserved.

RAW host disk access VMDK file r:\virtuals\extldata.vmdk created successfully.

Bug: The vmdk disk is now registered in the VirtualBox volume manager, but there is a wrong size. The size should be 22 GB, but it's only 1.9 GB in VirtualBox. I can access the disk from a Guest Linux OS.

#7740 obsolete BSOD on guest when installing XP Svein Seldal
Description

Running VBox 3.2.10 r66523 on Ubuntu Maverick 64-bit (10.10) *). Host is Intel Core 2 Duo T9900 @3.06GHz. 8 GB host memory. Guest is Windows XP (32-bit), slipstreamed (with MS ServicePack) up to SP3.

*) I observe same symptoms when running VBox on Win7 64-bit.

I've had troubles installing XP Guest with SATA support without getting BSOD.

The main problem for me was to A) find which SATA I could use B) what version of the driver and C) what product to select during installation.

So after reading on the web I found A) Intel AHCI a.k.a Intel Matrix Storage Manager driver and C) use the ICH8M-E/M driver.

However, VBox seems picky about which version of the SATA driver you pick. Hence:

iaStor.sys version:

  • 7.8.0.1012 Works
  • 8.8.0.1009 BSOD during installation
  • 8.9.0.1023 BSOD during installation
  • 9.6.0.1014 BSOD during installation

When installing all versions accepts the driver during the F6 phase and XP is capable of discovering the harddrive. However, the installation dies with BSOD when it is 32 minutes or so remaining. The BSOD has no message (no IRQL_xxx or similar), and the STOP is 0x000000F4 (0x00000003, ...)

I have not experimented with using other variants like ICH9 or ICH10 SATA drivers.

IMHO a notice should be available somewhere in docs/website to indicate which iaStor driver and version to use for XP Guest.

#1972 fixed A CEntOS 4.6 VM never finish to boot. svbu12
Description

The PC's hardware:

  • CPU: Intel Pentium 4 3.2 GHz Dual Core.
  • RAM: 3 GB
  • OS: Linux CEntOS 4.6 With all patches.
  • VM RAM: I assigned a whole GB of RAM just for the VM.

Problem Description:

  1. I downloaded a DVD-ROM .ISO of CentOS-4.6-i386-binDVD.iso from the CentOS mirror
  2. I start Sun VBox.
  3. I create a new VM.
  4. I install CEntOS 4.6 from the DVD image.
  5. I follow directions and install a CEntOS 4.6 into a logical VM 30 GB disk.
  6. The install process works properly until the end.
  7. Once it is completed, I reboot the VM, Then I change the boot order from DVD image to VM 30 GB hdd.
  8. I click on the start button to restart the CEntOS 4.6 VM.
  9. All we see is a black screen. even after an hour, it never change.

Other info:
I know the DVD image run properly. I used it to install the physical machine.

I know Sun VBox works properly too. I can run Linux DSL, Ubuntu 8.08, CentOS 5.2 And a few other very properly...

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy