Hi @hd-- and @Neobin - ok, I suppose this explains it all then... Thank you very much, mystery has been solved. I can see there's no need to not pass through everything in a group then, as those devices are unusable to the host, once anything in the IOMMU group has been passed through.
Thanks a...
Thanks! I did apply, but I think it was better to run "ifreload -a" as that revealed the following: "warning: enp1s0f3: interface not recognized - please check interface configuration". I both tried another ethernet-cable and I also rebooted - same warning and still not working... hmm...
I also...
Hi,
I'm running Proxmox with pfSense virtualized and have been doing that for around 1,5 years now... Now I'm migrating to new hardware and began messing with the configuration. Out of the box Proxmox works just nice with a static IP AFAIR. What I usually do is quickly to install pfSense...
As mentioned, I'm using the incredibly bad solution with a cron-script that runs maybe every 5 minutes or something (cannot remember) and then it pings to see if the network works: BAD_SOLUTION - and automatically restarts the LXC, if no ping reply. If you mean a "proper/real" solution, I'm also...
I agree - extremely difficult to debug... But, I think it's an LXC-issue and not a proxmox-issue, found a few threads that sounds similar:
https://www.reddit.com/r/Proxmox/comments/uf2bnr/lxc_container_keeps_losing_its_ip_address/...
Okay, thanks... hmm, I don't have more ideas. If more people experience this problem, please write which LXC container you use/see this problem with, maybe we'll see a pattern that could lead to a real/proper fix instead of using this "automatic restart"-work-around...
I'm glad that worked. It's nice that "pct reboot" for my LXC fileserver only takes a few seconds (maybe 5-8 secs and it's up again). My LXC fileserver container is this one: https://www.turnkeylinux.org/fileserver - now it doesn't even reboot for up to 3 weeks. But in the beginning it was much...
Hi @adystech. Unfortunately I don't think that modified /etc/network/interfaces-file completed fixed it, because I found out that the problem persisted. My only - last - "solution" was/is to have a cronjob that pings my server every 5 minutes. If it cannot ping, it reboots the LXC... Basically...
Hi,
I'm facing a conundrum because Proxmox makes it easy to install and run a "Turnkey (LXC) fileserver" and I have a very small low-power proxmox-pc turned on 24/7 that I want to run 1-2 VMs on in addition to pfSense. The problem I'm facing is that after weeks, the "Turnkey (LXC) fileserver"...
No problem, to begin with I couldn't figure out how to make an "easy" representation or drawing - but now I think I have. And enp1s0f3 is "free" to use and configure in any way possible, as it's not meant to be used for anything else, except that I would like to be able to contact proxmox via a...
Right, at least that's how it works when there's a DHCP-server in the system. When there's no DHCP-server, I'm confused about what it means to have a gateway ip-address? Maybe it doesn't mean anything at all, without a DHCP-server?
Right, vmbr0 is passed through to pfSense which knows that this...
Hi
I've been running proxmox and pfsense virtualized for some months now and am relatively happy about it. The proxmox-server is headless so when I once in a while screw things up, I physically move it and lose all internet connectivity, then plugin HDMI and usb keyboard so I can see what is...
Hi,
I have installed a Turnkey-fileserver (LXC) to create SMB/CIFS and NFS-shares with low resources and fast disk I/O instead of having to create a VM (also because I've read it's a bad idea to install those things directly on the host). The problem is that after a few days, I usually cannot...
Hi, no, sorry I never completely figured this stuff out - except I think I did a workaround with letting the container be a privileged container - as I vaguely remember it. I'm not really using that machine anymore but will soon setup a new machine, so I you figure this stuff out, please share...
I've been a bit busy, have marked this converation as solved. I didn't test it, because I'm too busy and have already spend many hours on this. But I'm sure the solution here works https://bugzilla.proxmox.com/show_bug.cgi?id=3729#c6 (comment #6) and hopefully the fix will be in the next release...
I'm not so sure about that, how can you see the error doesn't come from proxmox-boot-tool? Correct me if I'm wrong, but I think proxmox-boot-tool exists with an error code 1 or something (at least not 0) and I think this is not permitted. So it falls back to the next line which is # umount...
I completely understand that - but thanks for confirming my idea about this... There's just so much stuff out there on the internet, so but I've found a really good thread here...
This is on your system, right? I don't think I can see that in my install.log-file. Can you post your install.log so I can compare mine and yours? But otherwise: Yes, I look very much to hearing what @Stoiko Ivanov has to say about this (and if I/we should fill in a bug report somewhere so it...
I must admit that when choosing ZFS over EXT4, I think it's really difficult to figure out which is better because there are many posts saying both this and that. So - I think you're right - neither ZFS nor EXT4 are 100% resilient towards power failures. But still: Isn't ZFS better? At least it...
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.