Search results

Thanks for your hard work on this @spirit I'll definitely be keeping an eye on this.

@Helmut101 what you're saying isn't quite correct, but I realize my explanation above is misleading. Per the bug report, with zvol swap devices, high memory operations hang indefinitely despite there being a lot of swap space available. So this bug occurs during high memory stress situations...

@spirit That did the trick, thanks for explaining! Simple solution.

Worked for me. Thanks @chudak and @pcready.cl! I was also having a related issue where Proxmox GUI was logging me out every 30 seconds due to clocks being out of sync.

Hey all, I have a relatively uncomplicated setup but I can't for the life of me figure out how to pass tagged traffic from a VM through Proxmox. Probably something dumb but I'd love another set of eyes to help me debug. I have 2 nics on my server: eno1 and eno2. I want untagged VLAN11 (11U)...

No, they're not fixed yet. Per this AskUbuntu post that explains the bug well: Therefore, use swap on ZFS at your own risk. Based on my personal experience, I've never filled up 8GB of swap, so this isn't a big risk to me. However in a production environment I could see this being a huge issue...

This is actually a great question, and I'm surprised nobody has posted a solution yet. You have to create a ZFS swap pool. If you try to create a swapfile the old-fashioned way, you'll see the error root@PVE1:~# swapon /swapfile swapon: /swapfile: skipping - it appears to have holes. Later...

Followed and starred! Thank you for the hard work!

Just ran into this issue after having shut down a host and recycling the parts. Something got messed up in my cluster-manager, because pvecm expected 1 did not allow me to log back into the host via web GUI. I think it was because I had configured a QDevice, although I could not remove the...

Looks great, using it now. Thanks for maintaining it.

I'll add a few nuances to my configuration from what @dlasher posted: lxc mount $CTID did not work for me, I had to use pct mount $CTID and pct enter $CTID. Proxmox must think the container is running already for pct enter to work, unfortunately. I didn't have good luck with chroot when the...

Thanks @dlasher, you saved my bacon!

Glad I could help some users out. :)

Hi Mikenewmediary, thanks for reaching out. Unfortunately I posted this over 3 years ago and my memory is rather foggy on how exactly I ended up working this specific issue out. In general, I would assume guest memory issues are NOT Proxmox but rather the guest OS. Proxmox is really good at...

All, First off, thank you for the helpful write-up. I was able to get FreeNAS set up, and the iSCSI connection initiated and verified. I did have some trouble and frustrations along the way that I was able to get resolved. They were mostly due to me misinterpreting @anatoxin and @wits-zach's...

I haven't tried removing the "bond-xmit-hash-policy layer2+3" stanza, will give that a try when I have access to the server tonight. I am seeing on my NAS's syslog, I get lots of: arp: 192.168.0.3 moved from 30:9c:23:03:ce:a7 to 00:26:55:e2:c0:e4 on lagg0 arp: 192.168.0.5 moved from...

Do you have a power-saving feature enabled in your BIOS for the NIC?

Hi there! Reviving this thread because I'm having strange issues with ARP, LACP and my Cisco switch. The symptoms are Corosync fails occasionally on startup given certain routing conditions. Strangely enough, Corosync starts when I use the bonded network, but fails when I use the unbonded...

Something worth noting here is that "qemu64" is going to be more compatible for live migration between AMD and Intel or between different generations of processors. I believe that most of the issues I've been having with Ryzen are because I use live migration between my Ryzen 1700 and my Intel i5.

I know this is an older post but I figured I would post a temporary, possibly dangerous solution since it might circumvent dependencies. I got this error when I downgraded proxmox-ve then tried to re-upgrade it at a later date. This likely applies to anyone having issues related to: /bin/sh: 1...