similar to: Question: How to see existing xenstore watches

Displaying 20 results from an estimated 6000 matches similar to: "Question: How to see existing xenstore watches"

2011 Sep 22
4
[PATCH 0/2] reset xenstore watches to fix kexec in Xen PVonHVM guests
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
2012 Jul 10
2
[PATCH] xen/pv-on-hvm kexec: shutdown watches from old kernel
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
2006 Dec 07
6
problem restarting xenstored
As any other daemon, I''d assume it should be possible to restart xenstored (i.e. if it crashed or if, during development, a fix was made to it that needs to be tested). However, as I learned after over a day of digging, things don''t work anymore after doing so: Since the watches are transient, they''re lost with the daemon going away. Right now I specifically need this in
2005 Dec 15
10
watches not working from domU userspace
It seems that xenstore watches do not work from domU userspace (they obviously do for drivers). In some preliminary debugging of this, there are two aspects of the failure: not sending the watch to xenstore and not handling watch events for userspace watches. The former can be easily fixed by adding the missing ''case XS_WATCH:'' to xenbus_dev_write() in xenbus_dev.c. The
2018 Jan 29
0
geo-replication command rsync returned with 3
Hi all, by downgrade of ii? libc6:amd64 2.23-0ubuntu10 to ii? libc6:amd64 2.23-0ubuntu3 the problem was solved. at least in gfs testenvironment running gfs 3.13.2 and 3.7.20 and on our productive environment with 3.7.18. possibly it helps someone... best regards Dietmar Am 25.01.2018 um 14:06 schrieb Dietmar Putz: > > Hi Kotresh, > > thanks for your response... > > i
2018 Jan 24
4
geo-replication command rsync returned with 3
Hi all, i have made some tests on the latest Ubuntu 16.04.3 server image. Upgrades were disabled... the configuration was always the same...a distributed replicated volume on 4 VM's with geo-replication to a dist. repl .volume on 4 VM's. i started with 3.7.20, upgrade to 3.8.15, to 3.10.9 to 3.12.5. After each upgrade i have tested the geo-replication which worked well anytime. then i
2018 Jan 25
2
geo-replication command rsync returned with 3
Hi Kotresh, thanks for your response... i have made further tests based on ubuntu 16.04.3 (latest upgrades) and gfs 3.12.5 with following rsync version : 1. ii? rsync????????????????????????????? 3.1.1-3ubuntu1 2. ii? rsync????????????????????????????? 3.1.1-3ubuntu1.2 3. ii? rsync????????????????????????????? 3.1.2-2ubuntu0.1 in each test all nodes had the same rsync version installed. all
2012 Jul 27
3
Xenstore restart
Hi, I am using xen-4.1-testing with Linux 3.4.3. The hotplug script xencommons echoes that xenstore is not restartable. Can anyone tell me the exact reason why it is not restartable. I tried to restart xenstore by killing the xenstore and restarting it with xencommons but after that VM creation doesn''t work. I used to do the same with the setting <xen-3.4+Linux-2.6.18> and it used
2018 Jan 25
0
geo-replication command rsync returned with 3
It is clear that rsync is failing. Are the rsync versions on all masters and slave nodes same? I have seen that has caused problems sometimes. -Kotresh HR On Wed, Jan 24, 2018 at 10:29 PM, Dietmar Putz <dietmar.putz at 3qsdn.com> wrote: > Hi all, > i have made some tests on the latest Ubuntu 16.04.3 server image. Upgrades > were disabled... > the configuration was always the
2012 Feb 29
0
[PATCH] vpmu: cleanup structures
Hi, a small cleanup of vpmu structures: - struct msr_load_store_entry is unused - struct pmumsr is only used in the vmx part Dietmar. Signed-off-by: Dietmar Hahn <dietmar.hahn@ts.fujitsu.com> # HG changeset patch # Parent a7bacdc5449a2f7bb9c35b2a1334b463fe9f29a9 diff -r a7bacdc5449a xen/arch/x86/hvm/vmx/vpmu_core2.c --- a/xen/arch/x86/hvm/vmx/vpmu_core2.c Mon Feb 27 17:05:18 2012
2013 Mar 12
0
[PATCH] vpmu intel: pass through cpuid bits when BTS is enabled
Hi, this patch passes the orginal cpuid bits for X86_FEATURE_DTES64 (64-bit DS Area) and X86_FEATURE_DSCPL (CPL Qualified Debug Store) to the guest when the BTS feature is switched on. I forgot this when I did this BTS emulation. Thanks. Dietmar. Signed-off-by: Dietmar Hahn <dietmar.hahn@ts.fujitsu.com> diff -r a6b81234b189 xen/arch/x86/hvm/vmx/vpmu_core2.c ---
2013 Dec 05
7
POD: soft lockups in dom0 kernel
Hi, when creating a bigger (> 50 GB) HVM guest with maxmem > memory we get softlockups from time to time. kernel: [ 802.084335] BUG: soft lockup - CPU#1 stuck for 22s! [xend:31351] I tracked this down to the call of xc_domain_set_pod_target() and further p2m_pod_set_mem_target(). Unfortunately I can this check only with xen-4.2.2 as I don''t have a machine with enough memory for
2018 Jan 19
0
geo-replication command rsync returned with 3
Fwiw, rsync error 3 is: "Errors selecting input/output files, dirs" On January 19, 2018 7:36:18 AM PST, Dietmar Putz <dietmar.putz at 3qsdn.com> wrote: >Dear All, > >we are running a dist. repl. volume on 4 nodes including >geo-replication >to another location. >the geo-replication was running fine for months. >since 18th jan. the geo-replication is faulty.
2010 Sep 17
27
Problem: Pattern with vertical colored lines on the dom0 screen
Hi list, I have a problem with a new laptop (reproducable on other machines too) and the xen hypervisor. When the hypervisor gets booted with VESA mode 800x600 I see some messages and then the screen contents is switched into a pattern of vertical colored lines and never comes back. In text mode all works well, but later the pattern appears when the X servers starts. I disabled VTd in the bios
2007 Jan 03
4
Xenbus watch firing over and over
hi, I am trying to add xenbus watch support to mini-os, but am getting into a endless loop of watches firing over and over. Below is an excerpt from the xenstore tracefile: IN 0x805acc8 20070103 19:32:18 WATCH (/local/domain/0/backend/vif/26/0/state 00043818 ) CREATE watch 0x805a8b8 OUT 0x805acc8 20070103 19:32:18 WATCH (OK ) OUT 0x805acc8 20070103 19:32:18 WATCH_EVENT
2006 Aug 02
2
[PATCH][RFC] permit domU userspace to watch xenstore
Hello, This patch allows userspace tools on a domU to setup a watch on the xenstore. It does this by intercepting XS_WATCH requests written to /proc/xen/xenbus and then re-submitting the request to the in-kernel xenstore interface, in linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_xs.c. When a callback occurs, an in-kernel function is invoked, which then reconstructs a response in the format
2009 Aug 17
2
[LLVMdev] can't get it compiled
Is this the right mailing list ? I want to compile llvm-2.5 under Fedora 11 with gcc (GCC) 4.4.0 20090506 (Red Hat 4.4.0-4) and get In file included from Signals.cpp:31: Unix/Signals.inc: In function ‘void<unnamed>::PrintStackTrace()’: Unix/Signals.inc:81: error: invalid conversion from ‘const char*’ to ‘char*’ Unix/Signals.inc:96: error: invalid conversion from ‘const char*’ to ‘char*’
2006 Nov 23
5
Xen Dom0 with FibreChannel (FC) can''t export disk to DomU
Hello all, I have a problem with Xen and FibreChannel. The Dom0 can''t export a Disk on a FibreChannel SAN-Box to the DomU''s. In the DomU configuration I try: disk = [ ''phy:/dev/sdb1,/dev/sda1,w'' ] or disk = [ ''file:/mnt/sambashare.img,sda1,w'' ] sambashare.img is a 512MB great Diskimage on a Partition on the FC-SAN-Box, the Dom0 mount this
2012 Nov 14
2
Bug#693217: Removal of xenstore tdb file before xenstored daemon
Package: xen-utils-common Version: 4.0.0-1 Consider removal of xenstored tdb file (located at /var/lib/xenstored/tdb) before start of xenstored daemon during the boot (or removal during the shutdown/reboot of the server) as proposed by Ian Campbell during our discussions [1]. [1] http://lists.xen.org/archives/html/xen-users/2012-11/msg00111.html -- Peter Viskup
2008 Mar 25
0
[LLVMdev] Whole-function isel
On Mar 25, 2008, at 9:40 AM, Dietmar Ebner wrote: > Chris, > > Chris Lattner wrote: >> I would love to see any progress in this area. It is clearly an >> important thing to tackle, and it is blocking other interesting >> improvements in the code generator. It would also allow us to >> eliminate a significant amount of weirdness that exists to hack >>