Im' working on PVE 5.1 and i get some issues with cpu hotplugging.
I added /lib/udev/rules.d/80-hotplug-mem.rules and /lib/udev/rules.d/80-hotplug-cpu.rules file config on the node
I also modified vm config file to get this:
Has anyone ever faced this kind of problem?
I'm trying to install Proxmox on a Dell Poweredge 2950 server, and in one particularly moment, the server freeze without install Proxmox. Frozen such is need to press power button to shutdown the server.
I already tried Proxmox versions 4.4 and 5...
hey there, i just installed 5.0 from installer iso and ZFS is unable to load on boot now for some reason...
I constantly get
Sep 15 01:27:27 voltaxic systemd: Starting Mount ZFS filesystems...
Sep 15 01:27:27 voltaxic zfs: The ZFS modules are not loaded.
Sep 15 01:27:27 voltaxic...
So i have successfully upgraded my Proxmox 5.0-29 environment running Luminous 12.1.1, the weird thing is that when I look at the health screen in the GUI, it displays the Performance, but the Health is blank and so is what it thinks the OSD's are (0 in, 0 out). However if i go to the Ceph->OSD...
I've been a Proxmox user since v2.x, but am about to roll out a new lab environment using PVE 5.0 and Ceph, to do some testing with. Hardware-wise, I've got 3 nodes spec'd out like this:
dual Xeon E5-2670's
LSI 9207-8i HBA
x2 240GB SanDisk SSD...
So I just upgraded to 5.0-23 tonight.
When I try to boot the system, I now receive this error:
[28.072000] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:1]
The machine will keep spitting out variations of that error (only thing that changes is the timing. Instead of 23s it...
This doesn't seem to be the already mentioned ssh problem (which is at 1:7.4p1-10 anyway):
Jul 11 18:34:38 copying disk images
Jul 11 18:34:38 starting VM 103 on remote node 'bowie'
Jul 11 18:34:40 start remote tunnel
Jul 11 18:34:40 starting online/live migration on...
Thank for release 5, I just installed it and almost all works fine, but....
For one of my VM's (I've got 3 working) the console act a little strange. The VM runs fine and I can get to the VM but a SSH connection, but the console iProxmox stops a "Reached target Local File System (Pre)"
I installed 5.0 a few days ago and upon trying to bring up Open vSwitch, I'm having real problems getting it to work after reboots, though similar configurations worked in 4.x. /etc/network/interfaces looks like this:
### begin paste ###
iface lo inet loopback
I have three VMs on my Proxmox server (5.0 Beta). I have them all set to start at boot, and upon starting up the machine I can see in the log that the 'Start all VMs and Containers' command is run and returns 'OK'. However, none of the machines boot up, I have to then manually start...
Is it possible to install drivers for Mellanox ConnectX-3 in Proxmox v5.x?
The Mellanox site only has drivers for Debian 8.3.
I tried using the 8.3 drivers but I'm getting some errors.
# ./install --distro debian8.3
Logs dir: /tmp/mlnx-en.31026.logs
Below is the list...
I upgraded a test server and upon reboot got the error shown below.
# pveversion -v
proxmox-ve: 5.0-2 (running kernel: 4.10.1-2-pve)
pve-manager: 5.0-4 (running version: 5.0-4/e97c2852)