I started editing mxl58x.conf to choose the mode:
nano /etc/modprobe.d/mxl58x.conf
options mxl58x mode=1
reboot
And then the right version of pve-headers:
apt-cache search pve-headers
apt install pve-headers-$(uname -r)
Finally downloaded and installed the drivers:
wget...
I marked this thread as SOLVED after following the suggestions I received here.
I ended using a Turnkey fileserver plus the transmission torrent client, each one installed in a separated LXC with mountpoints for a common disk partition created in Proxmox host.
Thanks for all the help.
Thanks @Stefan_R
As you remind "mountpoints are not supported for full VMs".
I also tried the NFS approach but I had problems in the recognition of the NFS share by the container.
Where can I find information about those "feature flags"?
Thanks @mbosma!
I did something similar on a influxdb LXC. The database engine was installed in the container and the data was in a partition that I mounted in the host and passed to the LXC editing its conf file with a line similar with yours (mp0: ...).
But in the case of a OpenMediaVault VM...
Hi
I was trying to add to my Proxmox system the NAS + BitTorrent client functionalities.
After searching a bit I opted by the following:
- NAS: OpenMediaVault
- BitTorrent client: transmission
I found some tutorials to install OpenMediaVault in a Proxmox VM using an ISO which I did and had no...
Yes, that was my initial idea but this can not originate a eventual deadlock?
That is, imagine that for some reason I change something incorrectly in my pfSense settings that do not start its LAN the way I need, and then "Incorrect pfSense" => "No Proxmox host access" => "No pfSense error...
Thanks @vshaulsk for the quick reply!
The problem is that my ISP is very restrictive regarding its router. The most I could managed was to have an DMZ IP in its LAN.
I already have my pfSense VM working but please clarify me one thing:
How many NICs are you using?
The image shows two:
- one for the pfsense LAN
- one for the pfsense WAN
But that means that you are using the same IP for pfsense WAN and for Proxmox Host?
I tried to do that and did not worked...
After Googling a bit I ran the following command that confirm a 27s delay due to systemd-udev-settle.service:
root@pve:~# /usr/bin/systemd-analyze blame
27.102s systemd-udev-settle.service
5.413s pve-daily-update.service
4.581s pve-guests.service
2.009s...
Hi
I noticed in the last days that my Proxmox is taking more time to boot then normal.
When I watched the boot messages I can see the following:
Reading all physical volumes. This may take a while...
Found volume group "pve" using metadata type lvm2
/sbin/modprobe failed: 1
Can't process LV...
Well... let me clarity one last thing.
The problem was not Ubuntu16.04 after all!
The problem was the way I was editing the conf file of the container!
Let me explain...
I was using a container that had several snapshots, and for each one is created a new section in the conf file.
I though that...
Just to say that in fact with a Alpine template (default_20190224_amd64.tar.xz)... IT WORKS!!! :)
But why the template I was using (ubuntu-16.04-standard_16.04.5-1_amd64.tar.gz) did not?!?
By the way, I just also tried the ubuntu-18.04-standard_18.04.1-1_amd64.tar.gz template and ALSO WORKED...
Even unmounting it from the host I still can not access it inside the container!
I noticed that the /etc/fstab inside the container is still empty. Could not this be a problem?
Any other tip on how to solve this?
Thanks
PS - If I can not solve this I will try to do it through a NFS...
I know, I know there are here a lot of posts about this issue but I still can not do this apparently easy task! :(
The majority of those posts say that I need to edit the container conf file with the a line similar with:
mp0: /dev/sdb1,mp=/mnt/ext,backup=0
The container starts without any...
After contacting nicolai (the author of the YouTube video I already mentioned) he gave me the solution!
It is probably obvious to the majority of people here but for me was the key!
I need to create a privileged container!
With that the adapters already appear in the TvHeadend:
Can this problem be a question of permissions?
If I list the adapters in the host I get:
root@pve:~# ls -la /dev/dvb
total 0
drwxr-xr-x 10 root root 200 May 12 13:32 .
drwxr-xr-x 21 root root 4680 May 12 13:32 ..
drwxr-xr-x 2 root root 120 May 12 13:32 adapter0
drwxr-xr-x 2 root root 120...
I need to use a DVB-S2 card (TBS6909) on Proxmox.
In fact all I need is to use a TVHeadend app to stream some satellite TV channels inside my network.
It seems that the use in a VM is more tricky since it needs to be on a separate IOMMU group (someting that in my case does not happens as you...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.