I can reproduce the iostat -En issue (SATA is reported as ATA). I am  
not sure that this is what's causing the installer to take several  
minutes discovering the SATA disk. If it is, I'd strongly suggest to  
get the fix into 2008.11.

Achim.

On Nov 18, 2008, at 3:15 PM, jan damborsky wrote:

> Hi Achim, Alexander,
>
> as far as problem seen in VirtualBox is concerned, could you please
> provide more details about configuration you used when encountering
> that issue (HW, host operating system, how much memory you
> dedicated to the guest, other settings - VT-x/AMD-V,ACPI, ...) ?
>
> There were couple of SATA issues reported in 2.0.2, which are fixed
> in 2.0.4:
>
> http://www.virtualbox.org/ticket/2292
> http://www.virtualbox.org/ticket/2182
>
> I have tried to launch the installer on VB 2.0.2 guest (1GB memory)
> with one SATA disk attached and I haven't seen that hang in disk  
> discovery -
> Disk screen was displayed immediately.
> I haven't tried the installation.
>
> I have used following configuration:
>
> host:
> -----
> HW: Lenovo Thinkpad X61 (4GB RWM)
> SW: OpenSolaris build 101a
> VB: 2.0.2
>
> guest:
> ------
> base memory: 1024 MB
> OS Type: OpenSolaris
> ACPI: Enabled
> IO APIC: Enabled
> VT-x/AMD-v: disabled (workaround for bug 2292)
> PAE/NX: Enabled
>
>
> With respect to problems with SATA disk discovery hanging on bare  
> metal,
> do you happen to know, which HW configuration might be suffering
> from this issue ?
>
> Thank you,
> Jan
>
>
> William Schumann wrote:
>> There are two separate bugs that are addressing problems with  
>> library libdiskmgt correctly reporting type on SATA drives for real  
>> hardware:
>>
>> 6558646 DM_CTYPE attribute is set to "unknown" for SATA controllers  
>> handled by "sata" driver
>> http://monaco.sfbay/detail.jsf?cr=6558646
>>
>> auto-installer can not identify SATA disk type (most likely a  
>> duplicate of the former)
>> http://defect.opensolaris.org/bz/show_bug.cgi?id=4387
>>
>> The former has been in the 'accept' state since June.  If  
>> libdiskmgt bugs are now affecting VirtualBox, they should perhaps  
>> be escalated (currently P3).
>>
>> I will inquire about status of fixes for libdiskmgt - they are not  
>> presently being handled by the install group.
>> William Schumann
>>
>> Dave Miner wrote:
>>> Vincent Murphy wrote:
>>>> Achim,
>>>>
>>>> Best person to contact is Dave Miner - however, I would also send  
>>>> mail to indiana-eng as this may be a known issue. If not then  
>>>> raise a bug :-)
>>>>
>>>
>>> Achim, Alexander:  William Schumann on the install team is the  
>>> best person to work with on disk discovery issues; he's in Prague  
>>> and should be back in the office tomorrow since today's a holiday  
>>> there.  I've copied him.
>>>
>>> I believe I've seen this issue, though I rarely have used SATA in  
>>> my vbox instances, and I'm not aware of any existing bug reports  
>>> related to it.
>>>
>>> Dave
>>>
>>>> Thanks
>>>> Vincent
>>>>
>>>> On 11/17/08 12:46, Achim Hasenmueller wrote:
>>>>> Hi Vincent,
>>>>>
>>>>> when installing OpenSolaris (2008.5 or .11) in a VirtualBox VM  
>>>>> with a SATA disk configured for the VM, the installer takes  
>>>>> several minutes to discover the disk.
>>>>>
>>>>> We have been trying to debug this from our end but without  
>>>>> success. Also we have found reports on the web about people  
>>>>> having the same issue with physical hardware. Therefore, we now  
>>>>> need help from the OS team. Who in your team could Alexander  
>>>>> work with?
>>>>>
>>>>> Thanks!
>>>>> -- 
>>>>> Achim Hasenmueller
>>>>> Director Engineering, VirtualBox
>>>>> Sun Microsystems GmbH
>>>>> Werkstrasse 24
>>>>> 71384 Weinstadt, Germany
>>>>> phone: +49 7151 604050
>>>>>
>>>>>
>>>>> ================================================
>>>>> Sitz der Gesellschaft: Sun Microsystems GmbH,
>>>>> Sonnenallee 1, 85551 Kirchheim-Heimstetten
>>>>> Amtsgericht Muenchen: HRB 161028
>>>>> Geschaeftsfuehrer: Thomas Schroeder,
>>>>> Wolfgang Engels, Dr. Roland Boehmer
>>>>> Vorsitzender des Aufsichtsrates: Martin Haering
>>>>> ================================================
>>>>>
>>>>>
>>>>
>>>
>


Reply via email to