Adrien ze Urban
2012-Dec-02 11:53 UTC
[Pkg-xen-devel] Bug#694931: xenstored not started by init script on domU
Package: xen-utils-4.1 Version: 4.1.3-4 Severity: important Tags: patch Bug presented in sid, with patch attached. Similar bug is also present in stable and testing versions. How to reproduce: Install xen-utils-4.1 in a domU, and run: /etc/init.d/xen start Expected result: xenstored running (or to have any other easy way to get it running within a domU) xenstored is not just something you need to run in a dom0, it can also be useful in a domU. Example of informations you can retrieve: # domid=`xenstore-read domid` # xenstore-ls /local/domain/$domid [...] As some might not be aware of why else it might be usefull, here are some presentation of what I'm using it for: ------------------------------------------------------------------------ It is also required to get backends within a specific VM, rather than a dom0. Isn't it nice to have 2 domU able to have direct network connection, rather than having to go through the dom0 bridge, that might have a firewall to bypass (multiple copy, lag, ...) Example of vif configuration, to get the backend in a vm : 'mac=00:16:3E:de:ad:01,backend=firewall,script=vif-bridge,vifname=sandbox,bridge=brmisc', That require xen-utils to run in the domU named firewall. The script vif-bridge will be launched there, expecting to get put in a bridge 'brmisc'. The interface will also have a nice name, instead of 'vifX.Y'. Catch: it NEED to have xenstored running. I'd appreciate not to have to patch debian init script each time I install a vm that is supposed to receive backends. ------------------------------------------------------------------------ On the other hand, my dom0 is a debian/stable. So, when I checked if debian/sid would run xenstore or not, I found an other bug that also need to get fixed to have it work nicely. xen-version (used by xen-dir) checks what hypervisor is running. Which makes it search 4.0 directory (hypervisor from stable), though I have xen 4.1 utils installed (sid). Ugly patch attached, in case someone try to run a sid domU on a squeeze dom0 with 4.0 hypervisor. (not expecting that part to get anywhere near the repository) -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages xen-utils-4.1 depends on: ii e2fslibs 1.42.5-1 ii libc6 2.13-37 ii libgnutls26 2.12.20-2 ii libncurses5 5.9-10 ii libpci3 1:3.1.9-6 ii libtinfo5 5.9-10 ii libuuid1 2.20.1-5.2 ii libxen-4.1 4.1.3-4 ii libxenstore3.0 4.1.3-4 ii python 2.7.3-3 ii python2.7 2.7.3-5 ii xen-utils-common 4.1.3-4 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages xen-utils-4.1 recommends: ii bridge-utils 1.5-6 pn qemu-keymaps <none> pn qemu-utils <none> pn xen-hypervisor-4.1 <none> Versions of packages xen-utils-4.1 suggests: pn xen-docs-4.1 <none> -- no debconf information -------------- next part -------------- A non-text attachment was scrubbed... Name: init.d.xen.patch Type: text/x-diff Size: 1381 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20121202/ba2feb85/attachment-0002.patch> -------------- next part -------------- A non-text attachment was scrubbed... Name: xen-version.patch Type: text/x-diff Size: 379 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20121202/ba2feb85/attachment-0003.patch>
Debian Bug Tracking System
2012-Dec-02 12:45 UTC
[Pkg-xen-devel] Bug#694931: marked as done (xenstored not started by init script on domU)
Your message dated Sun, 2 Dec 2012 13:42:11 +0100 with message-id <20121202124211.GA14467 at waldi.eu.org> and subject line Re: [Pkg-xen-devel] Bug#694931: xenstored not started by init script on domU has caused the Debian Bug report #694931, regarding xenstored not started by init script on domU to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 694931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694931 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Adrien ze Urban <adrien.urban at nbs-system.com> Subject: xenstored not started by init script on domU Date: Sun, 02 Dec 2012 12:53:55 +0100 Size: 6935 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20121202/f3844db8/attachment.mht> -------------- next part -------------- An embedded message was scrubbed... From: Bastian Blank <waldi at debian.org> Subject: Re: [Pkg-xen-devel] Bug#694931: xenstored not started by init script on domU Date: Sun, 2 Dec 2012 13:42:11 +0100 Size: 3074 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20121202/f3844db8/attachment-0001.mht>
Apparently Analagous Threads
- Xenstore daemon is not running after boot; although can be started manually later. Any pointers why ?
- Xenstore daemon is not running after boot; although can be started manually later. Any pointers why ?
- [PATCH 08/13] xen init script: rewrite xenstored start logic
- Bug#693217: Removal of xenstore tdb file before xenstored daemon
- xl is unable to find xenstored.pid