similar to: xenconsoled needs restart after long dom0 uptime otherwise domU console output hangs and domU doesn''t come up

Hey, I''ve installed Xen 3.0 on a freshly installed Debian Sarge. dom0 is working nicely (kernel 2.6.12.6-xen0). Then I created a domU, again with Debian Sarge, booting Xen''s vmlinuz-2.6.12-xenU. Unfortunately ctrl-c does not work in the domU''s console, neither if I create the domU with "xm create -c ..." nor if I attach to it later. It doesn''t matter

Hello! I've noticed this problem two times now.. last time I fixed it by rebooting the (centos 5.1 x86 32b) xen host/dom0. Symptoms: - Already running domUs (debian 2.6.18-6-xen-686 32b PAE) continue running and working OK - Cannot start new domUs (debian 2.6.18-6-xen-686).. kernel bootup just hangs before running initrd. Same domU with the exact same xen domU cfgfile worked earlier.

Hi there guys. I''m using CentOS 5.4, I was able to compile my custom Dom0 kernel and boot it, now I''ve got some doubts. I''d like to compile a custom DomU image, the problem is that when I do, make kernels KERNELS="linux-2.6-xen0 linux-2.6-xenU" it tries to download the kernel from the HG repository which seems to have old 2.6.18 kernels, I want to use the GIT

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

Hi all, I have another problem with starting domainU (xenolinux). I took me pretty much quite some time and i can not figure out why starting a new domain is failing. I will really appreciate if somebody can help me with this error. The error I get when booting xen-domainU is: /======================= Red Hat nash version 4.1.18 starting Mounted /proc filesystem Mounting sysfs Creating /dev

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

Hello, i''ve a xen-4.0.0-rc1 with 2.6.31.6 pv_ops. Dom0 seams to work fine. But i can only boot "old" domU kernel. A pv_ops Kernel hangs after initrd. Regards, Stefan Kuhne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello, i''ve a xen-4.0.0-rc1 with 2.6.31.6 pv_ops. Dom0 seams to work fine. But i can only boot "old" domU kernel. A pv_ops Kernel hangs after initrd. Regards, Stefan Kuhne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello list. My server: Gentoo 2.6.21-xen dom0 xen-tools 3.2.1 lvm 2.02.28-r2 udev-115-r1 Symptoms: normally I run 4 domUs. About once a week I have a need to restart a domU. Sometimes it works just fine, but other times it does not and I''ll get a message back saying "Error: Device 0 (vif) could not be connected. Hotplug scripts not working". The domU config file has not

Hi list, I am starting a academic security related project and I was wondering if there is any documentation on compiling xen/dom0 with a recent kernel? I''ve seen a few good intentioned threads, but no real documentation so far. Any helpful pointers will be greatly appreciated! Thanks in advance, - SDG P.S: First mail, not sure if I should post it here...let me know if I am on the

Hi list! I''m trying to run 2.4.29-xenU with grsec. Jacob Gorm Hansen said couple of weeks ago, that grsec should work with xen when pax is disabled.. Well, to get the kernel compiling there''s some source hacking that needs to be done.. I''ll describe what I did and what error I got: I downloaded xen-2.0-testing-src.tgz and extracted it. I edited the toplevel Makefile

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 all, I''m using Xen4.0.1 with SLES11SP1 with Intel''s SRIOV NIC in passthrough mode to FedoraCore14 guest HVMs. From guest HVM I''m able to send packets out but not able to receive the same. Intel NIC HW counters are reporting receiving packets but the same is not reaching the guest HVM. My NIC uses MSI-X to report packets to SW. which should be received by Xen

Hello list! (resending, it seems the previous mail didn''t make it to the list) At some point Xen supported block-reconfigure to resize domU disks on the fly.. This is not working atm/anymore? Discussion about the subject.. (in the end of the thread): http://lists.xensource.com/archives/html/xen-users/2008-04/msg00246.html Support for online resizing Linux SCSI disks was accepted

Hi, I want to add 2 vlans by the following steps: 1. add the vlan interfaces: vconfig add eth0 100 --vlan100 vconfig add eth0 101 --vlan101 2. modify the network-bridge script by the websit, http://wiki.xensource.com/xenwiki/XenNetworking#head-04ebcc1760dbc4678e83b116afa310dc0612dc39 Comment each time ifup or ifdown commands are executed.The reason is that ifdown ends with

hi, I am trying to start a new domainU but got the error: Error: Device 0 (vif) could not be connected. Hotplug scripts not working I have struggled with it for a long time. I found somebody else report this but can not find a solution. The xen version is xen-3.0 latest version. I do not have a initrd. Domain0 works fine but when I create a new domain, it always gives an error as above. Thanks,

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

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

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