Hi there, I''ve built Xen for my AMD64 Debian machine running Debian unstable. I''m using the Linux-2.6-xen.hg repository and have the 2.6.14 kernel. The VMs start okay, but I can''t ssh in or open an XTerm when connecting via NX. If I try to ssh in I get "stdin: is not a tty". The xm console command works fine. Any clues as to what I''m missing? Cheers! Paul _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
on Wed, Nov 30, 2005 at 02:31:33PM +1300, Paul Dorman (paul.dorman@solnetsolutions.co.nz) wrote:> Hi there, > > I''ve built Xen for my AMD64 Debian machine running Debian unstable. I''m > using the Linux-2.6-xen.hg repository and have the 2.6.14 kernel. > > The VMs start okay, but I can''t ssh in or open an XTerm when connecting > via NX. If I try to ssh in I get "stdin: is not a tty". The xm console > command works fine. > > Any clues as to what I''m missing?Does your /dev include device files for console, null, zero, and tty? This is an occasional issue. ''MAKEDEV console null zero tty'' should create these. Check also permissions on these and pty files. Ensure /dev/pty is being mounted. Also try the ''-t'' (force pty allocation) and ''-v'' (multiple times for more verbose output) options to ssh. Any sshd log output on the remote host would be useful. xm console to the system would be useful. Cheers. -- Karsten M. Self <karsten@xensource.com> XenSource, Inc. 2300 Geng Road #250 +1 650.798.5900 x259 Palo Alto, CA 94303 +1 650.493.1579 fax _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
on Wed, Nov 30, 2005 at 03:47:34PM +1300, Paul Dorman (paul.dorman@solnetsolutions.co.nz) wrote:> Hi Karsten, > > Thanks for your reply. I''ve got the devices, so no need to use MAKEDEV. > > Here''s the result of mount on the VM: > > proc on /proc type proc (rw) > sysfs on /sys type sysfs (rw) > tmpfs on /dev/shm type tmpfs (rw) > tmpfs on /dev type tmpfs (rw,size=10M,mode=0755) > > No mention of devpts in there (which I presume is what you meant). How > can I get that set up?It Should Just Work[tm]. If not ... try to run your /etc/init.d/mountvirtfs script manually. Note any error output from either command. You might also want to review the init.d script directly and manually execute its steps if there''s no joy for more detail. Cheers. -- Karsten M. Self <karsten@xensource.com> XenSource, Inc. 2300 Geng Road #250 +1 650.798.5900 x259 Palo Alto, CA 94303 +1 650.493.1579 fax _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
"Should" is a very big word :o) The problem is that a bunch of things were missing from the linux-2.6-xen.hg kernel configuration. Under Device Drivers (in xconfig) I have: Generic Driver Options Block devices ->IO Schedulers SCSI device support Multi-device support (RAID and LVM) Network device support SD Devices I should have a lot more, including "Character devices", which include useful things like Legacy (BSD) PTY support. I can''t open a terminal because there''s no PTYs! Is this reproducible by anyone? I had started off by copying the .config from my normal 2.6.14 kernel into the linux-2.6-xen.hg directory before starting. Anyone know how to get these missing things back again? Cheers, Paul On Tue, 2005-11-29 at 19:07 -0800, Karsten M. Self wrote:> on Wed, Nov 30, 2005 at 03:47:34PM +1300, Paul Dorman (paul.dorman@solnetsolutions.co.nz) wrote: > > Hi Karsten, > > > > Thanks for your reply. I''ve got the devices, so no need to use MAKEDEV. > > > > Here''s the result of mount on the VM: > > > > proc on /proc type proc (rw) > > sysfs on /sys type sysfs (rw) > > tmpfs on /dev/shm type tmpfs (rw) > > tmpfs on /dev type tmpfs (rw,size=10M,mode=0755) > > > > No mention of devpts in there (which I presume is what you meant). How > > can I get that set up? > > It Should Just Work[tm]. > > If not ... try to run your /etc/init.d/mountvirtfs script manually. > Note any error output from either command. You might also want to > review the init.d script directly and manually execute its steps if > there''s no joy for more detail. > > > Cheers. >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Update: In the QT version of the kernel configuration, selecting Xen-compatible in the Subarchitecture Type gets rid of most of the stuff in the Device Drivers section. Clicking PC-compatible brings it all back... Regards, Paul _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users