similar to: [PATCH] add feature flag to xenstore for XS_RESET_WATCHES

Add xs_reset_watches function to shutdown watches from old kernel after kexec boot. The old kernel does not unregister all watches in the shutdown path. They are still active, the double registration can not be detected by the new kernel. When the watches fire, unexpected events will arrive and the xenwatch thread will crash (jumps to NULL). An orderly reboot of a hvm guest will destroy the

The following series improves kexec in a Xen PVonHVM guest. It is available via git: git://github.com/olafhering/linux.git xen-kexec-XS_RESET_WATCHES-3.0 A new xenstored command XS_RESET_WATCHES has been added in xen-unstable.hg changeset 23839:42a45baf037d. The command removes all watches and transactions for the guest. The following patches make use of the new command to wipe all existing

Changes since v1: - Fix a double-free bug introduced by v1, pointed out by Stefano where internal pointer was being passed back to caller from libxl_create_stubdom() 8<---------------------------------------------------------------------- Currently scratch variables allocated by libxl have the same lifetime as the context. While this is suitable for one off invocations of xl. It is not

Compiling xenbus_xs.o triggers this GCC warning: drivers/xen/xenbus/xenbus_xs.c:628:13: warning: function declaration isn?t a prototype [-Wstrict-prototypes] Add the obvious and trivial fix. While we're touching this function add some equally obvious and trivial whitespace fixes. Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- 0) Triggered by compiling v3.7-rc1 using

Compiling xenbus_xs.o triggers this GCC warning: drivers/xen/xenbus/xenbus_xs.c:628:13: warning: function declaration isn?t a prototype [-Wstrict-prototypes] Add the obvious and trivial fix. While we're touching this function add some equally obvious and trivial whitespace fixes. Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- 0) Triggered by compiling v3.7-rc1 using

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1341397625 -3600 # Node ID 167f013324e854a28fc7637cbb7211fa266dcbc5 # Parent 12011fcfd5cce2a831da3558c59f2c3622e71250 libxl: rename stubdomain when renaming domain. Otherwise after a localhost migrate of an HVM domain with a stubdomain we end up with domains called "FOO" and "FOO--incoming-dm".

* Introduce new variants of the logging functions which include errno values (converted using strerror) in the messages passed to the application''s logging callback. * Use the new errno-including logging functions everywhere where appropriate. In general, xc_... functions return errno values or 0; xs_... functions return 0 or -1 (or some such) setting errno. * When

This patch exposes a generic interface which can be expanded in the future to implement USB for PVUSB, qemu, and stubdoms. It can also be extended to include other types of USB other than host USB (for example, tablets, mice, or keyboards). For each device removed or added, one of two protocols is available: * PVUSB * qemu (DEVICEMODEL) The caller can additionally specify "AUTO", in

Hello, I've spent a few days googling and reading documentation, but I'm looking for clarification and advise on setting up KVM/libvirt with shared storage. I have 2 (for now) Ubuntu Karmic systems with KVM/virsh/virt-manager set up and running. I have a storage server that can do NFS/iSCSI/samba/ etc. I am trying to figure out the best way to set things up so that I can run

Hi,Olaf, I have some questions about event channel in Xenpaging to ask you. 1) In xenpaging it uses Inter-Domainain Commnication (IDC) between dom0 and domU to build bidirectional connection,but I found there is only an event channel notification from xen to dom0 when page faults happens.It seems that xenpaging_resume_page()->xc_evtchn_notify() doesn''t make any difference.So why

Hi, George sent a patch on this problem before, but it was not completed. This patch makes libxl use xenbus to communicate with xenstored if libxl cannot open a socket. There''s a place that does not close fd in the case of failure, which is also fixed in this patch. -----------------------------------------Patch------------------------------------------------------ diff -r eff592364826

My mailboxes are on a Dovecot (IMAP) server.On DNS there is an MX record pointing to the server.To read the mail I use Roundcube.If the server is down, I lose the new mail. I would like to do two things, alternatively. First option.1) I keeep the mail on the provider's server, restoring the original MX record.2) Dovecot does not receive the mail, but should go to download it.3) I can access

Andrea Miconi wrote: > My mailboxes are on a Dovecot (IMAP) server. > On DNS there is an MX record pointing to the server. > To read the mail I use Roundcube. > If the server is down, I lose the new mail. Really? What kind of downtime makes you loose emails? If your server is down, mail delivery is tried every couple of hours for days. So - if your server is down for a day or two, no

Hi folks, we (the company i am working for) are running several dozens of virtualisation servers using CentOS 6 + Xen4CentOS as the virtualisation infrastructure. With the latest versions of all packages installed [1], we see failures in live-migration of stock-CentOS6 HVM guests, leaving a "Domain-unnamed" on the source host, while the migrated guest runs fine on the target host.

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1297182367 0 # Node ID a46b91cd8202726aecd9ddefd8e75faff48144d6 # Parent deaa7bc1a7ff6cfad7865394cb8b7205741004c9 libxl: allow guest to write "control/shutdown" xenstore node. The PV shutdown/reboot/suspend protocol requires that the guest acknowledge a request by clearing the node therefore it is necessary

Currently PVHVM Linux guests after ddacf5ef684a "xen/pv-on-hvm kexec: add xs_reset_watches to shutdown watches from old kernel" hang when run against oxenstored because it does not handle the unknown XS_RESET_WATCHES operation and does not reply. The symptom of this issue is a hang during boot at this point: cpu 1 spinlock event irq 70 CPU 1 irqstacks, hard=dec94000

Hi all, I have a following problem: - Remus network buffering doesn''t work. It seems to be because of no vif is reported by the function server.xend.domain on line 29 of /usr/local/lib/python2.7/dist-packages/xen/remus/vm.py (seen using pdb) : 27 if domid: 28 try: 29 self.dominfo = server.xend.domain(domid, ''all'') >

being from a telecoms background, the thought of a single asterisk box solution (even in a low production environment of say <10 phones) worries me slightly! starting from say a base of asterisk@home, you would have several MySQL databases, in addition to numerous config files. I have looked at high availiblity solutions, and from a hardware monitoring point of view, its relitivly straight

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. Patch 1 modifies the guest ro and rw node creation to an open coding style and cleans up some extraneous node creation. Patch 2 modifies creation of the hvmloader key in xenstore and adds

libxl_device_generic_add: handle NULL fents or bents. This is going to be used by libxl_console_add in the next patch to avoid creating the device/console path on xenstore for console 0. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> diff -r 85bd0f6e8fed tools/libxl/libxl_device.c --- a/tools/libxl/libxl_device.c Fri Aug 13 13:55:51 2010 +0100 +++