search for: sos22

Steven, I found where the difference is, it may be my fault: My changeset number + 1 = your changeset number. My 11160 is your 11159, and my 11161 is your 11160. Attached please see those patches, Thanks, Winston, -----Original Message----- From: Steven Smith [mailto:sos22@hermes.cam.ac.uk] On Behalf Of Steven Smith Sent: Wednesday, October 11, 2006 10:33 AM To: Wang, Winston L Cc: Stefan Berger; Zheng, Shaohui; xen-devel@lists.xensource.com; sos22@srcf.ucam.org Subject: Re: [Xen-devel] W2K3 Server Installation fails with ACPI=1 on > Sorry to hear more ACPI Windo...

...ould be mostly comprehensible and reasonably stable. The plan is to add them to xen-unstable over the next few weeks, probably before 3.0.3, so any testing which anyone can do would be helpful. The Xen and tools changes are also available as a series of smaller patches at http://www.cl.cam.ac.uk/~sos22/pv-on-hvm/hvm_xen . The composition of these gives hvm_xen_unstable.diff. Steven. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

We found that cs 11554 increases some of timeout to fix the hot plug issue when starting 4 VMX simultaneously. Thanks for the quick reponse to nightly status report. But we found that when in an extremely condition, like creating 12 VMX domains and 4 XENU domains at the same time, sometimes we still can meet this bug. Attached is a demo script to start many domains. So we just wonder

Hi. Here is the short version: If dom0 experiences a short (< 120 second) network outage the guests whose disks are on iSCSI LUNs get (seemingly) unrecoverable IO errors. Is it possible to make Xen more resiliant to such problems? And now the full version: We''re testing Xen on iSCSI LUNs. The hardware/software configuration is: * Dom0 and guest OS: SLES10 x86_64 * iSCSI LUN on

Hi Stefan, The problem is cause by the VBD/VNIF PCI device in DM checked in changeset 11160: PCI Device ID: 5853(Xen),class:ff80 (unknown) ACPI Window does not understand this device and can not find device driver associate with it. To verify this just revert the patches of changset 11161/11160 We are working on the fix now, revert patch is not the solution anyway... Thanks, Winston

Hello, I''m trying to get PDB working in accordance with the instructions at http://www.cl.cam.ac.uk/~sos22/replay.bk/docs/misc/XenDebugger-HOWTO and a message from this list: http://lists.xensource.com/archives/html/xen-devel/2004-08/msg00017.html When I try to build pdb I first get errors because the Makefile is configured to treat warnings as errors, and there are some warnings. I decided to ta...

We have tested Xen for 3.0.3rc1. The test includes Guest installation, device model, control panel, guest os and basic function tests. Here are issues found in our tests, For the first 6 issues, I think it''s better to be fixed in 3.0.3: 1. Para-virtualization driver doen''t work for HVM guests The hvm guest always hanged or met kernel panic when trying to load xenbus.ko. So vbd

...*** [linux-2.6-xen0-build] Error 2 make[2]: Leaving directory `/tmp/xen-unstable.hg'' make[1]: *** [kernels] Error 1 make[1]: Leaving directory `/tmp/xen-unstable.hg'' make: *** [world] Error 2 changeset: 6274:3c1cd2486b7fecd5d97378a7d52e5bfb8eb7c718 tag: tip user: sos22@douglas.cl.cam.ac.uk date: Fri Aug 19 09:10:24 2005 summary: Unbreak the build in the non-CONFIG_SMP and x86_64 cases. David Barrera _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I totally agree with Luc Boudreau about this problem. On modern branded server they ALL use Broadcom chipset... I must admit that: a) lot of people are experiencing the problem but can tolerate it or b) someone already experienced this problem and solved it Lets'' approach the problem pragmatically... just start with a survey on the list. ... hope we solve this issue soon. Ivan

This patch series contains a set of patches making minios rather easier to use, from an application development point of view. Overview of patches: 1 Command line argument parsing support, from Xen. 2 Weak console handler function. 3 Build system tweaks for application directories. 4 Trailing whitespace cleanup. (because it is very messy) Patch 4 is likely to be more controversial than