Search results

Not at the moment, but you could work around by extracting to a seperate folder and using rsync (with --delete) to merge them.

For a RAID0, metadata mirroring doesn't make too much of a difference, both in terms of consistency and performance. It might help recover data from a slightly damaged disk.

Would make sense as a feature request for VM restore, though at least you can restore entire folders. For CTs this is already possible via the normal 'proxmox-backup-client' restore method, see here: https://pbs.proxmox.com/docs/backup-client.html#restoring-data

Nodes in einem cluster müssen auf der gleichen version sein, zumindest in Sachen major version (also PVE 6 und 7) ist das schon ein hard-requirement.

How do you mean "without edit config"? To change the behaviour of the ssh daemon in the container, you must edit it... If you mean how to edit it without SSHing into the container, you could use 'pct push' for example (see 'man pct'), or even just create a template you like and make (linked)...

For an OPNsense? Most likely not. QEMU's EPYC model is very close to real hardware, and only some esoteric features (as well as nesting) gets disabled, nothing that would slow down a router AFAICT.

You could also try booting PVE 7 with the 5.4 kernel, if you upgraded from 6 you should still have it in your boot menu to be selected.

It does, you need to append the folder you want to list. For starters, just try root /. If that doesn't help, what error message are you getting?

Hard to tell from the excerpts you posted, but I'd say this looks like your USB NIC filters incoming packets to match it's own MAC address. This is not really feasible for VM usage, where the VM has it's own MAC on the linux bridge interface. Either try a different NIC, or look into NATing the...

"single" means the data is allocated in a linear fashion. That is, if all your three drives are 1TB in size, the first terabyte of data would all go to sdb, then the next to sdc, then sdd. This means that if a drive fails, data recovery might be easier, as most files are stored exclusively on...

That has nothing to do with the NFS server, no matter if centos or debian. The issue is that you're trying to configure an NFS server storage, and not a local folder. If you mount the NFS share via means outside of PVE, you need to add it as a "directory storage", not an "NFS storage". "NFS...

Do you need your MAC address to remain constant? If not, I'd try just removing that. It is meant as a fix if you cannot tolerate your MAC changing for outside network reasons. Also, are you using 'ifupdown2'? (post 'pveversion -v' if you're not sure, or just install the package and reboot)

This certainly looks like a bug to me. If you're up for further debugging, could you attach 'gdb' to your VM and try to trigger it again (i.e. run your wsus cleanup workload)? Attaching would work as follows: apt install gdb pve-qemu-kvm-dbg # do this beforehand # start your VM if not...

Now that's a high-spec workstation! The storage setup in general is certainly possible and seems to make sense, if it fits your requirements. Here's some general pointers: With ZFS, there's no need to check for compatibility of the motherboard etc..., as everything happens in software - it will...

This is also dependant on the language settings of your browser and the device it is running on, as well as the keyboard settings *within* your VM. These need to match up.

If you enable the "Advanced" checkbox in the "Edit" dialog for your NIC in the PVE web GUI, you can set a rate limit. This will be applied to both up- and download speed of your VM. Note that the displayed speed within your VM will always be "100G" for virtio, this is not indicative of the...

Marked as solved, but for your and future reader's information: The IOMMU part is irrelevant here, but adding the 'vfio-pci' stanzas, i.e. loading the vfio-pci driver on the host (PVE), means the amdgpu driver cannot load. For some hardware, that AMD driver is what controls fans and power saving...

MSR 0xda0 is MSR_IA32_XSS, which is related to the 'xsaves' CPU feature. This looks to me like your provider's host fails to emulate a specific CPU feature correctly, which is in use for KVM with the updated 5.11 kernel of PVE 7. You may want to indicate this to your service provider, so they...

That's a valid approach, as long as your disk images stay intact. How is the performance drop noticeable? (I/O, memory, CPU, graphics performance, etc...) If possible, please post a VM config (qm config <vmid>) and your storage config (/etc/pve/storage.cfg).

Can you post the output of ip link and ip addr? Why did you add the "hwaddress" stanzas to your network config?