Search results

Keep in mind that containers aren't in fact virtualisation. If you run lsblk you'll see all block devices and mount will show that your root is mounted from somewhere else than an actual block device. Containers don't try to conceal the fact that the environment you're running is is a somewhat...

There's your problem. Find out what happened to the disk image. # lvscan should give a first impression of the situation.

If the network connected to ens192 offers DHCP you can let the container use that. If it doesn't or you don't want the IP to change, you can set a static IP in the configuration dialogue of net0/eth0. Remember, if you assign a static IP, to specify it in CIDR notation. Otherwise the container...

Can you remove sdc from the storage config?

man 8 vgremove should tell you what you need to know. In case you're talking about LVM Thin you need to remove the Thin pool, which is a logical volume manually, first.

Did you use the Host-only network? NAT is only meant to connect the guest to the internet.

I'd have to guess the compression ratio of gzip on those images. Just try it. https://pve.proxmox.com/wiki/Proxmox_VE_inside_VirtualBox

What do you hope to gain by passing the SATA controller instead of the raw disk? You can just pass the disk instead of an image.

You can restore a machine from the backup. Proxmox doesn't make a difference between local and remote storage. Proxmox doesn't make a difference between local and remote storage. No, you don't. I already told you that you can overprovision zvols. So the raw-sized image will be compressed...

I've seen that issue. Sometimes the machine hangs on "Watchdog didn't stop" or even "Reached target: Shutdown". The thing is, I've seen that on other distros, too. Could be an issue in systemd. As you can imagine, debugging issues with the shutdown is rather complicated, as the machine likely...

Containers make a file-level backup to a .tar.gz or .tar.lzo on whatever storage you specify. VMs use our own format, again with lzo or gzip compression. Size-wise it's roughly like raw, perhaps a bit larger. But why would you backup to the same disk the machines run on? That would be pointless...

What about the client? QEMU expects scan codes as input, but all NoVNC can read from the client is JS key events. So it has to guess the key symbols required by the VNC protocol, according to the client's locale and other factors. The VNC server then has to translate those into scan codes as...

What locale are the guests and your client set to? Try setting all parties to the same locale, as there is quite a bit of guesswork involved in NoVNC.

Sorry, just saw I had a typo in the command. It ought to be # pvesm set LVM1 -shared 0 of course. Or you can mark the storage as non-shared in the datacenter.

If the storage is marked as shared the image virtual disk won't be moved. Marking a storage as shared on creation does not result in Proxmox actively sharing the storage, but simply considering it as already shared. Like NFS for example. So if LVM1 is not actually available to all nodes this may...

Was lvm1/vm-101-disk-1 renamed/moved/deleted?

noVNC is a VNC server implemented in qemu. It has no knowledge of what's going on in the VM. You may be able to copy command output to the guest's clipboard, but the VNC server has no way of accessing it. Copying to the host's clipboard via VNC can only be done if the VNC server is run in the...

As expected the previous installation used the Cirrus virtual graphics, which is no longer used by default. You can either uninstall the cirrus driver, which should make the system fall back to VESA, which will work but won't be very fast. But with 2GB memory my VM handled 720p pretty well and...

Well then, standard network debugging it is. Give an IP to the bridge and see if you can ping it from a VM connected to it. Either check the log or start the dhcp client manually to see the result of a request.

Well, take a look into the Xorg.log. It'll likely tell you what ails it.