From mboxrd@z Thu Jan 1 00:00:00 1970 From: Min Lee Subject: Re: xen-unstable+pvops kernel, I don't have xenbus and xenwatch kernel thread. Date: Wed, 09 Jun 2010 14:37:21 -0400 Message-ID: <4C0FDF61.6080001@gatech.edu> References: <4C0FADC8.20204@gatech.edu> <4C0FDC22.8030709@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C0FDC22.8030709@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: Xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hi, Jeremy. Yes, xenstored is running and xenstore-ls dumps its contents, although I had to start it manually. I have only evtchn in /dev/xen. No gntdev. On 6/9/2010 2:23 PM, Jeremy Fitzhardinge wrote: > On 06/09/2010 08:05 AM, Min Lee wrote: >> Hello. folks. >> I've tried Xen-unstable + Jeremy's pvops kernel on ibm x3550M2 server >> machine, on centos 5.4. >> Also I've already checked these instructions.. >> http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher >> Now, it seems like domain creation cannot find its virtual devices.. >> So I couldn't start my domains. I had these messages.. >> >> xenconsole: Could not read tty from store: No such file or directory >> Error: Device 0 (vif) could not be connected. Hotplug scripts not >> working. >> Error: Device 2049 (vbd) could not be connected. Path closed or >> removed during hotplug add: backend/vbd/5/2049 state: 1 >> >> /proc/xen has these files. >> >> -r--r--r-- 1 root root 0 Jun 8 09:57 capabilities >> -rw------- 1 root root 0 Jun 8 09:57 privcmd >> -rw------- 1 root root 0 Jun 8 09:57 xenbus >> -rw------- 1 root root 0 Jun 8 09:57 xsd_kva >> -rw------- 1 root root 0 Jun 8 09:57 xsd_port >> >> 'make install-tools' didn't install links in my /etc/rc directories, >> so I had to run manually xenconsoled, xenstored, and xend, but >> I found that I have no xenbus and xenwatch kernel threads. >> Is this why it can't finds virtual devices?? > > Is xenstored running? Do you have the evtchn and gntdev devices in > /dev/xen? > > J >