Search results

Disconnecting a NIC, hotplug, pending changes : wonderful! Great job! Many Thanx to proxmox team, Christophe.

Hi all, In order to build a training platform, I spent some time trying things. Physical servers are IBM X3850 X5. CPUs are Xeon E7-4807 RAM is largely enough. The only hypervisor I tried was proxmox (What else?) v3.3-20. The goal is to teach how to build a 2 nodes proxmox cluster + drbd to...

Hi, Same problem here with 3.10.0-7. Did not try 2.6.32, but 3.10.0-5-pve boots fine. Christophe.

Hi, cat /proc/drbd on both nodes please? Christophe.

Because it is not started on all other nodes... Can you try to start rgmanager manually on proxmox02 to proxmox06? Christophe.

Well, something is probably wrong in your cluster config. Live migration of HA managed VM is a feature. What does "clustat" says, on each node? Christophe.

No. You can migrate a HA managed VM. You do not need to disable HA on that VM. Christophe.

If your goal is "demo mode", you can turn off your node with power button. iDRAC keeps power. In real life, your fencing device needs power. No, but keep in ming that you absolutely need to have quorum in your cluster. Without quorum, no start, move or stop VM. Quorum is lost as soon as you...

And your VMs will migrate as soon as you plug in AC! Christophe.

Hi all, Many installation problems on various hardware platforms recently with PVE 3.2 and PVE 3.3 : http://forum.proxmox.com/threads/20241-Proxmox-VE-3-3-does-not-Boot-after-install http://forum.proxmox.com/threads/19675-Fresh-install-of-PVE-3-2-won-t-boot-best-work-around...

Hi all, An easy fix for this proxmox installer bug : - install proxmox VE 3.1, - apt-get -update ; apt-get dist-upgrade and you get a working and up to date PVE 3.3 Christophe.

Yes, e100 gave a general way in an old thread (http://forum.proxmox.com/threads/9376-Bug-in-DRBD-causes-split-brain-already-patched-by-DRBD-devs). You only need to build drbd8-utils package, from sources, then install it. You don't need kernel module, it is bundled with kernel 3.10.0 now. Here...

Forward your Windows logs to a remote syslog, with eg nxlog (http://nxlog.org/). Christophe.

Hi Pegasus, No more crash / unresponsive VMs here, with IDE / e1000, balloon driver loaded but fixed RAM size, max performance in energy settings. Christophe.

Yes, power management was suspected. All servers are now at the same level : max performance. Thanks, Christophe.

Ah yes! But : - we (very) regularly watch io delay in proxmox (Quad Xeon IBM), and on EqualLogic 10gbE iSCSI SANs. Everything is OK (io delay never reached 4%), no lag at all. - why the hell an eventually slow storage would crash a VM with virtio drivers, and NEVER crash exactly the same VM with...

Hmm. May be when we updated / upgraded PVE, but now we do not migrate VMs every so often. Don't know. Christophe.

Hi, We had a similar problem but it is really difficult to establish a precise bug report! Yes, problems started after an upgrade, from PVE 3.1 to latest at this time : 2014-09-29. Before that, i upgraded a first proxmox cluster as soon as v3.3 was out. No problem. Mainly Linux machines. A...

Ok, it's for à remote customer, will try next week. Merci beaucoup! Christophe.

Hi all, Same problem here with latest PVE 3.3 (and kernel 2.6.32) : installs but doesn't boot. Any help or hope? Thanks, Christophe.