Search results

A follow-up 4 years later: See my new thread #134423 and my bug report #4983.

After an hour's debugging, I draw the conclusion that it's a bug in PVE Firewall. I've submitted it as #4983. To whoever stumbling upon this issue, go add nf_conntrack_allow_invalid: 1 to your host firewall config. This is the best workaround available at the moment. The reason why the RST...

Worked out the ACK number issue: By default tcpdump prints sequence numbers relative to previous packets. Adding -S to tcpdump options shows the correct numbers. Nothing wrong on this side. Still wondering what's wrong with conntrack INVALID state.

I'm running into exactly the same issue as #56300. The previous thread was old and I have more details on that, so I thought I'd just open a new thread. PVE version is almost up-to-date: proxmox-ve: 8.0.2 (running kernel: 6.2.16-6-pve) VM → Firewall → Options → Firewall = No: No effect VM →...

Unfortunately no. Since Proxmox VE is Debian under the hood, some level of familiarity with Linux CLI is required. Basic tasks like text editing shouldn't be too hard if you follow some tutorials online. Good luck on your learning.

Correct. Normally you just create another dataset for your VM/CT, like z-media/ampache2. If you really need the exact name, there's zfs rename to the rescue. In the zfs list output, if the mountpoint is a single dash, it's a ZVOL (obviously cannot be mounted by ZFS). If it's anything else...

TASK ERROR: unable to parse zfs volume name 'ampache' Your ZFS volume z-media/ampache is a dataset, not a ZVOL volume that PVE is expecting. You should give it a ZVOL to work with, like zfs create -s -V 64G z-media/ampache. For the extra disk, it's because PVE scans the given storage source...

1. ZFS keeps a record of which host OS last imported an array. If the array imports properly on the host but not the VM, try exporting it from the host first. You may also try zfs import -f in case of emergency but otherwise not recommended. 2. If the ZFS pool imports well, you can edit...

@namyounsu Thank you for the information. I've updated my blog article on https://ibug.io/p/49.

Trying to give this idea a bump. Given that Proxmox Offline Mirror tool is out, Rsync seems the best choice for it.

First, thanks to Proxmox GmbH for developing this wonderful open-source virtualization solution. I know of multiple universities and non-profits providing mirror for Proxmox repositories, and we're currently using lftp(1) to sync content via HTTP, which frequently causes de-sync. If Proxmox...

I can confirm pve-kernel-5.13.19-5-pve version 5.13.19-13 is having a good term with Windows KVM, including PCI passthrough (vfio-pci). Host is HP DL380 Gen 10 with Intel Xeon Scalable processors (Skylake). Thank you for the quick response.

@avladulescu For the time being we did put pve-qemu-kvm on hold. When we found that 9 KB MTU solved the issue for us, we released the hold and followed the latest versions. We've been running fine since. @benh7 Glad that I could help.

@avladulescu @benh7 Strangely enough, our issues were gone after enabling jumbo frame (9000 bytes MTU) on the management network where the problematic NIC is connected. You might want to give this a try unless you have incompatible devices. We were able to bisect the cause to QEMU 6.0 adding...

At grub screen, you can press e to edit grub configuration before booting. At that point, you can remove quiet from the kernel command line and then boot. There should be more output available, usually enough for you to locate the issue, like missing files or initramfs modules. Alternatively...

Can you be more specific about how "it doesn't come up"? For example, at which line does the boot sequence get stuck, or what do you observe in a faulty startup?

Well it's FreeBSD and it's beyond my knowledge. I thought it was a typical Linux system with ext4 because you mentioned resize2fs, which is for the ext filesystem family (ext2 / ext3 / ext4). You can consult guidances found online via Google-ing, like this one. The general idea is: Run any...

Depending on your VM type (LXC container or KVM full VM), you can use either pct resize or qm resize command. In the case of a KVM machine, you'll also need to manually resize the partition and then the filesystem manually.

We have a small PVE cluster that ran PVE 6.4, and when we upgraded them to PVE 7.0, our backup jobs for VMs failed (but not CTs). We have collected the following diagnoses. The majority of our compute servers are HPE ProLiant DL388 Gen10, with Intel X710-DA2 SFP+ NIC (HPE Ethernet 10Gb 2-port...

I'm managing a cluster of LXC containers with PVE 6.1. It's nice to be able to watch resource from the web interface, however I can't find how to horizontally scroll the graph, so I could only see resource usage in the last 70 minutes. Is there any way to get older usage history, preferably a...