I configured a domU to access to the physical serial port of the dom0 (/dev/ttyS0) typing this in the domU configuration file: irq = [ 4 ] ioports = [ "3f8-3ff" ] The domU starts without any error, but the serial port isn''t recognised. The /dev/ttyS0 device exists on the domU, and I blacklisted the serial_core, the 8250 and 8250_pnp modules on the dom0. What is the problem? Could you help me, please? Thank you very much! Bye. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
What version of xen are you using ? i''m using 3.0.3-1-amd64 on debian and have exactly the same problem. drivers load on domU, but do not detect any serial ports. subsequently loading the drivers on dom0 does work (if you un-blacklist them first), even if the domU is still running, so i thought the irq/ioports statement was simply not being picked up, but according to xend.log, they are. no obvious errors. my gamble is on CONFIG_XEN_DISABLE_SERIAL being set on the domU (also on dom0, but that works). is there anyone out there that can confirm serial ports working on domU with a kernel that has the above config entry set ? Sven On 9/6/07, shacky <shacky83@gmail.com> wrote:> > I configured a domU to access to the physical serial port of the dom0 > (/dev/ttyS0) typing this in the domU configuration file: > > irq = [ 4 ] > ioports = [ "3f8-3ff" ] > > The domU starts without any error, but the serial port isn''t recognised. > The /dev/ttyS0 device exists on the domU, and I blacklisted the > serial_core, the 8250 and 8250_pnp modules on the dom0. > > What is the problem? Could you help me, please? > > Thank you very much! > Bye. > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Dear list,
update on the serial to domU issue:
- confirmed that xen scripts are picking up the ioports and irq statement:
both are listed in the xend.log in a parseConfig statement (so the
scripts at least know about the ioports/irq statements)
however i cannot find any DevController stanzas in there for the serial
ports, i can find such statements for disks, nics, pci cards, ..
should there be any of those ?
- on the domU i am not sure:
- /proc/devices does list a ttyS0 device
- /proc/ioports do not show the transferred io ports
- /proc/interrupts do not show the transferred irq
i am trying to recompile a debian xen kernel to disable the
CONFIG_XEN_DISABLE_SERIAL config setting and see if that helps.
note that dom0 serial access works, even with a kernel were
CONFIG_XEN_DISABLE_SERIAL is set. domU does not.
Does anyone know from what version of (opensource) xen the ioports/irq
transfer works ?
3.0.3-1-amd64 + 2.6.18-4-amd64 (aka debian etch default) does not seem to
work.
Any help really appreciated.
Sven
On 9/7/07, sven waeyenbergh <sven.waeyenbergh@gmail.com>
wrote:>
> What version of xen are you using ?
> i''m using 3.0.3-1-amd64 on debian and have exactly the same
problem.
>
> drivers load on domU, but do not detect any serial ports.
> subsequently loading the drivers on dom0 does work (if you un-blacklist
> them first),
> even if the domU is still running, so i thought the irq/ioports statement
> was simply not being picked up,
> but according to xend.log, they are. no obvious errors.
>
> my gamble is on CONFIG_XEN_DISABLE_SERIAL being set on the domU (also on
> dom0, but that works).
> is there anyone out there that can confirm serial ports working on domU
> with a kernel that has the above config entry set ?
>
> Sven
>
> On 9/6/07, shacky <shacky83@gmail.com> wrote:
> >
> > I configured a domU to access to the physical serial port of the dom0
> > (/dev/ttyS0) typing this in the domU configuration file:
> >
> > irq = [ 4 ]
> > ioports = [ "3f8-3ff" ]
> >
> > The domU starts without any error, but the serial port isn''t
recognised.
> > The /dev/ttyS0 device exists on the domU, and I blacklisted the
> > serial_core, the 8250 and 8250_pnp modules on the dom0.
> >
> > What is the problem? Could you help me, please?
> >
> > Thank you very much!
> > Bye.
> >
> >
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
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@gmail.com> 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@lists.xensource.com > > 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@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@gmail.com> 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@gmail.com> 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@lists.xensource.com > > > 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@lists.xensource.com > > http://lists.xensource.com/xen-users > > > >-- Artiom _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@gmail.com> 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@gmail.com> 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@gmail.com> 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@lists.xensource.com > > > > 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@lists.xensource.com > > > http://lists.xensource.com/xen-users > > > > > > > > > > -- > Artiom >-- Artiom _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > All, >> i have now created a custom debian xen kernel that works fine and detects > the serial ports in domU, > so the problem was indeed the config setting. > > if others have the same amount of troubles getting a xen+debian kernel > source going, > i found all info in > http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official > > in short: > prep: add a proper deb-src entry in /etc/apt/sources.list > > cd /usr/src > apt-get source linux-2.6 > apt-get install build-essential fakeroot > apt-get build-dep linux-2.6 > cd linux-2.6-2.6.18.dfsg.1 > fakeroot debian/rules binary > fakeroot debian/rules debian/build debian/stamps > > vi debian/build/build-amd64-xen-amd64/.config > + and change the kernel config mentioned in the previous mail > > fakeroot make -f debian/rules.gen binary-arch-amd64-xen-amd64 > > .. and your .debs should be waiting for you in /usr/src > > Greetings, > Sven > > On 9/11/07, Artiom Shamis < artiom.shamis@gmail.com > wrote: > > > > 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 > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users