xen 3.2.1 from debian lenny (a debian) domU created by xen-tools (3.9-4) After lauching this domU (xm create ... etc.) I cannot ssh to the domU because there is no /dev/pts (and no shmfs is mounted, either).... i.e. the /etc/init.d/mountdevsubfs.sh script does not do its job but dunno why? (The booting messages are running away, so I cannot figure out the problem...) Any hint is appreciated, -- Zsolt _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, On Wed, Aug 12, 2009 at 03:35:48PM +0200, SZABO Zsolt wrote:> xen 3.2.1 from debian lenny > (a debian) domU created by xen-tools (3.9-4) > > After lauching this domU (xm create ... etc.) I cannot ssh to the domU > because there is no /dev/pts (and no shmfs is mounted, either).... i.e. > the /etc/init.d/mountdevsubfs.sh script does not do its job but dunno > why?For what it''s worth I see the same thing. You can put this in your cfg and then you can attach properly to the console: extra = ''console=hvc0 xencons=tty'' Then if you apt-get install udev that seems to sort things out. Doesn''t explain why it''s not working in the first place though (or even if that''s intentional). Cheers, Chris _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, 12 Aug 2009, Chris Pearson wrote:> On Wed, Aug 12, 2009 at 03:35:48PM +0200, SZABO Zsolt wrote: >> xen 3.2.1 from debian lenny >> (a debian) domU created by xen-tools (3.9-4) >> >> After lauching this domU (xm create ... etc.) I cannot ssh to the domU >> because there is no /dev/pts (and no shmfs is mounted, either).... i.e. >> the /etc/init.d/mountdevsubfs.sh script does not do its job but dunno >> why? > > For what it''s worth I see the same thing. You can put this in your cfg > and then you can attach properly to the console: > extra = ''console=hvc0 xencons=tty'' > Then if you apt-get install udev that seems to sort things out. Doesn''t > explain why it''s not working in the first place though (or even if > that''s intentional).Hmm... originally I had an extra = ''xencons=tty'' line (without ''console=hvc0'') and now after the suggested modification the domU does not start: I do not get back the prompt after "xm create" and xm list shows --p--- [...] oops: "Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working." And it is strange: I have restore the original domU.conf (undo the modification of "extra = ...") and "xm create" hangs as the undo has no effect... -- Zsolt _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, 12 Aug 2009, SZABO Zsolt wrote:> On Wed, 12 Aug 2009, Chris Pearson wrote: > >> For what it''s worth I see the same thing. You can put this in your cfg >> and then you can attach properly to the console: >> extra = ''console=hvc0 xencons=tty'' >> Then if you apt-get install udev that seems to sort things out. Doesn''t >> explain why it''s not working in the first place though (or even if >> that''s intentional). > > Hmm... originally I had an > > extra = ''xencons=tty'' > > line (without ''console=hvc0'') and now after the suggested modification > the domU does not start: I do not get back the prompt after "xm create" > and xm list shows --p--- > [...] > oops: "Error: Device 2049 (vbd) could not be connected. Hotplug scripts not > working." > > And it is strange: I have restore the original domU.conf (undo the > modification of "extra = ...") and "xm create" hangs as the undo has no > effect...OK. Finally installing udev solved the problem... (it was not installed in the domU) Zs _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users