From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Min Lee <min.lee@gatech.edu>
Cc: Xen-devel@lists.xensource.com
Subject: Re: xen-unstable+pvops kernel, I don't have xenbus and xenwatch kernel thread.
Date: Wed, 09 Jun 2010 11:23:30 -0700 [thread overview]
Message-ID: <4C0FDC22.8030709@goop.org> (raw)
In-Reply-To: <4C0FADC8.20204@gatech.edu>
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
next prev parent reply other threads:[~2010-06-09 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 15:05 xen-unstable+pvops kernel, I don't have xenbus and xenwatch kernel thread Min Lee
2010-06-09 18:23 ` Jeremy Fitzhardinge [this message]
2010-06-09 18:37 ` Min Lee
2010-06-09 18:43 ` Jeremy Fitzhardinge
2010-06-09 18:51 ` Min Lee
2010-06-09 18:54 ` Jeremy Fitzhardinge
2010-06-10 14:25 ` Min Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C0FDC22.8030709@goop.org \
--to=jeremy@goop.org \
--cc=Xen-devel@lists.xensource.com \
--cc=min.lee@gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).