similar to: [PATCH] Sync Xen sysctl header for 20762:a1d0a575b4ba

Displaying 20 results from an estimated 500 matches similar to: "[PATCH] Sync Xen sysctl header for 20762:a1d0a575b4ba"

2011 Jul 17
0
[xen-unstable test] 8091: regressions - FAIL
flight 8091 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/8091/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-rhel6hvm-intel 12 guest-localmigrate/x10 fail REGR. vs. 8071 Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable: test-amd64-amd64-xl-pcipt-intel 9
2011 Feb 19
0
[xen-4.0-testing test] 5856: regressions - FAIL
flight 5856 xen-4.0-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/5856/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-xcpkern-i386-rhel6hvm-amd 5 xen-boot fail REGR. vs. 5691 Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable: test-amd64-amd64-win 16
2011 Jul 17
0
[xen-4.1-testing test] 8111: regressions - FAIL
flight 8111 xen-4.1-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/8111/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-rhel6hvm-amd 12 guest-localmigrate/x10 fail in 8104 REGR. vs. 8020 Tests which are failing intermittently (not blocking): test-amd64-i386-rhel6hvm-amd 11 guest-localmigrate.2 fail pass in 8104
2012 Mar 24
0
[xen-4.0-testing test] 12413: regressions - FAIL
flight 12413 xen-4.0-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12413/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 4 xen-build fail REGR. vs. 12202 build-amd64-pvops 4 kernel-build fail REGR. vs. 12202 build-amd64-oldkern 4
2010 Oct 27
25
xend does not start
Hello, I''ve downloaded the xen 4.0.1 version as it is explained here: http://wiki.xensource.com/xenwiki/Xen4.0 <http://wiki.xensource.com/xenwiki/Xen4.0>So, I''ve made a clone from repository, with the following command: hg clone -r RELEASE-4.0.1 http://xenbits.xen.org/xen-4.0-testing.hg And finally I''ve built xen, tools and stubdom. I was looking for a
2010 Oct 27
25
xend does not start
Hello, I''ve downloaded the xen 4.0.1 version as it is explained here: http://wiki.xensource.com/xenwiki/Xen4.0 <http://wiki.xensource.com/xenwiki/Xen4.0>So, I''ve made a clone from repository, with the following command: hg clone -r RELEASE-4.0.1 http://xenbits.xen.org/xen-4.0-testing.hg And finally I''ve built xen, tools and stubdom. I was looking for a
2006 Sep 05
1
[PATCH] xenmon: --ms_per_sample: check a negative value
Hi, This patch adds the argument check of "--ms_per_sample=" option. For "--ms_per_sample=", a negative value should be invalid. e.g. % xenmon.py -n --ms_per_sample=-1 usage: xenmon.py [options] xenmon.py: error: option --ms_per_sample: invalid negative value: ''-1'' Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> -- KUWAMURA
2006 Jul 04
4
[PATCH] xenmon: remove magic number "31" (the idle domain)
Hi, This patch removes the magic number "31" for readability. The number "31" means the idle domain ID. In detail: - display the idle domain ID with "Idle" instead of "31" - write to the file "log-idle.log" instead of "log-dom31.log". Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> Thanks, -- KUWAMURA
2008 Jun 30
1
[PATCH] tools/python: fix TypeError for 17903:0728459b3c8d
Hi, If `hda'' is used in a domain config file and domain-0 has /dev/hda, creating the domain failed by TypeError: File "//usr/lib/python/xen/xend/server/blkif.py", line 84, in getDeviceDetails (device_path, devid) = blkif.blkdev_name_to_number(dev) TypeError: unpack non-sequence Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> -- KUWAMURA
2010 Jan 21
0
[PATCH] xentrace: XC_PAGE_SIZE should be used
Hi, 20827:fad80160c001 cannot be compiled on ia64: xentrace.c:647: error: ''PAGE_SIZE'' undeclared (first use in this function) This patch fixes it. Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> Best regards, -- KUWAMURA Shin''ya _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com
2008 Oct 08
0
[PATCH] [IOEMU] [IA64] Fix memory size calculation on VT-i over 3GB memory
Hi, VT-i domains have two memory holes: VGA I/O (under 1MB) and MMIO (3GB-4GB). This patch calculates the correct memory size with them. # This is based on xen-unstable 10936:a0b3cf802d99. Original patch by Zhang xiantao <xiantao.zhang@intel.com> Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> Best regards, -- KUWAMURA Shin''ya
2009 Feb 10
0
[PATCH] vtd: fix compilation error on ia64 for 19185:1eb6afcad849.
Hi, The staging tree 19185:1eb6afcad849 cannot be compiled on ia64: vtd.c: In function `alloc_pgtable_maddr'': vtd.c:60: error: too few arguments to function `iommu_flush_cache_page'' The attached patch fixes it. Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> Best regards, -- KUWAMURA Shin''ya
2008 Aug 29
1
Debian version and xend
Hello, I just upgraded my 64-bits dom0 from Etch to Lenny, I am still running the 2.6.18 Xen kernel by apt-pinning it (see later). But now xend does not start anymore: ------------ xen:~# /etc/init.d/xend start Starting XEN control daemon: xendTraceback (most recent call last): File "/usr/lib/xen-3.0.3-1/bin/xend", line 40, in <module> from xen.xend.server import SrvDaemon
2007 Apr 11
3
[PATCH][RFC] Support GPT (GUID Partition Table)
Hi, I made a patch for GPT support. As you see, this patch uses ad-hoc approach. If you give me an advice, it would be appreciated Signed-off-by: Shinya Kuwamura <kuwa@jp.fujitsu.com> Signed-off-by: Tomohiro Takahashi <takatom@jp.fujitsu.com> Thanks, Tomohiro Takahashi. diff -r 1bde28f762a6 -r 8e08fd1ffa24 tools/pygrub/src/pygrub --- a/tools/pygrub/src/pygrub Mon Apr 09 13:40:25
2013 Oct 19
1
Bug#726827: xen-utils-4.1: Xen doesn't start on a laptop with Nvidia Optimus graphics
Package: xen-utils-4.1 Version: 4.1.4-4 Severity: important Tags: patch Dear Maintainer, * What led up to the situation? Trying to start Xen on a Asus X53S laptop (which has dual Intel + Nvidia Geforce 610M Optimus graphics card) xend.log contains: [2013-10-19 17:14:26 4239] INFO (SrvDaemon:332) Xend Daemon started [2013-10-19 17:14:26 4239] INFO (SrvDaemon:336) Xend changeset: unavailable.
2007 May 15
0
[PATCH] Small fix to the host.get_name_description call
Signed-off-by: Stefan Berger <stefanb@us.ibm.com> diff -r 3ef0510e44d0 tools/python/xen/xend/XendAPI.py --- a/tools/python/xen/xend/XendAPI.py Tue May 08 10:21:23 2007 +0100 +++ b/tools/python/xen/xend/XendAPI.py Mon May 14 23:17:32 2007 -0400 @@ -905,7 +941,7 @@ class XendAPI(object): XendNode.instance().set_name(new_name) return
2007 Oct 11
1
Unable to connect to Xend. Connection refused
Hi all, after an emerge I wasn''t able to run xen correctly. Everytime I try the command xm list, I receive the error: Error: Unable to connect to xend: Connection refused. Is xend running? Inspecting /var/log/xen/xend.log i found that xend doesn''t find something at line 1 column 0. But I don''t know what is it. I tried with kernel 2.6.16.52 and with 2.6.20-r4 but
2011 Aug 10
2
xend fails on Open SUSE 11.4
I am seeing xend error on OpenSUSE 11.4, Has anyone else seen this ? Thanks Ranjith #uname -a Linux linux-ws7h 2.6.37.6-0.7-xen #1 SMP 2011-07-21 02:17:24 +0200 x86_64 x86_64 x86_64 GNU/Linux #/var/log/xen/xend.log 2011-08-09 14:36:38 21111] ERROR (SrvDaemon:349) Exception starting xend ((111, ''Connection refused'')) Traceback (most recent call last): File
2011 Apr 01
2
Need help with an issue after upgrading to 4.1.0
Hi all, This is my first post to the list. My first real major issue with xen. I started on 3.4.2 and upgraded to 4.0.1 without issues. Now I just attempted to go to 4.1.0 and I got the following errors in my log. # cat /var/log/xen/xend-debug.log Xend started at Fri Apr 1 13:51:15 2011. cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory cat:
2006 Jul 31
1
[PATCH 5/6] xen, tools: calculate nr_cpus via num_online_cpus
Once Xen calculates nr_nodes properly, all nr_cpu calculations based on nr_nodes * sockets_per_node * cores_per_socket * threads_per_core are broken. The easy fix is to replace those calculations with a new field, nr_cpus in physinfo which is calculated by num_online_cpus(). This patch does so and attempts to change all users over to nr_cpus field in physinfo. This patch touches