search for: is_run

During context switch is_running is set for the next vcpu before the gic state is actually saved. This leads to possible nasty races when interrupts need to be injected after is_running is set to the next vcpu but before the currently running gic state has been saved from the previous vcpu. Use current instead of is_running t...

help to understand is_running _on_xen ?    I don''t  understand why we check this condition is_running_on_xen  ?In all drivers(front & back) code we are checking this condition ?what is this function stands for ? what it does ? DISCLAIMER: ------------------------------------------------------------------...

...What I want is a class Task and a class TaskRunner. The TaskRunner should run a task in a background thread. It should also indicate the status of the running task when calling the running? method. That''s basically, what I came up with so far: class TaskRunner def initialize @is_running = false end def running? return @is_running end def execute(task) @is_running = true Thread.new do task.run @is_running = false end end end class SampleTask def run end end context "The TaskRunner...

...er is now very well covered by the specs - if you find a way to break TaskRunner without breaking the specs, please let me know. Unfortunately the specifications seem to be a little bit hard to read now. Any suggestions for improvements? bye, Tobias class TaskRunner def initialize @is_running = false end def running? return @is_running end def execute(task) @is_running = true Thread.new(task) do |myTask| myTask.run @is_running = false end end end context "The TaskRunner" do setup do...

Hello, in the last days I switched from Xen 4.2.1 to Xen 4.2.2 (source from git repository tag 4.2.2) commit a125ec6a4a2f028f97f0bdd8946d347a36dbe76b Author: Jan Beulich <jbeulich@suse.com> Date: Tue Apr 23 18:42:55 2013 +0200 update Xen version to 4.2.2 My "base system" is a debian squeeze. For Xen I use the xl toolstack. Since updating to 4.2.2 the autosave and

...mkdir -p $(dirname "$LOCKFILE") touch $LOCKFILE echo -n "Restoring Xen domains:" - for dom in $XENDOMAINS_SAVE/*; do + for dom in $XENDOMAINS_SAVED; do echo -n " ${dom##*/}" xm restore $dom if [ $? -ne 0 ]; then @@ -239,6 +240,7 @@ if is_running $dom; then echo -n "(skip)" else + echo "(booting)" xm create --quiet --defconfig $dom if [ $? -ne 0 ]; then rc_failed $? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/x...

...-e 's/^.*"name": "\(.*\)",$/\1/') elif [[ "$1" =~ '"domid":' ]]; then id=$(echo $1 | sed -e 's/^.*"domid": \(.*\),$/\1/') fi [ -n "$name" -a -n "$id" ] && return 0 || return 1 } is_running() { rdname $1 RC=1 name=;id= while read LN; do parseln "$LN" || continue if test $id = 0; then continue; fi case $name in ($NM) RC=0 ;; esac done < <($CMD list -l | grep "$LIST_GREP") return $RC } start() { if [ -f $LOCKFILE ]...

...-- 22.7 www.dione.com.ar.xen 15 64 1 -b---- 17.6 www.xarope.org.ar.xen 17 64 1 -b---- 17.3 so, if a domain has a name that starts with "Name", it won't be processed. this same bug can be found in the functions is_running()[2], all_zombies()[3] and check_domain_up()[4]. -- [1] /etc/init.d/xendomains:326 [2] /etc/init.d/xendomains:149 [3] /etc/init.d/xendomains:215 [4] /etc/init.d/xendomains:359 -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i...

...break; idletime = v->runstate.time[RUNSTATE_running]; + totaltime = idletime + v->runstate.time[RUNSTATE_runnable] + + v->runstate.time[RUNSTATE_blocked] + + v->runstate.time[RUNSTATE_offline]; if ( v->is_running ) idletime += NOW() - v->runstate.state_entry_time; ret = -EFAULT; - if ( copy_to_guest_offset(idletimes, i, &idletime, 1) ) + if ( copy_to_guest_offset(idletimes, i, &idletime, 1) ) + goto out; + if ( c...

Hi, Sometimes when stopping a virtual domain using virDomainDestroy(), I come across a domain that is already stopped. (For example when someone already stopped the domain manually using virsh or because the guest OS issued a shutdown.) This is a special case that I absolutely need to catch and handle. Unfortunately, when this happens, and I call virGetLastError() afterwards, I always just

Add self pause ability, which is required by vcpu0/dom0 when running on a AP. This can''t be satisfied by existing interface, since the new flag also serves as a sync point. Signed-off-by Kevin Tian <kevin.tian@intel.com> diff -r d5315422dbc8 xen/common/domain.c --- a/xen/common/domain.c Mon May 14 18:35:31 2007 -0400 +++ b/xen/common/domain.c Mon May 14 20:21:04 2007 -0400 @@

Patch 1 removes CONFIG_SMP Patch 2 removes separate smp_{,r,w}mb()s as a result of patch 1 Patch 4 removes __ia64__ defines from the x86 arch tree Patch 3 is related to patch 4 and changes the VIOAPIC to emulate version 0x20 as a performance gain. It preceeds Patch 4 so as to be more clear about the functional change. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>

From: Yang Zhang <yang.z.zhang@Intel.com> The follwoing patches are adding the Posted Interrupt supporting to Xen: Posted Interrupt allows vAPIC interrupts to inject into guest directly without any vmexit. - When delivering a interrupt to guest, if target vcpu is running, update Posted-interrupt requests bitmap and send a notification event to the vcpu. Then the vcpu will handle this

(I don't have a BZ# for this yet, but I'm expecting it to be filed as an RFE) Currently if the user is in the virt-p2v GUI and cancels the conversion, all that happens is we abruptly close the ssh session to virt-v2v. That is bad .. possibly (or maybe not). But in any case there is an alternative: we can send a ^C key to the virt-v2v process, which it could catch and handle gracefully,

I last posted this back in April to critical acclaim (AKA near total silence). I''m not sure who looks after tools/include/xen-foreign. I had thought it was Jan but I think I was confused and was thinking of the semi-related xen/include/compat stuff. IOW I think nobody felt "responsible". Unless there''s any objection lets just treat this as coming under tools. The

I am currently looking at a bug report[1] which is happening when a Xen PVM guest with multiple VCPUs is running a high IO database load (a test script is available in the bug report). In experimenting it seems that this happens (or is getting more likely) when the number of VCPUs is 8 or higher (though I have not tried 6, only 2 and 4), having autogroup enabled seems to make it more likely, too

Now that virt-p2v has its own repository [1] and releases [2], it is time to remove it from libguestfs. [1] https://github.com/libguestfs/virt-p2v [2] http://download.libguestfs.org/virt-p2v/ Pino Toscano (2): Remove virt-p2v Remove remaining virt-p2v bits .gitignore | 4 - Makefile.am | 7 +- bash/Makefile.am

...+2597,7 @@ select_main_loop_run (guestfs_main_loop *mlv, guestfs_h *g) r = select (ml->max_fd+1, &rset2, &wset2, &xset2, NULL); if (r == -1) { if (errno == EINTR || errno == EAGAIN) - continue; + continue; perrorf (g, "select"); ml->is_running = 0; return -1; @@ -2606,17 +2606,17 @@ select_main_loop_run (guestfs_main_loop *mlv, guestfs_h *g) for (fd = 0; r > 0 && fd <= ml->max_fd; ++fd) { events = 0; if (FD_ISSET (fd, &rset2)) - events |= GUESTFS_HANDLE_READABLE; + events |= GUEST...