Xen users - Mar 2012 - xenconsole: Could not read tty from store: No such file or directory

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:

# /usr/sbin/xenconsoled
# xm console domU
xenconsole: Could not read tty from store: No such file or directory

Can anyone take a look at this issue?

Any suggestions will be appreciated,

-- 
Su Zhang
Ph.D Candidate
Computing and Information Sciences
Kansas State University


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

On Fri, 2012-03-16 at 23:45 +0000, Su Zhang wrote:
> 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:
You might need to restart your guests and/or toolstack after starting
xenconsole.

This should all have been taken care of by the initscripts shipped with
xen -- are you not using them for some reason?
> 
> # /usr/sbin/xenconsoled 
> # xm console domU
> xenconsole: Could not read tty from store: No such file or directory
> 
> Can anyone take a look at this issue?
> 
> Any suggestions will be appreciated,
> 
> -- 
> Su Zhang
> Ph.D Candidate
> Computing and Information Sciences
> Kansas State University

Thanks Gavin,

But it seems that the approach doesn''t work for my case. As you can see
from the following, after I killed the xenconsoled and restart it, the
issue is still there.

[root@XenTester su]# ps -eaf | grep xencon
root      2898     1  0 12:39 ?        00:00:00 xenconsoled
--pid-file=/var/run/xenconsoled.pid
root     17101 30154  0 21:29 pts/1    00:00:00 grep xencon
[root@XenTester su]# kill -9 2898
[root@XenTester su]# xenconsoled restart
[root@XenTester su]# xm list
Name                                        ID   Mem VCPUs      State
Time(s)
Domain-0                                     0  2806     2     r-----
3320.7
f13                                          5   768     1     -b----
11.6
[root@XenTester su]# xm console f13
xenconsole: Could not read tty from store: No such file or directory


Any comments will be appreciated,

Thanks again,

On Fri, Mar 16, 2012 at 7:01 PM, Gavin Jones <gjones@where2getit.com>
wrote:
> Hi,
>
> This happens to me often, usually right after booting dom0.  Have you
> checked to see if xenconsoled was already running (ps -eaf | grep xeoncon)?
>  If so, give it a kill -9, and restart. I usually start mine with a pid
> file, eg /usr/sbin/xenconsoled --pid-file=/var/run/xenconsoled.pid .  After
> this, you should be able to connect to the domU console by "xm console
> <id>".
>
> Does this work for you?
>
> GWJ
>
> On Fri, Mar 16, 2012 at 6:45 PM, Su Zhang <westlifezs@gmail.com>
wrote:
>
>> 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:
>>
>> # /usr/sbin/xenconsoled
>> # xm console domU
>> xenconsole: Could not read tty from store: No such file or directory
>>
>> Can anyone take a look at this issue?
>>
>> Any suggestions will be appreciated,
>>
>> --
>> Su Zhang
>> Ph.D Candidate
>> Computing and Information Sciences
>> Kansas State University
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xen.org
>> http://lists.xen.org/xen-users
>>
>
>

-- 
Su Zhang
Ph.D Candidate
Computing and Information Sciences
Kansas State University


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

On Sat, Mar 17, 2012 at 3:24 AM, Ian Campbell
<Ian.Campbell@citrix.com>wrote:
> On Fri, 2012-03-16 at 23:45 +0000, Su Zhang wrote:
> > 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:
>
> You might need to restart your guests and/or toolstack after starting
> xenconsole.
>
> This should all have been taken care of by the initscripts shipped with
> xen -- are you not using them for some reason?
>
>
Ian,

   Do initscripts here refer to the xen-related scripts under /etc/init.d/ ?
   Like xencomms?
   I''ve actually used xencomms and xend, also I reinstalled the domU
(f13
here).
   However, the issue is still there.
  Could you please take a look at the following running script and see what
is the problem here?

  [root@XenTester su]# /etc/init.d/xencommons start
Starting xenstored...
Setting domain 0 name...
Starting xenconsoled...
[root@XenTester su]# /etc/init.d/xend start
RTNETLINK answers: Device or resource busy
[root@XenTester su]# /etc/init.d/xend start
[root@XenTester su]# xm list
Name                                        ID   Mem VCPUs      State
Time(s)
Domain-0                                     0  3328     2     r-----
122.2
f13                                              768     1
0.0
[root@XenTester su]# xm destroy f13
[root@XenTester su]# xm list
Name                                        ID   Mem VCPUs      State
Time(s)
Domain-0                                     0  3328     2     r-----
137.9
f13                                              768     1
0.0
[root@XenTester su]# xm delete f13
[root@XenTester su]# xm list
Name                                        ID   Mem VCPUs      State
Time(s)
Domain-0                                     0  3328     2     r-----
138.3
[root@XenTester su]# virt-install -l
http://mirror.centos.org/centos/5/os/i386/ -p -n f13 -r 768 --vcpus=1
--disk=/srv/xen/mailserver.img --graphics vnc,listen=0.0.0.0,port=5901
--noautoconsole

Starting install...
Retrieving file
.treeinfo...
|  826 B     00:00 ...
Retrieving file
vmlinuz...
| 4.4 MB     00:02 ...
Retrieving file
initrd.img...
|  22 MB     00:08 ...
Creating
domain...
|    0 B     00:01
Domain installation still in progress. You can reconnect to
the console to complete the installation process.
[root@XenTester su]# xm list
Name                                        ID   Mem VCPUs      State
Time(s)
Domain-0                                     0  3328     2     r-----
146.2
f13                                          1   768     1     -b----
0.5
[root@XenTester su]# xm console f13
xenconsole: Could not read tty from store: No such file or directory


Thanks,
>
> > # /usr/sbin/xenconsoled
> > # xm console domU
> > xenconsole: Could not read tty from store: No such file or directory
> >
> > Can anyone take a look at this issue?
> >
> > Any suggestions will be appreciated,
> >
> > --
> > Su Zhang
> > Ph.D Candidate
> > Computing and Information Sciences
> > Kansas State University
>
>
>

-- 
Su Zhang
Ph.D Candidate
Computing and Information Sciences
Kansas State University


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

On Sat, 2012-03-17 at 16:30 +0000, Su Zhang wrote:
> 
> 
> On Sat, Mar 17, 2012 at 3:24 AM, Ian Campbell
> <Ian.Campbell@citrix.com> wrote:
>         On Fri, 2012-03-16 at 23:45 +0000, Su Zhang wrote:
>         > 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:
>         
>         
>         You might need to restart your guests and/or toolstack after
>         starting
>         xenconsole.
>         
>         This should all have been taken care of by the initscripts
>         shipped with
>         xen -- are you not using them for some reason?
>         
>         
> 
> Ian,
> 
>    Do initscripts here refer to the xen-related scripts
> under /etc/init.d/ ?
>    Like xencomms?
xencommons, yes.
>  [...]
> [root@XenTester su]# virt-install -l
> http://mirror.centos.org/centos/5/os/i386/ -p -n f13 -r 768 --vcpus=1
> --disk=/srv/xen/mailserver.img --graphics vnc,listen=0.0.0.0,port=5901
> --noautoconsole
I''m not at all familiar with virt-install or Fedora but given this
domain is to be called "f13" I would have expected a Fedora mirror to
be
listed rather than the CentOS 5 mirror. Is this normal?

Do you know if this command will create a PV or an HVM guest?

If this is an HVM domain then it is possible that it simply doesn''t
have
a text console which you can connect to with xl console. The "Could not
read tty from store" message is often indicative of this.

It appears you have configured VNC for this domain, have you tried
connecting a vncviewer to port 5901 on the host? e.g. vncviewer
localhost:1 or localhost::5091 (check the vncviewer manpage, I''m not
sure of the syntax). Perhaps virt-* includes a command to do this for
you automatically?

If you want a text console from an HVM guest then you can do the
virt-install equivalent of adding
	series = ''pty''
to your guest configuration. I''m afraid I don''t know how to
actually do
that with virt-install though.

If this is a PV guest then I have no idea what might be wrong.

Ian.

On Mon, Mar 19, 2012 at 3:41 AM, Ian Campbell
<Ian.Campbell@citrix.com>wrote:
> On Sat, 2012-03-17 at 16:30 +0000, Su Zhang wrote:
> >
> >
> > On Sat, Mar 17, 2012 at 3:24 AM, Ian Campbell
> > <Ian.Campbell@citrix.com> wrote:
> >         On Fri, 2012-03-16 at 23:45 +0000, Su Zhang wrote:
> >         > 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:
> >
> >
> >         You might need to restart your guests and/or toolstack after
> >         starting
> >         xenconsole.
> >
> >         This should all have been taken care of by the initscripts
> >         shipped with
> >         xen -- are you not using them for some reason?
> >
> >
> >
> > Ian,
> >
> >    Do initscripts here refer to the xen-related scripts
> > under /etc/init.d/ ?
> >    Like xencomms?
>
> xencommons, yes.
>
> >  [...]
>
> > [root@XenTester su]# virt-install -l
> > http://mirror.centos.org/centos/5/os/i386/ -p -n f13 -r 768 --vcpus=1
> > --disk=/srv/xen/mailserver.img --graphics vnc,listen=0.0.0.0,port=5901
> > --noautoconsole
>
> I''m not at all familiar with virt-install or Fedora but given this
> domain is to be called "f13" I would have expected a Fedora
mirror to be
> listed rather than the CentOS 5 mirror. Is this normal?
>
> Do you know if this command will create a PV or an HVM guest?
>
> If this is an HVM domain then it is possible that it simply
doesn''t have
> a text console which you can connect to with xl console. The "Could
not
> read tty from store" message is often indicative of this.
>
> It appears you have configured VNC for this domain, have you tried
> connecting a vncviewer to port 5901 on the host? e.g. vncviewer
> localhost:1 or localhost::5091 (check the vncviewer manpage, I''m
not
> sure of the syntax). Perhaps virt-* includes a command to do this for
> you automatically?
>
> If you want a text console from an HVM guest then you can do the
> virt-install equivalent of adding
>        series = ''pty''
> to your guest configuration. I''m afraid I don''t know how
to actually do
> that with virt-install though.
>
> If this is a PV guest then I have no idea what might be wrong.
>
> Ian.
>
> Thanks Ian, I am actually installing a PV DomU here. Do you mean that it
is better for Dom0 and DomU using the same type OS? I am a newbie to Xen.
What I want to do right now is to install a usable domU ASAP. However, I
encountered different errors by using different approaches. Do you know
which way is the easiest way to install a domU system?




-- 
Su Zhang
Ph.D Candidate
Computing and Information Sciences
Kansas State University


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

On Mon, 2012-03-19 at 16:39 +0000, Su Zhang wrote:
>         
> Thanks Ian, I am actually installing a PV DomU here. Do you mean that
> it is better for Dom0 and DomU using the same type OS? 
Not at all, you should be free to mix and match. My point was that you
may need slightly different configuration for a PV guest vs an HVM one.
> I am a newbie to Xen. What I want to do right now is to install a
> usable domU ASAP. However, I encountered different errors by using
> different approaches. Do you know which way is the easiest way to
> install a domU system?
The approach you are taking should be easy, I''m at a loss to explain
why
it doesn''t work for you.

Did you try connecting to the VNC as I suggested?

Have you looked in /var/log/xen to see if there are any interesting
messages under there?

What version of Xen are you running and where did you get it from (e.g.
self-built vs. packages)? If you are just interested in getting a domain
up and running ASAP then I would strongly suggest you use the Xen
packages supplied by your distribution rather than building them
yourself. I''m not sure which distro you are running though.

Ian.

On Mon, Mar 19, 2012 at 11:53 AM, Ian Campbell
<Ian.Campbell@citrix.com>wrote:
> On Mon, 2012-03-19 at 16:39 +0000, Su Zhang wrote:
>
> >
> > Thanks Ian, I am actually installing a PV DomU here. Do you mean that
> > it is better for Dom0 and DomU using the same type OS?
>
> Not at all, you should be free to mix and match. My point was that you
> may need slightly different configuration for a PV guest vs an HVM one.
>
> > I am a newbie to Xen. What I want to do right now is to install a
> > usable domU ASAP. However, I encountered different errors by using
> > different approaches. Do you know which way is the easiest way to
> > install a domU system?
>
> The approach you are taking should be easy, I''m at a loss to
explain why
> it doesn''t work for you.
>
> Did you try connecting to the VNC as I suggested?
>
> I tried to connect to VNC, but the connection cannot be established, here
is the running script:

[su@XenTester xen]$ vncviewer localhost:5901

TigerVNC Viewer for X version 1.0.90 - built Dec  8 2011 01:41:17
Copyright (C) 2002-2005 RealVNC Ltd.
Copyright (C) 2000-2006 TightVNC Group
Copyright (C) 2004-2009 Peter Astrand for Cendio AB
See http://www.tigervnc.org for information on TigerVNC.

Mon Mar 19 12:36:16 2012
 main:        unable connect to socket: Connection refused (111)
[su@XenTester xen]$

Is there a walk-around to the issue?
> Have you looked in /var/log/xen to see if there are any interesting
> messages under there?
>
After I read the logs (qemu-de-*.log), I found all of them include several
"common" errors:

xs_read(/local/domain/0/
device-model/3/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error.
/vm/a11e9c05-7bed-f7cd-e0e7-00506415b739/vncpasswd.
Log-dirty: no command yet.
xen be core: xen be core: can''t open gnttab device
can''t open gnttab device

Could you tell what is happening here?


>
> What version of Xen are you running and where did you get it from (e.g.
> self-built vs. packages)? If you are just interested in getting a domain
> up and running ASAP then I would strongly suggest you use the Xen
> packages supplied by your distribution rather than building them
> yourself. I''m not sure which distro you are running though.
>
> Ian.
>

I am running Xen 4.1.2 and built it from source. Indeed I need a runnable
guest ASAP but we want to run it on a built-from-source Xen because we want
to modify Xen source code a bit later. By the way, I am running on CentOS
6.2


Thanks,
-- 
Su Zhang
Ph.D Candidate
Computing and Information Sciences
Kansas State University


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Hallo,
if it is a pv then look if the directory /var/log/xen/console exists. If some
logging options in /etc/default/xen* are enabled xenconsoled does not start on
boot. Because it could not write to /var/log/xen/console/hypervisor.log. The
make install does not create the missing directory (4.1.2) .
I run in this problem today.
I hope the above helps you.

Andreas
--



Ian Campbell <Ian.Campbell@citrix.com> schrieb:

On Sat, 2012-03-17 at 16:30 +0000, Su Zhang wrote:
> 
> 
> On Sat, Mar 17, 2012 at 3:24 AM, Ian Campbell
> <Ian.Campbell@citrix.com> wrote:
> On Fri, 2012-03-16 at 23:45 +0000, Su Zhang wrote:
> > 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:
> 
> 
> You might need to restart your guests and/or toolstack after
> starting
> xenconsole.
> 
> This should all have been taken care of by the initscripts
> shipped with
> xen -- are you not using them for some reason?
> 
> 
> 
> Ian,
> 
> Do initscripts here refer to the xen-related scripts
> under /etc/init.d/ ?
> Like xencomms?
xencommons, yes.
> [...]
> [root@XenTester su]# virt-install -l
> http://mirror.centos.org/centos/5/os/i386/ -p -n f13 -r 768 --vcpus=1
> --disk=/srv/xen/mailserver.img --graphics vnc,listen=0.0.0.0,port=5901
> --noautoconsole
I''m not at all familiar with virt-install or Fedora but given this
domain is to be called "f13" I would have expected a Fedora mirror to
be
listed rather than the CentOS 5 mirror. Is this normal?

Do you know if this command will create a PV or an HVM guest?

If this is an HVM domain then it is possible that it simply doesn''t
have
a text console which you can connect to with xl console. The "Could not
read tty from store" message is often indicative of this.

It appears you have configured VNC for this domain, have you tried
connecting a vncviewer to port 5901 on the host? e.g. vncviewer
localhost:1 or localhost::5091 (check the vncviewer manpage, I''m not
sure of the syntax). Perhaps virt-* includes a command to do this for
you automatically?

If you want a text console from an HVM guest then you can do the
virt-install equivalent of adding
	series = ''pty''
to your guest configuration. I''m afraid I don''t know how to
actually do
that with virt-install though.

If this is a PV guest then I have no idea what might be wrong.

Ian.


_____________________________________________

Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

On Mon, 2012-03-19 at 17:49 +0000, Su Zhang wrote:
> 
> 
> On Mon, Mar 19, 2012 at 11:53 AM, Ian Campbell
> <Ian.Campbell@citrix.com> wrote:
>         On Mon, 2012-03-19 at 16:39 +0000, Su Zhang wrote:
>         
>         >
>         > Thanks Ian, I am actually installing a PV DomU here. Do you
>         mean that
>         > it is better for Dom0 and DomU using the same type OS?
>         
>         
>         Not at all, you should be free to mix and match. My point was
>         that you
>         may need slightly different configuration for a PV guest vs an
>         HVM one.
>         
>         > I am a newbie to Xen. What I want to do right now is to
>         install a
>         > usable domU ASAP. However, I encountered different errors by
>         using
>         > different approaches. Do you know which way is the easiest
>         way to
>         > install a domU system?
>         
>         
>         The approach you are taking should be easy, I''m at a loss
to
>         explain why
>         it doesn''t work for you.
>         
>         Did you try connecting to the VNC as I suggested?
>         
> I tried to connect to VNC, but the connection cannot be established,
> here is the running script:
> 
> [su@XenTester xen]$ vncviewer localhost:5901
I think that VNC ports are offset by 5900 already so you would need
"vncviewer localhost:1". You can override that offsetting (i.e.
provide
a literal port number) by using ::, so the alternative is
localhost::5900.

[...]
>         Have you looked in /var/log/xen to see if there are any
>         interesting
>         messages under there?
> 
> After I read the logs (qemu-de-*.log), I found all of them include
> several "common" errors:
> 
> xs_read(/local/domain/0/
> device-model/3/xen_extended_power_mgmt): read error
> xs_read(): vncpasswd get
> error. /vm/a11e9c05-7bed-f7cd-e0e7-00506415b739/vncpasswd.
> Log-dirty: no command yet.
> xen be core: xen be core: can''t open gnttab device
> can''t open gnttab device
This one might mean you need to "modprobe xen-gntdev". Which may help.
What modules do you have loaded (e.g. the output of lsmod)

[...]
> I am running Xen 4.1.2 and built it from source. Indeed I need a
> runnable guest ASAP but we want to run it on a built-from-source Xen
> because we want to modify Xen source code a bit later. By the way, I
> am running on CentOS 6.2 
OK.

Getting something running with "known good" packages might have been a
useful first step before attempting to build something yourself but now
that you have taken that leap we may as well continue to try and figure
out what is going on.

What is your dom0 kernel?

Ian.

On Mon, Mar 19, 2012 at 1:56 PM, Andreas Greve
<andreas.greve@a-greve.de>wrote:
> Hallo,
> if it is a pv then look if the directory /var/log/xen/console exists. If
> some logging options in /etc/default/xen* are enabled xenconsoled does not
> start on boot. Because it could not write to
> /var/log/xen/console/hypervisor.log. The make install does not create the
> missing directory (4.1.2) .
> I run in this problem today.
> I hope the above helps you.
>
> Andreas
> --
>
>   Hi Andreas,
   Thanks for your reply. Interestingly, the file /var/log/xen/console
doesn''t exist on my machine. There is no any file or directory called
/etc/default/xen*. So how did you address the similar problem? Could you
please be a bit specific? Do I need to generate these files manually? Or
How can I generate these files automatically? Is this issue caused by these
missing files?

Thanks,
>
>
> Ian Campbell <Ian.Campbell@citrix.com> schrieb:
>>
>> On Sat, 2012-03-17 at 16:30 +0000, Su Zhang wrote:
>> >
>> >
>> > On Sat, Mar 17, 2012 at 3:24 AM, Ian Campbell
>> > <Ian.Campbell@citrix.com> wrote:
>> >         On Fri, 2012-03-16 at 23:45 +0000, Su Zhang wrote:
>> >         > 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
>> &gt!
>>  ;
>>  there. Please
>>
>> >         > see:
>> >
>> >
>> >         You might need to restart your guests and/or toolstack
after
>> >         starting
>> >         xenconsole.
>> >
>> >         This should all have been taken care of by the initscripts
>> >         shipped with
>> >         xen -- are you not using them for some reason?
>> >
>> >
>> >
>> > Ian,
>> >
>> >    Do initscripts here refer to the xen-related scripts
>> > under /etc/init.d/ ?
>> >    Like xencomms?
>>
>> xencommons, yes.
>>
>> >  [...]
>>
>> > [root@XenTester su]# virt-install -l
>> > http://mirror.centos.org/centos/5/os/i386/ -p -n f13 -r 768
--vcpus=1
>> > --disk=/srv/xen/mailserver.img --graphics
vnc,listen=0.0.0.0,port=5901
>> > --noautoconsole
>>
>> I''m not at all familia!
>>  r with
>> virt-install or Fedora but given this
>>
>> domain is to be called "f13" I would have expected a Fedora
mirror to be
>> listed rather than the CentOS 5 mirror. Is this normal?
>>
>> Do you know if this command will create a PV or an HVM guest?
>>
>> If this is an HVM domain then it is possible that it simply
doesn''t have
>> a text console which you can connect to with xl console. The
"Could not
>> read tty from store" message is often indicative of this.
>>
>> It appears you have configured VNC for this domain, have you tried
>> connecting a vncviewer to port 5901 on the host? e.g. vncviewer
>> localhost:1 or localhost::5091 (check the vncviewer manpage,
I''m not
>> sure of the syntax). Perhaps virt-* includes a command to do this for
>> you automatically?
>>
>> If you want a text console from an HVM guest then you can do the
>> virt-install equivalent of adding
>> 	series = ''pty''
>> to your guest configuration. I''m afraid I don''t know
h!
>>  ow to
>> actually do
>>
>> that with virt-install though.
>>
>> If this is a PV guest then I have no idea what might be wrong.
>>
>> Ian.
>>
>>
>> ------------------------------
>>
>> Xen-users mailing list
>> Xen-users@lists.xen.org
>> http://lists.xen.org/xen-users
>>
>>

-- 
Su Zhang
Ph.D Candidate
Computing and Information Sciences
Kansas State University


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

On Mon, Mar 19, 2012 at 2:54 PM, Ian Campbell
<Ian.Campbell@citrix.com>wrote:
> On Mon, 2012-03-19 at 17:49 +0000, Su Zhang wrote:
> >
> >
> > On Mon, Mar 19, 2012 at 11:53 AM, Ian Campbell
> > <Ian.Campbell@citrix.com> wrote:
> >         On Mon, 2012-03-19 at 16:39 +0000, Su Zhang wrote:
> >
> >         >
> >         > Thanks Ian, I am actually installing a PV DomU here. Do
you
> >         mean that
> >         > it is better for Dom0 and DomU using the same type OS?
> >
> >
> >         Not at all, you should be free to mix and match. My point was
> >         that you
> >         may need slightly different configuration for a PV guest vs an
> >         HVM one.
> >
> >         > I am a newbie to Xen. What I want to do right now is to
> >         install a
> >         > usable domU ASAP. However, I encountered different errors
by
> >         using
> >         > different approaches. Do you know which way is the
easiest
> >         way to
> >         > install a domU system?
> >
> >
> >         The approach you are taking should be easy, I''m at a
loss to
> >         explain why
> >         it doesn''t work for you.
> >
> >         Did you try connecting to the VNC as I suggested?
> >
> > I tried to connect to VNC, but the connection cannot be established,
> > here is the running script:
> >
> > [su@XenTester xen]$ vncviewer localhost:5901
>
> I think that VNC ports are offset by 5900 already so you would need
> "vncviewer localhost:1". You can override that offsetting (i.e.
provide
> a literal port number) by using ::, so the alternative is
> localhost::5900.
>
> Ian,
I tried both command line, but neither works, here is the process:

[su@XenTester xen]$ vncviewer localhost:1

TigerVNC Viewer for X version 1.0.90 - built Dec  8 2011 01:41:17
Copyright (C) 2002-2005 RealVNC Ltd.
Copyright (C) 2000-2006 TightVNC Group
Copyright (C) 2004-2009 Peter Astrand for Cendio AB
See http://www.tigervnc.org for information on TigerVNC.

Mon Mar 19 20:46:21 2012
 main:        unable connect to socket: Connection refused (111)
[su@XenTester xen]$ vncviewer localhost::5900

TigerVNC Viewer for X version 1.0.90 - built Dec  8 2011 01:41:17
Copyright (C) 2002-2005 RealVNC Ltd.
Copyright (C) 2000-2006 TightVNC Group
Copyright (C) 2004-2009 Peter Astrand for Cendio AB
See http://www.tigervnc.org for information on TigerVNC.

Mon Mar 19 20:47:00 2012
 main:        unable connect to socket: Connection refused (111)

> [...]
> >         Have you looked in /var/log/xen to see if there are any
> >         interesting
> >         messages under there?
> >
> > After I read the logs (qemu-de-*.log), I found all of them include
> > several "common" errors:
> >
> > xs_read(/local/domain/0/
> > device-model/3/xen_extended_power_mgmt): read error
> > xs_read(): vncpasswd get
> > error. /vm/a11e9c05-7bed-f7cd-e0e7-00506415b739/vncpasswd.
> > Log-dirty: no command yet.
> > xen be core: xen be core: can''t open gnttab device
> > can''t open gnttab device
>
> This one might mean you need to "modprobe xen-gntdev". Which may
help.
> What modules do you have loaded (e.g. the output of lsmod)
>
> When I run '''', nothing happened:
[root@XenTester xen]# modprobe xen-gntdev
[root@XenTester xen]#

Does it mean I''ve loaded necessary modules?

Following is  the output of lsmod:

[root@XenTester xen]# lsmod
Module                  Size  Used by
xen_gntdev             10232  0
ebtable_nat             1999  0
ebtables               27394  1 ebtable_nat
ipt_MASQUERADE          2328  3
iptable_nat             5103  1
nf_nat                 21350  2 ipt_MASQUERADE,iptable_nat
xt_CHECKSUM             1261  1
iptable_mangle          1727  1
bridge                 84951  0
stp                     2131  1 bridge
llc                     5560  2 bridge,stp
fuse                   71295  0
autofs4                32331  3
sunrpc                235886  1
ipt_REJECT              2344  4
nf_conntrack_ipv4       9136  6 iptable_nat,nf_nat
nf_defrag_ipv4          1473  1 nf_conntrack_ipv4
iptable_filter          1714  1
ip_tables              20023  3 iptable_nat,iptable_mangle,iptable_filter
ip6t_REJECT             4502  2
nf_conntrack_ipv6       8239  2
nf_defrag_ipv6         10327  1 nf_conntrack_ipv6
xt_state                1322  5
nf_conntrack           79260  6
ipt_MASQUERADE,iptable_nat,nf_nat,nf_conntrack_ipv4,nf_conntrack_ipv6,xt_state
ip6table_filter         1687  1
ip6_tables             20281  1 ip6table_filter
ipv6                  327216  40
bridge,ip6t_REJECT,nf_conntrack_ipv6,nf_defrag_ipv6
vhost_net              28861  0
macvtap                 9459  1 vhost_net
macvlan                 9827  1 macvtap
tun                    16357  1 vhost_net
uinput                  8401  0
r592                   12817  0
memstick               10517  1 r592
sg                     30105  0
thinkpad_acpi          73526  0
wmi                    10412  0
video                  12975  0
microcode             111929  0
pcspkr                  1926  0
arc4                    1433  2
i2c_i801               10328  0
iTCO_wdt               12450  1
iTCO_vendor_support     2982  1 iTCO_wdt
iwlagn                207520  0
mac80211              213480  1 iwlagn
cfg80211              181481  2 iwlagn,mac80211
rfkill                 18959  3 thinkpad_acpi,cfg80211
snd_hda_codec_conexant    51549  1
snd_hda_intel          24957  2
snd_hda_codec          92970  2 snd_hda_codec_conexant,snd_hda_intel
snd_hwdep               6692  1 snd_hda_codec
snd_seq                55873  0
snd_seq_device          6496  1 snd_seq
snd_pcm                85930  2 snd_hda_intel,snd_hda_codec
snd_timer              22542  2 snd_seq,snd_pcm
snd                    70269  13
thinkpad_acpi,snd_hda_codec_conexant,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer
soundcore               7604  1 snd
snd_page_alloc          8428  2 snd_hda_intel,snd_pcm
e1000e                199480  0
ext4                  414435  3
mbcache                 7222  1 ext4
jbd2                   80642  1 ext4
sr_mod                 15692  0
cdrom                  41191  1 sr_mod
sd_mod                 37218  3
crc_t10dif              1499  1 sd_mod
sdhci_pci               9889  0
sdhci                  27230  1 sdhci_pci
mmc_core               96131  1 sdhci
firewire_ohci          31340  0
firewire_core          58296  1 firewire_ohci
crc_itu_t               1675  1 firewire_core
yenta_socket           34666  0
pata_acpi               3691  0
ata_generic             3827  0
ata_piix               23224  2
radeon               1010971  2
ttm                    66780  1 radeon
drm_kms_helper         33063  1 radeon
drm                   226612  4 radeon,ttm,drm_kms_helper
i2c_algo_bit            5928  1 radeon
i2c_core               30420  5
i2c_i801,radeon,drm_kms_helper,drm,i2c_algo_bit
dm_mirror              14316  0
dm_region_hash         10843  1 dm_mirror
dm_log                  9734  2 dm_mirror,dm_region_hash
dm_mod                 79082  13 dm_mirror,dm_log
[root@XenTester xen]#

Could you please take a look and see if necessary modules are loaded?
> [...]
> > I am running Xen 4.1.2 and built it from source. Indeed I need a
> > runnable guest ASAP but we want to run it on a built-from-source Xen
> > because we want to modify Xen source code a bit later. By the way, I
> > am running on CentOS 6.2
>
> OK.
>
> Getting something running with "known good" packages might have
been a
> useful first step before attempting to build something yourself but now
> that you have taken that leap we may as well continue to try and figure
> out what is going on.
>
> What is your dom0 kernel?
>
> Following is dom0 kernel information:
[root@XenTester xen]# uname -a
Linux XenTester 3.1.0-rc9+ #1 SMP Mon Mar 12 18:18:34 CDT 2012 x86_64
x86_64 x86_64 GNU/Linux
[root@XenTester xen]#

Is this dom0 kernel suitable to xen?

Thanks,
> Ian.
>
>
> here is

-- 
Su Zhang
Ph.D Candidate
Computing and Information Sciences
Kansas State University


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

On Tue, 2012-03-20 at 01:56 +0000, Su Zhang wrote:
>         
>         
>         This one might mean you need to "modprobe xen-gntdev".
Which
>         may help.
>         What modules do you have loaded (e.g. the output of lsmod)
>         
> When I run '''', nothing happened:
> 
> [root@XenTester xen]# modprobe xen-gntdev
> [root@XenTester xen]# 
> 
> Does it mean I''ve loaded necessary modules? 
Yes, modprobe is silent on success.
> Following is  the output of lsmod:
> 
> [root@XenTester xen]# lsmod
> Module                  Size  Used by
> xen_gntdev             10232  0 
[...]
> [root@XenTester xen]# 
> 
> Could you please take a look and see if necessary modules are
> loaded?  
There don''t seem to be many Xen modules there. This may be OK if those
options are =y in your kernel configuration or it may be a problem if
they are =m.

Can you attach your kernel config please. Also the output of
	find /lib/modules/$(uname -r) -name xen\*.ko
might be interesting.
> [...]
> Following is dom0 kernel information:
> 
> [root@XenTester xen]# uname -a
> Linux XenTester 3.1.0-rc9+ #1 SMP Mon Mar 12 18:18:34 CDT 2012 x86_64
> x86_64 x86_64 GNU/Linux
> Is this dom0 kernel suitable to xen?
It should be fine. What exact changeset is it?

Ian.

On Tue, Mar 20, 2012 at 2:10 AM, Ian Campbell
<Ian.Campbell@citrix.com>wrote:
> On Tue, 2012-03-20 at 01:56 +0000, Su Zhang wrote:
>
> >
> >
> >         This one might mean you need to "modprobe
xen-gntdev". Which
> >         may help.
> >         What modules do you have loaded (e.g. the output of lsmod)
> >
> > When I run '''', nothing happened:
> >
> > [root@XenTester xen]# modprobe xen-gntdev
> > [root@XenTester xen]#
> >
> > Does it mean I''ve loaded necessary modules?
>
> Yes, modprobe is silent on success.
>
> > Following is  the output of lsmod:
> >
> > [root@XenTester xen]# lsmod
> > Module                  Size  Used by
> > xen_gntdev             10232  0
> [...]
> > [root@XenTester xen]#
> >
> > Could you please take a look and see if necessary modules are
> > loaded?
>
> There don''t seem to be many Xen modules there. This may be OK if
those
> options are =y in your kernel configuration or it may be a problem if
> they are =m.
>
> Can you attach your kernel config please.
I''ve attached the kernel config file I used to build this kernel.

> Also the output of
>        find /lib/modules/$(uname -r) -name xen\*.ko
> might be interesting.
>
Here is the output:

[root@XenTester su]#  find /lib/modules/$(uname -r) -name xen\*.ko
/lib/modules/3.1.0-rc9+/kernel/drivers/net/xen-netfront.ko
/lib/modules/3.1.0-rc9+/kernel/drivers/xen/xen-gntdev.ko
/lib/modules/3.1.0-rc9+/kernel/drivers/xen/xen-gntalloc.ko
[root@XenTester su]#

Are all necessary modules included?

>
> > [...]
> > Following is dom0 kernel information:
> >
> > [root@XenTester xen]# uname -a
> > Linux XenTester 3.1.0-rc9+ #1 SMP Mon Mar 12 18:18:34 CDT 2012 x86_64
> > x86_64 x86_64 GNU/Linux
> > Is this dom0 kernel suitable to xen?
>
> It should be fine. What exact changeset is it?
>
Could  you please let me know how can I find out what exact changeset it
is? Sorry I''m not quite familiar with the Linux kernel structure.

Thanks,
>
> Ian.
>
>
>
>

-- 
Su Zhang
Ph.D Candidate
Computing and Information Sciences
Kansas State University



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

On Tue, 2012-03-20 at 15:03 +0000, Su Zhang wrote:
> 
> 
> On Tue, Mar 20, 2012 at 2:10 AM, Ian Campbell
> <Ian.Campbell@citrix.com> wrote:
>         On Tue, 2012-03-20 at 01:56 +0000, Su Zhang wrote:
>         
>         >
>         >
>         >         This one might mean you need to "modprobe
>         xen-gntdev". Which
>         >         may help.
>         >         What modules do you have loaded (e.g. the output of
>         lsmod)
>         >
>         > When I run '''', nothing happened:
>         >
>         > [root@XenTester xen]# modprobe xen-gntdev
>         > [root@XenTester xen]#
>         >
>         > Does it mean I''ve loaded necessary modules?
>         
>         
>         Yes, modprobe is silent on success.
>         
>         > Following is  the output of lsmod:
>         >
>         > [root@XenTester xen]# lsmod
>         > Module                  Size  Used by
>         > xen_gntdev             10232  0
>         
>         [...]
>         > [root@XenTester xen]#
>         >
>         > Could you please take a look and see if necessary modules
>         are
>         > loaded?
>         
>         
>         There don''t seem to be many Xen modules there. This may be
OK
>         if those
>         options are =y in your kernel configuration or it may be a
>         problem if
>         they are =m.
>         
>         Can you attach your kernel config please. 
> I''ve attached the kernel config file I used to build this kernel.
>  
>         Also the output of
>                find /lib/modules/$(uname -r) -name xen\*.ko
>         might be interesting.
> 
> Here is the output:
> 
> [root@XenTester su]#  find /lib/modules/$(uname -r) -name xen\*.ko
> /lib/modules/3.1.0-rc9+/kernel/drivers/net/xen-netfront.ko
> /lib/modules/3.1.0-rc9+/kernel/drivers/xen/xen-gntdev.ko
> /lib/modules/3.1.0-rc9+/kernel/drivers/xen/xen-gntalloc.ko
> [root@XenTester su]# 
> 
> Are all necessary modules included? 
Of these only xen-gtndev is needed in dom0. Your config shows that
everything else which I would have expected has been built in.
>         
>         > [...]
>         > Following is dom0 kernel information:
>         >
>         > [root@XenTester xen]# uname -a
>         > Linux XenTester 3.1.0-rc9+ #1 SMP Mon Mar 12 18:18:34 CDT
>         2012 x86_64
>         > x86_64 x86_64 GNU/Linux
>         
>         > Is this dom0 kernel suitable to xen?
>         
>         
>         It should be fine. What exact changeset is it?
> 
> Could  you please let me know how can I find out what exact changeset
> it is? Sorry I''m not quite familiar with the Linux kernel
structure.
If you got it by cloning git then "git show" will include the
changeset
ID.

One other useful bit of information would be the output of
	xenstore-ls -fp
while the domain is (apparently) running and you cannot connect to the
console. Also "ps auxf" might be useful too.

Ian.

On Tue, Mar 20, 2012 at 10:07 AM, Ian Campbell
<Ian.Campbell@citrix.com>wrote:
> On Tue, 2012-03-20 at 15:03 +0000, Su Zhang wrote:
> >
> >
> > On Tue, Mar 20, 2012 at 2:10 AM, Ian Campbell
> > <Ian.Campbell@citrix.com> wrote:
> >         On Tue, 2012-03-20 at 01:56 +0000, Su Zhang wrote:
> >
> >         >
> >         >
> >         >         This one might mean you need to "modprobe
> >         xen-gntdev". Which
> >         >         may help.
> >         >         What modules do you have loaded (e.g. the output
of
> >         lsmod)
> >         >
> >         > When I run '''', nothing happened:
> >         >
> >         > [root@XenTester xen]# modprobe xen-gntdev
> >         > [root@XenTester xen]#
> >         >
> >         > Does it mean I''ve loaded necessary modules?
> >
> >
> >         Yes, modprobe is silent on success.
> >
> >         > Following is  the output of lsmod:
> >         >
> >         > [root@XenTester xen]# lsmod
> >         > Module                  Size  Used by
> >         > xen_gntdev             10232  0
> >
> >         [...]
> >         > [root@XenTester xen]#
> >         >
> >         > Could you please take a look and see if necessary modules
> >         are
> >         > loaded?
> >
> >
> >         There don''t seem to be many Xen modules there. This
may be OK
> >         if those
> >         options are =y in your kernel configuration or it may be a
> >         problem if
> >         they are =m.
> >
> >         Can you attach your kernel config please.
> > I''ve attached the kernel config file I used to build this
kernel.
> >
> >         Also the output of
> >                find /lib/modules/$(uname -r) -name xen\*.ko
> >         might be interesting.
> >
> > Here is the output:
> >
> > [root@XenTester su]#  find /lib/modules/$(uname -r) -name xen\*.ko
> > /lib/modules/3.1.0-rc9+/kernel/drivers/net/xen-netfront.ko
> > /lib/modules/3.1.0-rc9+/kernel/drivers/xen/xen-gntdev.ko
> > /lib/modules/3.1.0-rc9+/kernel/drivers/xen/xen-gntalloc.ko
> > [root@XenTester su]#
> >
> > Are all necessary modules included?
>
> Of these only xen-gtndev is needed in dom0. Your config shows that
> everything else which I would have expected has been built in.
>
> Thanks for your confirmation.
> >
> >         > [...]
> >         > Following is dom0 kernel information:
> >         >
> >         > [root@XenTester xen]# uname -a
> >         > Linux XenTester 3.1.0-rc9+ #1 SMP Mon Mar 12 18:18:34 CDT
> >         2012 x86_64
> >         > x86_64 x86_64 GNU/Linux
> >
> >         > Is this dom0 kernel suitable to xen?
> >
> >
> >         It should be fine. What exact changeset is it?
> >
> > Could  you please let me know how can I find out what exact changeset
> > it is? Sorry I''m not quite familiar with the Linux kernel
structure.
>
> If you got it by cloning git then "git show" will include the
changeset
> ID.
>
> Here is the output from git show:
[root@XenTester linux]# git show
commit 4c41042d1d4c29e596b31e2d14b26d2940fb24b4
Merge: e9308cf bf164c5
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Oct 15 08:29:09 2011 +1200

    Merge branch ''hwmon-for-linus'' of git://
git.kernel.org/pub/scm/linux/kernel/

    * ''hwmon-for-linus'' of git://
git.kernel.org/pub/scm/linux/kernel/git/groeck/
      hwmon: (w83627ehf) Properly report thermal diode sensors

(END)



> One other useful bit of information would be the output of
>        xenstore-ls -fp
>
I''ve attached the output of xenstore-ls -fp as it contains too many
lines.
Does it look okay?


> while the domain is (apparently) running and you cannot connect to the
> console. Also "ps auxf" might be useful too.
>
> In fact, the domU can never be run, it always under blocked.  Here is the
output of ps auxf:

[root@XenTester su]# ps auxf
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         2  0.0  0.0      0     0 ?        S    09:32   0:00 [kthreadd]
root         3  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[ksoftirqd/0]
root         6  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[migration/0]
root         7  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[watchdog/0]
root         8  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[migration/1]
root        10  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[ksoftirqd/1]
root        11  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[watchdog/1]
root        12  0.0  0.0      0     0 ?        S<   09:32   0:00  \_
[cpuset]
root        13  0.0  0.0      0     0 ?        S<   09:32   0:00  \_
[khelper]
root        14  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[kdevtmpfs]
root        15  0.0  0.0      0     0 ?        S<   09:32   0:00  \_ [netns]
root        16  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[xenwatch]
root        17  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[xenbus]
root        18  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[sync_supers]
root        19  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[bdi-default]
root        20  0.0  0.0      0     0 ?        S<   09:32   0:00  \_
[kintegrityd]
root        21  0.0  0.0      0     0 ?        S<   09:32   0:00  \_
[kblockd]
root        22  0.0  0.0      0     0 ?        S<   09:32   0:00  \_
[ata_sff]
root        23  0.0  0.0      0     0 ?        S    09:32   0:00  \_ [khubd]
root        24  0.0  0.0      0     0 ?        S<   09:32   0:00  \_ [md]
root        26  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[khungtaskd]
root        27  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[kswapd0]
root        28  0.0  0.0      0     0 ?        SN   09:32   0:00  \_ [ksmd]
root        29  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[fsnotify_mark]
root        30  0.0  0.0      0     0 ?        S<   09:32   0:00  \_
[crypto]
root        35  0.0  0.0      0     0 ?        S<   09:32   0:00  \_
[kthrotld]
root        38  0.0  0.0      0     0 ?        S<   09:32   0:00  \_
[xen_pciback_wor]
root        39  0.0  0.0      0     0 ?        S    09:32   0:00  \_ [khvcd]
root        40  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[netback/0]
root        41  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[netback/1]
root        42  0.0  0.0      0     0 ?        S<   09:32   0:00  \_
[kpsmoused]
root       112  0.0  0.0      0     0 ?        S<   09:32   0:00  \_
[ttm_swap]
root       274  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[scsi_eh_0]
root       275  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[scsi_eh_1]
root       287  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[pccardd]
root       290  0.0  0.0      0     0 ?        S<   09:32   0:00  \_
[firewire]
root       336  0.0  0.0      0     0 ?        S<   09:32   0:00  \_
[kdmflush]
root       338  0.0  0.0      0     0 ?        S<   09:32   0:00  \_
[kdmflush]
root       357  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[jbd2/dm-0-8]
root       358  0.0  0.0      0     0 ?        S<   09:32   0:00  \_
[ext4-dio-unwrit]
root       402  0.0  0.0      0     0 ?        S    09:32   0:00  \_
[kauditd]
root       696  0.0  0.0      0     0 ?        S<   09:33   0:00  \_
[hd-audio0]
root       733  0.0  0.0      0     0 ?        S<   09:33   0:00  \_
[cfg80211]
root       759  0.0  0.0      0     0 ?        S<   09:33   0:00  \_
[iwlagn]
root       887  0.0  0.0      0     0 ?        S<   09:33   0:00  \_
[ktpacpid]
root      1247  0.0  0.0      0     0 ?        S<   09:33   0:00  \_
[kmemstick]
root      1248  0.0  0.0      0     0 ?        S    09:33   0:00  \_
[r592_io]
root      1412  0.0  0.0      0     0 ?        S<   09:33   0:00  \_
[kdmflush]
root      1415  0.0  0.0      0     0 ?        S<   09:33   0:00  \_
[kdmflush]
root      1459  0.0  0.0      0     0 ?        S    09:33   0:00  \_
[jbd2/sda1-8]
root      1460  0.0  0.0      0     0 ?        S<   09:33   0:00  \_
[ext4-dio-unwrit]
root      1461  0.0  0.0      0     0 ?        S    09:33   0:00  \_
[jbd2/dm-2-8]
root      1462  0.0  0.0      0     0 ?        S<   09:33   0:00  \_
[ext4-dio-unwrit]
root      1766  0.0  0.0      0     0 ?        S    09:33   0:00  \_
[flush-253:0]
root      1767  0.0  0.0      0     0 ?        S    09:33   0:00  \_
[flush-253:2]
root      1852  0.0  0.0      0     0 ?        S<   09:33   0:00  \_
[rpciod]
root      3023  0.0  0.0      0     0 ?        S    09:42   0:00  \_
[kworker/u:1]
root      3244  0.0  0.0      0     0 ?        S    09:59   0:00  \_
[kworker/u:0]
root      3918  0.0  0.0      0     0 ?        S    10:10   0:00  \_
[kworker/1:1]
root      4119  0.0  0.0      0     0 ?        S    10:13   0:00  \_
[kworker/0:1]
root      4255  0.0  0.0      0     0 ?        S    10:23   0:00  \_
[kworker/1:2]
root      4445  0.0  0.0      0     0 ?        S    10:23   0:00  \_
[kworker/0:2]
root      4791  0.0  0.0      0     0 ?        S<   10:24   0:00  \_ [loop0]
root      4848  0.0  0.0      0     0 ?        S    10:28   0:00  \_
[kworker/0:0]
root      4869  0.0  0.0      0     0 ?        S    10:29   0:00  \_
[kworker/1:0]
root      4878  0.0  0.0      0     0 ?        S    10:30   0:00  \_
[kworker/u:2]
root         1  0.0  0.0  19380  1520 ?        Ss   09:32   0:00 /sbin/init
root       452  0.0  0.0  11776  1760 ?        S<s  09:32   0:00
/sbin/udevd -d
root      4722  0.0  0.0  11772  1972 ?        S<   10:24   0:00  \_
/sbin/udevd -d
root      4803  0.0  0.0  11772  1660 ?        S<   10:24   0:00  \_
/sbin/udevd -d
root      1712  0.0  0.0 248920  1236 ?        Sl   09:33   0:00
/sbin/rsyslogd -i /var/run/syslogd.pid -c 4
rpc       1749  0.0  0.0  19004   856 ?        Ss   09:33   0:00 rpcbind
dbus      1774  0.0  0.0  96160  2116 ?        Ssl  09:33   0:01
dbus-daemon --system
root      1785  0.0  0.2  95596  5420 ?        Ssl  09:33   0:00
NetworkManager --pid-file=/var/run/NetworkManager/NetworkManager.pid
root      4538  0.0  0.0   9152  1520 ?        S    10:24   0:00  \_
/sbin/dhclient -d -4 -sf /usr/libexec/nm-dhcp-client.action -pf
/var/run/dhclient-wlan0.pid -lf /var/lib/dhclient/dhclient-cda7e666-60a4-4
root      1789  0.0  0.1  55884  2452 ?        S    09:33   0:00
/usr/sbin/modem-manager
avahi     1797  0.0  0.0  27820  1540 ?        S    09:33   0:00
avahi-daemon: running [XenTester.local]
avahi     1798  0.0  0.0  27700   212 ?        Ss   09:33   0:00  \_
avahi-daemon: chroot helper
rpcuser   1817  0.0  0.0  23376  1324 ?        Ss   09:33   0:00 rpc.statd
root      1819  0.0  0.0  44744  1680 ?        Ss   09:33   0:00
/usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -B -u
-f /var/log/wpa_supplicant.log -P /var/run/wpa_supplicant.pid
root      1856  0.0  0.0  29488   420 ?        Ss   09:33   0:00 rpc.idmapd
root      1866  0.0  0.1 189304  3300 ?        Ss   09:33   0:00 cupsd -C
/etc/cups/cupsd.conf
root      1891  0.0  0.0   4112   604 ?        Ss   09:33   0:00
/usr/sbin/acpid
68        1900  0.0  0.2  26536  5232 ?        Ss   09:33   0:00 hald
root      1901  0.0  0.0  18140  1176 ?        S    09:33   0:00  \_
hald-runner
root      1933  0.0  0.0  20248  1076 ?        S    09:33   0:00      \_
/usr/libexec/hald-addon-generic-backlight
root      1940  0.0  0.0  20248   876 ?        S    09:33   0:00      \_
/usr/libexec/hald-addon-rfkill-killswitch
root      1950  0.0  0.0  20248   876 ?        S    09:33   0:00      \_
/usr/libexec/hald-addon-leds
root      1952  0.0  0.0  20256   884 ?        S    09:33   0:00      \_
hald-addon-input: Listening on /dev/input/event3 /dev/input/event9
/dev/input/event8 /dev/input/event0 /dev/input/event1 /dev/input/ev
68        1956  0.0  0.0  17840  1016 ?        S    09:33   0:00      \_
hald-addon-acpi: listening on acpid socket /var/run/acpid.socket
root      1976  0.0  0.0 381596  1644 ?        Ssl  09:33   0:00 automount
--pid-file /var/run/autofs.pid
root      2000  0.0  0.0  64076  1068 ?        Ss   09:33   0:00
/usr/sbin/sshd
ntp       2008  0.0  0.0  30188  1580 ?        Ss   09:33   0:00 ntpd -u
ntp:ntp -p /var/run/ntpd.pid -g
root      2089  0.0  0.1  78696  3176 ?        Ss   09:33   0:00
/usr/libexec/postfix/master
postfix   2095  0.0  0.1  78776  3200 ?        S    09:33   0:00  \_ pickup
-l -t fifo -u
postfix   2097  0.0  0.1  78948  3264 ?        S    09:33   0:00  \_ qmgr
-l -t fifo -u
root      2113  0.0  0.0 118820  1156 ?        Ss   09:33   0:00
/usr/sbin/abrtd
root      2121  0.0  0.0   9196   724 ?        Ss   09:33   0:00
abrt-dump-oops -d /var/spool/abrt -rwx /var/log/messages
root      2135  0.0  0.0 108240   800 ?        S    09:33   0:00 /bin/bash
/usr/sbin/ksmtuned
root      4884  0.0  0.0 100940   472 ?        S    10:30   0:00  \_ sleep
60
qpidd     2147  0.0  0.1 334300  3936 ?        Ssl  09:33   0:00
/usr/sbin/qpidd --data-dir /var/lib/qpidd --daemon
root      2180  0.0  0.0 117184  1376 ?        Ss   09:33   0:00 crond
root      2191  0.0  0.0  21472   392 ?        Ss   09:33   0:00
/usr/sbin/atd
root      2202  0.0  0.0  10424  2224 ?        SLs  09:33   0:00 wdmd
root      2213  0.0  1.7 318220 39680 ?        SLsl 09:33   0:00 sanlock
daemon
root      2227  0.0  0.0  27232   524 ?        S    09:33   0:00
/usr/sbin/cimserver
cimsrvr   2228  0.0  0.4 391864 10088 ?        Sl   09:33   0:00  \_
cimservermain --executor-socket 3
root      2243  0.0  0.1 220784  3440 ?        Ssl  09:33   0:00
libvirt-qmf --broker 127.0.0.1 --daemon --reconnect=yes
root      2252  0.0  0.0 121512  2060 ?        Ss   09:33   0:00
/usr/sbin/gdm-binary -nodaemon
root      2290  0.0  0.1 152268  3244 ?        S    09:33   0:00  \_
/usr/libexec/gdm-simple-slave --display-id
/org/gnome/DisplayManager/Display1 --force-active-vt
root      2292  1.4  2.2 155660 52464 tty1     Ss+  09:33   0:51      \_
/usr/bin/Xorg :0 -nr -verbose -auth
/var/run/gdm/auth-for-gdm-a4kksW/database -nolisten tcp vt1
root      2438  0.0  0.1 176920  2948 ?        S    09:33   0:00      \_
pam: gdm-password
su        2470  0.0  0.2 245792  6308 ?        Ssl  09:33   0:00
\_ gnome-session
su        2583  0.0  0.5 422184 12392 ?        Sl   09:33
0:00              \_ metacity
su        2592  0.0  0.5 324792 13472 ?        S    09:33
0:00              \_ gnome-panel
su        2596  0.0  0.9 1070992 21312 ?       S    09:33
0:00              \_ nautilus
su        2618  0.0  0.2 249980  6292 ?        S    09:33
0:00              \_ /usr/libexec/gdu-notification-daemon
su        2623  0.0  0.3 256724  7724 ?        S    09:33
0:00              \_ bluetooth-applet
su        2627  0.0  0.4 364364 10712 ?        S    09:33
0:00              \_ gnome-volume-control-applet
su        2632  0.0  0.2 228140  5028 ?        S    09:33
0:00              \_ abrt-applet
su        2639  0.0  0.8 331820 19880 ?        S    09:33
0:00              \_ python /usr/share/system-config-printer/applet.py
su        2642  0.0  0.3 280428  8712 ?        S    09:33
0:00              \_ gnome-power-manager
su        2643  0.0  0.2 224320  5140 ?        S    09:33
0:00              \_ /usr/libexec/polkit-gnome-authentication-agent-1
su        2644  0.0  0.3 275972  8308 ?        S    09:33
0:00              \_ gpk-update-icon
su        2660  0.0  0.6 315944 14552 ?        S    09:33
0:00              \_ nm-applet --sm-disable
su        2711  0.0  0.2  27792  4904 ?        S    09:33
0:00              \_ /usr/sbin/restorecond -u
root      2259  0.0  0.0   4096   536 tty2     Ss+  09:33   0:00
/sbin/mingetty /dev/tty2
root      2261  0.0  0.0   4096   532 tty3     Ss+  09:33   0:00
/sbin/mingetty /dev/tty3
root      2263  0.0  0.0   4096   536 tty4     Ss+  09:33   0:00
/sbin/mingetty /dev/tty4
root      2265  0.0  0.0   4096   532 tty5     Ss+  09:33   0:00
/sbin/mingetty /dev/tty5
root      2273  0.0  0.0   4096   532 tty6     Ss+  09:33   0:00
/sbin/mingetty /dev/tty6
root      2305  0.0  0.1 1031628 2912 ?        Sl   09:33   0:00
/usr/sbin/console-kit-daemon --no-daemon
gdm       2375  0.0  0.0  20064   476 ?        S    09:33   0:00
/usr/bin/dbus-launch --exit-with-session
root      2381  0.0  0.1  45236  2752 ?        S    09:33   0:00
/usr/libexec/devkit-power-daemon
root      2421  0.0  0.1  50028  4068 ?        S    09:33   0:00
/usr/libexec/polkit-1/polkitd
rtkit     2432  0.0  0.0 164388  1180 ?        SNl  09:33   0:00
/usr/libexec/rtkit-daemon
su        2460  0.0  0.1 144412  3468 ?        Sl   09:33   0:00
/usr/bin/gnome-keyring-daemon --daemonize --login
su        2478  0.0  0.0  20064   480 ?        S    09:33   0:00
dbus-launch --sh-syntax --exit-with-session
su        2479  0.0  0.0  30268  1764 ?        Ssl  09:33   0:00
/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
su        2553  0.0  0.2 133448  5588 ?        S    09:33   0:00
/usr/libexec/gconfd-2
su        2562  0.0  0.4 488008  9736 ?        Ssl  09:33   0:00
/usr/libexec/gnome-settings-daemon
su        2565  0.0  0.3 292684  7668 ?        Ss   09:33   0:00
seahorse-daemon
su        2568  0.0  0.0 134604  1956 ?        S    09:33   0:00
/usr/libexec/gvfsd
su        2589  0.0  0.2 441824  4960 ?        S<sl 09:33   0:00
/usr/bin/pulseaudio --start --log-target=syslog
su        2595  0.0  0.1  90292  2416 ?        S    09:33   0:00  \_
/usr/libexec/pulse/gconf-helper
su        2598  0.0  0.1 698396  3128 ?        Ssl  09:33   0:00
/usr/libexec/bonobo-activation-server --ac-activate --ior-output-fd=18
su        2603  0.0  0.5 341832 12680 ?        S    09:33   0:00
/usr/libexec/wnck-applet --oaf-activate-iid=OAFIID:GNOME_Wncklet_Factory
--oaf-ior-fd=18
su        2606  0.0  0.3 311124  9240 ?        S    09:33   0:00
/usr/libexec/trashapplet
--oaf-activate-iid=OAFIID:GNOME_Panel_TrashApplet_Factory --oaf-ior-fd=24
su        2612  0.0  0.1 141380  2876 ?        S    09:33   0:00
/usr/libexec/gvfsd-trash --spawner :1.7 /org/gtk/gvfs/exec_spaw/0
su        2614  0.0  0.1 143616  3008 ?        S    09:33   0:00
/usr/libexec/gvfs-gdu-volume-monitor
root      2616  0.0  0.1  40724  2884 ?        S    09:33   0:00
/usr/libexec/udisks-daemon
root      2620  0.0  0.0  40376   472 ?        S    09:33   0:00  \_
udisks-daemon: polling /dev/sr0
su        2631  0.0  0.0 148276  1936 ?        S    09:33   0:00
/usr/libexec/gvfs-gphoto2-volume-monitor
su        2636  0.0  0.0 229896  1956 ?        Sl   09:33   0:00
/usr/libexec/gvfs-afc-volume-monitor
su        2646  0.0  0.1 114360  3724 ?        S    09:33   0:00
/usr/libexec/im-settings-daemon
su        2729  0.0  0.1 258504  2456 ?        Ss   09:33   0:00
gnome-screensaver
su        2816  0.0  0.0  38292  1960 ?        S    09:33   0:00
/usr/libexec/gconf-im-settings-daemon
su        2819  0.0  0.7 399432 17548 ?        S    09:33   0:00
/usr/bin/gnote --panel-applet --oaf-activate-iid=OAFIID:GnoteApplet_Factory
--oaf-ior-fd=22
su        2825  0.0  0.5 462256 13452 ?        S    09:33   0:00
/usr/libexec/clock-applet
--oaf-activate-iid=OAFIID:GNOME_ClockApplet_Factory --oaf-ior-fd=31
su        2827  0.0  0.4 386232 10908 ?        S    09:33   0:00
/usr/libexec/gdm-user-switch-applet
--oaf-activate-iid=OAFIID:GNOME_FastUserSwitchApplet_Factory --oaf-ior-fd=25
su        2828  0.0  0.3 285172  7760 ?        S    09:33   0:00
/usr/libexec/notification-area-applet
--oaf-activate-iid=OAFIID:GNOME_NotificationAreaApplet_Factory
--oaf-ior-fd=37
su        2854  0.0  0.0 132488  1684 ?        S    09:34   0:00
/usr/libexec/gvfsd-metadata
su        2860  0.0  0.0 134632  2112 ?        S    09:34   0:00
/usr/libexec/gvfsd-burn --spawner :1.7 /org/gtk/gvfs/exec_spaw/1
su        2908  3.1 12.4 1038804 288480 ?      Sl   09:34   1:47
/usr/lib64/firefox/firefox
su        3092  0.0  0.5 290764 13688 ?        Sl   09:47   0:01
gnome-terminal
su        3093  0.0  0.0   8260   684 ?        S    09:47   0:00  \_
gnome-pty-helper
su        3094  0.0  0.0 108372  1780 pts/0    Ss   09:47   0:00  \_ bash
root      3108  0.0  0.1 163032  4196 pts/0    S    09:47   0:00  |   \_ su
root      3116  0.0  0.0 108472  1864 pts/0    S    09:47   0:00  |
\_ bash
root      4254  0.0  0.2 917412  5788 pts/0    Sl+  10:23   0:00
|           \_ libvirtd start
su        3311  0.0  0.0 108368  1784 pts/1    Ss+  10:03   0:00  \_ bash
su        3767  0.0  0.0 108368  1816 pts/2    Ss   10:09   0:00  \_ bash
root      3787  0.0  0.1 163036  4192 pts/2    S    10:10   0:00      \_ su
root      3796  0.0  0.0 108472  1868 pts/2    S    10:10   0:00
\_ bash
root      4885  4.0  0.0 110336  1160 pts/2    R+   10:31
0:00              \_ ps auxf
root      3820  0.0  0.0  10716   944 ?        S    10:10   0:00 xenstored
--pid-file=/var/run/xenstored.pid
root      3826  0.0  0.0  90480   348 ?        SLl  10:10   0:00
xenconsoled --pid-file=/var/run/xenconsoled.pid
root      3957  0.0  0.5 231444 11788 ?        S    10:10   0:00
/usr/bin/python /usr/sbin/xend start
root      3959  0.1  1.1 1046752 25520 ?       SLl  10:10   0:01  \_
/usr/bin/python /usr/sbin/xend start
root      4694  0.0  0.1 150456  3492 ?        Sl   10:24   0:00      \_
/usr/lib/xen/bin/qemu-dm -d 1 -serial pty -domain-name cent5 -videoram 4 -k
en-us -vnc 0.0.0.0:1 -M xenpv
nobody    4321  0.0  0.0  12916   536 ?        S    10:23   0:00
/usr/sbin/dnsmasq --strict-order --bind-interfaces
--pid-file=/usr/local/var/run/libvirt/network/default.pid
--conf-file--except-interface l
[root@XenTester su]#

Does it look normal?
> Ian.
>
>

-- 
Su Zhang
Ph.D Candidate
Computing and Information Sciences
Kansas State University



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

On Tue, Mar 20, 2012 at 2:33 AM, Andreas Greve
<andreas.greve@a-greve.de>wrote:
> **
>  Hallo Su Zhang,
>
> sorry for the short answer yesterday it was written on train on my handy.
>
> /var/log/xen/console must be a directory.
>
> > There is no any file or directory called /etc/default/xen*.
> Sorry that was specific to my debian system.  The correct name is
> /etc/sysconfig/xend
>
Andreas,

There is no file at /etc/sysconfig/xend, instead, there are files called
/etc/sysconfig/xencommons and /etc/sysconfig/xendomains

> If in this file the  option
> #XENCONSOLED_TRACE=[none|guest|hv|all]
> is aktivated and set to all (in my case) and if the directory
/var/log/xen/console
> does not exist
> the daemon xenconsoled dies directly after start on boot because
> xenconsed want to write to /var/log/xen/console/hypervisor.log.
> but the directory does not exist.
>
There is a line "#XENCONSOLED_TRACE=[none|guest|hv|all]" within
/etc/sysconfig/xencommons. Currently, this line ("
#XENCONSOLED_TRACE=[none|guest|hv|all]") is commented out, so it seems that
it is not activated right now?
again, there is no file or directory at /var/log/xen/console in my file
system.

>  Bevor you try to start a DomU look if xenconsoled is running (ps augx |
> grep xenconsoled). If xenconsoled is not running perhaps you have the
> same problem.
>
Actually, I the output of the command line does indicate that the
xenconsoled is running:

[root@XenTester su]# ps augx | grep xenconsoled
root      3826  0.0  0.0  90480   348 ?        SLl  10:10   0:00
xenconsoled --pid-file=/var/run/xenconsoled.pid
root      5119  0.0  0.0 103284   800 pts/2    S+   10:53   0:00 grep
xenconsoled
[root@XenTester su]#

So it seems that your issue is not exactly same as mine because the
XENCONSOLED TRACE is inactivated under my default settings, do you think so?
>
> my way arround the problem was (as root):
>
>     mkdir /var/log/xen/console
>
> starting daemon by hand
>
>     /usr/sbin/xenconsoled
>
> making sure the the xenconsoled is running
>
>     ps augx | grep xenconsoled
>
> and than trying to start a domU (pv).
>
>     xm create <domU>
>
> After that all works fine for me including for a system reboot too.
>
> I inspected the "make install" of  (4.1.2) and  only found the
creation
> of  /var/log/xen directory but nothing for the creation of
> /var/log/xen/console. But the source from xenconsoled depends on that
> directory.
>
> So I think that it is a bug in the "make install"
>
> Andreas
>
>
> -----Ursprüngliche Nachricht-----
> *Von:* Su Zhang [mailto:westlifezs@gmail.com]
> *Gesendet:* Dienstag, 20. März 2012 02:46
> *An:* Andreas Greve
> *Cc:* Ian Campbell; xen-users@lists.xen.org
> *Betreff:* Re: [Xen-users] xenconsole: Could not read tty from store: No
> such file or directory
>
>
>
> On Mon, Mar 19, 2012 at 1:56 PM, Andreas Greve
<andreas.greve@a-greve.de>wrote:
>
>> Hallo,
>> if it is a pv then look if the directory /var/log/xen/console exists.
If
>> some logging options in /etc/default/xen* are enabled xenconsoled does
not
>> start on boot. Because it could not write to
>> /var/log/xen/console/hypervisor.log. The make install does not create
the
>> missing directory (4.1.2) .
>> I run in this problem today.
>> I hope the above helps you.
>>
>> Andreas
>> --
>>
>>   Hi Andreas,
>
>    Thanks for your reply. Interestingly, the file /var/log/xen/console
> doesn''t exist on my machine. There is no any file or directory
called
> /etc/default/xen*. So how did you address the similar problem? Could you
> please be a bit specific? Do I need to generate these files manually? Or
> How can I generate these files automatically? Is this issue caused by these
> missing files?
>
> Thanks,
>
>>
>>
>> Ian Campbell <Ian.Campbell@citrix.com> schrieb:
>>>
>>> On Sat, 2012-03-17 at 16:30 +0000, Su Zhang wrote:
>>> >
>>> >
>>> > On Sat, Mar 17, 2012 at 3:24 AM, Ian Campbell
>>> > <Ian.Campbell@citrix.com> wrote:
>>>
>>> >         On Fri, 2012-03-16 at 23:45 +0000, Su Zhang wrote:
>>> >         > 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
>>> &gt!
>>>  ;
>>>  there. Please
>>>
>>> >         > see:
>>> >
>>> >
>>> >         You might need to restart your guests and/or toolstack
after
>>> >         starting
>>> >         xenconsole.
>>>
>>> >
>>> >         This should all have been taken care of by the
initscripts
>>> >         shipped with
>>> >         xen -- are you not using them for some reason?
>>> >
>>> >
>>> >
>>>
>>> > Ian,
>>> >
>>> >    Do initscripts here refer to the xen-related scripts
>>> > under /etc/init.d/ ?
>>> >    Like xencomms?
>>>
>>> xencommons, yes.
>>>
>>> >  [...]
>>>
>>> > [root@XenTester su]# virt-install -l
>>>
>>> > http://mirror.centos.org/centos/5/os/i386/ -p -n f13 -r 768
--vcpus=1
>>> > --disk=/srv/xen/mailserver.img --graphics
vnc,listen=0.0.0.0,port=5901
>>>
>>> > --noautoconsole
>>>
>>> I''m not at all familia!
>>>  r with
>>> virt-install or Fedora but given this
>>>
>>> domain is to be called "f13" I would have expected a
Fedora mirror to be
>>> listed rather than the CentOS 5 mirror. Is this normal?
>>>
>>> Do you know if this command will create a PV or an HVM guest?
>>>
>>> If this is an HVM domain then it is possible that it simply
doesn''t have
>>> a text console which you can connect to with xl console. The
"Could not
>>> read tty from store" message is often indicative of this.
>>>
>>> It appears you have configured VNC for this domain, have you tried
>>> connecting a vncviewer to port 5901 on the host? e.g. vncviewer
>>> localhost:1 or localhost::5091 (check the vncviewer manpage,
I''m not
>>> sure of the syntax). Perhaps virt-* includes a command to do this
for
>>>
>>> you automatically?
>>>
>>> If you want a text console from an HVM guest then you can do the
>>> virt-install equivalent of adding
>>> 	series = ''pty''
>>> to your guest configuration. I''m afraid I don''t
know h!
>>>  ow to
>>> actually do
>>>
>>> that with virt-install though.
>>>
>>> If this is a PV guest then I have no idea what might be wrong.
>>>
>>> Ian.
>>>
>>>
>>> ------------------------------
>>>
>>> Xen-users mailing list
>>> Xen-users@lists.xen.org
>>> http://lists.xen.org/xen-users
>>>
>>>
>
>
> --
> Su Zhang
> Ph.D Candidate
> Computing and Information Sciences
> Kansas State University
>
>

-- 
Su Zhang
Ph.D Candidate
Computing and Information Sciences
Kansas State University


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

On Tue, 2012-03-20 at 15:35 +0000, Su Zhang wrote:
>         
> Here is the output from git show:
> 
> [root@XenTester linux]# git show
> commit 4c41042d1d4c29e596b31e2d14b26d2940fb24b4
> Merge: e9308cf bf164c5
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date:   Sat Oct 15 08:29:09 2011 +1200
Bit dated and in the middle of a dev series, you might be better of with
e.g. v3.2.12 which was just released.

[...]
>         One other useful bit of information would be the output of
>                xenstore-ls -fp
> 
> I''ve attached the output of xenstore-ls -fp as it contains too
many
> lines. 
> Does it look okay?
It seems to be missing the node which should contain the tty for the
console (hence the error message).

Have you restarted xenstored at all? If so then you may need to reboot
(might be a good idea anyway). Remember add the modprobe xen-gntdev to
the xencommons initscript somewhere before starting the daemons and
ensure that it is set to run on startup.

I''m afraid that if rebooting doesn''t help then I''m at
a loss. Might be a
virt manager thing I guess but I don''t know anything about that side of
things.
> while the domain is (apparently) running and you cannot connect to the
>         console. Also "ps auxf" might be useful too.
>         
> In fact, the domU can never be run, it always under blocked.  Here is
> the output of ps auxf:
[...]
> Does it look normal?
Looks ok to me.

I''m not sure why you can''t connect to the VNC -- it appears to
be up and
running. Perhaps a firewall issue?

Ian.

On Tue, Mar 20, 2012 at 11:07 AM, Ian Campbell
<Ian.Campbell@citrix.com>wrote:
> On Tue, 2012-03-20 at 15:35 +0000, Su Zhang wrote:
>
> >
> > Here is the output from git show:
> >
> > [root@XenTester linux]# git show
> > commit 4c41042d1d4c29e596b31e2d14b26d2940fb24b4
> > Merge: e9308cf bf164c5
> > Author: Linus Torvalds <torvalds@linux-foundation.org>
> > Date:   Sat Oct 15 08:29:09 2011 +1200
>
> Bit dated and in the middle of a dev series, you might be better of with
> e.g. v3.2.12 which was just released.
>
Thanks for the useful info.
> [...]
> >         One other useful bit of information would be the output of
> >                xenstore-ls -fp
> >
> > I''ve attached the output of xenstore-ls -fp as it contains
too many
> > lines.
> > Does it look okay?
>
> It seems to be missing the node which should contain the tty for the
> console (hence the error message).
>
> Have you restarted xenstored at all? If so then you may need to reboot
> (might be a good idea anyway). Remember add the modprobe xen-gntdev to
> the xencommons initscript somewhere before starting the daemons and
> ensure that it is set to run on startup.
>
> I''m afraid that if rebooting doesn''t help then
I''m at a loss. Might be a
> virt manager thing I guess but I don''t know anything about that
side of
> things.
>

After I reboot (with "modprobe xen-gntdev" added into xencommons), the
domainU seems to be offline. When I was starting the domU, there is another
error
popped out.
[root@XenTester su]# xm list
Name                                        ID   Mem VCPUs      State
Time(s)
Domain-0                                     0  3328     2     r-----
57.3
cent5                                            768     1
0.0
[root@XenTester su]# xm start cent5
Error: Boot loader didn''t return any data!
Usage: xm start <DomainName>

Start a Xend managed domain
  -p, --paused                   Do not unpause domain after starting it
  -c, --console_autoconnect      Connect to the console after the domain
                                 is created
  --vncviewer                    Connect to display via VNC after the
                                 domain is created
  --vncviewer-autopass           Pass VNC password to viewer via stdin and
                                 -autopass

[root@XenTester su]#

Can you see a problem here?
>
> > while the domain is (apparently) running and you cannot connect to the
> >         console. Also "ps auxf" might be useful too.
> >
> > In fact, the domU can never be run, it always under blocked.  Here is
> > the output of ps auxf:
> [...]
> > Does it look normal?
>
> Looks ok to me.
>
> I''m not sure why you can''t connect to the VNC -- it
appears to be up and
> running. Perhaps a firewall issue?
>
> Here is the iptable output,
[root@XenTester su]# iptables -nL
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state
RELATED,ESTABLISHED
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp
dpt:22
REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with
icmp-host-prohibited

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with
icmp-host-prohibited

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
[root@XenTester su]#

Does it look ok to you?
there may be a firewall at the gateway blocked the connection. I may double
check with our system admin.
>  Ian.
>
>

-- 
Su Zhang
Ph.D Candidate
Computing and Information Sciences
Kansas State University


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

On Tue, 2012-03-20 at 16:39 +0000, Su Zhang wrote:
> 
> After I reboot (with "modprobe xen-gntdev" added into
xencommons), the
> domainU seems to be offline. When I was starting the domU, there is
> another error
> popped out. 
> [root@XenTester su]# xm list
> Name                                        ID   Mem VCPUs      State
> Time(s)
> Domain-0                                     0  3328     2     r-----
> 57.3
> cent5                                            768     1
> 0.0
> [root@XenTester su]# xm start cent5
> Error: Boot loader didn''t return any data!
> Usage: xm start <DomainName>
> Can you see a problem here?
I expect that because you couldn''t get to the console the VM was never
installed so there is nothing to boot. You probably need to destroy and
reinstall.
> Here is the iptable output,
> [root@XenTester su]# iptables -nL
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination         
> ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state
RELATED,ESTABLISHED
> ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           
> ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           
> ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp
dpt:22
> REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with
icmp-host-prohibited
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination         
> REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with
icmp-host-prohibited
> 
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination         
> [root@XenTester su]# 
> 
> Does it look ok to you? 
It seems to reject all non-ssh connections, which would explain things I
think.

Try flushing your firewall rules perhaps? Or reconfigure to allow
5900-6000.
> there may be a firewall at the gateway blocked the connection. I may
> double check with our system admin.  
That shouldn''t impact localhost connections.

Ian.

On Tue, Mar 20, 2012 at 11:47 AM, Ian Campbell
<Ian.Campbell@citrix.com>wrote:
> On Tue, 2012-03-20 at 16:39 +0000, Su Zhang wrote:
>
> >
> > After I reboot (with "modprobe xen-gntdev" added into
xencommons), the
> > domainU seems to be offline. When I was starting the domU, there is
> > another error
> > popped out.
> > [root@XenTester su]# xm list
> > Name                                        ID   Mem VCPUs      State
> > Time(s)
> > Domain-0                                     0  3328     2     r-----
> > 57.3
> > cent5                                            768     1
> > 0.0
> > [root@XenTester su]# xm start cent5
> > Error: Boot loader didn''t return any data!
> > Usage: xm start <DomainName>
>
> > Can you see a problem here?
>
> I expect that because you couldn''t get to the console the VM was
never
> installed so there is nothing to boot. You probably need to destroy and
> reinstall.
>
> After I rebooted &&deleted&& reinstalled domU, an
interesting thing
happened, the error seems to have gone away, instead, there is a long
script following the command line, but it just stuck there. nothing can be
done here, here is the running script:

[root@XenTester su]# xm console cent5
Linux version 2.6.18-308.el5xen (mockbuild@builder10.centos.org) (gcc
version 4.1.2 20080704 (Red Hat 4.1.2-52)) #1 SMP Tue Feb 21 21:26:03 EST
2012
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000030800000 (usable)
48MB HIGHMEM available.
727MB LOWMEM available.
NX (Execute Disable) protection: active
ACPI in unprivileged domain disabled
Built 1 zonelists.  Total pages: 198656
Kernel command line: method=http://mirror.centos.org/centos/5/os/i386/
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
CPU 0 irqstacks, hard=c0784000 soft=c0764000
PID hash table entries: 4096 (order: 12, 16384 bytes)
Xen reported: 2527.042 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Software IO TLB disabled
vmalloc area: ee000000-f4ffe000, maxmem 2d7fe000
Memory: 757676k/794624k available (2212k kernel code, 28436k reserved,
1038k data, 184k init, 49160k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 6351.52 BogoMIPS
(lpj=12703058)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 6144K
Checking ''hlt'' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 14k freed
Brought up 1 CPUs
checking if image is initramfs... it is
Freeing initrd memory: 14496k freed
Grant table initialized
NET: Registered protocol family 16
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
type=2000 audit(1332262662.268:1): initialized
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
alg: No test for crc32c (crc32c-generic)
ksign: Installing public key data
Loading keyring
- Added public key E4B7FFDB66F0F649
- User ID: CentOS (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
brd: module loaded
Xen virtual console successfully installed as xvc0
Event-channel device installed.
Console: switching to colour frame buffer device 100x37
input: Xen Virtual Keyboard/Mouse as /class/input/input0
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
XENBUS: Device with no driver: device/vbd/51712
XENBUS: Device with no driver: device/vif/0
XENBUS: Device with no driver: device/console/0
Initalizing network drop monitor service
Freeing unused kernel memory: 184k freed
Write protecting the kernel read-only data: 401k

Anything can be done to get it around?
> > Here is the iptable output,
> > [root@XenTester su]# iptables -nL
> > Chain INPUT (policy ACCEPT)
> > target     prot opt source               destination
> > ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state
> RELATED,ESTABLISHED
> > ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0
> > ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
> > ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW
> tcp dpt:22
> > REJECT     all  --  0.0.0.0/0            0.0.0.0/0
> reject-with icmp-host-prohibited
>
>
> > Chain FORWARD (policy ACCEPT)
> > target     prot opt source               destination
> > REJECT     all  --  0.0.0.0/0            0.0.0.0/0
> reject-with icmp-host-prohibited
> >
> > Chain OUTPUT (policy ACCEPT)
> > target     prot opt source               destination
> > [root@XenTester su]#
> >
> > Does it look ok to you?
>
> It seems to reject all non-ssh connections, which would explain things I
> think.
>
> Try flushing your firewall rules perhaps? Or reconfigure to allow
> 5900-6000.
>
Thanks a lot. I''ve already re-configured the firewall rules to allow
5900-6000 [both in and out]. The command "vncviewer localhost:5901"
can
bring a VNC window to me.

Right now the only issue left seems to be how to get through the stuck
virtual machine after I do "xm console cent5"
>
> > there may be a firewall at the gateway blocked the connection. I may
> > double check with our system admin.
>
> That shouldn''t impact localhost connections.
>
> Ian.
>
>
>

-- 
Su Zhang
Ph.D Candidate
Computing and Information Sciences
Kansas State University


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

On Tue, 2012-03-20 at 17:20 +0000, Su Zhang wrote:

> After I rebooted &&deleted&& reinstalled domU, an
interesting thing
> happened, the error seems to have gone away, instead, there is a long
> script following the command line, but it just stuck there. nothing
> can be done here, here is the running script:
> [root@XenTester su]# xm console cent5
[...]

This is the console log of the domain, which is good because it means
this problem is solved.

I expect the installer is running on the VNC console and not this serial
console. Not sure how you convince CentOS (esp, using virt-install) to
use the serial console for install, google perhaps?

[...]
> Thanks a lot. I''ve already re-configured the firewall rules to
allow
> 5900-6000 [both in and out]. The command "vncviewer
localhost:5901"
> can bring a VNC window to me. 
Great what is on the VNC window? Do you see the RH installer?

Ian.

On Tue, Mar 20, 2012 at 12:44 PM, Ian Campbell
<Ian.Campbell@citrix.com>wrote:
> On Tue, 2012-03-20 at 17:20 +0000, Su Zhang wrote:
>
>
> > After I rebooted &&deleted&& reinstalled domU, an
interesting thing
> > happened, the error seems to have gone away, instead, there is a long
> > script following the command line, but it just stuck there. nothing
> > can be done here, here is the running script:
>
>
> > [root@XenTester su]# xm console cent5
> [...]
>
> This is the console log of the domain, which is good because it means
> this problem is solved.
>
> I expect the installer is running on the VNC console and not this serial
> console. Not sure how you convince CentOS (esp, using virt-install) to
> use the serial console for install, google perhaps?
>
Do you mean if I just leave it stuck here and connect to VNC manually then
I can still get it around?  So that I can do the rest over VNC?
>
> [...]
> > Thanks a lot. I''ve already re-configured the firewall rules
to allow
> > 5900-6000 [both in and out]. The command "vncviewer
localhost:5901"
> > can bring a VNC window to me.
>
> Great what is on the VNC window? Do you see the RH installer?
>
I guess so, it starts with language selection and followed by network
configuration. But I cannot pass through the network (IP) configuration.
It doesn''t allow me to go forward but no error info is displayed. Do
you
think it is because the VNC hasn''t been setup appropriately? or the
guest
OS kernel issue?

Thanks,
>
> Ian.
>
>
>

-- 
Su Zhang
Ph.D Candidate
Computing and Information Sciences
Kansas State University


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

On Tue, 2012-03-20 at 19:14 +0000, Su Zhang wrote:
> 
> 
> On Tue, Mar 20, 2012 at 12:44 PM, Ian Campbell
> <Ian.Campbell@citrix.com> wrote:
>         On Tue, 2012-03-20 at 17:20 +0000, Su Zhang wrote:
>         
>         
>         > After I rebooted &&deleted&& reinstalled domU,
an
>         interesting thing
>         > happened, the error seems to have gone away, instead, there
>         is a long
>         > script following the command line, but it just stuck there.
>         nothing
>         > can be done here, here is the running script:
>         
>         
>         > [root@XenTester su]# xm console cent5
>         
>         [...]
>         
>         This is the console log of the domain, which is good because
>         it means
>         this problem is solved.
>         
>         I expect the installer is running on the VNC console and not
>         this serial
>         console. Not sure how you convince CentOS (esp, using
>         virt-install) to
>         use the serial console for install, google perhaps?
> 
> Do you mean if I just leave it stuck here and connect to VNC manually
> then I can still get it around?  So that I can do the rest over VNC?
That is what I would expect, yes.

>         [...]
>         > Thanks a lot. I''ve already re-configured the firewall
rules
>         to allow
>         > 5900-6000 [both in and out]. The command "vncviewer
>         localhost:5901"
>         > can bring a VNC window to me.
>         
>         
>         Great what is on the VNC window? Do you see the RH installer?
> 
> I guess so, it starts with language selection and followed by network
> configuration. But I cannot pass through the network (IP)
> configuration.
> It doesn''t allow me to go forward but no error info is displayed.
Do
> you think it is because the VNC hasn''t been setup appropriately?
or
> the guest OS kernel issue?
It won''t be anything to do with VNC. Most likely a guest side issue but
I don''t know enough about CentOS to guess based on what you have said.

Ian.

On Tue, 2012-03-20 at 19:58 +0000, Ian Campbell wrote:
> >         [...]
> >         > Thanks a lot. I''ve already re-configured the
firewall rules
> >         to allow
> >         > 5900-6000 [both in and out]. The command "vncviewer
> >         localhost:5901"
> >         > can bring a VNC window to me.
> >         
> >         
> >         Great what is on the VNC window? Do you see the RH installer?
> > 
> > I guess so, it starts with language selection and followed by network
> > configuration. But I cannot pass through the network (IP)
> > configuration.
> > It doesn''t allow me to go forward but no error info is
displayed. Do
> > you think it is because the VNC hasn''t been setup
appropriately? or
> > the guest OS kernel issue?
> 
> It won''t be anything to do with VNC. Most likely a guest side
issue but
> I don''t know enough about CentOS to guess based on what you have
said.
I guess it''s worth checking the network setup in dom0. What do
"ifconfig
-a" and "brctl show" output?

Ian.

On Tue, Mar 20, 2012 at 3:23 PM, Ian Campbell
<Ian.Campbell@citrix.com>wrote:
> On Tue, 2012-03-20 at 19:58 +0000, Ian Campbell wrote:
>
> > >         [...]
> > >         > Thanks a lot. I''ve already re-configured
the firewall rules
> > >         to allow
> > >         > 5900-6000 [both in and out]. The command
"vncviewer
> > >         localhost:5901"
> > >         > can bring a VNC window to me.
> > >
> > >
> > >         Great what is on the VNC window? Do you see the RH
installer?
> > >
> > > I guess so, it starts with language selection and followed by
network
> > > configuration. But I cannot pass through the network (IP)
> > > configuration.
> > > It doesn''t allow me to go forward but no error info is
displayed. Do
> > > you think it is because the VNC hasn''t been setup
appropriately? or
> > > the guest OS kernel issue?
> >
> > It won''t be anything to do with VNC. Most likely a guest side
issue but
> > I don''t know enough about CentOS to guess based on what you
have said.
>
> I guess it''s worth checking the network setup in dom0. What do
"ifconfig
> -a" and "brctl show" output?
>
Here are the output:

[root@XenTester su]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:21:86:A1:CD:54
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:20 Memory:fc200000-fc220000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:5724 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5724 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:492872 (481.3 KiB)  TX bytes:492872 (481.3 KiB)

tmpbridge Link encap:Ethernet  HWaddr 6A:27:D8:0C:8D:D0
          inet addr:10.131.65.96  Bcast:10.131.71.255  Mask:255.255.248.0
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

vif2.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:31 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3503 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:5416 (5.2 KiB)  TX bytes:185362 (181.0 KiB)

virbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:31 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5416 (5.2 KiB)  TX bytes:410 (410.0 b)

wlan0     Link encap:Ethernet  HWaddr 00:21:6B:AE:0D:A2
          inet addr:10.131.65.96  Bcast:10.131.71.255  Mask:255.255.248.0
          inet6 addr: fe80::221:6bff:feae:da2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:31354 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20012 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:25052928 (23.8 MiB)  TX bytes:4458490 (4.2 MiB)

[root@XenTester su]# brctl show
bridge name    bridge id        STP enabled    interfaces
tmpbridge        8000.000000000000    no
virbr0        8000.feffffffffff    yes        vif2.0
[root@XenTester su]#

Does the dom0 network settings look good?


>
> Ian.
>
>
>

-- 
Su Zhang
Ph.D Candidate
Computing and Information Sciences
Kansas State University


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users