[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] xenconsole: Could not read tty from store: No such file or directory

On Tue, Mar 20, 2012 at 11:07 AM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxx>
> 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

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 

[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  --             state RELATED,ESTABLISHED
ACCEPT     icmp --            
ACCEPT     all  --            
ACCEPT     tcp  --             state NEW tcp dpt:22
REJECT     all  --             reject-with icmp-host-prohibited

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination        
REJECT     all  --             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. 

Su Zhang
Ph.D Candidate
Computing and Information Sciences
Kansas State University
Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.