WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18421 StatusReport --- ioemu er

To: "Zhang, Jingke" <jingke.zhang@xxxxxxxxx>, Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Subject: RE: [Xen-ia64-devel] Xen/IPF Unstable CS#18421 StatusReport --- ioemu error
From: "Zhang, Jingke" <jingke.zhang@xxxxxxxxx>
Date: Tue, 2 Sep 2008 15:02:20 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-ia64-devel@xxxxxxxxxxxxxxxxxxx" <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 02 Sep 2008 00:02:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BB1F052FCDB1EA468BD99786C8B1ED2C013B9CE546@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <BB1F052FCDB1EA468BD99786C8B1ED2C013B9CE486@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080902041743.GB4485%yamahata@xxxxxxxxxxxxx> <BB1F052FCDB1EA468BD99786C8B1ED2C013B9CE546@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AckMst14Xnk3lgEIQSqOSbRTrZVRYwABqGuAAAQFz9A=
Thread-topic: [Xen-ia64-devel] Xen/IPF Unstable CS#18421 StatusReport --- ioemu error
Zhang, Jingke wrote:
> Isaku Yamahata wrote:
>> On Tue, Sep 02, 2008 at 11:22:27AM +0800, Zhang, Jingke wrote:
>>> Hi all,
>>>     We found all the VTI guests can not be booted up with this
>>>     Cset#18421 (XenU can boot). Last test on Cset#18369 is good to
>>> work. The failure is: when we boot up VTI, qemu will show a white
>>> box and disappeared after 1 second. I have checked both local ioemu
>>> and remote-ioemu, they both can not work. Did anyone find this by
>>> using latest Xen-ia64?
>>
>> Hmm, I'm afraid that c/s 18394:dade7f0bdc8d causes it.
>> Could you confirm that?
>>
>> I suppose that even if the window of virtual frame buffer dissapears,
>> VTi guest OS is still working and serial console can be accessed.
>> If so, GFW should be patched to tell qemu-dm where the virtual frame
>> buffer memory is.
>
> Hi Isaku,
>     I checked the console of VTI, it does not work. CPU time always
>     stays 0.2 (guest should hang). Anyway, I will try 18394 to narrow
> down this issue.
>

Hi Isaku,
    It should be as you said. 18394 caused the issue. I tested 18394, issue 
exists. With 18393, VTI can be booted well. Thanks!


>
> Thanks,
> Zhang Jingke
>
> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel



Thanks,
Zhang Jingke

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