Recent content by dcsapak

falls das setup noch läuft, was sagt denn cat /proc/meminfo ?

das kommt drauf an, wie sieht denn der task log vom verify task aus?

thanks for the report, i updated the page to fix the typo as for honestly, i did only skim the page but i don't think there changed much in recent years.

i think you're conflating two hookscripts here: there are the vm hookscripts (which you can set with qm/pct): these are for vm start/stop/etc. and there is a vzdump hookscript which is intended for job start, backup start, etc. -> this can be set in the /etc/vzdump.conf on the specific host...

can you please post the config when spice is not working correctly. I'd just like to see what the config looks like when it fails. also the output of 'pveversion -v' could be interesting

hi, what kernel do you run? can you post the output of pveversion -v? also can you share the full 'dmesg' output?

how did you arrive at this config? how does spice work at all for you? you'd have to use a different vga model (e.g. SPICE or virtio-gpu) for the ui to offer spice in the first place. also i'd remove the custom '-spice ...' option

hi, Can you check if the spice client (remote-viewer) has any errors on the cli? What OS do you use on the client? did not yet see such behavior, so no idea currently why that shouldn't work. I440fx vs q35 should not make a difference. can you also post the vm config here? (qm config ID)

i don't have any experience with that exact card, but it having no display output probably means you have to install some virtual display driver. since you're on windows you could try to use apollo (https://github.com/ClassicOldSong/Apollo) which is a sunshine fork with extra features like a...

ok, if neither qemu downgrade nor kernel downgrade changes anything, then i don't really have an idea what might have caused this change. There are not that many components involved, and you ruled out the main ones. Did something else change maybe? windows update? driver update (in the guest) ...

maybe a kernel issue? if you have the time (and are willing ofc ;) ) could you reenable resizable bar in the bios and try with an older kernel?

this sounds like a permission or user/group issue? do the device nodes have the same user/group and permissions in the container? maybe trying to start steam with 'strace' in the container could reveal what they're actually trying to do with them and which error they get from the kernel? i...

is that the log from the guest or the host? could you attach a full journal from both?

can you post the full config? (qm config ID) also what desktop environment do you use inside the vm? i just installed forky from the debian-testing-netinst iso and both novnc and spice work as usual.

mhmm in the subscription registry we already show the socket count per remote, maybe a node count there + total count there could be enough? or does it have to be on the dashboard?