similar to: is the xenconsoled crash solved?

Hi Ian, On Tue, Jan 17, 2017 at 10:58 +0000, Ian Jackson wrote: > Wolodja Wentland writes ("Bug#851654: Prerm maintainer script unconditionally > stops xend/xenconsoled"): > We triggered a xen stop by removing obsolete > xen-utils-4.1 packages while already using xen-utils-4.4. > I think a xenconsoled restart should be harmless, so I think it is > probably right that

Hello, Is there any documention on "xenconsoled" ? (I have installed xen from source) /usr/sbin/xenconsoled --help Usage: /usr/sbin/xenconsoled [-h] [-V] [-v] [-i] What do the different options mean? Should xenconsoled always be running, even when no "xm console" commands are active? I killed it in error, but now need to know how to start it with it''s default

xenconsoled: do not write the pty under serial in xenstore if xenconsoled is handling a consolepath. The idea is that pv consoles use the "console" prefix in xenstore and emulated serials use the "serial" prefix in xenstore. There is no need to write the pty for a pv console under "serial", considering that xenconsoled is already writing the pty under

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: wishlist Hi, this morning I spend some time to find out how to log console output of Xen guest domains into a file in dom0. I ended up using a quick 'n dirty solution: mario:/usr/lib/xen-3.2-1/bin 0-# diff -u xend.orig xend --- xend.orig 2009-03-02 16:49:49.000000000 +0100 +++ xend 2009-03-02 16:16:03.000000000 +0100 @@ -100,7 +100,8 @@

Grant references for the xenstore and xenconsole shared pages exist, but currently only xenstore uses these references. Change the xenconsole daemon to prefer using the grant reference over map_foreign_range when mapping the shared console ring. This allows xenconsoled to be run in a domain other than dom0 if set up correctly - for libxl, the xenstore path /tool/xenconsoled/domid specifies the

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

Grant references for the xenstore and xenconsole shared pages exist, but currently only xenstore uses these references. Change the xenconsole daemon to prefer using the grant reference over map_foreign_range when mapping the shared console ring. This allows xenconsoled to be run in a domain other than dom0 if set up correctly - for libxl, the xenstore path /tool/xenconsoled/domid specifies the

Hello list! I''ve noticed this problem a couple of times now.. so I''m wondering if it''s a known bug? Symptoms: After "long" dom0 uptime (174 days when it happened now, was something similar on previous times too) cannot start new pv domUs anymore.. pygrub runs and boots the kernel, but kernel newer gets to actually running initrd and the console output

Package: xen-utils-4.4 Severity: normal Dear Maintainer, the xen-utils-4.4 and xen-utils-4.1 prerm maintainer scripts contain the following code snippet: remove|upgrade) update-alternatives --remove xen-default /usr/lib/xen-4.4 if [ -x "/etc/init.d/xen" ]; then invoke-rc.d xen stop || exit $? fi ;; which, in conjunction with the postinst

Under the right circumstances, xenconsoled will corrupt its internal list of domains causing a SEGV. This is usually characterized by a rapid number of creations/destructions. The attached patch fixes this. Regards, Anthony Liguori _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I''m trying to get XCI running on a Lenovo T61 with Intel-based graphics following the steps in the HOWTO in the build directory. I was able to get to the GRUB screen but never get to the "Welcome to XenClient" prompt. When I boot with the full console output, the system hangs indefinitely after "Starting XenConsoled". I''m well trained in the XenServer

Hi everyone, I know this process is started by xend with no command parameters , if I want xenconsoled''s log facility , I must pass the --log parameter . So I change the following line from: os.execvp(''xenconsoled'', [''xenconsoled'']) to os.execvp(''xenconsoled'', [''xenconsoled'',''--log=all'']) but this

Package: xen-utils-common Version: 4.4.1-9+deb8u1 Severity: normal Dear Maintainer, When booting a PV guest (xl create -c /etc/xen/foo.conf), immediately after pygrub has determined which kernel/initramfs it will use, the following error messages are logged: xenconsole: Could not open tty `': No such file or directory libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console

Hello everyone: When i starting a linux domU, i get the error message: "xenconsole: Could not read tty from store: No such file or directory" #xm create -c /etc/xen/fc6.cfg Using config file ... ....... xenconsole: Could not read tty from store: No such file or directory ----------------- #xm list Name ID Mem VCPUs State Time(s) Domain-0 0 251

# HG changeset patch # User max.zhen@sun.com # Date 1171024588 28800 # Node ID a2d15838ea72ee049d8a657e9ecd406b5c6cb53e # Parent d609929f140809ec1c9a059f2eeaffb7ce56c891 Xenconsoled should ignore spurious watch event. Otherwise, xenconsoled could bind to a dying domU during its suspending and cause complaint from Xen: (XEN) event_channel.c:177:d0 EVTCHNOP failure: domain 0, error -22, line 177

Came across this issue in 3.0.2; looks to also be present in the latest unstable sources: # ls -l /var/run/xenconsoled.pid -rwS--x--T 1 root root 5 Aug 31 00:29 /var/run/xenconsoled.pid setuid, group-execute, and sticky...? This happens because daemonize() in tools/console/daemon/utils.c isn''t specifying a "mode" parameter when creating the file: fd = open(pidfile, O_RDWR

Hi, I was trying to attach console to my virtual node created by xen but I am getting the following error: *varun:~# xm console xenDomain1* *xenconsole: Could not read tty from store: No such file or directory.* I have tried starting the xenconsoled service but still I am facing the same problem. Can anyone please help me out with this one? Regards, Varun

Hi, i''m running a two dom0 nodes cluster for HA, and xen domUs running on top, currently it handles 5 domUs. The issue is that there''s a domU that can only run on one node, it''s not possible to start it on the other one. I get a ''b'' status and can''t access the console. Other domUs can start in either node and I can access their console without

Hi. On my FreeBSD 4.8 configured IPFW2+IPF+IPNAT and I use them all: - IPFW - traffic accounting, shaping, balancing and filtering; - IPFilter - policy routing; - IPNAT - masquerading. I want to know, how IP-packets flow through all of this components? What's the path? incoming: IPFW Layer2 -> IPFW&Dummynet -> IPNAT -> IPFilter ? outgoing: IPFW Layer2 ->

Package: xen-utils-common Version: 4.4.0-1 Severity: important Tags: patch Under some circumstances the xl toolstack needs to create a loopback mount of a guest disk in dom0 (e.g. in order to run pygrub). Depending on the nature of the guest disk (e.g. qcow2 or raw file image based) this can require a qemu instance in dom0. The upstream xencommons starts such a qemu on boot. The following patch