This issue should be there for a little long time (before 3.0.3). But it performs a little strange. We found VTI domain can not be created up with 4096M memory by command "xm create vti.config" in recent changeset. But at least in xen 3.0.3 it still can be created up with same command.
We have the automatic case to check 4096M memory of VTI domain, but every time it can pass in nightly testing. The difference is nightly testing use following script to create VTI domain: "xterm -display localhost:1.0 -e ' xm create vti.config"
Best Regards,
Yongkang (Kangkang) ÓÀ¿µ
>-----Original Message-----
>From: xen-devel-bounces@lists.xensource.com
>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Zhang,
>Xiantao
>Sent: 2006Äê11ÔÂ8ÈÕ 12:00
>To: xen-devel@lists.xensource.com
>Cc: xen-ia64-devel
>Subject: [Xen-devel] [Qemu]Fix for VTi's 3G memroy limit
>
>This patch fixed 3G memory limit for VTi domain.
>Due to some logic change in Qemu, so initializing ram_size should be
>moved up.
>
>Signed-off-by : Zhang xiantao <xiantao.zhang@intel.com>
>
>Thanks & Best Regards
>-Xiantao
>
>OTC,Intel Corporation
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
fix_vti_3G.patch (0.88 KB)