similar to: [PATCH 1/2] xen: Populate xenbus device attributes

Hi, This patch series fixes the S3 resume of a domain running xenstored and a frontend over xenbus (xen-netfront in my use case). As device resume is happening before process resume, the xenbus frontend resume is hanging if xenstored is not running, thus causing a deadlock. This patch series is fixing that issue by deferring the xenbus frontend resume when we are running xenstored in that same

Use PM_FREEZE, PM_THAW and PM_RESTORE power events for suspend/resume/checkpoint functionality, instead of PM_SUSPEND and PM_RESUME. Use of these pm events fixes the Xen Guest hangup when taking checkpoints. When a suspend event is cancelled (while taking checkpoints once/continuously), we use PM_THAW instead of PM_RESUME. PM_RESTORE is used when suspend is not cancelled. See

Hi, The following patch series fixes hangup after creating checkpoint on Xen. The Linux Xen guest can be saved the state to restore later, and also created snapshot like checkpoint via the hypervisor. But, when the snapshot is created for the PV guest, it will hangup. We added ''PMSG_CANCEL'' message and ''cancel'' handler in dev_pm_ops struct in the pm-linux

This commit delays the point at which bdrv_new (and hence blk_open on the underlying device) is called from blk_init to blk_connect. This ensures that in an inbound live migrate, the block device is not opened until it has been closed at the other end. This is in preparation for supporting devices with open/close consistency without using O_DIRECT. This commit does NOT itself change O_DIRECT

From: Stefano Stabellini <stefano.stabellini@eu.citrix.com> When disk is a cdrom and the drive is empty the "params" node in xenstore might be missing completely: cope with it instead of segfaulting. Updated in v2: - actually removed the strchr(blkdev->params, '':'') that caused the segfault; - free all the allocated strings from xenstore before returning;

From: Stefano Stabellini <stefano.stabellini@eu.citrix.com> When disk is a cdrom and the drive is empty the "params" node in xenstore might be missing completely: cope with it instead of segfaulting. Updated in v2: - actually removed the strchr(blkdev->params, '':'') that caused the segfault; - free all the allocated strings from xenstore before returning;

From: Ruslan Pisarev <ruslan at rpisarev.org.ua> Signed-off-by: Ruslan Pisarev <ruslan at rpisarev.org.ua> --- drivers/xen/xenbus/xenbus_probe.c | 7 +++---- 1 files changed, 3 insertions(+), 4 deletions(-) diff --git a/drivers/xen/xenbus/xenbus_probe.c b/drivers/xen/xenbus/xenbus_probe.c index 7397695..3b53452 100644 --- a/drivers/xen/xenbus/xenbus_probe.c +++

From: Ruslan Pisarev <ruslan at rpisarev.org.ua> Signed-off-by: Ruslan Pisarev <ruslan at rpisarev.org.ua> --- drivers/xen/xenbus/xenbus_probe.c | 7 +++---- 1 files changed, 3 insertions(+), 4 deletions(-) diff --git a/drivers/xen/xenbus/xenbus_probe.c b/drivers/xen/xenbus/xenbus_probe.c index 7397695..3b53452 100644 --- a/drivers/xen/xenbus/xenbus_probe.c +++

From: Ruslan Pisarev <ruslan at rpisarev.org.ua> Signed-off-by: Ruslan Pisarev <ruslan at rpisarev.org.ua> --- drivers/xen/xenbus/xenbus_probe.c | 7 +++---- 1 files changed, 3 insertions(+), 4 deletions(-) diff --git a/drivers/xen/xenbus/xenbus_probe.c b/drivers/xen/xenbus/xenbus_probe.c index 7397695..3b53452 100644 --- a/drivers/xen/xenbus/xenbus_probe.c +++

qemu-xen: ignore console disconnect events for console/0 The first console has a different location compared to other PV devices (console, rather than device/console/0) and doesn''t obey the xenstore state protocol. We already special case the first console in con_init and con_initialise, we should also do it in con_disconnect. This patch should be applied to 4.1 too. Signed-off-by:

From: Stefano Stabellini <stefano.stabellini@eu.citrix.com> When disk is a cdrom and the drive is empty the "params" node in xenstore might be missing completely: cope with it instead of segfaulting. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> --- hw/xen_disk.c | 16 +++++++++++----- 1 files changed, 11 insertions(+), 5 deletions(-) diff --git

changeset: 7144:fe401301929e tag: tip user: emellor@ewan date: Fri Sep 30 08:59:28 2005 +0100 summary: Change rebooting specification so that we can have domains crash and stay make dist failed with above changset on FC4. make[3]: Entering directory `/media/sdb2/usr/src/redhat/SOURCES/xen-unstable.hg/linux-2.6.12-xen0'' CHK include/linux/version.h

While for the "normal" case (called from blk_send_response_all()) decrementing requests_finished is correct, doing so in the parse error case is wrong; requests_inflight needs to be decremented instead. Change in v2: Adjust coding style. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/hw/xen_disk.c +++ b/hw/xen_disk.c @@ -154,7 +154,7 @@ static void ioreq_finish(struct

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21 + 2.6.21-070428-1 + the patches I've posted over the last couple of days. Changes since the last posting: - update per review comments - comment each file - comment barrier use - use common cpu sibling setup - fixed a few minor bugs, specifically a traceirq mismatch warning - some

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21 + 2.6.21-070428-1 + the patches I've posted over the last couple of days. Changes since the last posting: - update per review comments - comment each file - comment barrier use - use common cpu sibling setup - fixed a few minor bugs, specifically a traceirq mismatch warning - some

Hi Jeremy, I backported the branch I have in linux-next plus some older PV on HVM fixes to stable-2.6.32.x. Please pull: git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git stable-2.6.32-pvhvm Ian Campbell (11): xen: do not respond to unknown xenstore control requests xen: use new schedop interface for suspend xen: switch to new schedop hypercall by default. xen:

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

(Sorry, lost Keir''s mail). I''m unclear on why we have to have the mapping part of solving the xendev problem. Can''t we just allocate a transaction as usual if we see an ID without a transaction existing, mark it as pre-fail, and when we see the transaction end, discard the copy as if it had raced? Surely the ID lookup is guaranteed to fail in the circumstances we care