Search results

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

hi, i can reproduce here with our current 6.14.8 kernel too. we're looking into this

ah ok i guess i see what's happening you connect to *-VPSLAB01 but the vm is on *-VPSLAB02 the console task is actually started on the node where you connect to, not the one where the vm is (the latter part of the connection is then tunneled to the right server) so you should see the task on...

regarding the screenshot, that's interesting indeed. Does it show the task on the vm task history itself? Was the vm moved between hosts? (the task won't migrate with the vm, but stays on the host where it was started) can you open the status pane of the task log window and post a screenshot ...

The cluster task list is distributed over the cluster file system, and to keep the load small, only a certain amount (i think 32k bytes, but i'm not sure, don't quote me on that ;) ) is retained there (otherwise it could grow quite quickly, increasing the load on the cluster network that's also...

Hi, yes it seems the patch was not yet applied, i pinged it so i hope it'll be included soon

there is a bit of special syntax, where you can use the inner filenames in an ova, e.g. --sata0 local:0,import-from=import/some.ova/some.vmdk uses 'some.vmdk' from inside 'some.ova' from the import folder of the local storage sadly it's underdocumented a bit

yeah, adding a Proxmox Mail Gateway is not supported in the datacenter manager currently. sorry! EDIT: you can of course open a feature request on https://bugzilla.proxmox.com

hi, under what circumstances do you get this error? a bit more information would be nice, e.g. the pve versions, the mask where you put in the information and where you get the error, thanks!