Search results

ok, thank you Udo. I will test if i need, after testing other kernel version (i think)

Hello, i have the same problem for a few days. A kvm guest (Windows 2012r2) is killed by OOM. Proxmox host have 32 Go ram. 20 Go free ram. Storage is drbd 8.4 (compiled with http://coolsoft.altervista.org/it/blog/2016/08/proxmox-41-kernel-panic-downgrade-drbd-resources-drbd-9-84). Kernel...

Hello, a little hint ?

Hello, On 2 servers, I reinstalled proxmox on a LSI 2208 card with 3 volumes. 1 volume for Proxmox, the other 2 for DRBD. I created the volumes DRBDr0 and DRBDr1. Restoring a backup to DRBDr1 is going well. The following message appears on DRBDr0. One or more drive were used. restore vma...

Hello, i use the guide in production. It work perfect. Sure, leaving the choice of the drbd version at the installation would be better, but compiling from the source allows to have the latest version.

@fireon : i mean, disabled. I have this option on supermicro board, but same result. Sometimes, VM freeze on live migration. Tested with 2012, Win7, Win2000. Vmware recommands to disabled it : https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1018206...

Hello Fireon, it's seem CPU powersaving disturb Windows time synchronisation.

i had updated the two node with last kernel, apply bios settings with powersaving option disabled. I had done 6 live migration without problem. Next hang. VM is a Win2012r2. Thank you.

Hello, I have exactly the same problem. Same hardware for node A and node B. Drbd for shared storage. Tested with NFS on a synology. Same result. Only node B is up to date with those settings. I can't stop VM on node A at this moment. Linux Guest can migrate without problems, but Windows...

Hello, I migrate VMs from a cluster PVE 3 to a PVE 4. Ideally, it should use a backup / restore of each VM from the old node proxmox 3 (A), to the new node proxmox 4 (B). Here's an idea to have very little downtime : Migrate hard drives between each node with NFS storage, then, stop VM on old...

if interfaces aren't up when proxmox finish to boot, this will not prevent sending or receiving a quorum in a cluster to start the vm ?

5 to 10 minutes is very long :) i didn't move the 70-persistent-net.rules. and, if i unplug an plug again a cable, it takes around 30 sec again to bringup. I write it if it ever can help Thank you very much for your help. If maybie one of Proxmox team would like some tests, no problem.

as I don't know systemd files, i have created 6 files in /etc/systemd/network : 10-eth0.link, 11-eth1.link, 12-eth2.link, ..., like this for 10-eth0.link. No possibility to have 1 file for all eth ? [Match] MACAddress=00:25:90:82:bf:fc [Link] Name=eth0 of course, i had change Name=eth0 to...

Yes, Nothing else changed. ok, i will test now systemD method. Another issue, on every boot /var/log/dmesg is empty. Only this line in its content : (Nothing has been logged yet.)

Here is # PCI device 0x8086:0x1521 (igb) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="0c:c4:7a:51:91:97", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth5" # PCI device 0x8086:0x1528 (ixgbe) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*"...

I only change the eth number to assign eth at the right card that i wanted, but that was before my changes also. No double eth<x> number in my file.

Hello, thanks ctcknows. i have done the second solution, maybie more clean. Install Promox 4.1 iso and apt-get update && apt-get distupgrade. udev is ok now. I have a another little problem. I have this message at boot prompt : a start job is running for lsb raise network interfaces when...

Hello, i made a fresh install of proxmox 4.2 ISO on a supermicro server, motherboard X9DR7-TF+. Here is, in /var/log/syslog : May 16 10:52:12 prox03 udev-finish[1374]: /lib/udev/udev-finish: 6: /lib/udev/udev-finish: cannot create /etc/udev/rules.d/70-persistent-net.rules: Read-only file system...

Thanks for your feedback

had you got see this wiki ? https://pve.proxmox.com/wiki/Pci_passthrough i had just see it and it mention So, don't use it in production environment. it's ok with bridged, so, go ahead and give it a try :) (all my virtual networks cards in pfsense are virtio model).