similar to: [PATCH] /sys/hypervisor/uuid

This patch is for linux-2.6.18-xen. - get the machine address of the vmcoreinfo area of xen - expose the machine address and the size of the vmcoreinfo area via /sys/hypervisor/vmcoreinfo so that the kexec-tools looks them. Signed-off-by: Itsuro Oda <oda@valinux.co.jp> diff -r e01b3a133ddc drivers/xen/core/machine_kexec.c --- a/drivers/xen/core/machine_kexec.c Wed Jun 11 09:28:01 2008

Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: head-2007-05-31/drivers/xen/Kconfig =================================================================== --- head-2007-05-31.orig/drivers/xen/Kconfig 2007-06-06 17:04:59.000000000 +0200 +++ head-2007-05-31/drivers/xen/Kconfig 2007-06-04 13:48:38.000000000 +0200 @@ -216,6 +216,7 @@ config XEN_DISABLE_SERIAL config XEN_SYSFS tristate

Hello, Sometimes the backend of PVFB knows that it doesn''t need permanent refresh, when the window is minimized for instance (no refresh at all), or the administration tools know that the window is thumnailed, and so a slow refresh rate is fine. Also, some users may want to tune the refresh rate according to the smoothness they would like, balanced with the CPU time that requires.

This makes the Xen console just work. Before, you had to ask for it on the kernel command line with console=hvc0 Signed-off-by: Markus Armbruster <armbru at redhat.com> --- diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c index 49e5358..df63185 100644 --- a/arch/x86/xen/enlighten.c +++ b/arch/x86/xen/enlighten.c @@ -25,6 +25,7 @@ #include <linux/mm.h> #include

This is an update to the Linux part of the Xen PVFB. Linux Xen PVFB is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. Their backends run in dom0 user space. Parts in this patch series: 1. Enable Xen console by default in domU 2. Pointer z-axis (mouse wheel) support 3. Module

This is an update to the Linux part of the Xen PVFB. Linux Xen PVFB is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. Their backends run in dom0 user space. Parts in this patch series: 1. Enable Xen console by default in domU 2. Pointer z-axis (mouse wheel) support 3. Module

This is an update to the Linux part of the Xen PVFB. Linux Xen PVFB is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. Their backends run in dom0 user space. Parts in this patch series: 1. Enable Xen console by default in domU 2. Pointer z-axis (mouse wheel) support 3. Module

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

The functions these get passed to have been taking pointers to const since at least 2.6.16. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/drivers/xen/balloon/sysfs.c +++ b/drivers/xen/balloon/sysfs.c @@ -97,7 +97,7 @@ static struct attribute *balloon_info_at NULL }; -static struct attribute_group balloon_info_group = { +static const struct attribute_group balloon_info_group = {

This patch was created for 3.1.0. Based on inspection, I believe the current version has the same problem, but I did not actually try it. I hope you''ll find the patch useful anyway. Xen cannot work when xenstored''s tdb is corrupt. When that happens somehow (and we''ve seen it happen), even reboot doesn''t recover from it. It could: there is no state in tdb

CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 drivers/built-in.o: In function `vmcoreinfo_show'': /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/xen_sysfs.c:340: undefined reference to `vmcoreinfo_size_xen'' /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/xen_sysfs.c:340: undefined reference to `paddr_vmcoreinfo_xen'' make[4]: ** [.tmp_vmlinux1]

Hi folks, I tried to find out what xen version upstream intends to use in 5.3, but did not find anything. So now I hope that there is some secret knowledge among the CentOS people you could share? :-) Any hint or link would be helpful. Thanks in advance, Dirk

Seems currently xenstore transaction provides confusing message in different places: a) comment of xs_transaction_start says "You can only have one transaction at any time." However do_transaction_start allows up to 10 transactions created, as long as all other existing transaction channel is idle at the time (conn->transaction == NULL) b) when multiple transactions can be

Samuel Thibault, le Tue 04 Mar 2008 16:12:20 +0000, a écrit : > Markus Armbruster, le Tue 04 Mar 2008 16:48:20 +0100, a écrit : > > I imagine (perhaps naively): > > > > * The domU writes to a framebuffer provided by the frontend. > > > > * The framebuffer (not a copy of it) can be shared with the backend, > > which only reads. > > Well,

I''ve seen some people asking why exposing xenstore attributes via sysfs could be useful. Here''s why I would really like to see such a patch make it into Xen: I''ve been working on getting domU''s to know enough about themselves to be manageable. I require a 128-bit UUID for each domU, and I require that each domU be able to determine its own UUID in userspace.