Search results

Just hit this issue on our proxmox, applied the patch from the mail thread. root@pve:/usr/share/proxmox-acme# diff -u dns-challenge-schema.json~ dns-challenge-schema.json --- dns-challenge-schema.json~ 2022-12-07 13:20:49.000000000 +0100 +++ dns-challenge-schema.json 2023-01-19...

Indeed host is PVE 7.3 with kernel Linux version 6.1.0-1-pve and root filesystem is on 2 disk ZFS mirror, and /tmp on it.

After setting snapdir=visible on the zpool I redid a backup, "file restore" on it shows .zfs/snashot/ but when I try to click on "+" on one of the snapshot I get an "Error" popup with the following message: Tried a few things but still got the above Error popup from "file restore", may be...

Yes indeed snapdir is set to hidden (default value). I will try zfs set snapdir=visible Thanks!

Hi, When I backup a VM disk formatted in ZFS in PVE 7.3 to a PBS 2.3 datastore, I can use "file restore" to see files on the various ZFS dataset. But I couldn't find a ".zfs/snapshot/" on the file restore interface, is it possible to browse the dataset snapshots in some way in PVE/PBS ...

One blocking issue has been fixed recently about the upload of small files via the API: https://bugzilla.proxmox.com/show_bug.cgi?id=3990 Upload of small iso fails with error 501 upload failed So nothing blocks the snippet yaml patch technically now.

Note: it didn't last long and even with latest 5.15.64-1-pve I had an issue of losing connection to disks with ASM1062 startech 8P6G-PCIE-SATA-CARD has 4xASM1062 inside and shows the issue too. Looking for recommandations for a PCIe 8 port SATA or 2xminiSAS PCIe non RAId card that doesn't have...

Thanks! I tested updating the trunk list via qm set NNN -net0 and it worked as expected without having to reboot the VM.

Hi, I have a proxmox VM with the following network configuration: net0: virtio=xx,bridge=vmbr0,trunks=2;3;4 I wanted to add VLAN 5 to the trunk without having to reboot the VM. I first added ";5" to the configuration line. But I ended up doing on the hypervisor where the VM is running...

Patch but not working yet, help welcomed! https://lists.proxmox.com/pipermail/pve-devel/2022-April/052548.html

For reference it has been opened: https://bugzilla.proxmox.com/show_bug.cgi?id=2208 Bumped multiple times

No issue after two weeks with 5.4.157. I see that PVE 7.1 has now 5.13.19-2 which should have the fix too.

Testing 5.4.157-1-pve, after 24 hours no issue so far.

We already have a new VM with the newer software and operating system installed and validated by our user test team. The new VM just lacks the real data which is on the current (old) VM in production and quite large in size relative to our infrastructure (otherwise we would just have copied the...

Hi, To help upgrade a VM with a large disk (on ceph/rbd storage) we'd like to copy the VM disk and mount the copy on a new VM. I didn't see an obvious way to do it in the proxmox VE UI, did I miss something? I'm thinking of doing like described here...

There is only the root@pam user on our PBS server, our PVE cluster has access to it via PVE root@pam datacenter / storage / add PBS where we provided once the root@pam credentials of our PBS server. The nightly backups are scheduled by PVE root@pam user via datacenter / backup / add job. If...

Hmm may be this is due to PVE/PBS versions: On PVE 6.4-9 I have /etc/pve/user.cfg with: user:mytestuser1@pve:1:0:::::: role:PVEDatastoreAuditor:Datastore.Audit: acl:1:/storage/backup1:mytestuser1@pve:PVEDatastoreAuditor,PVEVMUser: acl:1:/vms/195:mytestuser1@pve:PVEVMUser: And in...

Hi, I want to give read only access to backups (mainly for "file restore") to one of our users so I added Datastore.Audit on the PBS storage for this user but it was not enough: empty backup list for the user. I had to add Datastore.AllocateSpace which is a write permission (allows the user to...

Done (we have "BASIC" level support on PBS but I didn't look how to link account to that yet :) https://bugzilla.proxmox.com/show_bug.cgi?id=3727 For proxmox-backup-debug it looks like it's not there in 1.x, will test a 2.x ASAP, thanks for the hint!

We had various crash with older PBS version and the PBS was undersized (CPU, RAM), we also had some reboot issues. So far my manual checks show all zero sized chunks on "backup2" are dated Jun 18 on "backup1". So probably not a direct PBS bug. Found another "blob too small" in the forum...