similar to: [PATCH 9/12] Pull Linux CPU hotplug logic to Xen

Add TSC stop support for Deep C state TSC may stop at deep C state (C3/C4...) entry/exit. this patch add the logic that save and restore TSC during deep C state entry/exit, by using platform timer (PIT/HPET) signed-off-by: Yu Ke <ke.yu@intel.com> signed-off-by: Tian Kevin <kevin.tian@intel.com> signed-off-by: Wei Gang<gang.wei@intel.com>

This patch adds lost logic for vga initialization. It was lost after changing to new Qemu. Signed-off-by : Kevin Tian <kevin.tian@intel.com> Signed-off-by : Zhang Xiantao <xiantao.zhang@intel.com> Thanks & Best Regards -Xiantao OTC,Intel Corporation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1336153082 -7200 # Node ID 9a430b7e2df2893f7f4f75d10e66d52bdffa7efa # Parent 113fd57259b91af06a5352404dd94b484a98d2bc tools/hotplug: remove 4 from default runlevel in xen-watchdog, xend and xendomains Similar to what changeset 24847:0900b1c905f1 does in xencommons, remove runlevel 4 from the other runlevel scripts. LSB defines

Jason Wang <jasowang at redhat.com> writes: > We're trying to re-configure the affinity unconditionally in cpu hotplug > callback. This may lead the issue during resuming from s3/s4 since > > - virt queues haven't been allocated at that time. > - it's unnecessary since thaw method will re-configure the affinity. > > Fix this issue by checking the

"Michael S. Tsirkin" <mst at redhat.com> writes: > On Thu, Oct 17, 2013 at 09:57:41AM +1030, Rusty Russell wrote: >> Jason Wang <jasowang at redhat.com> writes: >> > We're trying to re-configure the affinity unconditionally in cpu hotplug >> > callback. This may lead the issue during resuming from s3/s4 since >> > >> > - virt

On Thu, Oct 17, 2013 at 09:57:41AM +1030, Rusty Russell wrote: > Jason Wang <jasowang at redhat.com> writes: > > We're trying to re-configure the affinity unconditionally in cpu hotplug > > callback. This may lead the issue during resuming from s3/s4 since > > > > - virt queues haven't been allocated at that time. > > - it's unnecessary since thaw

On Thu, Oct 17, 2013 at 09:57:41AM +1030, Rusty Russell wrote: > Jason Wang <jasowang at redhat.com> writes: > > We're trying to re-configure the affinity unconditionally in cpu hotplug > > callback. This may lead the issue during resuming from s3/s4 since > > > > - virt queues haven't been allocated at that time. > > - it's unnecessary since thaw

> -----Original Message----- > From: Ewan Mellor [mailto:ewan@xensource.com] > Sent: Tuesday, December 06, 2005 5:25 AM > To: Dave Thompson (davetho) > Cc: Xen Mailing List > Subject: Re: [Xen-devel] Hotplug scripts not working... > xen/ia64 domU stoppedworking > > On Mon, Dec 05, 2005 at 03:03:54PM -0500, Dave Thompson > (davetho) wrote: > > > >

Package: xen-utils-common Version: 4.0.0-1 Hi, I discovered that one of the scripts does something wrong on my squeeze machine. /etc/xen/scripts/xen-hotplug-cleanup: line 24: [: !=: unary operator expected /etc/xen/scripts/xen-hotplug-cleanup: line 24: [: !=: unary operator expected /etc/xen/scripts/xen-hotplug-cleanup: line 24: [: !=: unary operator expected

Hi all, I use Centos 5.2 as Dom0 and DomU(pv). I have two fundamental questions about Xen 1. Is Xen support online increase or decrease memory for DomU? Or it is a must to reboot taking effect of memory adjustment? 2. Is Xen support online increase or decrease memory for DomU? Or it is a must to reboot taking effect of memory adjustment? Regards, Felix

Hi, all, Attached patch set is the first support to S3 (suspend to ram) on Xen environment. We know that 3.0.5 is feature freeze now, and thus this version is just for trial and review first. X86-64 is to go (failed to compile), but we have a preliminary support in house which is however on an old version and not very stable yet. It''s supposed to be out with next version. Totally

hi guys My OS is centos 5.4 uname -a : Linux localhost.localdomain 2.6.18-prep #1 SMP Mon Jul 12 20:03:46 CST 2010 x86_64 x86_64 x86_64 GNU/Linux and my xen version is 3.3.1, I install xen from souce code. The xen dom0 and xend is ok but I can''t use virt-install to install a domU. The error is below:

Package: xen-utils-common Version: 3.4.2-4 Severity: important File: /usr/lib/xen-common/bin/xen-utils-wrapper xm invoke vtpm-common.sh from /etc/xen/hotplug, wich one call gawk, but gawk is not listed as dependence for xen packages. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux

xen_play_dead calls cpu_bringup() which looks weird, because xen_play_dead() is invoked in the cpu down path, whereas cpu_bringup() (as the name suggests) is useful in the cpu bringup path. Getting rid of xen_play_dead()'s dependency on cpu_bringup() helps in hooking on to the generic SMP booting framework. Also remove the extra call to preempt_enable() added by commit 41bd956 (xen/smp: Fix

xen_play_dead calls cpu_bringup() which looks weird, because xen_play_dead() is invoked in the cpu down path, whereas cpu_bringup() (as the name suggests) is useful in the cpu bringup path. Getting rid of xen_play_dead()'s dependency on cpu_bringup() helps in hooking on to the generic SMP booting framework. Also remove the extra call to preempt_enable() added by commit 41bd956 (xen/smp: Fix

Stamp softlockup thread earlier before do_timer, because the latter is the one to actually trigger lock warning for long-time offline. Or else, I obserevd softlockup warning easily at manual vcpu hot-remove/plug, or when suspend cancel into old context. One point here is to cover both stolen and blocked time to compare with offline threshold. vcpu hotplug falls into ''stolen''

I''m using kubuntu dapper, so /proc/sys/kernel/hotplug is disabled, and instead udevd is running to get events from kernel and do what is necessary. in my first steps with xen (unstable), I get this error: root@nandemonai:~# xm create myxm Using config file "/etc/xen/myxm". Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. root@nandemonai:~#

We're trying to re-configure the affinity unconditionally in cpu hotplug callback. This may lead the issue during resuming from s3/s4 since - virt queues haven't been allocated at that time. - it's unnecessary since thaw method will re-configure the affinity. Fix this issue by checking the config_enable and do nothing is we're not ready. The bug were introduced by commit

We're trying to re-configure the affinity unconditionally in cpu hotplug callback. This may lead the issue during resuming from s3/s4 since - virt queues haven't been allocated at that time. - it's unnecessary since thaw method will re-configure the affinity. Fix this issue by checking the config_enable and do nothing is we're not ready. The bug were introduced by commit

We're trying to re-configure the affinity unconditionally in cpu hotplug callback. This may lead the issue during resuming from s3/s4 since - virt queues haven't been allocated at that time. - it's unnecessary since thaw method will re-configure the affinity. Fix this issue by checking the config_enable and do nothing is we're not ready. The bug were introduced by commit