VTI (vcpus=2)
SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild
UPVTI_Kernel_Build 1 UP VTI and do kernel build
SMPVTI_Windows SMPVTI windows(vcpu=2)
SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU
Thanks,
Zhang Jingke
) was just
before the 19246. Please merge the xen-unstable again for fix. :-)
BTW, the qcow-VTI boots slowly issue can be fixed by latest ioemu code.
After your merging, we will verify that fix. Thank you very much!
Thanks,
Zhang Jingke
___
Xen-ia64
Isaku Yamahata wrote:
Could you try the attached patch?
Hi Isaku,
Sorry for replying late, I just retruned to work after weekend.
On our machine, I verified this issue was gone with Cset#19206. Thank you
for your fix!
On Fri, Feb 13, 2009 at 05:03:07PM +0800, Zhang, Jingke wrote
-20090213/xen/include/xen/list.h:170
(XEN)
(XEN)
(XEN) Reboot in five seconds...
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
/Windows XenU
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
Zhang, Jingke wrote:
Hi all,
The dom0 crash with 2048M memory issue has been fixed. One
issue was found in Cset#18952 for Qcow image.
One issue was fixed:
=
[FIXED] With dom0_max_mem=2048M, dom0 will crash while booting.
(no such issue before dom0#742
Linux/Windows XenU
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
UPVTI_Kernel_Build 1 UP VTI and do kernel build
SMPVTI_Windows SMPVTI windows(vcpu=2)
SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel
Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel
Isaku Yamahata wrote:
On Mon, Dec 08, 2008 at 11:31:15AM +0800, Zhang, Jingke wrote:
Hi Isaku,
We re-get the detail information from serial port, please see
below. Two comments add:
Thank you.
1. We can be sure the Cset#18832 works well on the same tiger4
machine. But we did
to kill init!
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
SMPVTI Linux/Windows XenU
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
/Windows XenU
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
each other
3. When all the vcpus are taken by Dom0, SMP_VTI booting speed is very slow
during NVRAM loading period.
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
=f002f9fffe00 bsp=f002f9ff93b0
(XEN)
(XEN)
(XEN) Panic on CPU 3:
(XEN) Fault in Xen.
(XEN)
(XEN)
(XEN) Reboot in five seconds...
Thanks,
Zhang Jingke
___
Xen-ia64-devel
SMP VTI (vcpus=2)
SMPVTI_Kernel_Build VTI (vcpus=4) and do KernelBuild
UPVTI_Kernel_Build 1 UP VTI and do kernel build
SMPVTI_Windows SMPVTI windows(vcpu=2)
SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU
Thanks,
Zhang
. */
/* Here page-count_info = PGC_allocated | N where N = 1*/
__guest_physmap_add_page(d, xatp.gpfn, mfn);
-page = NULL; /* prevent put_page() */
out:
domain_unlock(d);
Yes, I retest it with your patch. VTI guest can be booted when domain_id is
62.
Thanks,
Zhang Jingke
1 UP VTI and do kernel build
SMPVTI_Windows SMPVTI windows(vcpu=2)
SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
?
Thanks! :)
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
SMPVTI_Windows SMPVTI windows(vcpu=2)
SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
regards,
Hi KUWAMURA and Isaku,
With the patch on CS#18580, Linux#687, ioemu#0f3d6384..., the two issues
can be fixed!
I also rerun the whole test, no regression. Thanks!
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel
,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
Isaku Yamahata wrote:
On Mon, Oct 06, 2008 at 09:54:13AM +0800, Zhang, Jingke wrote:
Hi all,
There is no new regression found in Cset#18580. Three old issues
still existed.
Old issue (3):
1. Qemu will disappear and VTI hangs when we do 'xm restore' and
'xm migrate'
Hi. Does
Isaku Yamahata wrote:
On Mon, Oct 06, 2008 at 11:16:02AM +0800, Zhang, Jingke wrote:
Isaku Yamahata wrote:
On Mon, Oct 06, 2008 at 09:54:13AM +0800, Zhang, Jingke wrote:
Hi all,
There is no new regression found in Cset#18580. Three old
issues still existed.
Old issue (3):
1
Isaku Yamahata wrote:
On Sat, Sep 20, 2008 at 01:27:03PM +0800, Zhang, Jingke wrote:
Hi all,
Cset#18501 has one new issue.
1. Qemu will disappear and VTI hangs when we do 'xm restore' and
'xm migrate'
Given that the last report is based on the change set of 18483,
I is likely
VTI live-migration
One_SMPVTI_4096M1 VTI (vcpus=2, mem=4096M)
---
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http
Isaku Yamahata wrote:
On Mon, Sep 15, 2008 at 12:47:31PM +0800, Zhang, Jingke wrote:
Hi all,
With remote-ioemu, Cset#18483 has two new issues (both can pass
with local ioemu):
1. Qemu windows will disappear soon after booting, with 4095M
memory.
(Did you mean 4096M?)
No, just
Isaku Yamahata wrote:
On Fri, Sep 12, 2008 at 11:18:12AM +0800, Zhang, Jingke wrote:
Isaku Yamahata wrote:
Hi.
It would be very nice to arrange to send mails to the xen-changelog
mailing list when commiting to qemu-xen-unstable.git.
thanks,
On Thu, Sep 11, 2008 at 04:54:51PM +0100, Keir
-j3. But they both use local ioemu (ia64 is
different with x86?). What command did you use to enable ioemu-remote?
So, remote-ioemu may not affect VTI booting, I will double check that with
your patch. Thanks.
Thanks,
Zhang Jingke
___
Xen-ia64
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
:
58cbd0ecff9e12e75b32fe21c51083ac9550e40d
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
, they both can not work.
Did anyone find this by using latest Xen-ia64?
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
openGFW binary
(xenia64-gfw-126.bin).
This issue is very easy to reproduce. Could you please help to look at it?
Thank you very much!
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http
Tristan Gingold wrote:
On Tue, Sep 02, 2008 at 11:43:58AM +0800, Zhang, Jingke wrote:
Hi Tristan,
We found VTI guest with 3073M (memory is a little more than 3G)
can not be booted up. After some investigation, our engineer
found some pages are ruined by unknow reason. A EFI driver
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
Akio Takebe wrote:
Zhang, Jingke wrote:
Tristan Gingold wrote:
On Tue, Sep 02, 2008 at 11:43:58AM +0800, Zhang, Jingke wrote:
Hi Tristan,
We found VTI guest with 3073M (memory is a little more than 3G)
can not be booted up. After some investigation, our engineer
found some pages
) and do KernelBuild
UPVTI_Kernel_Build 1 UP VTI and do kernel build
SMPVTI_Windows SMPVTI windows(vcpu=2)
SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU
---
Thanks,
Zhang
UPVTI_Kernel_Build 1 UP VTI and do kernel build
SMPVTI_Windows SMPVTI windows(vcpu=2)
SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU
---
Thanks,
Zhang Jingke
That is good, thanks!
By the way, as Keir has suggested IPF-Xen does not need to support remote-qemu
(or stubdom) in Xen3.3, will IPF plan to support them in Xen3.3 release?
Thanks,
Zhang Jingke
-Original Message-
From: Isaku Yamahata [mailto:[EMAIL PROTECTED]
Sent: 2008年8月1日 19:14
build
SMPVTI_Windows SMPVTI windows(vcpu=2)
SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU
---
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing
Isaku Yamahata wrote:
On Thu, Jul 31, 2008 at 10:33:25AM +0800, Zhang, Jingke wrote:
This error should be related to the remote-qemu building (we have
disabled stub-domain compiling). If I use CONFIG_QEMU=ioemu make
-j3 command to make, it can work. Does anyone also meet this issue
). If I use CONFIG_QEMU=ioemu make -j3
command to make, it can work. Does anyone also meet this issue? If so,
we need to fix this for IPF in Xen3.3 release. Thanks!
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
Samuel Thibault wrote:
Zhang, Jingke, le Thu 24 Jul 2008 09:07:03 +0800, a écrit :
As we know, Xen has some changes in the building process now. For
x86 side can not play with stub-domain well, we did not compile the
stub-domain in IPF.
Oh? I'm interested in the build log then, because
windows(vcpu=2)
SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU
---
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http
Hi Tristan,
There should be some mistake of my setting. With latest open-GFW#126, this
bug can be fixed! Sorry for the misleading.
Thanks,
Zhang Jingke
-Original Message-
From: Tristan Gingold [mailto:[EMAIL PROTECTED]
Sent: 2008年7月21日 9:36
To: Zhang, Jingke
Cc: [EMAIL PROTECTED
appreciate your help! :)
On Wed, Jul 09, 2008 at 01:36:19PM +0800, Zhang, Jingke wrote:
Hi all,
When we check the /proc/meminfo in the VTI, we found the total
memory is about 100MB less than what we config. For x86_64 and KVM
side, they are different. So, I want to ask a question
: 1024772k/1048512k available
(2105k kernel code, 0k reserved, 1297k data, 196k init)
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
---
Failed case id Description
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
issue did not happen on ia32 part. So, I am afraid there
may be some issue here. Thanks!
On Sun, Jun 22, 2008 at 11:50:11AM +0800, Zhang, Jingke wrote:
Hi Isaku,
Recently, we tried to make and make install Xen-17892 on RHEL5u2
native (not installed the virtualization rhel5u2-ia64). Its
test now. I tried to use some old
version of Xen, such as 17772. It still had the same error. So did you
ever meet the same thing by using GCC 4.1.2 as your building env? Thanks
very much!
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
)
SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU
---
Failed case id Description
Thanks,
Zhang Jingke
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
. Link is
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1253.
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
, Zhang, Jingke wrote:
Hi all,
With Cset#17671, qcow creating issue was fixed! It can use qcow
file to create a VTI with disk = [ 'tap:qcow:/***,hda,w' ] config
file.
One old issue still existed:
==
Windows guest still can not be booted up
)
SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
(vcpu=2)
SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU
---
Failed case id Description
Thanks,
Zhang Jingke
Description
SMPVTI_Windows SMPVTI windows(vcpu=2)
SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU
VTI_Windows_PV Windows VTI PV
Thanks,
Zhang Jingke
:
On Fri, May 16, 2008 at 10:53:09AM +0800, Zhang, Jingke wrote:
Issue2. Windows guest can not be booted up.
--- VTI_Windows2008 can not be booted. When we ran
bootmgfw.efi, it would also report failure in the qemu screen.
--- VTI_Windows2003 guest will crash at starting
windows
Zhang, Jingke wrote:
Hi all,
The old VTI Save-Restore issue was fixed now. Then VTI
saverestore, live-migration can pass!
Two new block isses were found:
Issue1. Qcow image made by qcow-create of this Cset failed to be
recognazied.
--- On IA32 part, we still met
)
SMPWin_SMPVTI_SMPxenU SMPVTI Linux/Windows XenU
VTI_Windows_PV Windows VTI PV
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
xc.domain_set_policy_cpuid(self.vm.getDomid())
AttributeError: domain_set_policy_cpuid
Thanks,
Kouya
Yes, my xend.log reported the same with you. Thank you very much!
Zhang, Jingke writes:
Hi all,
This is today's Xen/IPF nightly test report against Cset#17602.
One new issue was found in VTI
/A
Thanks,
Zhang Jingke
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
Xen/IA64 Healthiness Report
All the cases passed in this changeset.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with Dual Core)
PAL version: 9.08
Service OS: RHEL4u3 IA64
Xen/IA64 Healthiness Report
Only Win pv failed in this changeset, network still does not work in the
Windows vti with pv driver.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2
Xen/IA64 Healthiness Report
Only Win pv failed in this changeset, network still does not work in the
Windows vti with pv driver.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2
Xen/IA64 Healthiness Report
Only Win pv failed in this changeset, network still does not work in the
Windows vti with pv driver.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2
Xen/IA64 Healthiness Report
Only Win pv failed in this changeset, network still does not work in the
Windows vti with pv driver.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2
Xen/IA64 Healthiness Report
Only Win pv failed in this changeset, network still does not work in the
Windows vti with pv driver.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2
Xen/IA64 Healthiness Report
All the cases in the test passed. No new issues in this Cset.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with Due Core)
PAL version: 8.47
Xen/IA64 Healthiness Report
Only one issue:
1. SMP_VTI domain will meet kernel panic after rebooting itself for some
times.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with
Xen/IA64 Healthiness Report
All the cases passed in the test. There are no issues in the recent
Csets.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with Due Core)
PAL
Xen/IA64 Healthiness Report
All the cases could pass in the test.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with Due Core)
PAL version: 8.47
Service OS: RHEL4u3 IA64
Xen/IA64 Healthiness Report
All testing cases pass. The qume's problem in Cset#13773 has been
solved.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with Due Core)
Service OS:
Xen/IA64 Healthiness Report
One issues:
1. Qemu can not be opened when creating a VTI domain. But the VTI can be
created successfully without qemu.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors
Xen/IA64 Healthiness Report
All the cases passed in the test. So, only one issue:
1. With serial='pty', UP_VTI booting speed is a little slower.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number:
Hi all,
Cset#13360 met a dom0 crash. So tests can not be made.
The serial port log is in the attachment.
Thanks,
Zhangjingke
(XEN) Your elilo is not Xen-aware. Bootparams fixed
(XEN) Xen command line: BOOT_IMAGE=scsi0:\EFI\redhat\xen.gz com2=57600,8n1 cons
ole=com2 sched=credit
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Zhang,
Jingke
Sent: Thursday, January 11, 2007 9:17 AM
To: xen-ia64-devel@lists.xensource.com
Subject: [Xen-ia64-devel] With Cset#13360, dom0-booting crashed.
Hi all,
Cset#13360 met a dom0 crash. So tests can not be made
Xen/IA64 Healthiness Report
Totally one old issue:
1. With serial='pty', UP_VTI booting speed is a little slower.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with Due Core)
Hi Alex,
With the new Cset#13122, I met the xen0's crash even dom0_mem=512M. My
elilo.conf and the serial port information are in the attachments. Thank you.
Thanks,
Zhangjingke
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alex
Williamson
Sent:
Okay Alex,
I will try 13117 as you said. Thanks!
Thanks,
Zhangjingke
-Original Message-
From: Alex Williamson [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 12:22 PM
To: Zhang, Jingke
Cc: xen-ia64-devel
Subject: RE: [Xen-ia64-devel] crash while initializing balloon driver
Hi Alex,
As you said, I use hg export 13117 | patch -p1 -R in the
Cset#13122. Without 13117's patch, dom0 can boot up (Mem=1024M).
Thanks,
Zhangjingke
-Original Message-
From: Alex Williamson [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 12:22 PM
To: Zhang, Jingke
Cc
Xen/IA64 Healthiness Report
Two issues:
1. UP_VTI booting speed is very slow. (Without serial='pty')
2. SMP_VTI LTP test could not finish within 80 minutes. If we made
UP_xen0 and MT_disabled, that case could pass.
Testing Environment:
Xen/IA64 Healthiness Report
Several issues:
1. If we enable MT and make xen0 to be UP, all the cases can pass.
2. If we disable MT and make xen0 to be SMP, VTI booting speed is very
slow and SMPVTI_LTP performed slowly.
Testing Environment:
Xen/IA64 Healthiness Report
Several issues:
1. VTI Linux domain boots slowly. UP_VTI's booting needs 170s or so.
2. SMPVTI_LTP performed slowly.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors
Xen/IA64 Healthiness Report
Several issues:
1. VTI Linux domain boots slowly, given 'serial=pty' is enabled.
2. SMPVTI_LTP performed slowly.
Except SMPVTI_LTP case, all the other nightly cases can pass in manually
testing.
Testing Environment:
Xen/IA64 Healthiness Report
Several issues:
1. VTI Linux domain boot slowly, if enabled 'serial=pty'.
2. Even without serial='pty', the VTI domain boots very slowly. (UPVTI
needs 150s and VTI_Win2k3svr needs 8 minutes or so)
3. SMPVTI_LTP performed slowly.
Except
Hi Alex,
Using Flash.fd.2006.12.01 and Cset#12796 (with the accel_ide_pio
patch from FJ), I have done the VTI_Win2k3server installation within an
hour. ( Please make sure that serial='pty' has been commented in your
VTI config file.)
I did not meet the problem you said.
Thanks,
)
-
Maybe you can do a compare with your settings.
Thanks,
Zhangjingke
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Zhang,
Jingke
Sent: Friday, December 08, 2006 4:03 PM
To: Alex Williamson; You, Yongkang
Cc: [EMAIL PROTECTED]; xen-ia64-devel
Xen/IA64 Healthiness Report
This Cset is the same with the last Cset#12796
Several issues:
1. VTI Linux domain boot slowly, if enabled 'serial=pty'.
2. SMPVTI_LTP performed slowly.
Except SMPVTI_LTP case, all the other nightly cases can pass in manually
testing.
Xen/IA64 Healthiness Report
Several issues:
1. VTI Linux domain boot slowly, if enabled 'serial=pty'.
2. SMPVTI_LTP performed slowly.
Except SMPVTI_LTP case, all the other nightly cases can pass in manually
testing.
Testing Environment:
Hi Kouya,
With your patch, win2k3 installation can be done within 40 minutes!
I have integrated #Cset12525 with the accelerating patch.
It took 20 minutes to load file (you will see it in a blue screen).
And then the guest quickly installed the win2k3 from the CD-ROM, totally
within
Xen/IA64 Healthiness Report
Several issues:
1. VTI Linux domain boot slowly, if enabled 'serial=pty'.
(performance issues):
2. SMPVTI LTP test has a 100% performance downgrade.
3. UPVTI Kernel build has a performance downgrade.
Testing Environment:
Ok, let me try. Thanks!
Thanks,
Zhangjingke
-Original Message-
From: Keir Fraser [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 22, 2006 4:01 PM
To: Zhang, Jingke
Cc: xen-ia64-devel
Subject: Re: The vcpus can change from one LP to another LP very
frequently
Can you narrow it down
Xen/IA64 Healthiness Report
Several issues:
1. Destroying XenU domains makes Xen0 Crash.
2. VTI Linux domain boot slowly, if enabled 'serial=pty'.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors
Hi all,
On Cset 12444, when creating and destroying two SMP_XenU guests, I
met xen0 crashed. I can reproduce it for many times. This problem also
existed on Cset 12425. The steps are:
1. Create 2 SMP_XenU guests at the same time;
2. When they booted up, type xm destroy id, xen0 will crash.
1 - 100 of 114 matches
Mail list logo
