Search results

What does the task log say? Could you have kvm enabled for the VM but it's disabled/not supported by the hardware?

Because pve/data is used more like a partition than like a filesystem. pve/root is usually formatted with ext4 so man resize2fs will tell you how to grow the FS.

And you can't ping the container from the host? Or vice-versa? Or you can't reach the container from another host? Or do you have intermittent availability? Do you ping by name or IP? Debugging networks is hard enough without direct access, so we need as much information as possible. What is the...

You don't need special hardware. You need software to support them. In this case the file system. Usually, when software writes to a file the state before a write is replaced by the state after the write. The previous state is lost. With snapshots the state of a volume is saved and when a file...

Those may be the important lines. The cgroup already exists. Is the container still running? Your gid_map is not correct. The error regarding cgroup chown may be related to the first one. Did you make the container unprivileged just by adding unprivileged: 1 to the lxc.conf? Because that's not...

OpenVZ is no longer supported. We switched to LXC with 4.0. There exists an import tool, that allows to restore OpenVZ backups to LXC. You will probably have to adjust the config manually. As for the VMs, the restore might just work. Back then the defaults were different and some settings could...

Sorry, I seem to have missed half of your post. I got the part that you have a privileged container running samba, that you want to convert to an unprivileged container running samba. The id_maps look fine. lxc probably tells you why it won't start. Could you need another entry in /etc/subgid?

Without more information barely anything can be said. A good start would be to post the container config # pct config <ID> and the host's network config cat /etc/network/interfaces

It might be much easier to make a backup, destroy the container and restore it from the backup as unprivileged container.

Did you reload the page ignoring the cache? You may still be stuck on the old worker. Also, did you reboot the VM? LVM may be designed to handle hot resizing, but partitions are not. Also you need to grow the FS inside the LV of course. Otherwise the space won't be usable.

Check your network and firewall configurations. The Console in Proxmox does not involve the network, as it directly hooks into qemu. So make sure that all clients can reach the VM via network and that the required ports are accessible.

You have some sort of management environment from your hoster, I presume. The same interface where you installed the proxmox image from. You load a live image of any Linux distro and use the chroot command to switch into the installed proxmox. man chroot explains how the command works. When...

Hands on recovery it is then. Boot to bash, reset the password. If you don't have local access you could try chrooting into the install. And after you regained access, double check the access you gave to that user.

If you point your browser to <host-ip>:8006/api2/html you can click through the API interactively. That's pretty handy for tasks like these. I'd expect the URL to end on something like nodes/<node-name>/spiceshell on the guest IP. However I'm getting a null there, too. The html view shows a "not...

If you were going for hardware RAID anyway, great. I don't see why Redmine would not be happy in a RAIDz2. ZFS relies heavily on caching and will happily gobble up any and all RAM that you assign to its ARC. So if you suspect Redmine to be by far the most active VM on the HDDs you could...

So host, guest and client all have the same locale, you tried different browsers and operating systems and it's the same issue everywhere. That feels like we're terribly far to the side of the bell curve. But unless the JS console or the qemu-server log contain further clues, I'm running out of...

Don't forget do activate the other volumes in that pool, if they aren't already. lvm-systems also has some inactive VM disks. Glad that it works, but it would be kinda interesting to know what caused that behaviour.

And what locale are the clients configured to?

Ok. So you pve pool is enabled as far as PVE is concerned, but for some reason didn't activate. If you didn't already, you can try giving the host a clean reboot, if that's feasible. If that didn't fix it or you can't do it right now, please post the output of vgdisplay and pvdisplay. You could...

Not sure why a crash would deactivate the volumes. Your whole LVM Thin pool is inactive. Please post yout /etc/pve/storage.cfg before you do anything. You should be able to activate the volume with # lvchange -ay pve/vm-109-disk-1