> For the complete documentation index, see [llms.txt](https://docs.tvheadend.org/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tvheadend.org/documentation/installation/virtualisation-proxmox.md).
# Virtualisation - Proxmox
Tvheadend can be installed either as a VM (linux guest OS) or as an LXC container.
The TV tuner must be passed through to the VM/container
## Proxmox VM - Debian
* Host OS: Proxmox 8.3.1
* Guest OS: Debian 12.8 (bookworm) amd64
Note: the TV tuner is passed through from the Host to Guest (PCI or USB pass through) - installation of the tuner is done on the VM/Guest OS
1. Install Debian as a VM with at least the minimum requirements - command-line only installs (without desktop environment) recommended to minimise resource usage
2. Update Debian to latest package versions with
```sh
# apt update
# apt upgrade
```
3. Install Curl package to allow set up of Apt repository
```bash
# apt install curl
```
4. Set up Apt repository - for DEB packages using Curl
```bash
# curl -1sLf 'https://dl.cloudsmith.io/public/tvheadend/tvheadend/setup.deb.sh' | sudo -E bash
```
5. Update Apt package list
# apt update
6. Install Tvheadend
```bash
# apt install tvheadend
```
7. Passthrough TV tuner hardware to VM guest OS\
(this can be done through the proxmox web GUI)
8. Install the TV tuner on the VM guest OS
9. Access the Tvheadend web configuration interface at:\
https\://\:9981
10. Continue setup/configuration (in next section)
## Proxmox LXC - Debian
* Host OS: Proxmox 8.3.1
* Container Template (Guest OS): Debian 12 standard (12.2-1-amd64)
Note: the TV tuner is first installed on the Host OS (Proxmox) and then passed through to the LXC container (see below) - the pass through must be the whole enumerated device in /dev/dvb/adapter0/\ and not /dev/usb or /dev/pci as the LXC does not have the kernel modules to install the device.
1. Set up an LXC container with at least the minimum requirements\
The Debian 12 standard LXC template can be downloaded from the Proxmox web GUI
2. Update Debian packages to latest version\
Note: a lot of packages will be updated as the Proxmox LXC template is quite old
```bash
# apt update
# apt upgrade
```
3. Install Curl package to allow set up of Apt repository
```bash
# apt install curl
```
4. Set up Apt repository - for DEB packages using Curl
```bash
# curl -1sLf 'https://dl.cloudsmith.io/public/tvheadend/tvheadend/setup.deb.sh' | sudo -E bash
```
5. Update Apt package list
# apt update
6. Install Tvheadend
```bash
# apt install tvheadend
```
7. Passthrough TV tuner hardware to VM guest OS\
\
Passthrough all the devices files under /dev/dvb/adapter0/\
Set UID=0 (root) and GID=44 (video) for all devices\
\
\- GUI method:\
From web GUI, nagivate to container, resources, add, pass through - add the devices:\
\
/dev/dvb/adapter0/demux0\
/dev/dvb/adapter0/dvr0\
/dev/dvb/adapter0/frontend0\
/dev/dvb/adapter0/net0\
\
OR\
\
\- Command-line method:\
Manually edit the LXC config file at: /etc/pve/lxc/\.conf\
Add in the following lines\
\
/dev/dvb/adapter0/demux0,gid=44,uid=0\
/dev/dvb/adapter0/dvr0,gid=44,uid=0\
/dev/dvb/adapter0/frontend0,gid=44,uid=0\
/dev/dvb/adapter0/net0,gid=44,uid=0
8. Restart LXC container to allow passthrough
9. Access the Tvheadend web configuration interface at:\
https\://\:9981
10. Continue setup/configuration (in next section)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.tvheadend.org/documentation/installation/virtualisation-proxmox.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.