Never mind, it's not a proxmox issue at all. It's a problem with the lspci command.
Running: lspci -v -s $(lspci | grep VGA | cut -d" " -f 1)
It killing the server ! Can you believe that ? Even worst considering this can be run with root permissions.
Anyhow, this command was run by our...
Sorry, I cut corner while explaning the situation. I've configure ipmi watchdog first. Then disable the ipmi watchdog thinking it would disable the fencing. With your help now I've completely disable the ipmi watchdog and softdog.
Now, I can get a better understanding of what happening.
When I...
We have recently added a new node in our already existing cluster. Recently while moving a VM to the new node, the server failed unexpectedly. Since then, every time the server get started it get rebooted after a couple of minute. This prevent us to investigate and fix the problem on the node...
Adding "options bonding max_bonds=0" to "/etc/modprobe.d/bonding.conf" did not work.
Applying the path with "sleep 2" to ifslave script is working. Don't really understand why tough.
With or without "bridge_maxwait" doesn't change anything. I've remove the "bridge_maxwait 0", then reboot.
Yesterday, I've cross this post: https://forum.proxmox.com/threads/after-upgrade-to-5-0-network-does-not-start-correctly-every-time.36677/
Might it be related ?
Cause I do see this error...
I have one server with proxmox 4.5, other server are still on version 4.4 until fix resolved this issue.
On proxmox 4.5, we have kernel message as follow:
[ 202.482275] vmbr0: received packet on bond0 with own address as source address (addr:0c:c4:7a:40:c1:3a, vlan:0)
[ 206.048280]...
Sorry to bring this old post back, but I'm facing the same issue. Defining `lxc.aa_profile` in Proxmox 5.5 result to this message:
“The configuration file contains legacy configuration keys.”
When adding `lxc.apparmor.profile: lxc-container-default-with-nfs`, the container is not starting.
Hello,
I see multiple reference to it on Internet and this forum. It's seams to be possible to run kvm with 4k sector size using the `-set 'device.scsi0.physical_block_size=4096' -set 'device.scsi0.logical_block_size=4096'` in command line, but it doesn't seams to be possible to do it properly...
It seams I can force import of "rpool" using the following command line in busybox:
zpool import -d /dev/disk/by-id/ rpool
exit
Then the system continue the booting, but it's a workarround since I need to do it everytime the server reboot.
Hello,
I want to install Proxmox 4.4 on a ZFS raidz2 on a four (4) disk system. I proceed with the installation using the proxmox iso and a usb key. The installation went smooth, but the system cannot properly start. It drop into Busybox.
Help to properly re-import the pool whould be nice. See...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.