similar to: xend / xenstored performance & scalability issues

Waay back at the end of 3.0.3 dev cycle I brought up the issue of XenD running far too many xenstore transactions per-request http://lists.xensource.com/archives/html/xen-devel/2006-10/msg00487.html Short summary: # nc -U /var/lib/xend/xend-socket GET /xend/domain/test Resulted in approx 16 xenstore transactions for a domain with one disk and one NIC - this increases as # of devices

Package: xen-utils-4.0 Version: 4.0.1-2 Severity: normal Tags: squeeze I have 3 VM running. I have upgraded debian squeeze to 6.0.1 (new kernel package 2.6.32-31) and restarted my server. VM were still running. After reboot I could not start xend service (from init.d). I got following errors: kern.log: Mar 22 15:07:30 router kernel: [53888.212756] xenstored[7232]: segfault at 7fff056b5ff8 ip

Hi all, xend communicates with xenstored using unix domain sockets right? So, would it be possible to convert the unix domain sockets to tcp/ip sockets and let xenstored run on a different machine? Regards, Hayawardh _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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. --

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

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

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

Package: xen-utils-common Version: 4.0.0-1 Severity: important After running modules_setup you need to have the following line: [ -x /sbin/restorecon ] && /sbin/restorecon -R /dev/xen The reason is that the module load causes the kernel to create device nodes in the devtmpfs. This bypasses the udev code for labelling the device node and results in xenstored being unable to access

Hi, I have recompiled xen-3_3.4.3~rc3-1 in Lenny, together with the 2.6.32-10 kernel. While my dom0 boots without issue under Xen, xend refuses to start. I have cut/past my xend.log is bellow. Is there any reason why a backport of this version of Xen wouldn't work in Lenny? Should I try the already compiled SID binaries in Lenny without trying to build myself? Cheers, Thomas When I start

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

I''m currently running snv_76 on my laptop to run a windows XP hvm domU. Everything has been working great until recently when I started getting the following messages during boot (from dmesg): Dec 11 16:31:19 pdlaptop xenstored: [ID 702911 daemon.error] Checking store ... Dec 11 16:31:19 pdlaptop xenstored: [ID 702911 daemon.error] Checking store complete. Dec 11 16:31:19 pdlaptop

This fast-track covers the SMF-related changes for dom0. This is a final draft, so any comments by the end of the week please... Man pages are attached. thanks john SMF services for Xen 1. Introduction This case introduces the SMF services used by a Solaris-based domain 0 when running on Xen, or a Xen-compatible hypervisor. All of these services only run on domain 0 when booted

Hi, A few people are having problems with the new console daemon and I''ve tracked the problem down to the order in which daemons are started. Here''s what currently happens: 1) xend (the script in tools/misc) start will launch xcs and consoled 2) xend (the python server) will launch xenstored whenever it needs it This creates a bit of a chicken and the egg problem since

Package: xen-utils-3.0 Version: 3.0.2+hg9697-2 Severity: wishlist Hi, it would be nice to run xend under the supervision of runit. xenconsoled and xenstored already provide relevant switches (-i and --no-fork). Thanks Andras -- Andras Korn <korn at chardonnay.math.bme.hu> <http://chardonnay.math.bme.hu/~korn/> QOTD: Paranoid: someone

This patch moves some dom0 variables and backend device configuration from frontend directories to /local/domain/<backdomid>/backend or /vm. Also, - the first console is created as a xend device and moves from console/0 to device/console/0 - /vm_path/<domid> is introduced, referencing the /vm path - /vm_path/device/backend holds the backend device location, rather than storing it

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

# 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

This patch was created for 3.1.0. Based on inspection, I believe the current version has the same problem, but I did not actually try it. I hope you''ll find the patch useful anyway. Xen cannot work when xenstored''s tdb is corrupt. When that happens somehow (and we''ve seen it happen), even reboot doesn''t recover from it. It could: there is no state in tdb

Hello, Fedora 19 running Xen 4.2.3 rpms, "xl list" after dom0 reboot: [root@localhost ~]# xl list Name ID Mem VCPUs State Time(s) (null) 0 1024 8 r----- 16.3 Why is dom0''s name "(null)" ? It seems also xenstore is quite empty: [root@localhost ~]# xenstore-ls tool =