Separate names with a comma.
there is a project called 'looking-glass' which uses display mirroring and guest/host memory sharing for displaying a guest display on the host...
ja alle die im status 'ii' sind, sind auch installiert, die bitte mittels 'apt remove' entfernen, dann das upgrade nochmal starten, dann sollte es...
you could try to reinstall the package with
apt install --reinstall libjs-extjs
ist vielleicht noch ein stock-debian kernel installiert? wenn ja bitte den entfernen
mhmm... works here without problems:
1. disabled storage in datacenter->storage
2. edited vdev_id.conf (in my example a single device with alias...
i think its available with >= 5.3
in any case you can do the same on the cli with the lvs/vgs/pvs commands also blkid may be helpful
sometimes the guest does not correctly list all available options for the resolution and they must be set in the xorg.conf for example
welche rechte/privilegien hat denn der user?
kannst du die user.cfg posten?
do you see anything in the syslog ?
the only times i saw that (and it was fixed), it was caused by the network or browser
i guess you use a directory storage on top of zfs? if yes, please don't, use zfs directly via a 'zfs storage'
did you activate/install the guest agent in the vm ? (and verified it works?) 1 hour is exactly our timeout of the guest filesystem freeze
you want to disable the storage to prevent an automatic import
there should be a 'lvm' tab where you can see which lvm volume groups are on which harddrives, then match the storages to the lvm volume groups
there should be a task log "start all vms and containers" and also a task log for each vm it tried to start, there should be more information
if it is a bug, the only solution to fix it is update... i do not want to chase something which might already be fixed in a new version
please upgrad to the current version (5.4) and try again
can you output of
on the hosts ?
also what is your pveversion -v ?
this is a bug (fixed in git already) as a workaround give the users Sys.Audit rights on /nodes/<NODENAME>