[mythtv-users] ATSC Unwatchable

Scot Kreienkamp skreien at wcnet.org
Fri Sep 14 02:27:21 UTC 2012



From: mythtv-users-bounces at mythtv.org
[mailto:mythtv-users-bounces at mythtv.org] On Behalf Of Joseph Fry
Sent: Tuesday, September 11, 2012 10:26 PM
To: Discussion about MythTV
Subject: Re: [mythtv-users] ATSC Unwatchable



Do you mean running a hypervisor on the machine beside MythTV, or running
MythTV in a VM?

I've been running a CentOS 6 box with software raid 5, Silicondust ATSC
tuner, and VirtualBox with a Windows 7 VM all on the same box for months
with no problem.  The MythTV has always been running on the base OS though,
not in the VM.  Before that I ran a NextPVR (formerly GBPVR) instance under
a Windows 7 VM in VirtualBox with no problems at all for well over a year.

-----Original Message-----
From: mythtv-users-bounces at mythtv.org
[mailto:mythtv-users-bounces at mythtv.org] On Behalf Of Devin Heitmueller
Sent: Sunday, September 09, 2012 5:55 PM
To: Discussion about MythTV
Subject: Re: [mythtv-users] ATSC Unwatchable

On Sun, Sep 9, 2012 at 4:47 PM, Keith Wait <kwait at alumni.rice.edu> wrote:
> Here's an overview of my setup:
> xbmcbuntu (based on oneiric), running kernel 3.0.0-22-xen-dom0 (so
> running the xen hypervisor).

Wow, please seriously don't tell me you've been running a hypervisor all
this time and are just mentioning this now.  If so, then you've just engaged
in a colossal waste of my time.

Hypervisors are not supported, in particular on the backend.  They screw
with the PCI latency, causing packets to get dropped.

Think it's not the hypervisor?  Prove it.  Do a stock install of the OS
without the hypervisor and report back in if you're still having problem.

As an intermediate step, you may also wish to try a *current* LiveCD with
the same 3.0.0 kernel but not in hypervisor mode.  At least that lets you do
an apples-to-apples comparison with the same kernel revision.


First, don't top post.


Second... Xen works differently than VMware or  Virtualbox... both of those
operate ON TOP of an OS.... hypervisors like Xen and HyperV operate below
the OS... the DOM0 OS is only there to manage the hypervisor, it's actually
virtualized itself.



May I remind you that top (or bottom) posting is a preference.  I say each
to his own.  Personally, I hate it when people bottom post.  When I open a
message I don't like scrolling all the way to the bottom to see the new


I'm aware of how hypervisors operate.  I wasn't sure if the same PCI latency
COULD be induced by running a hypervisor inside the base OS as opposed to
running the OS on the hypervisor, which is why I asked for clarification.
Each hypervisor/platform have their own intricacies, and I'm not familiar
with Xen.  I also don't want to run into potential problems in the future
with my own rig.  



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20120913/186bd795/attachment.html>

More information about the mythtv-users mailing list