RE: [Xen-ia64-devel] [PATCH] [RESEND][PATCH 1/3]clean up vti code

["Xu, Anthony" <anthony.xu@xxxxxxxxx>]

Hi Alex,
Please ignore this patch.

Thanks,
-Anthony 

>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Xu, Anthony
>Sent: 2006?5?25? 22:27
>To: Alex Williamson; Zhang, Xiantao
>Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [Xen-ia64-devel] [PATCH] [RESEND][PATCH 1/3]clean up vti code
>
>Hi Alex,
>Thinks for your detailed information,
>I did see the bad swapfile entry, but VTIdomain still can boot up
>in my box, so I didn't notice this issue.
>
>These new patches has fixed this issue.
>
>
>Thanks,
>-Anthony
>
>>-----Original Message-----
>>From: Alex Williamson [mailto:alex.williamson@xxxxxx]
>>Sent: 2006?5?24? 12:49
>>To: Zhang, Xiantao
>>Cc: Xu, Anthony; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>>Subject: RE: [Xen-ia64-devel] [PATCH] [RESEND]clean up vti code
>>
>>On Wed, 2006-05-24 at 10:57 +0800, Zhang, Xiantao wrote:
>>> Hi Alex,
>>>     I have checked this patch on tip(10146), and didn't met the issue
>>> with rhel4-u2 and urhel4-u3 image. Maybe the issue you mentioned is
>>> not caused by Anthony's patch :)
>>
>>   It's possible, but I verified that removing the patch allowed domVTI
>>to boot normally and re-adding it produced the error mentioned.  My
>>domVTI setup uses a physical disk device.  Note that the system is
>>seeing the disk devices, but there are some VM issues with the bad
>>swapfile entry and killing udevstart.  Thanks,
>>
>>      Alex
>>
>>--
>>Alex Williamson                             HP Linux & Open Source Lab

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