On Thursday, May 07, 2009 10:22 AM Isaku Yamahata wrote:
On Wed, May 06, 2009 at 01:54:15PM +0800, You, Yongkang wrote:
On xen-ia64-devel-boun...@lists.xensource.com wrote:
Hi,
When I try recently Xen (Xen 3.4 rc3) on IA64 machine
(Tiger4), I found some strange issue.
My two systems
Hi,
When I try recently Xen (Xen 3.4 rc3) on IA64 machine (Tiger4), I found some
strange issue.
My two systems have 4 and 8 pcpus separately
If VTI guest's vcpus is near pcpus, guest booting will meet some issues:
1. Guest boot might be hang at switch to new root and run init; unmounting old
On xen-ia64-devel-boun...@lists.xensource.com wrote:
Hi,
When I try recently Xen (Xen 3.4 rc3) on IA64 machine
(Tiger4), I found some strange issue.
My two systems have 4 and 8 pcpus separately
If VTI guest's vcpus is near pcpus, guest booting will meet
some issues:
1. Guest boot
On Thursday, January 08, 2009 7:23 PM, Ian Jackson wrote:
Isaku Yamahata writes (Re: [Xen-ia64-devel] [Test Report] Xen/IPF
Unstable CS#18957 Status (Linux#767, ioemu#b36996b3..) --- one new
issue):
Oh great. I'm forwarding the mail to Ian Jackson suspecting
that he is not on the ia64
time. If the
default compilation is okay, do you think it is worthy to do more
investigating?
Any suggestion will be much appreciated.
Best Regards,
Yongkang You
On Tuesday, December 16, 2008 10:22 AM, Isaku Yamahata wrote:
On Tue, Dec 09, 2008 at 05:56:25PM +0800, You, Yongkang wrote
On Monday, December 08, 2008 2:10 PM, Isaku Yamahata wrote:
On Mon, Dec 08, 2008 at 01:52:38PM +0800, Zhang, Jingke wrote:
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.
Em, it might be the issue of using default Linux e100 driver/
Qin, you can try with eepro100 driver.
Best Regards,
Yongkang You
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Zhang, Xing Z
Sent: Wednesday, November 28, 2007 10:11 PM
To: Mu, Qin
Cc:
Hi Tristan,
We met two main issues when building open guest firmware (OGFW).
1. The OGFW can not work, if we compile it in RHEL5 or 5.1 standard
environment. And in RHEL5.1, we didn't meet the .dll copying issue.
2. Compiling OGFW in Dom0, Dom0 met hang (or crashing).
Above issues might affect
Hi Alex,
We didn't use Debian on our machine. :(
At beginning, we want to put the OGFW into nightly testing too. Then it would
monitor the OGFW's changing, and do normally testing to track its status. So we
want to setup an easy building environment for it. But meeting a lot of
troublesome.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Jarod Wilson
Sent: Wednesday, November 14, 2007 10:46 AM
To: Kayvan Sylvan
Cc: xen-ia64-devel
Subject: Re: [Xen-ia64-devel] IA64 using Redhat 5.1: xm
createfails: Hotplugscripts not working.
Two other
Xen/IA64 Healthiness Report
IA64 PV driver build failure issue has been fixed.
All cases passed in this changeset.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with Dual
Hi Alex,
It is a case issue to report wrong in past a few days. At beginning of
case failure, we made a walk around for the case to let the testing
runing smoothly. So it would always report fail. But we didn't check it
often. It causees we didn't catch the bug fixing in time. :(
Maybe it has
Hi Keir and all,
All build failure issues have been fixed. The blocked issue is same with RC1.
Creating HVM domain would crash IA32pae system.
Beside the block issue, we got good testing results on IA32e and IA64 platform.
Old issue:
-
1)when using xm cr,dom0 will
Hi Keir and all,
We did a testing towards 3.1.1 RC1. Several block issue we found. We
only get full testing report on IA32e system.
Issues list:
1. PV Driver can not build out. (Already report.)
2. IA64 build failure. (Alex has alread reported)
3. IA32 pae Dom0 is easily crashing, when
in 64bit Dom0. So this issue
should be wrong info. Maybe the wrong env issue to cause the above
failure.
Best Regards,
Yongkang You
-Original Message-
From: Keir Fraser [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 22, 2007 4:28 AM
To: You, Yongkang
Cc: xen-devel; xen-ia64-devel
About XenU case fail, I have retested the changeset 15666, and
I found that if I just tried only one xenU case it usually
passed, and if I test more cases including xenU case
sequentially, the bug usually occurred. But with changeset
15659 this bug occurs rarely.
Hi Alex and Liuqing,
I
Hi Alex and all,
Our nightly testing system report last night testing met Xen crashing.
The problem changeset would before 15556. I think the issue was brought
in by 32 side's codes.
After manually checking, the crashing would happen when destroy a VTI
domain.
The serial log:
(XEN) Xen
Xen/IA64 Healthiness Report
No issue is found in this changeset.
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 SMP
Xen/IA64 Healthiness Report
Nightly testing doesn't find any issue.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with Due Core and HT)
PAL version: 8.47
Service OS: RHEL4u3
The PV testing fail is because xen-balloon.ko insert failure.
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Yang,
Liuqing
Sent: 2007年4月13日 14:49
To: [EMAIL PROTECTED]
Subject: [Xen-ia64-devel] Xen/IA64 Healthiness
Hi Alex,
We met following issue:
/home/build/nightly/builds_xen_ia64_unstable/xen-3.0-hg-xen_ia64_unstable-14794-20070411/unmodified_drivers/linux-2.6/platform-pci/evtchn.c:44:
warning: type defaults to `int' in declaration of `DEFINE_MUTEX'
Ok, I see there are some problems with the PV-on-HVM drivers. Does
your PV testing only involve PV-on-HVM (ie. not PV-domains)? Thanks,
Yes, Alex. We only tested HVM domain's PV drivers. Any hints about PV-domains?
I just thought XenU is the PV domain.
Best Regards,
Yongkang (Kangkang)
We have tried the PV driver in changeset #14366. It is workable. :) We would
add some basic regular nightly testing for them in the next week.
We built them in a RHEL4u4 system and used in another VTI guest with same OS.
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From:
Hi all,
Our QA would be on vocation from 14 Feb to 25 Feb for the Spring Festival.
There would be no nightly healthiness report for xen-ia64-unstable tree in this
period.
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Hi all,
In latest Changeset 13773, if creating XenU, Xen0 would crash and hang.
The hang happened when XenU try to bring up its network.
The serial console log is attached.
BTW. VTI domain creation also meets a little issue, which is brought from
xen-unstable. If try to create VTI domain with
:
On Thu, Feb 01, 2007 at 05:48:33PM +0800, You, Yongkang wrote:
In latest Changeset 13773, if creating XenU, Xen0 would crash and hang.
The hang happened when XenU try to bring up its network.
At least domU network works for me.
Looking the panic log, the issue looks similar which I was seeing
Xen/IA64 Healthiness Report
All testing cases pass.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with Due Core)
Service OS: RHEL4u3 IA64 SMP with 2 vcpus 1G memory
VTI
Xen/IA64 Healthiness Report
1 SMP VTI testing case failed in daily testing progress. But after
retesting more
than 100 times for this case, we can not reproduce the failure. So just
look it as the occasional case.
Testing Environment:
Xen/IA64 Healthiness Report
All 16 cases pass testing.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with Due Core)
Service OS: RHEL4u3 IA64 SMP with 2 vcpus 1G memory
VTI
Xen/IA64 Healthiness Report
The latest changeset testing results are very stable.
Both UP and SMP VTI domain can be created up in 1 minute.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8
I've tried this many times, and I always seem to get stuck here. I
do step #4 above, exit from EFI shell, and get a quick text flash that
looks like it's selecting and booting Windows 2003, then my VNC session
goes blank. It runs for a little over an hour consuming 100% of a vcpu,
then
Xen/IA64 Healthiness Report
Several issues are still in this changeset:
1. VTI Linux domain boot slowly, if enabled 'serial=pty'
2. VTI Windows almost can not boot up with 'serial=pty'
3. Destroying 2 SMP XenU domains might meet Xen0 Crashing.
4. XenU might stop to
Hi all,
VTI Windows 2003 has brought up in IA64 platform for a long time. Recently, by
community and Intel's several important bugs fixing, SMP VTI Windows
(8vcpus) could pass HCT stress testing for 24 hours.
Here, I provide some steps for VTI Windows 2k3 installation and booting.
Xen/IA64 Healthiness Report
Several issues:
1. VTI Linux domain boot slowly, if enabled 'serial=pty'
2. VTI Windows almost can not boot up with 'serial=pty'
3. Destroying 2 SMP XenU domains might meet Xen0 Crashing. Jingke has
reported it alone.
4. XenU might stop to
HI Takanori,
Thank you for the investigation and bug fixing. As you mentioned, X86 side also
meets this problem recently, because there are some mechanism changing. Wait
for your patches. :)
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
Hi Takanori,
I cannot correct this problem yet.
I wanted only to confirm the correction method to the community.
When the mechanism is changed, could you correct this problem?
In this case, is it scheduled to be corrected about when?
I saw an email from He, Qing in last month. He threw the
Xen/IA64 Healthiness Report
Several issues:
1. VTI Linux domain boot slowly, if enabled 'serial=pty'
2. VTI Windows almost can not boot up with 'serial=pty'
3. Destroying 2 SMP XenU domains might meet Xen0 Crashing.
Except above issue, all nightly cases can pass in
Hi Alex and Isaku,
I have tried VTI using Alex merged tree
(http://free.linux.hp.com/~awilliam/xen-ia64-merge/)
When I tried to create VTI domain, the Xen0 crash and whole system rebooted.
The logs are:
---
(XEN) tlb_track_allocate_entries:69 allocated 256 num_entries 256
Hi Alex,
Is this http://free.linux.hp.com/~awilliam/xen-ia64-merge/ tree still there?
I can not access it.
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alex
Williamson
Sent: 2006年11月8日 8:18
To: xen-ia64-devel
Alex,
Oops, it is my network issue. The website is alive. :)
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of You,
Yongkang
Sent: 2006年11月8日 9:53
To: Alex Williamson; xen-ia64-devel
Subject: RE: [Xen-ia64-devel] xen
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
Hi Alex,
I also met the GPT issue, if I didn't use the GPT partitioned disk image file.
But I can do installation successfully in VTI with ioemu(Qemu) disk. And
installing again, the GPT issue is gone.
But I did not understand how to install VTI Linux in a VBD disk. I just have
the
Xen/IA64 Healthiness Report
Nightly testing failed in several XenU cases, but pass when retest. The reasons
are not clear.
When doing retesting, we also catch once Xen0 crashing in multi guest (SMP
VTI Linux+XenU+WIndows) creating. No special serial log printed out.
Xen/IA64 Healthiness Report
Although all cases passed in nightly testing, we can still catch 4 VTI creating
might fail at the same time. This issue also happened in IA32 side.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2
This Patch could fix Xen might crashing issue when keeping creating/destroy VTI
domains multi times. :) Thanks Anthony~
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Xu,
Anthony
Sent: 2006年11月1日 12:05
To:
Xen/IA64 Healthiness Report
We caught 1 unstable issue in this Changeset. Creating 4 SMP VTI domain
might fail. Sometimes 1 or 2 VTI domain can not be created up. Their CPU time
just stop around 0.1 . Not sure if 12004 has the same issue. We will test more
and
Xen/IA64 Healthiness Report
All nightly testing cases pass in changeset #12004
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with Due Core)
PAL version: 8.15
Service OS:
Hi all,
We have done several stress testing for SMP VTI domain. The testing results are
good. SMP VTI domains can pass 2 kinds of Stress testing.
1. 16 hours Crashme for 14 vcpus SMP VTI domain on 2 vcpus SMP Xen0
Description: VTI+Xen0 vcpu number (14+2) = logical cpu number 16
Xen/IA64 Healthiness Report
VTI can not be created with default config bug has been fixed, after Alex help
to
pull the latest xen-unstable source. Now Xen/IA64 status comes back to stable
again. :)
There is still 1 strange issue will hang Xen0. It is doing a lot of
Xen/IA64 Healthiness Report
VTI Windows creation failure has been fixed in latest changeset.
SMP VTI hang Xen0 issue has been fixed in latest changeset.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: 2006年10月18日 15:56
To: You, Yongkang
Cc: DOI Tsunehisa; xen-ia64-devel
Subject: Re: [Xen-ia64-devel] Please try PV-on-HVM on IPF
Hi Yongkang,
Thank you for your report.
Does
What is the guest OS vesion ?
The VTI guest OS is RHEL4u3.
Did you change kernel to linux-2.6.16 ?
Yes. Or I can not even insert xen-platform.ko and xenbus.ko. ;)
Best Regards,
Yongkang (Kangkang) 永康
___
Xen-ia64-devel mailing list
Hi Tsunehisa,
I have tried your patch and tried the modules in VTI domains.
VBD hasn't problem. I can mount VBD hard disk xvda successfully.
But VNIF modules has problems. After I tried to insmod VNIF driver, VTI domain
crashed.
My vnif config: vif= [ 'type=ioemu, bridge=xenbr0', ' ' ]
BTW, I
=eb15fbf0 bsp=eb1592e0
[a001c3c0] ia64_leave_kernel+0x0/0x280
sp=eb15fbf0 bsp=eb1592e0
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of You,
Yongkang
HI Tsunehisa,
More testing results based on changeset 11810:
--
1. I did a continuous KB in VTI VBD disk 35 times, all passed. The KB speed in
VBD is a little faster than in IOEMU disk.
2. I did a lot of scp 1G file by VTI VNIF, all pass. The scp speed is
extraordinary higher than
Hi all,
When I tried to create VTI in kernel-xen-2.6.18-1.2784.fc6, I met another
strange issue.
It would report disk image does not exist. If I not giving disk option, it
will report guest firmware does not exist (kernel). But they are all in the
path. :(
Did you meet it? My xen is
Sorry to send to the wrong mailling list. :(
I should send it to fedora-ia64-xen.
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of You,
Yongkang
Sent: 2006年10月17日 11:40
To: xen-ia64-devel@lists.xensource.com
Subject
Xen/IA64 Healthiness Report
VTI Windows Creating failed. It kept crashing and recreating, when loading
Windows boot load. Please see the attachment for the log.
BTW, the changeset 11803 has good testing results.
Testing Environment:
Platform: Tiger4
Processor:
This issue only happened on creating VTI domain in IPF platform.
Creating IA32 or IA32E VMX domain is okay.
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Zhang,
Jingke
Sent: 2006年10月11日 16:35
To:
be 11635.
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: Tristan Gingold [mailto:[EMAIL PROTECTED]
Sent: 2006年9月28日 14:41
To: You, Yongkang; xen-ia64-devel@lists.xensource.com
Subject: Re: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11609
Le Mercredi 27 Septembre 2006
HI Yoshinori,
Thanks for reproduce. But if want to create xenU successfully again, I have to
reboot the machine. :)
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: Yoshinori Katase [mailto:[EMAIL PROTECTED]
Sent: 2006年9月28日 16:47
To: You, Yongkang; xen-ia64-devel
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of You,
Yongkang
Sent: 2006年9月27日 15:05
To: xen-ia64-devel@lists.xensource.com
Subject: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11609
Xen/IA64 Healthiness Report
2 XenU coexisting case failed.
If try to create 2 XenU
Griffis
Sent: 2006年9月21日 22:45
To: You, Yongkang
Cc: xen-ia64-devel@lists.xensource.com; [EMAIL PROTECTED]
Subject: [Fedora-xen] Re: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3
Xentest result
You, Yongkang wrote: [Wed Sep 20 2006, 01:46:22AM EDT]
[Bug 207227] New: Xen0 reboot command can
Xen/IA64 Healthiness Report
All 16 nightly testing cases pass in #11605 and #11609
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with Due Core)
PAL version: 8.15
Service OS: RHEL4u3 IA64 SMP with 2 VCPUs
(Kangkang) 永康
-Original Message-
From: Akio Takebe [mailto:[EMAIL PROTECTED]
Sent: 2006年9月22日 13:06
To: You, Yongkang; Yang, Fred; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Cc: xen-ia64-devel@lists.xensource.com; Akio Takebe
Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result
to check hda, hdb etc.
again. Thanks for this information.
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: Akio Takebe [mailto:[EMAIL PROTECTED]
Sent: 2006年9月21日 10:18
To: Akio Takebe; You, Yongkang; Yang, Fred; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Cc: xen-ia64-devel
Hi Fred Yoshi,
The former XenU creating failure issue seemed to be the config issue. Now I can
create XenU. But XenU booting process met an old bug. It will cost a long time
to check hard disk IRQ response from hda to hdh.
After that, xenU met the problem of mounting root partition to start
.
Sometime Xen0 monitor will print Bug: soft lockup detected on CPU#0(or #1)
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of You,
Yongkang
Sent: 2006年9月20日 10:07
To: Yang, Fred; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc
Xen/IA64 Healthiness Report
We didn't meet vif vbd issue in this changeset by some testing.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with Due Core)
PAL version: 8.15
Service OS: RHEL4u3 IA64 SMP
Xen/IA64 Healthiness Report
Nightly testing still met:
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
, after a lot of times creating and destroying domains. IA32 side also met
similar
issue sometimes, but not so easy like IA64 side. It has to reboot testing
Xen/IA64 Healthiness Report
11416 do has 11414 issues, when try several times creating/destroying multi
Guest at the same time. For example, VTI domain or XenU creating failed with
error message: Error: Device 768 (vbd) could not be connected. Hotplug scripts
not working.
Other issues is if
Xen/IA64 Healthiness Report
11414 got regression. VTI and XenU couldn't be created, after doing
several times creating and destroying. It is why nightly testing report shows
so
many testing cases failed. But they can be pass in manually retest.
Three main issues I met:
1. vif could not be
Xen/IA64 Healthiness Report
The good news is all automatically nightly testing cases passed. We didn't see
this for a long time.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with Due Core)
PAL
:35
To: You, Yongkang; xen-devel; [EMAIL PROTECTED]
Cc: xen-ia64-devel@lists.xensource.com
Subject: Re: [Xen-ia64-devel] vcpu-pin bug to dom0 ?
Hi Yongkang,
Hi all,
I find a strange issue that if I only assign 1 or 2 vcpus to dom0, I can
not use vcpu-pin to pin the No. 0 vcpu. It will report
Xen/IA64 Healthiness Report
11320 has some improvements in VTI and XenU stability.
In nightly testing, it only catches can not allocate memory issue twice.
VTI unstable issue has been fixed by Anthony.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2
Xen/IA64 Healthiness Report
We switch default nightly testing from UP Xen0 to SMP Xen0.
11270 can not create VTI domain if Xen0 is UP and using credit scheduler.
But SMP xen0 hasn't problem with credit scheduler. This problem also doesn't
happen if changing to bvt scheduler.
Testing
Xen/IA64 Healthiness Report
Nightly testing still meet several issues. I reported a bug about xm list
fail,
after try to create 4 XenU guest at the same time.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=747
Testing Environment:
Platform: Tiger4
Xen/IA64 Healthiness Report
A lot of testing cases failed in 11052, including VTI and XenU testing.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with Due Core)
PAL version: 8.15
Service OS: RHEL4u3 IA64
Hi Akio,
Thank you for your information~ :)
I am expecting next Rawhide can boot up Xen0.
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Akio
Takebe
Sent: 2006年8月24日 11:52
To: ia64 Fedora Core Development
Cc:
Hi all,
I just tried to do such a testing. But it is failed.
2 of them disappeared in the middle. And after that, Xend seemed broken.
Xm list will report Device 769 not connected
Best Regards,
Yongkang (Kangkang) 永康
___
Xen-ia64-devel mailing list
Xen/IA64 Healthiness Report
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with Due Core + HT)
PAL version: 8.15
Service OS: RHEL4u3 IA64
VTI Guest OS: RHEL4u2 RHEL4u3
XenU Guest OS: RHEL4u2
Xen IA64
Hi Fujita,
Xen-devel also met issue.
We can use following patch can resolve it. Have a try.
diff -r 0e32095a7b46 tools/examples/xend-config.sxp
--- a/tools/examples/xend-config.sxpWed Aug 9 21:34:27 2006 +0100
+++ b/tools/examples/xend-config.sxpThu Aug 10 10:52:41 2006 +0800
@@ -54,7
Xen/IA64 Healthiness Report
11031 has two issues, which will block testing.
1. xend couldn't start.
2. qemu window couldn't pop up.
Xin Li has helped to fix above two issues and send out the patch to xen-devel
We only do several manually testing with the patch.
Or all testing will fail.
Hi Alex,
This patch is to keep VTI config file to fit for new QEMU and control panel
changing. The differences were copied from xmexample.hvm .
Signed-off-by: Yongkang You [EMAIL PROTECTED]
Best Regards,
Yongkang (Kangkang) 永康
vticonfig.patch
Description: vticonfig.patch
Xen/IA64 Healthiness Report
We did nightly testing with bvt and credit separately. We found VTI domain
was hardly created successfully with credit scheduler.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 4
PAL
Xen/IA64 Healthiness Report
10931 doesn’t find new bugs compared with 10927
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 4
PAL version: 8.15
Service OS: RHEL4u3 IA64
VTI Guest OS: RHEL4u2 RHEL4u3
XenU Guest OS:
Xen/IA64 Healthiness Report
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 4
PAL version: 8.15
Service OS: RHEL4u3 IA64
VTI Guest OS: RHEL4u2 RHEL4u3
XenU Guest OS: RHEL4u2
Xen IA64 Unstable tree: 10932:571022d5afa2
Xen
Xen/IA64 Healthiness Report
10927 doesn’t find new bugs compared with 10922
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 4
PAL version: 8.15
Service OS: RHEL4u3 IA64
VTI Guest OS: RHEL4u2 RHEL4u3
XenU Guest OS:
Xen/IA64 Healthiness Report
We met several new issues in this Changeset. It cost us a lot time to reproduce
and locate the problem.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 4
PAL version: 8.15
Service OS: RHEL4u3
booting output in my serial console. But I can
not input anything, just like I didn't set agetty in /etc/inittab. :(
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: Alex Williamson [mailto:[EMAIL PROTECTED]
Sent: 2006年7月31日 23:04
To: You, Yongkang
Cc: xen-ia64-devel
Hi all,
I just recognized I couldn’t operate Xen0 from its serial console in recent
Changeset. But it is okay before.
I am not sure if it needs some new configurations in Xen0. Or it is a bug?
Best Regards,
Yongkang (Kangkang) 永康
___
Xen-ia64-devel
]
[mailto:[EMAIL PROTECTED] On Behalf Of You,
Yongkang
Sent: 2006年7月28日 13:20
To: Alex Williamson
Cc: xen-ia64-devel@lists.xensource.com
Subject: RE: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#10831
Yes. Xm list shows everything is right. But I can not connect to the 2nd one.
Could you? :(
Best
to this patch? Maybe it fix some potential
issue for VTI domain.
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: Isaku Yamahata [mailto:[EMAIL PROTECTED]
Sent: 2006年7月27日 19:15
To: You, Yongkang
Cc: xen-ia64-devel@lists.xensource.com
Subject: Re: [Xen-ia64-devel] Xen/IA64
-Original Message-
From: Isaku Yamahata [mailto:[EMAIL PROTECTED]
Sent: 2006年7月28日 9:39
To: You, Yongkang
Cc: xen-ia64-devel@lists.xensource.com
Subject: Re: [Xen-ia64-devel] Xen/IA64 Healthiness Report
-Cset#10811:254c090854de
little hard to reproduce. Actually we only see a few times
Xen/IA64 Healthiness Report
Good news: VTI domain can start up in new Qemu 0.8.1 without vif option.
Bad news: __coexisting__ domain testing failed in latest upstream. That means
can not create 2 domains at the same time.
Testing Environment:
Platform: Tiger4
BTW, two XenU domain coexisting testing can pass in Changeset 10818:199d53efd029
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of You,
Yongkang
Sent: 2006年7月28日 10:49
To: xen-ia64-devel@lists.xensource.com
Subject
Yes. Xm list shows everything is right. But I can not connect to the 2nd one.
Could you? :(
Best Regards,
Yongkang (Kangkang) 永康
-Original Message-
From: Alex Williamson [mailto:[EMAIL PROTECTED]
Sent: 2006年7月28日 11:11
To: You, Yongkang
Cc: xen-ia64-devel@lists.xensource.com
Subject: RE
Xen/IA64 Healthiness Report
Today we have done 2 times testing. The tip 10784:97cc7ed90061 has Qemu
issue in building and testing. So no testing results for it.
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 4
Service
Hi all,
I will try to send out the daily testing report for Xen/IA64 unstable tree from
now
on, if there is any new patch checked in. This is the first issue.
Xen/IA64 Healthiness Report
Testing Environment:
Platform: Tiger4
Processor: Itanium 2 Processor
Logic
Hi all,
In early of this week, creating VTI will hang Xen0 in our platform. This issue
had disappeared in Changeset 10696.
Major Issues:
==.
1. Xen0 XWindows can not start up.
Bugs fixed:
==
1. Fix creating VTI hang Xen0 issue.
2. Fix creating VTI may crash Xen0 issue with new
1 - 100 of 153 matches
Mail list logo
