WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Re: Re: Re: MythTV and Xen

lists wrote:

> Bastiaan wrote:
>> lists wrote:
>>
>>   
>>> Bastiaan wrote:
>>>     
>>>> lists wrote:
>>>>
>>>>   
>>>>       
>>>>> Hello All,
>>>>>
>>>>> Is anyone successfully running MythTV in either a Dom0 or DomU?  I
>>>>> have mythtv running with 4 PCI Hauppauge Nova-T DVB cards in a C2D
>>>>> system
>>>>> with a G33 chipset mobo under OpenSUSE 10.3.  Everything works
>>>>> perfectly under the x86-64 kernel, as soon as I reboot into the Xen
>>>>> kernel I get picture tearing and eventually mythtv will crash, usually
>>>>> with a glibc
>>>>> malloc error.  The best way I can describe the picture tearing is that
>>>>> it's almost like the TV signal has become very weak, there are lots of
>>>>> mpeg artifacts on the screen like squares of static image and blocks
>>>>> of strange coloured pixels.
>>>>>
>>>>> I'm open to suggestions of other distros to try.  Fedora Core 8
>>>>> springs to mind as a possibility since it was only recently released
>>>>> so should have a very up-to-date version of Xen included.
>>>>>
>>>>> Kind regards,
>>>>>
>>>>> Steve.
>>>>>     
>>>>>         
>>>> I got mythtv working in xen, both te backend and frontend run in
>>>> domU's, sharing the dom0 with some other (distcc) domU's.
>>>> I haven't had any trouble with is.
>>>> Distro is gentoo, on amd64.
>>>> If you have any specific questions, you can always mail me off-list (I
>>>> do not check the lists too often)
>>>>
>>>>   
>>>>       
>>> Hi Bas,
>>>
>>> Thanks for replying. It would be useful to keep this discussion on the
>>> list so that other people can benefit if they have a similar problem and
>>> search the list.
>>>     
>>
>>
>>
>> I'll keep all reply's on the list, just send me an email if you need
>> (urgent) info. I do check my inbox several times a day, lists more like
>> once every two weeks...
>>
>>
>>   
>>> Could you let me know what kernel version and xen version you are using.
>>> Also, what hardware are you using for your backend? I am especially
>>> interested in the motherboard, CPU and TV cards that you're using.
>>>     
>>
>> I use the gentoo distribution, and everything is straight from portage.
>> xen-sources and xen are the current ~amd64 (thats gentoo unstable for
>> amd64)
>> kernel = 2.6.20 and xen 3.1.2
>>
>>   
> I'm using kernel 2.6.22 but I'm not sure how I go about finding the xen
> version.

there is no ebuild in portage for 2.6.22 yet, 2.6.20 is the latest available
xennified kernel in gentoo.

> 
>> Motherboard is a gigabyte board, ill have to look up the exact type
>> later, i am not at home right now.
>> CPU's are AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ (3200+ for file
>> backends)
>>
>> Capturecards are all WinTV cards. All anolog input. I am experimenting
>> with a TV over IP provider here in the Netherlands, but nut much luck
>> yet!
>>
>>   
> Do you have to pass any boot arguments such as noacpi, noapic or
> irqpoll? (I'm not sure if I spelt those arguments correctly, I can't
> remember them without my notes.)

I used to add the noapic parameter, but that seems to be fixed now, all i've
got left are framebuffer arguments and evms.

> 
> TV over IP, sounds interesting! :-)

The provider hooks us up on a vpn, where all channels are broadcasted, and
video on demand is unicasted to the settopboxes. Problem is the
authorisation (handshake) between settopbox and server... 

We will work this out, eventually ;)

> 
>>> Ultimately, I would like to be able to pass the DVB cards to the DomU
>>> and run the backend in a DomU. This would make upgrading easier since I
>>> could take a copy of the current myth backend, upgrade it and if
>>> something doesn't work I could simply boot up the original DomU. :-)
>>>
>>>     
>>
>> That was one of the reasons i made this setup.
>>
>>   
>>> Regards,
>>>
>>> Steve.
>>>
>>>     
>>>> regards,
>>>>  Bas
>>>>
>>>>
>>>> _______________________________________________
>>>> Xen-users mailing list
>>>> Xen-users@xxxxxxxxxxxxxxxxxxx
>>>> http://lists.xensource.com/xen-users
>>>>
>>>>
>>>>       
>>
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
>>
>>



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