Search results

I meant, ssh into the hypervisor not the dead container.

Huh? Can you ssh into it? I feel like the web terminal is doing something funny? Seems like is not even trying to start if I reading it correctly? Alternatively, you can back it up and restore it as a LAST resort

Sorry, try lxc-start -n <ctid> -l fatal -F ?

You provided very little information to help. How about posting what the error was? In fact, try lxc-start -n <CTID> -l FATAL ?

According to https://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM and looking at my kernel config on my HP DL360e Gen8. CONFIG_DMAR_DEFAULT_ON doesn't appear to be set, you might need to set the below on the kernel command line for iommu to function: intel_iommu=on...

AFAIK, you define network settings inside the VM, not the host?

Note, pveversion might help to see if those systems are not partially upgraded.

Okay, you could open a bug on https://bugs.proxmox.org/. A little bit about your hardware specs might help. I will upgrade one of my nodes to see, usually I upgrade through the GUI. It shouldn't matter

This is normal behavior, read more here https://utcc.utoronto.ca/~cks/space/blog/linux/ConsoleBlankingOff

You haven't mentioned what you are running inside the VM

Click 'Advanced'

Proxmox doesn't support shrinking disks, you would likely need to backup the data, recreate the disk at desired size, and restore the data. Note, if you using LVM thin, only the blocks that contain data uses disks space. You can over provision, although caution must be taken to make sure you...

The bottleneck is likely going to be how you setup you HDD Controller and Disk type. qm config <vmid>

Orrrrr, disable password authentication and keep the system up2date and avoid doing either of the two.

Is Firewall trully enabled? There a few places to enable Firewall, they might as well, all need to be ticked?

At the time of compiling, what was you running kernel and what version of pve-headers was installed?

idk wha tags you're referring to? man lvrename, it clearly states lvrename VG LV_name NewName So, in your case, that will be: lvrename Data-Storage vm-100-disk-0 vm-105-disk-0 As mentioned earlier, when you detach the drive, there will be residue of the drive in 100.conf. You might want to...

Additionally, they maybe a residue of the old disk in 100.conf file, that might need to be removed. Etc.

What happens, Windows poweroff of course, detach the drive from 100 (becomes an unused disk), then trying re-attach it to 105 (From the hardware section)? This hoping the process is seamless and no need to lvrename (hopefully done automatically)? Otherwise, is as simple of detach the drive from...

This might help https://forum.proxmox.com/threads/bsod-server-2008.60093/post-277153