Xen users - Mar 2010 - Anyone have success with ivtv in a pvm? I got DMA TIMEOUT messages on xen-next/4.0-rc9-pre...

Hi,


For some weeks now, i''m running a xen-4 based system, which i want to
take
over the tasks of my previous xen-3.2 based server.
One of the things i used to do with my 3.2 system, was running a mythtv server
inside a pvm with ivtv based hardware. This seemed to work fine with xen 3.2.

Trying to get this to work with xen-4, i don''t seem to have much
success...
older versions of the kernel would lock-up (well that''s what you get
for
trying bleeding edge, i know), but now it seems to boot fine.
However, as soon as i try to record something from /dev/video0 (e.g. using cat 
/dev/video0 > tmp0.mpg), i get a ivtv0 DMA TIMEOUT message on my console.
When i break off the action (after about 30 seconds or so), the tmp0.mpg file 
has a 0 size, indicating nothing at all was recorded.

Is there something i can do about this? Or am i just asking too much of the 
system right now? I also tried various swiotlb options (on 3.2 those were 
absolutely necessary), but to no avail.

Any hints/tips would be very much appreciated!


Regards,
Mark.

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

On Tue, Mar 30, 2010 at 12:36:48AM +0200, Mark Hurenkamp
wrote:
> Hi,
> 
> 
> For some weeks now, i''m running a xen-4 based system, which i want
to take
> over the tasks of my previous xen-3.2 based server.
> One of the things i used to do with my 3.2 system, was running a mythtv
server
> inside a pvm with ivtv based hardware. This seemed to work fine with xen
3.2.
> 
> Trying to get this to work with xen-4, i don''t seem to have much
success...
> older versions of the kernel would lock-up (well that''s what you
get for
> trying bleeding edge, i know), but now it seems to boot fine.
> However, as soon as i try to record something from /dev/video0 (e.g. using
cat
> /dev/video0 > tmp0.mpg), i get a ivtv0 DMA TIMEOUT message on my
console.
> When i break off the action (after about 30 seconds or so), the tmp0.mpg
file
> has a 0 size, indicating nothing at all was recorded.
> 
> Is there something i can do about this? Or am i just asking too much of the
> system right now? I also tried various swiotlb options (on 3.2 those were 
> absolutely necessary), but to no avail.
> 
> Any hints/tips would be very much appreciated!
> 
Maybe this wiki page helps?:
http://wiki.xensource.com/xenwiki/XenPCIpassthrough

-- Pasi


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

> On Tue, Mar 30, 2010 at 12:36:48AM +0200, Mark Hurenkamp wrote:
>> Hi,
>>
>>
>> For some weeks now, i''m running a xen-4 based system, which i
want to
>> take over the tasks of my previous xen-3.2 based server.
>> One of the things i used to do with my 3.2 system, was running a mythtv
>> server inside a pvm with ivtv based hardware. This seemed to work fine
>> with xen 3.2.
>>
>> Trying to get this to work with xen-4, i don''t seem to have
much
>> success...
>> older versions of the kernel would lock-up (well that''s what
you get for
>> trying bleeding edge, i know), but now it seems to boot fine.
>> However, as soon as i try to record something from /dev/video0 (e.g.
>> using cat /dev/video0 > tmp0.mpg), i get a ivtv0 DMA TIMEOUT message
on
>> my console.
>> When i break off the action (after about 30 seconds or so), the
tmp0.mpg
>> file has a 0 size, indicating nothing at all was recorded.
>>
>> Is there something i can do about this? Or am i just asking too much of
>> the system right now? I also tried various swiotlb options (on 3.2
those
>> were absolutely necessary), but to no avail.
>>
>> Any hints/tips would be very much appreciated!
>>
>
> Maybe this wiki page helps?:
> http://wiki.xensource.com/xenwiki/XenPCIpassthrough
Thanks for your input, i had read this page before, but now noticed there
is one option mentioned there which i had not tried before: iommu=soft.
Tried to boot with that just now, and i don''t get the errors anymore,
and
the tmp0.mpg file now contains data.
Not sure if everything works ok now, I will do more tests in the course of
this week.
At least I''m one more step closer to running mythtv in domU again!


Regards,
Mark



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

On Tue, Mar 30, 2010 at 10:47:06AM +0200, Mark Hurenkamp
wrote:
> > On Tue, Mar 30, 2010 at 12:36:48AM +0200, Mark Hurenkamp wrote:
> >> Hi,
> >>
> >>
> >> For some weeks now, i''m running a xen-4 based system,
which i want to
> >> take over the tasks of my previous xen-3.2 based server.
> >> One of the things i used to do with my 3.2 system, was running a
mythtv
> >> server inside a pvm with ivtv based hardware. This seemed to work
fine
> >> with xen 3.2.
> >>
> >> Trying to get this to work with xen-4, i don''t seem to
have much
> >> success...
> >> older versions of the kernel would lock-up (well that''s
what you get for
> >> trying bleeding edge, i know), but now it seems to boot fine.
> >> However, as soon as i try to record something from /dev/video0
(e.g.
> >> using cat /dev/video0 > tmp0.mpg), i get a ivtv0 DMA TIMEOUT
message on
> >> my console.
> >> When i break off the action (after about 30 seconds or so), the
tmp0.mpg
> >> file has a 0 size, indicating nothing at all was recorded.
> >>
> >> Is there something i can do about this? Or am i just asking too
much of
> >> the system right now? I also tried various swiotlb options (on 3.2
those
> >> were absolutely necessary), but to no avail.
> >>
> >> Any hints/tips would be very much appreciated!
> >>
> >
> > Maybe this wiki page helps?:
> > http://wiki.xensource.com/xenwiki/XenPCIpassthrough
> 
> Thanks for your input, i had read this page before, but now noticed there
> is one option mentioned there which i had not tried before: iommu=soft.
> Tried to boot with that just now, and i don''t get the errors
anymore, and
> the tmp0.mpg file now contains data.
> Not sure if everything works ok now, I will do more tests in the course of
> this week.
> At least I''m one more step closer to running mythtv in domU again!
> 
Yeah, we''ve been updating the wiki pages lately.

pvops domU kernels do require iommu=soft, so that explains your earlier
problem.. :)

-- Pasi


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

> > Thanks for your input, i had read this page before, but now noticed
there
> > is one option mentioned there which i had not tried before:
iommu=soft.
> > Tried to boot with that just now, and i don''t get the errors
anymore, and
> > the tmp0.mpg file now contains data.
> > Not sure if everything works ok now, I will do more tests in the
course
> > of this week.
> > At least I''m one more step closer to running mythtv in domU
again!
> 
> Yeah, we''ve been updating the wiki pages lately.
> 
> pvops domU kernels do require iommu=soft, so that explains your earlier
>  problem.. :)
> 
> -- Pasi
I can now confirm that mythtv with 3 ivtv tuners is working well in my PV DomU.
I''ve had the system up and running for about a day now, and recorded 3 
parallel movies today.
Even when it ran out of disk space at one point, there were no unexpected 
issues in the DomU nor in the Dom0, and after cleaning up the disk, and 
restarting mythtv, recording continued without any problems.

I''m impressed!


Regards,
Mark.



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

On Wed, Mar 31, 2010 at 09:05:46PM +0000, Mark Hurenkamp
wrote:
> > > Thanks for your input, i had read this page before, but now
noticed there
> > > is one option mentioned there which i had not tried before:
iommu=soft.
> > > Tried to boot with that just now, and i don''t get the
errors anymore, and
> > > the tmp0.mpg file now contains data.
> > > Not sure if everything works ok now, I will do more tests in the
course
> > > of this week.
> > > At least I''m one more step closer to running mythtv in
domU again!
> > 
> > Yeah, we''ve been updating the wiki pages lately.
> > 
> > pvops domU kernels do require iommu=soft, so that explains your
earlier
> >  problem.. :)
> > 
> > -- Pasi
> 
> I can now confirm that mythtv with 3 ivtv tuners is working well in my PV
DomU.
> I''ve had the system up and running for about a day now, and
recorded 3
> parallel movies today.
> Even when it ran out of disk space at one point, there were no unexpected 
> issues in the DomU nor in the Dom0, and after cleaning up the disk, and 
> restarting mythtv, recording continued without any problems.
> 
> I''m impressed!
> 
Good to hear it works OK for you! 
I CC''d Konrad, who''s probably interested about positive
feedback :)

-- Pasi


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

Mark Hurenkamp said the following:
> I can now confirm that mythtv with 3 ivtv tuners is working well in my PV
DomU.
> I''ve had the system up and running for about a day now, and
recorded 3
> parallel movies today.
> Even when it ran out of disk space at one point, there were no unexpected 
> issues in the DomU nor in the Dom0, and after cleaning up the disk, and 
> restarting mythtv, recording continued without any problems.
>
> I''m impressed!
>
>   
Just catching up on my list reading.

I''ve been running a mythtv backend on a domU for a while now with 
reasonable results.  Two things I''ve had issues with that you may run 
into are:

- PCI latency - the ivtv driver tries to change the pci latency for the 
tuners when it is loaded, but can''t because it doesn''t have
permission.
I''ve tried to set the latency on boot from the dom0, but without 
success.  Changing it manually seems to work fine, not sure what the 
issue is here, but haven''t spent any real time looking into it.  More
on
mythtv and pci latency here http://www.mythtv.org/wiki/PCI_Latency
- DMA interrupts issues - about once a month my system starts reporting 
problems with DMA interrupts.  Sometimes this only takes out a single 
ivtv tuner, other times it takes out a NIC, HD, the Mythtv DomU, or the 
Dom0.  The only way to sort it out is to reboot the Dom0.  I''ve spent 
more time on this than I''d care to admit, and have very little to show 
for the work.  Because it happens so infrequently I''m not even 100%
sure
it''s ivtv related.  Most recently I''ve pulled the ivtv tuners
out of the
system entirely and am hoping that in a month and a bit I''ll know 
whether ivtv is involved or not.

- Ben

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

> > I can now confirm that mythtv with 3 ivtv tuners is working well in my
PV
> > DomU. I''ve had the system up and running for about a day now,
and
> > recorded 3 parallel movies today.
> > Even when it ran out of disk space at one point, there were no
unexpected
> > issues in the DomU nor in the Dom0, and after cleaning up the disk,
and
> > restarting mythtv, recording continued without any problems.
> >
> > I''m impressed!
> 
> Just catching up on my list reading.
> 
> I''ve been running a mythtv backend on a domU for a while now with
> reasonable results.  
The reason i was impressed is that it works on xen 4.0 with a pvops kernel, 
which only recently got a working pciback/pcifront implementation to do pci 
passthrough.
> Two things I''ve had issues with that you may run into are:
> 
> - PCI latency - the ivtv driver tries to change the pci latency for the
> tuners when it is loaded, but can''t because it doesn''t
have permission.
> I''ve tried to set the latency on boot from the dom0, but without
> success.  Changing it manually seems to work fine, not sure what the
> issue is here, but haven''t spent any real time looking into it. 
More on
> mythtv and pci latency here http://www.mythtv.org/wiki/PCI_Latency
Thanks for the info, the tweaks on that page may prove useful if i need to 
improve performance on my system (could have helped my previous setup).
My new (P55 based) system doesn''t seem to have any problems with
throughput or
latency at this point.
> - DMA interrupts issues - about once a month my system starts reporting
> problems with DMA interrupts.  Sometimes this only takes out a single
> ivtv tuner, other times it takes out a NIC, HD, the Mythtv DomU, or the
> Dom0.  The only way to sort it out is to reboot the Dom0.  I''ve
spent
> more time on this than I''d care to admit, and have very little to
show
> for the work.  Because it happens so infrequently I''m not even
100% sure
> it''s ivtv related.  Most recently I''ve pulled the ivtv
tuners out of the
> system entirely and am hoping that in a month and a bit I''ll know
> whether ivtv is involved or not.
Haven''t seen these issues at all... not even on my old 1.2Ghz AMD Duron
based
system... What version of xen and linux kernel are you running?


Mark.

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

Mark Hurenkamp said the following:
>>
>> - PCI latency - the ivtv driver tries to change the pci latency for the
>> tuners when it is loaded, but can''t because it
doesn''t have permission.
>> I''ve tried to set the latency on boot from the dom0, but
without
>> success.  Changing it manually seems to work fine, not sure what the
>> issue is here, but haven''t spent any real time looking into
it.  More on
>> mythtv and pci latency here http://www.mythtv.org/wiki/PCI_Latency
>>     
> Thanks for the info, the tweaks on that page may prove useful if i need to 
> improve performance on my system (could have helped my previous setup).
> My new (P55 based) system doesn''t seem to have any problems with
throughput or
> latency at this point.
>   
If your previous set-up wasn''t on a virtual system it wouldn''t
have been
an issue because the ivtv driver would have adjusted the latency when it 
loaded.
>   
>> - DMA interrupts issues - about once a month my system starts reporting
>> problems with DMA interrupts.  Sometimes this only takes out a single
>> ivtv tuner, other times it takes out a NIC, HD, the Mythtv DomU, or the
>> Dom0.  The only way to sort it out is to reboot the Dom0. 
I''ve spent
>> more time on this than I''d care to admit, and have very little
to show
>> for the work.  Because it happens so infrequently I''m not even
100% sure
>> it''s ivtv related.  Most recently I''ve pulled the
ivtv tuners out of the
>> system entirely and am hoping that in a month and a bit I''ll
know
>> whether ivtv is involved or not.
>>     
> Haven''t seen these issues at all... not even on my old 1.2Ghz AMD
Duron based
> system... What version of xen and linux kernel are you running?
>
>   
It''s good to know you haven''t had issues.

I''m currently running kernel 2.6.26-2 from Debian Lenny (but on a Sarge
based dom0) with xen 3.4.2 from source.  Previously I was running 2.6.18 
/ xen 3.2.0.

It could very well be a hardware issue, it''s running on an old AMD 
Athlon 2600+, which is what I''m hoping to be able to confirm/deny if
the
system stays up past ~45 days without the ivtv tuners in it.

- Ben


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

Sorry, just want to make sure I know what exactly worked that well, as I want to
try it
on my 3 DVB-C VDR system: the pv_ops kernel used is that which comes default
with Xen 4.0?

BR,
Carsten.

----- Originalnachricht -----
Von: Mark Hurenkamp <mark.hurenkamp@xs4all.nl>
Gesendet: Don, 1.4.2010 00:55
An: xen-users@lists.xensource.com
Cc: Ben Holt <ben@computerdolt.com>
Betreff: Re: [Xen-users] [SOLVED] Anyone have success with ivtv in a pvm? I	got
DMA TIMEOUT messages on xen-next/4.0-rc9-pre...
> > I can now confirm that mythtv with 3 ivtv tuners is working well in my
PV
> > DomU. I''ve had the system up and running for about a day now,
and
> > recorded 3 parallel movies today.
> > Even when it ran out of disk space at one point, there were no
unexpected
> > issues in the DomU nor in the Dom0, and after cleaning up the disk,
and
> > restarting mythtv, recording continued without any problems.
> >
> > I''m impressed!
> 
> Just catching up on my list reading.
> 
> I''ve been running a mythtv backend on a domU for a while now with
> reasonable results.  
The reason i was impressed is that it works on xen 4.0 with a pvops kernel, 
which only recently got a working pciback/pcifront implementation to do pci 
passthrough.
> Two things I''ve had issues with that you may run into are:
> 
> - PCI latency - the ivtv driver tries to change the pci latency for the
> tuners when it is loaded, but can''t because it doesn''t
have permission.
> I''ve tried to set the latency on boot from the dom0, but without
> success.  Changing it manually seems to work fine, not sure what the
> issue is here, but haven''t spent any real time looking into it. 
More on
> mythtv and pci latency here http://www.mythtv.org/wiki/PCI_Latency
Thanks for the info, the tweaks on that page may prove useful if i need to 
improve performance on my system (could have helped my previous setup).
My new (P55 based) system doesn''t seem to have any problems with
throughput or
latency at this point.
> - DMA interrupts issues - about once a month my system starts reporting
> problems with DMA interrupts.  Sometimes this only takes out a single
> ivtv tuner, other times it takes out a NIC, HD, the Mythtv DomU, or the
> Dom0.  The only way to sort it out is to reboot the Dom0.  I''ve
spent
> more time on this than I''d care to admit, and have very little to
show
> for the work.  Because it happens so infrequently I''m not even
100% sure
> it''s ivtv related.  Most recently I''ve pulled the ivtv
tuners out of the
> system entirely and am hoping that in a month and a bit I''ll know
> whether ivtv is involved or not.
Haven''t seen these issues at all... not even on my old 1.2Ghz AMD Duron
based
system... What version of xen and linux kernel are you running?


Mark.

_______________________________________________
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

On Thursday 01 April 2010 08:14:42 Carsten Schiers
wrote:
> Sorry, just want to make sure I know what exactly worked that well, as I
>  want to try it on my 3 DVB-C VDR system: the pv_ops kernel used is that
>  which comes default with Xen 4.0?
What i''m running right now, is xen-unstable (mine is at 4.0-rc9-pre),
with
Jeremy Fitzhardinge''s pvops kernel from his xen/next branch. (which is 
currently 2.6.32 based).

This pvops kernel from Jeremy is aimed at integrating dom0 support into
the mainline kernel at some point in the (hopefully near) future, and will
probably be the default kernel of choice for 4.0.

I noticed that a new xen-4.0-testing branch appeared recently, this is 
probably the best xen branch to work with if you want to try 4.0.
For the pvops kernel, you may be best of starting with the xen/stable branch 
of Jeremy.


Regards,
Mark.

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

Ah, thanks. Do I change kernel version by changing mk.linux-2.6-pvops? 
Currently it builds 2.6.31.12.


BR,
Carsten.

-----Ursprüngliche Nachricht-----
Von: Mark Hurenkamp [mailto:mark.hurenkamp@xs4all.nl] 
Gesendet: Freitag, 2. April 2010 01:47
An: Carsten Schiers
Cc: xen-users@lists.xensource.com
Betreff: ***SPAM*** Re: AW: [Xen-users] [SOLVED] Anyone have success 
with ivtv in a pvm? I got DMA TIMEOUT messages on 
xen-next/4.0-rc9-pre...

On Thursday 01 April 2010 08:14:42 Carsten Schiers
wrote:
> Sorry, just want to make sure I know what exactly worked that well, as 
I
>  want to try it on my 3 DVB-C VDR system: the pv_ops kernel used is 
that
>  which comes default with Xen 4.0?
What i''m running right now, is xen-unstable (mine is at 4.0-rc9-pre), 
with
Jeremy Fitzhardinge''s pvops kernel from his xen/next branch. (which is 
currently 2.6.32 based).

This pvops kernel from Jeremy is aimed at integrating dom0 support into
the mainline kernel at some point in the (hopefully near) future, and 
will
probably be the default kernel of choice for 4.0.

I noticed that a new xen-4.0-testing branch appeared recently, this is 
probably the best xen branch to work with if you want to try 4.0.
For the pvops kernel, you may be best of starting with the xen/stable 
branch 
of Jeremy.


Regards,
Mark.



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

> Ah, thanks. Do I change kernel version by changing mk.linux-2.6-pvops?
> Currently it builds 2.6.31.12.
I don''t know how that would work, i used git to checkout
Jeremy''s kernel
in a different directory, and installed it separately.

Mark.
>
>
> BR,
> Carsten.
>
> -----Ursprüngliche Nachricht-----
> Von: Mark Hurenkamp [mailto:mark.hurenkamp@xs4all.nl]
> Gesendet: Freitag, 2. April 2010 01:47
> An: Carsten Schiers
> Cc: xen-users@lists.xensource.com
> Betreff: ***SPAM*** Re: AW: [Xen-users] [SOLVED] Anyone have success
> with ivtv in a pvm? I got DMA TIMEOUT messages on
> xen-next/4.0-rc9-pre...
>
> On Thursday 01 April 2010 08:14:42 Carsten Schiers wrote:
>> Sorry, just want to make sure I know what exactly worked that well,  
>> as
> I
>> want to try it on my 3 DVB-C VDR system: the pv_ops kernel used is
> that
>> which comes default with Xen 4.0?
>
> What i''m running right now, is xen-unstable (mine is at
4.0-rc9-pre),
> with
> Jeremy Fitzhardinge''s pvops kernel from his xen/next branch.
(which is
> currently 2.6.32 based).
>
> This pvops kernel from Jeremy is aimed at integrating dom0 support  
> into
> the mainline kernel at some point in the (hopefully near) future, and
> will
> probably be the default kernel of choice for 4.0.
>
> I noticed that a new xen-4.0-testing branch appeared recently, this is
> probably the best xen branch to work with if you want to try 4.0.
> For the pvops kernel, you may be best of starting with the xen/stable
> branch
> of Jeremy.
>
>
> Regards,
> Mark.
>
>
>

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

On Fri, Apr 02, 2010 at 11:56:31PM +0200, Mark Hurenkamp
wrote:
>> Ah, thanks. Do I change kernel version by changing mk.linux-2.6-pvops?
>> Currently it builds 2.6.31.12.
>
> I don''t know how that would work, i used git to checkout
Jeremy''s kernel
> in a different directory, and installed it separately.
>
http://wiki.xensource.com/xenwiki/XenParavirtOps

That wiki page has instructions for how to change the branch.

-- Pasi
> Mark.
>
>>
>>
>> BR,
>> Carsten.
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Mark Hurenkamp [mailto:mark.hurenkamp@xs4all.nl]
>> Gesendet: Freitag, 2. April 2010 01:47
>> An: Carsten Schiers
>> Cc: xen-users@lists.xensource.com
>> Betreff: ***SPAM*** Re: AW: [Xen-users] [SOLVED] Anyone have success
>> with ivtv in a pvm? I got DMA TIMEOUT messages on
>> xen-next/4.0-rc9-pre...
>>
>> On Thursday 01 April 2010 08:14:42 Carsten Schiers wrote:
>>> Sorry, just want to make sure I know what exactly worked that well,
>>> as
>> I
>>> want to try it on my 3 DVB-C VDR system: the pv_ops kernel used is
>> that
>>> which comes default with Xen 4.0?
>>
>> What i''m running right now, is xen-unstable (mine is at
4.0-rc9-pre),
>> with
>> Jeremy Fitzhardinge''s pvops kernel from his xen/next branch.
(which is
>> currently 2.6.32 based).
>>
>> This pvops kernel from Jeremy is aimed at integrating dom0 support  
>> into
>> the mainline kernel at some point in the (hopefully near) future, and
>> will
>> probably be the default kernel of choice for 4.0.
>>
>> I noticed that a new xen-4.0-testing branch appeared recently, this is
>> probably the best xen branch to work with if you want to try 4.0.
>> For the pvops kernel, you may be best of starting with the xen/stable
>> branch
>> of Jeremy.
>>
>>
>> Regards,
>> Mark.
>>
>>
>>
>
>
> _______________________________________________
> 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