similar to: [PATCH] libxl: implement trigger s3resume

Displaying 20 results from an estimated 400 matches similar to: "[PATCH] libxl: implement trigger s3resume"

2004 Apr 02
2
Futzing with TaskScheduler
Hi all, Thought I should say something - it''s been a little while. :) Anyway, I''m still futzing with how I want the Ruby API to look. The more I look at the Perl version, the more I think it was too faithful to the C API. Right now I''m looking at the trigger() method. For example, I don''t see any reason to make the "type" key take a hash as an
2012 Apr 24
8
[PATCH v2] libxl: prevent xl from running if xend is running.
Prevent xl from doing any operation if xend daemon is running. That prevents bugs that happened when xl and xend raced to close a domain. Changes since v1: * Add documentation to xl man page. * Permit the execution of commands that don''t modify anything. * Indent error message. Cc: george.dunlap@eu.citrix.com Cc: ian.jackson@eu.citrix.com Signed-off-by: Roger Pau Monne
2007 Mar 05
2
Scheduled workers only run once unless you call self.delete inside the worker
I had a worker scheduled to run every minute with backgroundrb_schedules.yml: ebay_runner: :class: :ebay_auction_worker :job_key: :ebay_auction_runner :trigger_type: :cron_trigger :trigger_args: 0 * * * * * * This worker posts an auction to eBay from a queue of auctions every minute. I was having a problem where the worker would run ok the first time, but never any subsequent minutes
2008 Aug 29
0
[PATCH] vtd: fix Dom0 S3 when VT-d is enabled.
Now if VT-d is enabled, when Dom0 does S3, Xen doesn''t suspend/resume the IOMMU states. The patch adds the missing invocations of iommu_suspend()/iommu_resume() and makes some nesessary fixes: 1) In iommu_set_root_entry(), we should not re-allocate the root-entry when Xen returns from S3; 2) Define the array iommu_state correctly (u8 -> u32); 3) Only save/restore the necessary IOMMU
2010 Aug 19
17
xl fails to work with some command
Hi As we will use xl in xen 4.1. I had try use xl to do something. And I find some command is fails. For config file, when give "disk=" too args, it will show segment fault if we use xl create to start guest. Is there any change for xl''s config file? Following command can not work: xl migrate: when I use xl migrate domain localhost to do migrate, it shows error:
2008 May 08
8
[Patch 4/4]: Xend interface for HVM S3
[Patch 4/4]: Xend interface for HVM S3 - extend "xm resume <domid>" to be able to S3 resume HVM domain. - when user issue "xm resume" command for HVM domain, xend will use xc lib API to call HVMOP_s3_resume hypercall. Note: it may not appropriate use xm resume for HVM s3, since xm resume is originally designed for save/restor purpose. It will be fine that
2004 Jul 31
3
Bug in new_work_item
Hi all, Windows 2000 Ruby 1.8.2 R7 VC++ 6.0 I noticed that if I try to call new_work_item and give the task a name that already exists, I get a segfault: C:\eclipse\workspace\win32-taskscheduler>ruby test.rb "0.1.0" test.rb:22:in `new_work_item'': NewWorkItem() function failed (Win32::TaskSchedul erError) from test.rb:22 test.rb:22: [BUG] Segmentation fault ruby
2010 Sep 09
2
[PATCH]: add libxl python binding
Changes since last time: - split auto-generated code in to c and h files - un-break the build system - fix ocaml binding due to libxl API change - lot''s of tidy-ups too numerous to mention Please consider and apply :) -----8<--------------------------------------------------------------- Introduce python binding for libxl. The binding is not yet complete but list_domains,
2007 Mar 13
3
Scheduled worker dies after about 30-45 runs
I have a scheduled worker that runs every minute, checking for new eBay auctions to post. If it finds an auction, then it posts it. If there are no auctions in the database that are queued up, it simply does nothing. I got the worker to finally run as a scheduled worker, every minute. However, after about 30-45 scheduled runs, it simply stops running. My backgroundrb_schedules.yml file: ------
2012 Nov 14
0
libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 1 device model: spawn failed (rc=-3
Hello, I've tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can't support SPICE, so I installed upstream qemu. (http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and spice-protocol
2012 Jan 25
0
Re: [PATCHv2 1 of 2] libxl: extend pCPUs specification for vcpu-pin.
On Mon, 2012-01-23 at 18:21 +0000, Dario Faggioli wrote: > Allow for "^<cpuid>" syntax while specifying the pCPUs list > during a vcpu-pin. This enables doing the following: > > xl vcpu-pin 1 1 0-4,^2 > > and achieving: > > xl vcpu-list > Name ID VCPU CPU State Time(s) CPU Affinity > ... > Squeeze_pv
2013 Feb 06
1
[PATCH RESEND] tools/libxl: Disable useless empty floppy drive with qemu-xen
From: Fabio Fantoni <fabio.fantoni@heliman.it> Signed-off-by: Fabio Fantoni <fabio.fantoni@heliman.it> --- tools/libxl/libxl_dm.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c index 51f9914..c265618 100644 --- a/tools/libxl/libxl_dm.c +++ b/tools/libxl/libxl_dm.c @@ -406,6 +406,9 @@ static char **
2012 Dec 04
1
libxl: stable-4.2 git tree dirty after a build
It appears that something about the 4.2.1-rc1 tree is leaving around generated files in a modified state after a build: # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: tools/libxl/libxlu_cfg_y.c # modified:
2012 Jan 13
1
[PATCH] libxl: fix parse_backend_path and device_backend_path to be mutual
# HG changeset patch # User Roger Pau Monne <roger.pau@entel.upc.edu> # Date 1326454799 -3600 # Node ID 58c924a72ab7af658a888ff39411229a9e6a12f6 # Parent 887a3229fd7a50c04981e29709bc7210dafef38f libxl: fix parse_backend_path and device_backend_path to be mutual Currently if libxl__parse_backend_path is used and then you try to get the original path again with libxl__device_backend_path the
2011 Sep 07
0
[PATCH] libxl: vcpu_avail is a bitmask, use it as such
vcpu_avail is a bitmask of available cpus but we are currently using it as the number of cpus available. This patch fixes it. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> diff -r 6580ff415189 tools/libxl/libxl_dm.c --- a/tools/libxl/libxl_dm.c Wed Sep 07 13:29:15 2011 +0000 +++ b/tools/libxl/libxl_dm.c Wed Sep 07 15:39:46 2011 +0000 @@ -360,8 +360,13 @@ static char
2010 Aug 26
1
[PATCH] libxl: minor portability nits
Hi! Use #defines for network related default settinsg. Distinguish between default Linux and NetBSD network bridge interfaces. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- ---to satisfy European Law for business letters: Advanced Micro Devices GmbH Einsteinring 24, 85609 Dornach b. Muenchen Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd Sitz: Dornach, Gemeinde Aschheim,
2012 Jul 20
0
[help]What's the relationship between libxl libxc xenstore privcmd hypercall?
Hi all, In xen-4.1.2 source tree, under directory tools are there many library such lib*, what''s their individual feature? Besides, where is the log info for xl ? I try to trace using gdb after running xl, huge amounts of files\variable structure , complicated relationship between the components make me proceed slowly. Best regards
2010 Apr 15
0
libxl bootloader support
Hey, Just playing around with xl, it is fast! Seems it doesnt support pygrub? I assume the suggested way to do this would be to write a script to handle pygrub and supply the kernel/initrd to xl? Thanks, David _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
2013 Apr 17
0
libxl device xenstore entries cleanup
Hi, Currently libxl removes entries from xenstore "device/" tree only in case of: a) domain destroy (clean all domain directory) b) dom0-initiated device remove But this doesn''t cover all the cases. At least this isn''t done: a) backend domain shutdown, backend-initiated remove b) backend domain destroy (here backend driver doesn''t have chance to signal
2011 Feb 08
0
[PATCH] libxl: allow guest to write "control/shutdown" xenstore node
# 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