similar to: about xenconsoled log

Hi all , When I xm create a domain , it seemed that it never got scheduled , why? Following is the out put of xm list: Name ID Mem VCPUs State Time(s) Domain-0 0 236 2 r----- 74.9 winxp 5 192 1 ------ 0.0 which command should I try further ? Thank you

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

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

Hi All , What does PV driver standard for . Does it mean I can run windows as a paravirt guest ? If so , that sounds cool . It seems paravirt''s performance is better , right ? Thank you yushang _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

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

What follows below is an outline of what we''re changing in Xen startup for Fedora 8. I know historically when getting into initscripts you tend to hit distro specific issues. So I''m posting this to see if there''s any interest from others in having these changes integrated upstream. I''d like to thing that with a few minor tweaks this is general enough to be

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

Xen patchbot -unstable wrote: ># HG changeset patch ># User cl349@firebug.cl.cam.ac.uk ># Node ID 8fe8a99b1c2a6ea88624546ab625eaa0758e3a17 ># Parent e69cbfee4011da1648718f1f5cbe8dabb956e72a >New console transport and update xenconsoled. >Add a new console interface using a seperate shared page and event channel >instead of passing the console input/output over control

These xm info, top, dmesg and log requre no parameter. But log''s error message differs from other 3 command''s error messages, when parameter is given. # xm log 1 Error: ''xm log'' requires 0 argument. log Print the xend log Other 3 commands ignore parameter. I think it might be better symmetricalize. Signed-off-by: Yoshinori

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

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

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

so I am tenitively moving towards the xen 4/pv_ops kernel (2.6.32.18, xen/stable-2.6.32.x as of yesterday). I need a lot of guests, as our smallest hardware has 32GiB ram, and our median guest has 256MiB ram. we followed http://lists.xensource.com/archives/html/xen-devel/2010-04/msg01537.html and changed NR_DYNAMIC_IRQS in arch/x86/include/asm/irq_vectors.h to 2048. we changed the

Hardware: blade HS20 on RHEL4 U1 base kernel. # hg tip changeset: 6811:a8edb2655c5d220b1bbf2b8d8415aae0ac136da3 tag: tip user: cl349@firebug.cl.cam.ac.uk date: Wed Sep 14 10:47:48 2005 summary: Add methods to read/write Vm/Domain store entries. I created domU and got the messages: # xm create -c vm2.cfg Using config file "vm2.cfg". Started domain

-------- Исходное сообщение -------- Тема: Fwd: bug on create domain0 Дата: Mon, 04 Apr 2011 14:54:13 +0600 От: net administrator Отвечать: tkpiuk@gmail.com Кому: xen-devel@lists.xensource.com -------- Исходное сообщение -------- Тема: bug on create domain0

# 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,