similar to: Bug#517863: Make logging of guest console output in dom0 via xenconsoled configurable

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

When installing xen-utils-V in a driver domain domU, it drags in xen-utils-common, which also contains the init script for xenstored and xenconsoled. Installing the package will fail right away, because it exits non-zero after checking whether it's running in a xen dom0 or not: systemd[1]: Starting LSB: Xen daemons... xen[7215]: Starting Xen daemons: (warning). systemd[1]: xen.service:

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

One of our machines are being bitten by that bug, once every 2-4 weeks or so xenconsoled dies and all the VMs stop responding intil xenconsoled is restarted. I googled for it and I saw many people reporting it but no solution for it. Does anyone know if it is solved in 5.5? I can't upgrade the box (it's a production box) unless I can prove the problem will go away. thanks in advance

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

https://bugzilla.mindrot.org/show_bug.cgi?id=2110 Bug ID: 2110 Summary: ssh-copy-id fails on nonexisting private key Product: Portable OpenSSH Version: 6.2p1 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P5 Component: Miscellaneous Assignee: unassigned-bugs

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

Hi, I see a round of bug fixes and well as xenbus were pulled upstream. Is anything else going into .38? -- 2. That which causes joy or happiness. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u4 Severity: critical Hi, Not sure how come I'm the first one to file this kind of a bug report :) but here goes JFTR... http://xenbits.xen.org/xsa/advisory-123.html was embargoed, but advance warning was given to several big Xen VM farms, which led to e.g. https://aws.amazon.com/premiumsupport/maintenance-2015-03/

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 just dumping all I got in here, after initial feedback we can see how to organize todo's around it. tl;dr: * Does not upgrade cleanly from 4.8 packages, so we have to prevent this from entering testing until we fix that. * Live migration is broken, explodes with memory allocation errors. ---- >8 ---- 1. Build packages * I have built salsa/master using pbuilder targeting sid.

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

The contents are the wip.testme branch currently on salsa. I combined the wip.initscript and wip.oxenstored into this and added more things today. I think this is pretty gtg and it's smoke tested (in several cases by scping files around instead of doing package build), so it needs a final extra review and test round before putting it in master branch (which I don't want to force push). I

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