WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] xen and sshd

To: "Jaswinder S. Ahluwalia" <jahluwal@xxxxxxxxxxx>
Subject: Re: [Xen-devel] xen and sshd
From: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Date: Sun, 16 Nov 2003 18:16:57 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx, Steven.Hand@xxxxxxxxxxxx
Delivery-date: Sun, 16 Nov 2003 18:16:58 +0000
Envelope-to: Steven.Hand@xxxxxxxxxxxx
In-reply-to: Message from "Jaswinder S. Ahluwalia" <jahluwal@xxxxxxxxxxx> of "Sun, 16 Nov 2003 09:17:11 PST." <200311161717.hAGHHJDt004743@xxxxxxxxxxxxx>
>Here is what I am currently doing:
>
> 
>
>1)       Login
>
>2)       dhclient
>
>3)       mv /etc/xenctl.xml-publicip /etc/xenctl.xml
>
>4)       xenctl domain new -4<192.168.1.5> -g<192.168.1.1> -m<255.255.255.0>
>

Just after the above try "xen_nat_enable; xen_read_console &"; hopefully
this will allow you to see the console messages from the new domain as 
it starts up, and hence to observe if sshd gets started.


>5)       xenctl domain start -n1
>
>6)       then I try to ssh into the domain and I get a connection refused
>message. I can ping it so I do believe it is up, I just think sshd is not
>running.

Is sshd configure to start at the relevant runlevel on the root filesystem 
of the new domain? I.e. what does "ckconfig --list sshd" produce if that 
filesystem is root (via e.g. chroot or booting explicitly with it as root)? 

cheers, 

S.


<Prev in Thread] Current Thread [Next in Thread>