similar to: problem restarting xenstored

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

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

I just downloaded Xen-4.1.1 from xen.org, compiled it, and installed it. I then compiled kernel 3.0.0 and added the hypervisor and dom0 kernel in a grub 2 entry. After booting, I executed "xl list," to confirm the hypervisor was running. I was greeted with this message: libxl: error: libxl.c:56:libxl_ctx_init Is xenstore daemon running? failed to stat /var/run/xenstored.pid: No such

I''m looking at building a xenstore-based watchdog, as described at http://lists.xensource.com/archives/html/xen-users/2005-07/msg00597.html However, being somewhat new to xenstore, I''d appreciate some pointers. - What portions of the xenstore namespace should I use? I''m looking for at least two settings writable by the DomUs: A flag to enable/disable the watchdog

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

I''m running Xen3 7775 with udev 073 (which was a PITA to get working, as the initrd I''ve been running for quite some time uses an older one -- but that''s an entirely different story). My dom0 is Gentoo-based. When I try to start a DomU, it times out waiting for hotplug-based notification, as per the following: DEBUG (DevController:69) Waiting for devices vif. DEBUG

I''m running Xen3 7775 with udev 073 (which was a PITA to get working, as the initrd I''ve been running for quite some time uses an older one -- but that''s an entirely different story). My dom0 is Gentoo-based. When I try to start a DomU, it times out waiting for hotplug-based notification, as per the following: DEBUG (DevController:69) Waiting for devices vif. DEBUG

I''ve been trying to track down just why talking to XenD is resulting in so much CPU time being comsumed by both xend & xenstored. As a test case, I''m running ''virsh dominfo demo'' which results in a single HTTP request to Xend to fetch domain info, eg ''GET /xend/domains/demo'' Run this in a tight loop & I''ll see xenstored

Package: xen-utils-4.0 Version: 4.0.1-2 Hi, When you change XENCONSOLED_ARGS in /etc/default/xend, there's no normal way to apply it. Even if you do '/etc/init.d/xend stop', that doesn't stop xenconsoled, despite the fact the analogous 'start' action did start it. There isn't even a separate init script action to stop it, it has to be killed manually. Same goes for

Hi All, I just tried a new installation of Ubuntu 10.04 (64bit) + Xen and am having some trouble starting XEN. I am using the latest mercurial checkout (4.0.2-rc2) and the only change I made was to Config.mk to enable building the OCAML version of xenstored. " CONFIG_OCAML_XENSTORED ?= y". I am using the same kernel I built earlier for a similar Ubuntu 10.04-64bit / Xen 4.0.0

Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal There should be a clean and clearly defined way to restart all the Xen daemons in the case of error. If the file /var/lib/xenstored/tdb is corrupt then you must stop xenstored, rm the file, and then restart it. Currently there is no defined way of doing this so the solution is to kill -9 the process, rm the file, and then reboot. --

Hi, I am running XEN 4.1 on Debian 6 and I cannot find blktapctrl process running. xend is started. I installed XEN from 4.1 source following instructions here: http://wiki.xensource.com/xenwiki/XenParavirtOps http://wiki.xensource.com/xenwiki/Xen4.0 Should there be a blktapctrl process running in this version? The problem I have encountered is that I can create a domain on a raw disk image but

hello all, it''s my first time ever with xen (or even virtualization in general). I installed Xen 3.2 on top of a Debian Lenny kernel 2.6.26-2-686 via apt-get. Boot options are: title Xen 3.2-1-i386 / Debian GNU/Linux, kernel 2.6.26-2-xen-686 root (hd0,0) kernel /xen-3.2-1-i386.gz dom0_mem=512000 module /vmlinuz-2.6.26-2-xen-686 root=/dev/mapper/athena-root ro console=tty0 module

Hi all, I have some serious problems making Xen run. I have spent a couple of days looking in Google and trying a lot of different things, but none of them has worked. I hope you can help me... First of all: xen was running smoothly on my machine, but suddenly (I think I haven''t changed any configuration) it doesn''t work anymore. I am using a Debian 4.0 with Xen 3. When

Hi, recently on irc channel (##xen) was some "discussion" about xen vs kvm... There was idea that it would be nice if domUs could survive dom0 restart, but this needs, for example, to have xenstored running in separate domain. In 2009 Alex Zeffertt posted some patches (http://lists.xensource.com/archives/html/xen-devel/2009-04/msg00696.html) to add this functionallity, but they

I''ve migrated my Dom0 host to Xen 4.2.0 + xl toolstack. With ''xm'' toolstack, configs in /etc/xen/auto are autostarted, assuming xend/xendomains services are started. IIUC, when using xl toolstack, those services are not to be started; and, afaict, the installation process for 4.2 has them disabled by default. Now, the configs in /etc/xen/auto are simply ignored. I

Hi all I was reading through Xen 3 user manual and saw this tap:aio should be used instead of loopback... Then I came to do that, but I can get it working with replacing `file'' URI''s with `tap:aio''. My OS: Debian Lenny 2.6.26-2-xen-amd64 DomU Xen configuration file: kernel = ''/boot/vmlinuz-2.6.26-2-xen-amd64'' ramdisk =

Hi experts, First I post my log root@intel_5500_server:/> ifconfig eth0 Link encap:Ethernet HWaddr 00:15:17:BB:5E:88 inet addr:128.224.165.205 Bcast:128.224.165.255 Mask:255.255.255.0 inet6 addr: fe80::215:17ff:febb:5e88/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2375 errors:0 dropped:0 overruns:0 frame:0

Hi... I have had a problem when I am going to detach one specific LVM partitions of Xen, so I have been trying xm destroy <domain>, lvchange -an <lvm_partition>, lvremove -f.... So I haven''t had sucess. I restarted the server with init 1 yet and nothing... I have seem two specific process started xenwatch and xenbus, but I am not sure if this processes have some action over

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