Thanks it also solved my problem, and got Proxmox booting on 80x24 .
While starting grub, I got a message about "vga=normal" was deprecated, and suggested using gfxpayload=text
So my line now shows
GRUB_CMDLINE_LINUX_DEFAULT="quiet gfxpayload=text nomodeset"
And it works as expected.
Regards
Could solve by :
/etc/init.d/cman restart
sleep 5
/etc/init.d/pve-cluster restart
sleep 5
/etc/init.d/rgmanager restart
May be it is because I am using a STOP to the virtual machine that is runnig PVE, to simulate a problem with a server ?
Regards
Hi I'm experiencing similar problem as described here, so I've reused this thread.
I'm testing CLUSTER using proxmox 'self-virtualization' as suggested by some user on this forum (thanks to him, can not find the thread where I read it, sorry).
I've created 3 virtual machines, each of them...
Workaround found:
fence_ilo3 works (only with ILO2 version 2.23)
Result previously found:
was corrected using a 'new' flag -M used as stated in fence_ilo3 -h
-M <method> Method to fence (onoff or cycle (default onoff)
It seems hat default is cycle. So:
#fence_ilo3 -o off -M onoff...
Tested, same problem.
I'm testing again two servers:
1.- ILO version 1.5 (year 2008)
2.- ILO version 2.23 (actual version)
Both of them work with the Fedora workstation.
Tested also from two pve servers...
Regards
Follow-up:
I've installed on a workstation with Fedora 19:
-fence_agents_common
-fence_agents_ilo2
and it works!! (from this workstation). It has installed fence_ilo2 version 4.0.4. The one in PVE 3.1 is Version 4.0.0
I've copied fence_ilo2 to PVE server, and tried : same...
Hi, I have the same problem.
Mi DL-360 G5 server has ILO2 version 2.23 (just upgraded).
Tested with fence_ilo & fence_ilo2 I get same message:
# fence_ilo -o status -a 192.168.200.xxx -l user -p passw -v
<?xml version="1.0"?>
<?xml version="1.0"?>
<RIBCL VERSION="2.22">...
There are times, mainly on tests servers, that you do not want to automatic start VMs and containers at the last part of boot.
Instead of disable automatic start on every machine, a global solution, was wanted.
Looking at the way PVE starts, got to /etc/rc2.d/S20pve-manager script (link to...
I found the problem !!
I was using a wrong node name. I edited manually /etc/hosts with the wrong hostname used in the second curl, hence it was resolved, and I could obtain a TICKET...
Thanks for your help...
Same result, no output of curl. Created a new script, just to test:
$ more test
TICKET=`curl -k -d "username=root@pam&password=*********" https://proxmox179:8006/api2/json/access/ticket | sed 's/\\\\\//\//g' | sed 's/[{}]//g' | awk -v k="text" '{n=split($0,a,","); for (i=1; i<=n; i++) print...
@ spirit. Could you please help me to diagnose this NO working script ?
# cat Spice5214.sh
#!/bin/bash
USERNAME=root@pam
PASSWORD=mipasswordhere
VMID=5214
NODE=proxmox179
PROXY=proxmox179
TICKET=`curl -k -d "username=$USERNAME&password=$PASSWORD"...
Installation finished. Created one machine with Proxmox VE 2.2-32 . Thanks. :)
Only point to the instructions (in case it helps someone) is that 2.2-32 last kernel is pve-kernel-2.6.32-17-pve
Regards.
No I'm not a commercial subscriber
I understand your position (old system, no support), but ...
I have a remote server, that I can not upgrade.
I need to restore a KVM machine there, and unfortunatelly, backup changed from tar to vma on 2.3.
Is there any way I can restore a backup (done in...
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.