Re: [Xen-devel] Re: logs attached. Re: [Xen-users] Can not findthe cdrom device in /dev/ afterbooted into xen(3.0.3)

[Keir Fraser <keir@xxxxxxxxxxxxx>]

Looks like the I/O ports are allocated correctly to the device in both cases
(both Xen and native). So I have no idea why the IDE PCI probing code isn't
picking up on this. At this point I'd be adding tracing to the two kernels
to find out where their probing paths diverge.

 -- Keir

On 1/12/06 7:19 pm, "Liang Yang" <multisyncfe991@xxxxxxxxxxx> wrote:

> See attached.
> 
> ----- Original Message -----
> From: "Keir Fraser" <keir@xxxxxxxxxxxxx>
> To: "Keir Fraser" <keir@xxxxxxxxxxxxx>; "Liang Yang"
> <multisyncfe991@xxxxxxxxxxx>; <tim.post@xxxxxxxxxxxxxxx>; "Petersson, Mats"
> <Mats.Petersson@xxxxxxx>
> Cc: <xen-devel@xxxxxxxxxxxxxxxxxxx>; <xen-users@xxxxxxxxxxxxxxxxxxx>
> Sent: Friday, December 01, 2006 11:58 AM
> Subject: Re: [Xen-devel] Re: logs attached. Re: [Xen-users] Can not findthe
> cdrom device in /dev/ afterbooted into xen(3.0.3)
> 
> 
>> Lspci -vvv output for native and Xen kernels may be useful, just for
>> device
>> 00:1f.1 (the IDE device). Then we could see which I/O resources the device
>> is claiming in each case
>> 
>> -- Keir
>> 
>> On 1/12/06 6:56 pm, "Keir Fraser" <keir@xxxxxxxxxxxxx> wrote:
>> 
>>> Actually, now I look closer it seems that on native the IDE I/O ports are
>>> detected as 0x1860-0x1867, but the Xen kernel is failing to detect this
>>> and
>>> is then failing to register at the default 0x1f0, probably because a
>>> legacy
>>> ISA IDE driver is registered there. So there is definitely something odd
>>> going on here but tracking it down will probably require adding some
>>> kernel
>>> tracing (e.g., to ide_hwif_configure(), to determine why it is failing to
>>> find the special location of the IDE I/O ports).
>>> 
>>>  -- Keir
>>> 
>>> On 1/12/06 6:48 pm, "Liang Yang" <multisyncfe991@xxxxxxxxxxx> wrote:
>>> 
>>>> I just download Xen source and do "make world;make
>>>> install;depmod..;mkinitrd...". I don't know which config file will be
>>>> used
>>>> if I build Xen like this (maybe the config-2.6.16.29-xen under the
>>>> directory
>>>> dist/install/boot).
>>>> 
>>>>  I did a grep with "CONFIG_BLK_DEV_PIIX" and found it it set to m in the
>>>> config-2.6.16.29-xen. I did a modprobe piix, however my CD-ROM is still
>>>> not
>>>> fired up (nothing is show up /dev/ as either cdrom or hd*).
>>>> 
>>>> Liang
>>>> 
>>>> ----- Original Message -----
>>>> From: "Keir Fraser" <keir@xxxxxxxxxxxxx>
>>>> To: "Liang Yang" <multisyncfe991@xxxxxxxxxxx>;
>>>> <tim.post@xxxxxxxxxxxxxxx>;
>>>> "Petersson, Mats" <Mats.Petersson@xxxxxxx>
>>>> Cc: <xen-devel@xxxxxxxxxxxxxxxxxxx>; <xen-users@xxxxxxxxxxxxxxxxxxx>
>>>> Sent: Friday, December 01, 2006 11:34 AM
>>>> Subject: [Xen-devel] Re: logs attached. Re: [Xen-users] Can not find the
>>>> cdrom device in /dev/ afterbooted into xen(3.0.3)
>>>> 
>>>> 
>>>>> On 1/12/06 6:27 pm, "Liang Yang" <multisyncfe991@xxxxxxxxxxx> wrote:
>>>>> 
>>>>>> Hi Tim, Keir and Mats,
>>>>>> 
>>>>>> I attached all the detailed log files (text file format). The file
>>>>>> extension
>>>>>> indicate the version of environment. Please take a look.
>>>>> 
>>>>> ESB2 should be supported by the piix IDE driver. Which XenLinux kernel
>>>>> config are you using? Either you need the driver compiled into the
>>>>> kernel,
>>>>> or you need to load it as a module. Look for a line containing
>>>>> CONFIG_BLK_DEV_PIIX in your .config -- it should be "=m" or "=y".
>>>>> 
>>>>> If it's compiled as a module, and you installed the modules on your
>>>>> filesystem, you may be able to fire up the CDROM drive by typing
>>>>> 'modprobe
>>>>> piix'.
>>>>> 
>>>>> -- Keir
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> Xen-devel mailing list
>>>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>>>> http://lists.xensource.com/xen-devel
>>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>>> http://lists.xensource.com/xen-devel
>>> 
>> 
>> 
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
>> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel