Search results

We are on 7.1-8 For the April 2022 round of Microsoft Windows updates, i.e. 2022-04 Cumulative, looks like it is hanging 100% of our Windows guest VM upon restart. I.e. after applying patches within VM, restart per normal process, but the VM gets stuck on the MS-logo with swirl. Will stay...

Thanks for those points - that sounds plausible i.e. I am seeing a mis-match between messages in PVE task window vs actual writing of data. However my point about the 2nd PVE... I did the same VM on both systems, offline/not running, and did the backup to Synology via NFS... I watch the timer...

Can you connect the server to a laptop directly? Set a static IP on the laptop... and then re-try the basic ping commands between the server/laptop? Quick search suggests your MB is probably ok with Linux/Proxmox...

From the terminal/console... can you ping out? i.e. ping 8.8.8.8 or the Comcast modem IP? Can you do a ip addr to see what interfaces were configured, which one is picking up. Try different network cables / different ports on the server.

Have been doing backups to a NFS share on a TrueNAS successfully from a PVE 3-node cluster Now trying to do backups to NFS share on a Synology NAS from the cluster. Finding that the backups eventually finish... problem is a major delay from when the task viewer messages show INFO: transferred...

What version of PVE were you on prior to the upgrade? Possible that your network card interface name got renamed (debian 11 upgrade) If you can console-access PVE, have a look at /etc/network/interfaces file, vs what interfaces you have showing in ip a You may need to revise the interface...

Based on your screen-shots doesn't look like you have much in /var/lib/vz on that local partition However, your output of df -H shows you have 100% use on your root partition... anything that hits 100% usage is usually a problem. Did data get stored somewhere outside of /var/lib/vz that could...

With the quad-card plugged in, and you are at the shell/console, if you do a ip a command to see what interfaces it lists... this can give you an idea of what are now active. Per avw's tip - you can then manually revise the /etc/network/interfaces file. I recently had a similar issue when...

This tip was helpful, pointed me in the direction! I have a Synology NFS share mounted - VMs would backup OK, containers did not. Checked and found that all containers were unprivileged. On the Synology, under NFS Permissions there was a "Squash" setting where it was showing options to map...

Not sure what happened, but had to power-off the PVE server. After restarting, console/shell is just colored blocks. Tried changing to different shell (VNC, xterm.js) How to fix this?

Follow-up on my original post, this is working. As wolfgang wrote, enabling first in Options Qemu Agent and then booting the VM... then device now shows up. We have done multiple Windows VM installs (Server 2012r2, Win7, Win10, Server 2016) now it works great.

Currently testing pfSense and ProxMox 5.3 as VirtualBox VM's. pfSense setup to route traffic -- this was tested OK with a different VBox VM (systemrescueCD) PVE could see Internet OK. Any LXC container could only ping hosts on local host-only network. Working off of this wiki page...

Trying to get the qemu agent working for my Windows 2012 R2 VM's Following https://pve.proxmox.com/wiki/Qemu-guest-agent Problem is that in my VM, in the Device Manager, there is no "PCI Simple Communications Controller" I have installed all the virtio drivers, and there are no unknown...

While trying to correct a DRBD9 problem on PVE 4.2 2-node cluster, I did a drbdmanage -uninit and mangled my setup :) I have only test VM's so I am trying to recover without re-installing. I rebuilt /var/lib/drbd.d/*.res files by hand On both servers # drbdadm create-md vm-100-disk-1 #...