search

jonpanozzo / OpenELEC

An OpenELEC (XBMC) appliance-built virtual machine designed for use with unRAID 6.0 beta 10a or later. Must have HVM / IOMMU capable hardware (Intel VT-x/VT-d AMD-V/Vi) to utilize VFIO for graphics card pass through to the virtual machine.
0 stars 2 forks source link

Openelec image source #1

Open piotrasd opened 9 years ago

piotrasd commented 9 years ago

Hi @eschultz Sorry this is not issue :) i just want ask do you have source which you use for build openelec image ? fork ? and could you share ? im ask becuase from years i was using own compiled version, with some patches for kodi, remote, skins etc.

I just start migrating from zotac id42 which was under TV, to unraid VM - Openelec and i just want also using my mods in vm OE.

Thanks

eschultz commented 9 years ago

Actually, most of my modding was to add additional kernel flags (mainly for VirtFS) and modifying the init script to allow a virtfs mapped folder to be mounted inside the VM. Haven't touched anything under kodi, skins, etc.

I might throw up another github repo (a fork of openelec's) with my changes in the next day or two

piotrasd commented 9 years ago

Great - thanks !!

piotrasd commented 9 years ago

any news in topic ? also maybe you can check if your patches/changes are still compatible with OE 5.0 ? because i saw you use 4.2.1

piotrasd commented 9 years ago

Hi @eschultz I have a request - because it looks like a frozen topic :( Could you make new image based on OE 5.0.2 or release your changes ?? then i will be could make myself ... i will be very grateful, even i can send some donation just tell me where ...

I just want finly switch off my zotac's nettops under TV's and use VM OE ... problem with network and PVR a was resolved by mount second LAN card and map do VM OE (this is temporary before vm OE will be can comunicate localy with unraid host and docker,)

jonpanozzo commented 9 years ago

Sorry piotrasd,

Eric has one more major project internally for us before he can be retasked to look at this. I can tell you this is DEFINITELY important to us and shouldn't take too much time, but it will probably be at least a week or two before I can get back to updating the VM.

jonpanozzo commented 9 years ago

Well, a quick update on this:

1) We were able to build OE 5.0.2 and get it to work. 2) We were able to do this using an OVMF virtual machine as opposed to the traditional methods we’ve been doing (more on this later)

The big problem now is that Eric was trying to create a build that would explicitly highlight the diffs in our build from the base, but it’s not working. The old method we have done works fine, but that doesn’t get you what you need. Will hit you back when we have something.

piotrasd commented 9 years ago

@ jonpanozzo Thanks for update :) in the meantime could you share with 5.0.2 image ? (or actual 5.0.4 ... )

About problem i hope you will be able with Eric resolve this, or if this will be to difficult maybe you can share with me full source (then i dont will be need diff's/patch's and i will be able to make my own modification or update in the future what i need.

i was try myself compile OE with all KVM guest stuff and replace in img or second method change in plugin disk RO to RW and update over catalog update puting KERNEL and SYSTEM but after restart do not boot anymore :( so i wait for news from you guys ...

Thanks for all work ...

eschultz commented 9 years ago

@piotrasd Sorry for the delay, I finished posting the source (now upgraded to 5.0.4) here: https://github.com/eschultz/OpenELEC.tv/tree/openelec-5.0-unraid

I'll continue to push updates to the openelec-5.0-unraid branch as new versions of OpenELEC hit the streets or any other changes we need to make it jive well with unRAID.

I'm in the process of compiling 5.0.4 now but you should be able clone my repo, checkout the openelec-5.0-unraid branch and run make unraid to build a new OpenELEC + unRAID fused baby :+1:

Let us know how the build works out!

piotrasd commented 9 years ago

WOW !!! great job guys !!!

jonpanozzo commented 9 years ago

No problem! This is very important to us. Combining the value of a storage solution with a media player and PVR into a single box will be a huge benefit.

I desperately want to buy a tuner card and try out TV Headend + OpenELEC, but just don’t have the time or the $$$ right now to do so. Please let me know how this works out and what else we can do to make this work better.

Sent from Windows Mail

From: piotrasd Sent: ‎Friday‎, ‎February‎ ‎27‎, ‎2015 ‎4‎:‎24‎ ‎AM To: jonpanozzo/OpenELEC Cc: jonp@lime-technology.com

WOW !!! great job guys !!!

— Reply to this email directly or view it on GitHub.

piotrasd commented 9 years ago

hi @jonpanozzo What DVB tuner you need ?? DVB-T ? DVB-S2 ? (this i have i can send you for free ;) ) let me know ...

I just back to home and i think i have already compiled .... so i will be testing ;) i know in the last version when i have PVR backend on host (unraid) i had problem with network

Maybe when will be possible comunicate over unraid host and KVM virtu localy problem will gone (for now i just map second LAN card special for VM OE)

jonpanozzo commented 9 years ago

Honestly not sure which one I need just yet and would hate for you to spend the cash to ship something to the US. Between time and money, time is the resource I’m most short on at this point.

I would like a recommendation though on what you feel has been the best unit for you. As for the OpenELEC picture freezing, is this with our VM / plugin or with your build. Our image uses VirtFS as the mechanism to communicate with storage on the host, negating the need to travel through the network at all.

To access your media through the VM, you browse the root filesystem from with OpenELEC and you will see a folder there called unraid. That folder will map to /mnt/user on your system, thereby exposing all your user shares to the VM. You can even make access to this data read only should you desire.

Now if there is something I’m missing on how TVHeadend works with KODI, please elaborate as I want to make sure I fully understand this. We should be able to make it so these applications can talk to each other through a unix socket, avoiding network and even filesystem level access altogether. This would be the equivalent of the two applications being installed within a single OS without virtualization (the fastest communication possible).

Sent from Windows Mail

From: piotrasd Sent: ‎Friday‎, ‎February‎ ‎27‎, ‎2015 ‎12‎:‎09‎ ‎PM To: jonpanozzo/OpenELEC Cc: jonp@lime-technology.com

hi @jonpanozzo What DVB tuner you need ?? DVB-T ? DVB-S2 ? (this i have i can send you for free ;) ) let me know ...

I just back to home and i think i have already compiled .... so i will be testing ;) i know in the last version when i have PVR backend on host (unraid) i had problem with network when i watching TV picture freezing every few sec and i get bufforing information. ( im suppose that why because this comunication betwen PVR backend (tvheadend on unraid) and frontend KODI was over router and over this same LAN card )

Maybe when will be possible comunicate over unraid host and KVM virtu localy problem will gone (for now i just map second LAN card special for VM OE)

— Reply to this email directly or view it on GitHub.

piotrasd commented 9 years ago

Hi I know about VirtFS ;) and movies from unraid shares (HDD) works briliant !!! Freezing picture i mean when i watch LiveTV

PVR backend (example VDR or tvheadend) comunicate over network IP on specific for PVR client port (example tvheadend: 9981-9982, vdr xvdr: 34890 etc.) they use some own protocol for that - this is not generic IPTV.

So on KVM OE - KODI in PVR client i setup ip of unraid (example 192.168.2.150, when KVM OE get from router example 192.168.2.155) i can`t use localhost or 127.0.0.1 to cominicate localy :(

So all packets from PVR Backend go to router from unraid IP and back over this same LAN card i suppose this make issue ...

And yes is possible just map DVB tuner to KVM OE and keep PVR backend on this same virtual machine and then backend PVR can communicate localy - but i never keep OE KODI running 24h - im just turn on when i something watch. And PVR backend i prefer keep 24h/7 online - because i record many stuff, sometime stream to phone when im out etc.