Search results

does it work with the older kernel? if yes, check/post the syslog from the boot with the blank display to see what might cause the errors

it uses the api call /node/localhost/network api call and shows everything with a cidr so if you post the output of pvesh get /nodes/localhost/network --output-format json-pretty i can check what might be the problem

you can remove a config line again with qm set VMID -delete <config> so e.g. if you added a 'hostpci0' config you can do qm set VMID -delete hostpci0 note that e.g. disks will be added as unusedX if you do this (only when the unused config is deleted, the underlying disk will be deleted)

the template file name is included in the api call, but not currently shown on the webui but on the cli it's shown: pveam available if i may ask, why do you want to know the format? this should not matter really how it's compressed? also lxc templates are always tarballs (with various...

fyi: i opened a tracking bug for that: https://bugzilla.proxmox.com/show_bug.cgi?id=6668

yes, these are call 'group filters' in the code and have 3 types, 'type' (so either host/ct/vm), 'group' (e.g. vm/100) and 'regex'

Hi, looking at the code, the group filters are really only effective on group names, not including the namespace so no, regex filtering will not work here what you can do however is to add a tape backup job for each namespace with it's own group filter, and schedule them close one after...

ah ok, the latest version of the patches are here: https://mail.gnu.org/archive/html/qemu-devel/2025-06/msg00011.html and they are not yet applied in qemu, so maybe in a later qemu 10.x release

that property (context_init) does not exist here, i'll have to look if there is some compile flag that has to be activated...

i tested on the pve9 beta with kvm version:

Hi, AFAIK one must add multiple new options for venus to work, according to the docs: `virtio-gpu-gl,hostmem=8G,blob=true,venus=true` (the 8G are just as an example) but i tried here on a test machine (with an radeon RX560 on the host and i always got `error_out_of_host_memory` when running...

note that a new package for the 6.8 kernel is already on pvetest, so no need to compile the kernel yourself

fyi, i'll probably look into doing similar changes to other parts of the code. e.g. i already sent a patch to try to improve verify speed: https://lore.proxmox.com/pbs-devel/20250707132706.2854973-1-d.csapak@proxmox.com/ it's not configurable yet (the biggest hurdle here is that we don't simply...

hi, wenn das wirklich der einzige unterschied ist, ist es wahrscheinlich der grund. kritisch ist es nicht, daher nur die warnung Die fehlermeldung selbst sagt dass der changer/das drive gerade nicht 'ready' ist ist während dem backup job irgendein log im journal zu sehen?

it's already applied in our git, so you could clone that repository, change to the appropriate branch and build it otherwise the patch could be applied with something like 'git am <path-to-file>' but since it's already applied, bumped and is currently being synced to pvetest, this should not...

just fyi, 6.8.12-13 (with the fix) should be up soon on the pvetest repository

just fyi, i sent a patch for this: https://lore.proxmox.com/pve-devel/20250722095659.79468-1-d.csapak@proxmox.com/T/#t

just fyi, i sent a patch for this: https://lore.proxmox.com/pve-devel/20250722095659.79468-1-d.csapak@proxmox.com/T/#t

i sent a patch on the list that worked for me here: https://lore.proxmox.com/pve-devel/20250722095659.79468-1-d.csapak@proxmox.com/T/#t

just fyi: we're currently looking into this, and believe we have identified a commit (+possible fix) that's responsible, i'll send a patch later if it turns out that it fixes the issue