Search results

I stand corrected. I dredged up old logs from my problem site from a month ago--the VMs are suspending. I find it funny that a 24/7 outfit that has its servers regularly suspending for several hours at a time hasn't made a peep...

It's working at 3 different sites right now--just not the one I apt-get dist-upgraded.

kvm3:~# lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert data pve -wi-ao 166.33G root pve -wi-ao 58.00G swap pve -wi-ao 4.00G kvm3:~# lvdisplay ---...

About a week ago I did my usual 'apt-get update && apt-get dist-upgrade' on one of my Proxmox machines and rebooted. Now the nightly backup is suspending the VM rather than doing a snapshot. Other than installing the updates, the box hasn't seen changes in several months. I missed the problem...

*facepalm* I had it in my clipboard, but forgot to paste it. Sorry. kvm1:~# pveversion -v pve-manager: 1.7-11 (pve-manager/1.7/5470) running kernel: 2.6.32-4-pve proxmox-ve-2.6.18: 1.7-10 pve-kernel-2.6.32-4-pve: 2.6.32-30 pve-kernel-2.6.18-2-pve: 2.6.18-5 pve-kernel-2.6.18-4-pve...

I have three proxmox boxes (kvm1, kvm2, kvm3). All the virtual machines are running under kvm using iscsi targets as their storage. It doesn't seem to matter what host I am transferring to or what guest I am moving--they fail: kvm3:~# qmigrate --online --verbose 10.47.0.181 109 Mar 22...

That fixes it. It's a bit inconvenient to not have the network settings sync *and* be required to put network settings on the master that you don't need. Then again, I don't see a better way around it at the moment... ;)

If I'm understanding you correctly, I need to add the bridge to both the master, and the node that has the VM that actually needs it. I'll give that a shot today. Thanks.

That's what I figured. So now I'm stuck with KVM3 with the correct network settings, but vmbr100 not showing up in the drop-down when setting up a new NIC. KVM3 has been rebooted, and I've verified vmbr100 is up correctly in Linux--it just doesn't show in the Proxmox web interface.

I have 3 physical machines clustered together named KVM1, KVM2, and KVM3. I logged directly into the KVM3 web interface and setup vmbr100 using physical interface eth0.1. After rebooting KVM3, eth0.1 is correctly brought up and put into the bridge vmbr100. When I log into the cluster...

I have a Win2k VM that is exhibiting the same problems. I am switching it to a standard PC instead of ACPI and will report back in a few days if that fixed it or failed. Thanks for the info. -A