Search results

I've had great luck with Seagate ES drives.

Proxmox uses libgfapi

Look in /root/.forward, it calls the command /usr/bin/pvemailforward

All emails sent to 'root' are forwarded to that address. So, apt notices, etc. The email address is stored in /etc/pve/user.cfg Curious, what KVM are you using? I've installed Proxmox via iLO, DRAC, IPMI, and Avocent KVMs many times, without issues.

apcupsd isn't a web server, so it won't work from a browser. If you want a web interface for it, you'll need to setup a web server running the apcupsd CGI scripts, http://www.apcupsd.org/manual/manual.html#apcupsd-network-monitoring-cgi-programs

Add the bs parameter to dd, and set it to 64k. Example... dd if="IE11 - Win7-disk1.raw" --bs=64k|pv| dd --bs=64k of=/dev/mapper/pve-vm--103--disk--1

FWIW, we've yet to have an Intel SSD fail in any of our nodes, or other servers for that matter. So, it is likely a problem with the SSDs themselves.

Probably best to upgrade to latest Gluster 3.7, or 3.8 from the Gluster repo. I recall some fixes recently related to issues with ZFS based bricks. That said, RedHat currently only recommends XFS for bricks.

What version of Gluster are you using? And, what file system are your bricks using?

This is what /etc/network/interfaces looks like on one my hosts. auto lo iface lo inet loopback auto vmbr0 iface vmbr0 inet static address 192.168.1.10 netmask 255.255.255.0 gateway 192.168.1.1 bridge_ports eth0 bridge_stp off bridge_fd 0

Yep, http://www.intel.com/content/www/us/en/support/processors/000005567.html

FWIW, Proxmox with kernel 4.4.10 detects the E5-2698 V4 CPUs that are in one of my boxes. And correctly indicates they have 20 cores. processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 79 model name : Intel(R) Xeon(R) CPU E5-2698 v4 @ 2.20GHz stepping : 1...

I only install the VirtIO SCSI (block driver), and VirtIO Network. That method works for me with Server 2008R2 and 2012R2.

What's the file system type of the physical disk? I'm curious as your fdisk output is showing "Microsoft basic data" for the partition type, and I'd expect that to say Linux.

Proxmox 4 is based on Debian Jessie which uses systemd.

How big is the LUN? I ask, as I had a similar issue with a 6TB local RAID array, it would only work with Writethrough mode.

I suspect this may be related to the 6TB volume being 4K native without 512 byte emulation. Also experienced a similar crash with an old RHEL5 VM on the same RAID volume. Switched it to "Write through", and the VM was fine.

Interestingly enough, changing the Cache mode on the VM's disk from Default to "Write through" enables it to work. Though, I'm hoping to figure out why that is needed.

proxmox-ve-2.6.32: 3.4-160 (running kernel: 2.6.32-40-pve) pve-manager: 3.4-9 (running version: 3.4-9/4b51d87a) pve-kernel-2.6.32-40-pve: 2.6.32-160 pve-kernel-2.6.32-39-pve: 2.6.32-157 lvm2: 2.02.98-pve4 clvm: 2.02.98-pve4 corosync-pve: 1.4.7-1 openais-pve: 1.1.4-3 libqb0: 0.11.1-2...