Search results

could you try the options from here: https://pve.proxmox.com/wiki/PCI_Passthrough#%22BAR0_is_0M%22_error_or_Windows_Code_12_Error so setting the cpu to 'x86-64-v2-AES,phys-bits=host,flags=+pdpe1gb' via the cmdline

is the time of your client and the server correct?

can you post more of the journal, maybe it does contain a hint? is it actually broken or does everything work like usual with just the addition of the new log lines?

'remove' removes the tape from the inventory without deleting the data from the tape itself (if there is data on it, even the remove won't work by default, only with the 'force' flag) this is the same as 'proxmox-tape media destroy' (not sure why it's 'destroy' on the cli vs remove on web ui...

there are two 'log rotation' tasks in your list, can you post the content of those? EDIT: just looked again, the time on those say 'september' so is that the current list of tasks you see there?

interessantes projekt, aber hast du schonmal gedacht, zumindest teile davon bei uns upstream zu bringen? zb zusätzliche spalten im tree ist denk ich etwas was wir vllt reinnehmen würden. bei dem cluster resources ist es so, dass wenn die config im backend da ist, sollte es auch sofort beim...

das forum ist zwar nicht wirklich der richtige ort um sowas zu fragen, eher geeignet wäre die pve-devel liste: https://lists.proxmox.com/postorius/lists/pve-devel.lists.proxmox.com/ ein update erzwingen kann man zwar mit 'PVE.data.ResourceStore.startUpdate()' dieses wird aber asynchron...

can you post the config of the container? pct config 109

aside from that video very obviously being ai generated, the underlying point is not wrong. in modern windows versions, using 'host' cpu mode activates VBS (virtualization based security) which can incur a heavy performance penalty. Alternatively to changing the cpu mode, it might be possible to...

Hi, yeah, i guess we're missing an 'activate_storage' in the exec hookscript path that would trigger the mount, etc. would you mind opening a bug for that: https://bugzilla.proxmox.com so we can track it more easily?

yes this is possible, i'll see if i have time today to test this a bit more (and/or look at the code ;) )

mhmm does it progress if you change the ostype from windows 11 to linux? this only sets a few specific parameters, but maybe one of them is the culprit

Hi, There are only 2 ways to share (phsyical) GPU resource to guests AFAIK: * use of virtio-gl (though that is currently limited to opengl, vulkan is in the works) * use of vgpus, though there are multiple ways: - for intel, there is the intel arc b50 pro which can split the gpu with sr-iov...

hi, yep it's currently not implemented, would you mind opening a bug report on https://bugzilla.proxmox.com (maybe check if there already is one) so we can keep better track of it?

one other issue that could be happening is that allocating the memory of the windows vm just takes an (absurd) amount of time. we had such behavior in the past, especially if the memory is fragmented. Could you try to reduce the amount of memory in the windows vm (temporarily) to e.g. 8G to...

this is the problem, the tape job sees a tape that is already part of the media set and writable, and still available (for a standalone drive, 'offline' means not in the drive, but on-site) i'd bet that if you mark this too as vaulted, it would start a new media-set with a different tape a new...

can you try with the following changes to the config: instead of hostpci0: 0000:e1:00.0,pcie=1 hostpci1: 0000:e1:00.1,pcie=1 please use hostpci0: 0000:e1:00,pcie=1 this will passthrough both functions as one device, like it is visible on the host also instead of machine...

mhmm indeed it did not allocate a new media-set, this would look like this (what it did in my tests) 2026-02-18T10:39:19+01:00: Starting tape backup job '...' 2026-02-18T10:39:19+01:00: update media online status 2026-02-18T10:39:19+01:00: starting new media set - reason: writable media...

hi, can you post the vm config ? does the windows vm boot without the passed through devices? also the journal from the host during that time would be interesting.

aside from the install notes might needing an update, what problem do you have with secure boot with our shim/grub/kernel? They should be signed and bootable with secure boot?