similar to: 1000 Domains: Not able to access Domu via xm console from Dom0

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

The original implementation utilies select(). In Linux select() typically supports up to 1024 file descriptors. This can be a problem when user tries to boot up many guests. Switching to poll() has minimum impact on existing code and has better scalibility. Up to 8192 file descriptors are supported in the current implementation. Signed-off-by: Wei Liu <wei.liu2@citrix.com> ---

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

# 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

# HG changeset patch # User john.levon@sun.com # Date 1171946682 28800 # Node ID e8a7491ed4c57d4d82642dd954b8909d9065b377 # Parent 24a6bc1d1b93405558741a2a8fa7ba2f7c44964a Xenconsoled should ignore spurious watch event. Otherwise, it can rebind to the same evtchn of a dying domU during suspending and cause below error message: (XEN) event_channel.c:177:d0 EVTCHNOP failure: domain 0, error -22,

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and

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

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

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

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

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

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

Hello Community, I encountered an error while running "xm console domU". Here is the running script: # xm console domU xenconsole: Could not read tty from store: No such file or directory I googled and found out that this issue is mostly result from forgetting starting xenconsole service. However, after I started xenconsole, the issue is still there. Please see: #

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

I''m unable to start xl console on latest xen-unstable (build with commit 8e0da8c07f4f80e14314977a11f738bd74a5b62b). > xl -vvv console sid > xenconsole: Could not read tty from store: No such file or directory I also tried "xl create -c", and it shows console from pygrub but when the "xl create" reaches the end I got the same error: > xenconsole: Could not

Hi, I installed one debian HVM guest (VT virtualization). I didnt configured the network (I dont know if it is related to my problem): When I start the domU , I received this error: desktop:/etc/xen# xm create -c debian-web.cfg Using config file "./debian-web.cfg". Started domain debian-web xenconsole: Could not read tty from store: No such file or directory Here is my cfg: kernel

I''ve noticed that after I create 83 domains on a server, ''xm create'' will create domains without a valid console tty value. This corresponds approx. to 256 file descriptors. I''ve bumped up the limits for all daemon processes to 1500 file descriptors, so I''m really puzzled where xen is hitting a resource limit. Where is the code that creates the xs

I''ve noticed that after I create 83 domains on a server, ''xm create'' will create domains without a valid console tty value. This corresponds approx. to 256 file descriptors. I''ve bumped up the limits for all daemon processes to 1500 file descriptors, so I''m really puzzled where xen is hitting a resource limit. Where is the code that creates the xs

Hello All, After a few months of hiatus, we have resumed working on mips port of Xen. We are at the point of booting dom0 userland (init process and its children). The init process gets spawned and in turn forks off processes to run commands in /etc/rc.d/init.d/rcS. However, the getty process does not seem to run subsequently and hence the login prompt is not displayed. Dom 0 does not use the