Search results

Hi, just FYI, Pavel did respond on our devel list to the question where to report bugs to with the following: so maybe in their forum would be best? EDIT: see here: https://lore.proxmox.com/pve-devel/mailman.50.1727091601.332.pve-devel@lists.proxmox.com/

if you want to restore a vm completly on a pve, i'd recommend using the pve side api/webui instead ot trying to manually restore from config and disk image but on pve the configs are found in /etc/pve/nodes/NODENAME/qemu-server and /etc/pve/nodes/NODENAME/lxc for vms and containers respectively

hi, not completely sure what you mean by 'mdev groups' , but if you use resource mappings instead of the raw pci devices, you can create a mapping with both cards in them and it should work. it won't the summary of the available mdevs in the ui (on my todo list) but it should simply try to...

this was a bug: https://bugzilla.proxmox.com/show_bug.cgi?id=5731 and is already fixed: https://lore.proxmox.com/pve-devel/20240920090506.231780-2-f.gruenbichler@proxmox.com/ since pve-manager 8.2.6 which should already be in the pve-enterprise repository

ok wenn ich das richtig verstehe ist es so: ein media set wird in pool A angelegt (mo + fr jobs) und dann erst wieder 6 wochen später gestartet? oder sind es mehrere media-sets pro pool? am besten wäre die ausgabe von folgenden cmds von vorher (wenn sie als expired markiert sind) und nachher...

in the same view, you should be able to download the conf (.blob) file and download it

in the content view of a datastore, there is a 'download' button on the img.fidx files

hi sorry für die späte antwort. wie sieht denn die allocation und retention policy von dem pool aus? diese bestimmen nämlich wann tapes full, writable oder expired sind. siehe auch hier: https://pbs.proxmox.com/docs/tape-backup.html#media-pools

Hi, for the proxmox backup server to communicate with the tape library, it must see it as a scsi device. afaics this: https://www.quantum.com/en/products/tape-storage/scalar-i3/ is the library? this says that the drive connection is done via fibre channel or sas, so using an hba for either...

why do you think this? we have two daemons running pveproxy (running as www-data and doing most of the work) and pvedaemon, which is running as root for things that can only be done as root (e.g. mounting storages, etc) the template list info is downloaded from our mirror and gpg signed, which...

mhmm, could you check the influxdb container for logs? i'm interested in what path/url the metrics code tries to connect to, and maybe that's wrong? also for testing, could you try if a bucket name without spaces works? (i'm thinking maybe the space is not properly encoded when building the url)

thanks for noticing, should be fixed now

depends on multiple factors e.g. how the code looks, how exactly it's integrated, but most important, the author should use our development workflow (e.g. sending patches to our list): https://pve.proxmox.com/wiki/Developer_Documentation also, maybe it would be good to write to the devel list...

sorry for the late answer, no not yet, after some discussion simply upping the thread count is probably not the way to go here, otherwise it becomes to easy to overload the pbs (storage and cpu wise), but we're still looking into that and hopefully will come up with a better fix :)

hi, the patch is already applied in our repository and will be included in the next package update of proxmox-backup https://git.proxmox.com/?p=proxmox-backup.git;a=commit;h=e97132bb64a203535c28214c1cec4c1e49cf9009

hi, thanks for investigating, seems that it's just a simple fuse configuration error. i opened a bug report : https://bugzilla.proxmox.com/show_bug.cgi?id=5728 and sent a potential fix for that: https://lore.proxmox.com/pve-devel/20240919095202.1375181-1-d.csapak@proxmox.com/T/#u

Hi, can you post your sync job configuration? i just tested this (albeit with a "local" sync instead of remote) and it behaves like expected to me: datastore1: ns: a => host/test snapshot datastore2: ns: b => empty sync job: local namespace: b source datastore: datastore1 source namespace...

mhmm what happens when you shutdown the vm and then add it, does that work? i can only see a single usb port (spice) that is configured/pending maybe that spice port blocks the addition? also can you try to set it on the cli? qm set ID --usb0 <your usb device port/vendor/id> (see man...

hi, the default is defined here: https://git.proxmox.com/?p=pve-container.git;a=blob;f=src/PVE/LXC/Config.pm;h=1664a35a60b53e9a1c450f37a397dc3575008bd1;hb=HEAD#l581 and the code that extracts that default is here...

sent a first version of the patch, sorry for the long delay: https://lore.proxmox.com/pbs-devel/20240910070818.268267-1-d.csapak@proxmox.com/T/#u