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

Re: [Xen-users] Serial port on the domU


  • To: "sven waeyenbergh" <sven.waeyenbergh@xxxxxxxxx>
  • From: "Artiom Shamis" <artiom.shamis@xxxxxxxxx>
  • Date: Tue, 11 Sep 2007 15:01:09 -0400
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 11 Sep 2007 12:02:22 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=g6bKpERJGprp8b+ZdmQ2gsNtwwTp1FilKpLhFAijxZAX+NXFcdE/FzgrV89A8vCXNZ/xJGf6BsQukxJ6o+6shiY6jwU2rINkL06THEYpJy0VW0JFIxdcgjrhvL0w3H9K/fwLtTXtnZ0EAj9HXgzZuRQroumn7weBTbPu00GcwwU=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Sven,
Thanks a lot, rebuilding kernel with serial driver enabled and without
CONFIG_XEN_DISABLE_SERIAL fixed the problem.
I loaded original kernel I've used without Xen and got the proper
serial ports configuration from there. Then copied settings to vm
.config file, made sure the CONFIG_XEN_DISABLE_SERIAL is not set and
rebuild the kernel.

Thanks for your help,
Artiom

On 9/11/07, Artiom Shamis <artiom.shamis@xxxxxxxxx> wrote:
> Sven,
> Good catch!
> The CONFIG_XEN_DISABLE_SERIAL is set to 'y' in my .config file. I'm
> going to rebuild the kernel now without this option.
>
> Thanks,
> Artiom
> On 9/11/07, sven waeyenbergh <sven.waeyenbergh@xxxxxxxxx> wrote:
> > Artiom,
> >
> > as far as i understood there are only a few things that will block the
> > transfer of the serial ports to domU:
> > - serial drivers need to be blacklisted on dom0 (you did that)
> > - serial drivers need to be compiled and installed on domU (you did that)
> > - the ioports and irq stuff needs to be added to the domU config file (you
> > did that)
> > and 1 more of which i'm not sure:
> > - kernel config option CONFIG_XEN_DISABLE_SERIAL should not be set on the
> > domU kernel (i'm not sure if you changed that before recompiling - i'm
> > having a lot of troubles getting my kernel compiled, so i haven't tested
> > this yet)
> >
> > can you confirm that the above option is NOT set for your domU ? you would
> > save me a lot of work.
> >
> > Greetings,
> > Sven
> >
> > On 9/11/07, ArtiomSh <artiom.shamis@xxxxxxxxx> wrote:
> > >
> > > Hi guys,
> > > I've got the same problem. Following recommendations above I added serial
> > > stuff on dom0 to blacklist.
> > > In /etc/xen/vm/vm2 file I added irq and ioports section. I added 8250 and
> > > serial_core and rebuild the kernel on domU. When vm get loaded there is no
> > > word about serial in dmesg output. On the other side there  are /dev/ttyS0
> > > to ttyS7 on dom0
> > > Have I missed something?
> > >
> > > Thanks,
> > > Artiom
> > >
> > >
> > > shacky wrote:
> > > >
> > > >> What's about /dev/ttyS* in dom0? If any ttyS* exists in dom0 you cannot
> > > >> use it in domU. You must disable all serial port modules like "8250" or
> > > >> "serial_core".
> > > >
> > > > I disabled that modules and they are not loded. In reality they was
> > > > not loaded neither before blacklisting them. I think the kernel was
> > > > compiled with the serial support built in it..
> > > >
> > > > _______________________________________________
> > > > Xen-users mailing list
> > > > Xen-users@xxxxxxxxxxxxxxxxxxx
> > > > http://lists.xensource.com/xen-users
> > > >
> > > >
> > >
> > > --
> > > View this message in context:
> > http://www.nabble.com/Xen-and-serial-port-tf4327425.html#a12603816
> > > Sent from the Xen - User mailing list archive at Nabble.com.
> > >
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-users
> > >
> >
> >
>
>
> --
> Artiom
>


-- 
Artiom

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

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