Re: [Xen-devel] Xen doesnt recognize my root fs, while native kernel can ???

[Keir Fraser <keir@xxxxxxxxxxxxx>]

That's fine. My conclusion is that this is user error: you are trying to
mount /boot/sda2 and you actually mean /dev/sda2.

 -- Keir

On 13/6/07 10:21, "Jun Koi" <junkoi2004@xxxxxxxxx> wrote:

> Here is the screenshot taken with a digital camera. I hope the screen
> is clear enough for you to see.
> 
> Thanks,
> Jun
> 
> 
> 
> On 6/13/07, Jun Koi <junkoi2004@xxxxxxxxx> wrote:
>> Hi Mats,
>> 
>> On 6/13/07, Petersson, Mats <Mats.Petersson@xxxxxxx> wrote:
>>> 
>>> 
>>>> -----Original Message-----
>>>> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>>> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Jun Koi
>>>> Sent: 13 June 2007 09:54
>>>> To: Keir Fraser
>>>> Cc: xen-devel
>>>> Subject: Re: [Xen-devel] Xen doesnt recognize my root fs,
>>>> while native kernel can ???
>>>> 
>>>> On 6/13/07, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
>>>>> On 13/6/07 08:49, "Jun Koi" <junkoi2004@xxxxxxxxx> wrote:
>>>>> 
>>>>>>>> The point is that Xen doesnt boot in the first place,
>>>> so I cannot
>>>>>>>> provide xm dmesg!
>>>>>>>> 
>>>>>>>> Below is the output from dmesg (native kernel) and
>>>> Dom0's .config.
>>>>>>>> Anything else do you need?
>>>>>>> 
>>>>>>> Can you get a serial line on the machine?
>>>>>> 
>>>>>> Opps, that is compicated, as I dont have a cable to do that.
>>>>>> 
>>>>>> So if you have no suggestion, perhaps I must try this
>>>> way. But perhaps
>>>>>> it take more than a week, as I am away in few days.
>>>>> 
>>>>> There's a decent chance that comparing the two dmesg
>>>> outputs will show some
>>>>> important deviation in the case of running on Xen that is
>>>> causing the boot
>>>>> failure. Without the failing output it's hard to know where to start
>>>>> looking.
>>>>> 
>>>> 
>>>> I see, but can you imagine some reasons why that happens?  It makes
>>>> absolute no sense to me.
>>> 
>>> There are lots of possible reasons. The most likely is that your kernel
>>> in the native has drivers that are not part of the Xen default
>>> configuration.
>>> 
>>> The other very common problem is that you don't have those necessary
>>> drivers in the "initrd" for your Xen. This is a problem that is posted
>>> about three times a week (at least) on the Xen Users mailing list [where
>>> this problem probably should be discussed - but I think since it's
>>> started here, we'll keep it here].
>>> 
>> 
>> No, that is not a reason in my case. I did it this way:
>> - Native kernel (2.6.18) is compiled with all the necessary drivers
>> built-in. That means I dont need initrd to boot my machine with this
>> kernel. And it boots well.
>> - I copied the .config of native kernel above to Dom0, and compile
>> Dom0 with this option. (Of course before compiling, I enabled Xen
>> option, as you can see in the .config of Dom0 I sent in the last
>> mail). Again this time I dont need initrd.
>> 
>> So it is logical that Dom0 must boot, but it fails actually. That is
>> why I find the situation very strange.
>> 
>> 
>>>> I have found that my machine has no serial port, so perhaps I must buy
>>>> a serial card to debug this problem. Wonder if there is another way to
>>>> avoid that (?)
>>> If you have a digital camera and you add "noreboot" to the commandline
>>> of "xen.gz" in your grub configuration, maybe you can upload (to some
>>> photo-web-site or such) a screen-shot of the final few lines of the boot
>>> and send a link to the list - that may not give all clues, but at least
>>> it will indicate what's going on.
>> 
>> OK, I will do that, as it is not desired to buy a serial card :-)
>> 
>> Thanks,
>> Jun
>> 


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