Change resolution of installer

Y

yatesco

Well-Known Member
Sep 25, 2009
211
5
58
Hi,

I am trying to install proxmox onto my ovh hosted server but the vKVM console appears to be 800x600 where as the proxmox installation appears to be 1024x768.

What magical parameters do I pass to the proxmox installer on the grub menu list (i.e. after pressing tab) to boot into 800x640 (or 600 whichever it is)?

Ta.

Col
 
No, they can answer the "how do I change the resolution of vKVM" question I posted.

I was hoping you would be able to answer questions about your own software - hence I deliberately didn't ask you anything about OVH :)
 
yatesco said:
No, they can answer the "how do I change the resolution of vKVM" question I posted.

I was hoping you would be able to answer questions about your own software - hence I deliberately didn't ask you anything about OVH :)
Click to expand...

vKVM is a OVH tool, our installer needs 1024x768.

OVH is actively supporting and installing Proxmox VE, so they know how to do it on their servers.
 
I wish I never mentioned OVH now - that seems to have muddied the waters somewhat - if you read the question again you will see I am only asking about your installer, not about vKVM or anything else. I provided that merely as background.

tom said:
our installer needs 1024x768.
Click to expand...
Yes, indeed. My question is can this reduced to 800x640?

Better stop typing now before I get a reputation as a grumpy git ;)
 
Hi yatesco :)
All proxmox @ OVH users knows that OVH change a lot at original proxmox installation.
I do understand that PROXMOX's people can not help you (they simply do not know what OVH have been changed)

please note that this procedure was tested for proxmox 1.2, 1.3 and 1.4 only - we use it in production on our 5 servers @OVH

I have some dirty Hack solution for your both of OVH's users problems:
instalation in vKVM mode
-- please install firebug extension to your Firefox (http://getfirebug.com/)
-- after you reboot your vKVM and select installation of proxmox from FTP with 64bit option enabled you will see 800x600 X-window installation of proxmox
-- please use firebug to change the resolution of vKVM iframe to 1025x769
than you can follow the installation in "NORMAL" way
(please note that it is OVH issue - they should give possibility to change this resolution of vKVM - I have asked them and they said this is impossible ! - but ask them again maybe two voices will convince them ;)

Hanging GRUB boot at very and of proxmox installation.
-- when you have it (boot manager is hanging at 9x%) - simply stop installation of proxmox.
-- reboot your OVH machine in RESCUE MODE (you can setup this at OVH manager)
-- when you are in logged into your server inrescue mode do this what PROXMOX perl installation script could not do during emulated vKVM mode:
Code: 
#------------------ please collect information about your machine
#gateway and ip address - please note them on some paper
ip route list
#-------- scan for LVM discs
lvscan #/dev/pve/root
#--------------- fix filesystems 
e2fsck -fcv /dev/sda1
e2fsck -fv /dev/pve/root
#------------ make change root environment at 'p' directory
mkdir p
mount /dev/pve/root p
mount --bind /proc/ p/proc/
mount --bind /sys/ p/sys/
mount --bind /dev p/dev
# ---------- change the root
chroot p
#------------------ reinstall boot manager
mount /dev/sda1 /boot/
grub-install /dev/sda1
grub-install /dev/sda
update-grub 
sync
#------setup the network and DNS settings for this machine 
vim /etc/network/interfaces
vim /etc/resolv.conf
#------------------ set password for root user
passwd root
#------------------ clean-up (copied from PROXMOX installation script)
unlink /etc/mtab 
touch /etc/mtab 
unlink /usr/sbin/policy-rc.d
rm -f /sbin/start-stop-daemon
dpkg-divert --remove "/sbin/start-stop-daemon"

#------------------ save buffers and exit the chroot
sync
exit

#----------- setup BOOT FROM HD at OVH server administration panel
#------------------ reboot the server
reboot

both of PROXMOX at OVH user's problems could be solved by Proxmox and by ovh.
proxmox culd make boot options for changing the resolution of installation process and culd also give an option for skiping grubb installation proccess
OVH culd fix their vKVM change resolution option (it is so easy)

Having objective point of view:
OVH should NEVER give people NOT working/changed version of proxmox.
all problems with proxmox at ovh are because OVH changed a loot - they made proxmox useless (no LVM means no snapshots)

From my point of view OVH should ask Proxmox for help in preparation of the image of the proxmox environment @OVH.

But also Proxmox could talk with OVH and suggest this help.

So at the and PROXMOX, OVH and USERS would be very happy :)

all best for Proxmox OVH and users
aNeutrino :)

ps. before setting up KVM machines at OVH's proxmox please read this:
http://www.proxmox.com/forum/showthread.php?p=8216
http://help.ovh.co.uk/Proxmox
 
aNeutrino said:
Hi yatesco :)
All proxmox @ OVH users knows that OVH change a lot at original proxmox installation.
I do understand that PROXMOX's people can not help you (they simply do not know what OVH have been changed)

please note that this procedure was tested for proxmox 1.2, 1.3 and 1.4 only - we use it in production on our 5 servers @OVH

I have some dirty Hack solution for your both of OVH's users problems:
instalation in vKVM mode
-- please install firebug extension to your Firefox (http://getfirebug.com/)
-- after you reboot your vKVM and select installation of proxmox from FTP with 64bit option enabled you will see 800x600 X-window installation of proxmox
-- please use firebug to change the resolution of vKVM iframe to 1025x769
than you can follow the installation in "NORMAL" way
(please note that it is OVH issue - they should give possibility to change this resolution of vKVM - I have asked them and they said this is impossible ! - but ask them again maybe two voices will convince them ;)

Hanging GRUB boot at very and of proxmox installation.
-- when you have it (boot manager is hanging at 9x%) - simply stop installation of proxmox.
-- reboot your OVH machine in RESCUE MODE (you can setup this at OVH manager)
-- when you are in logged into your server inrescue mode do this what PROXMOX perl installation script could not do during emulated vKVM mode:
Code: 
#------------------ please collect information about your machine
#gateway and ip address - please note them on some paper
ip route list
#-------- scan for LVM discs
lvscan #/dev/pve/root
#--------------- fix filesystems 
e2fsck -fcv /dev/sda1
e2fsck -fv /dev/pve/root
#------------ make change root environment at 'p' directory
mkdir p
mount /dev/pve/root p
mount --bind /proc/ p/proc/
mount --bind /sys/ p/sys/
mount --bind /dev p/dev
# ---------- change the root
chroot p
#------------------ reinstall boot manager
mount /dev/sda1 /boot/
grub-install /dev/sda1
grub-install /dev/sda
update-grub 
sync
#------setup the network and DNS settings for this machine 
vim /etc/network/interfaces
vim /etc/resolv.conf
#------------------ set password for root user
passwd root
#------------------ clean-up (copied from PROXMOX installation script)
unlink /etc/mtab 
touch /etc/mtab 
unlink /usr/sbin/policy-rc.d
rm -f /sbin/start-stop-daemon
dpkg-divert --remove "/sbin/start-stop-daemon"

#------------------ save buffers and exit the chroot
sync
exit

#----------- setup BOOT FROM HD at OVH server administration panel
#------------------ reboot the server
reboot
both of PROXMOX at OVH user's problems could be solved by Proxmox and by ovh.
proxmox culd make boot options for changing the resolution of installation process and culd also give an option for skiping grubb installation proccess
OVH culd fix their vKVM change resolution option (it is so easy)

Having objective point of view:
OVH should NEVER give people NOT working/changed version of proxmox.
all problems with proxmox at ovh are because OVH changed a loot - they made proxmox useless (no LVM means no snapshots)

From my point of view OVH should ask Proxmox for help in preparation of the image of the proxmox environment @OVH.

But also Proxmox could talk with OVH and suggest this help.

So at the and PROXMOX, OVH and USERS would be very happy :)

all best for Proxmox OVH and users
aNeutrino :)

ps. before setting up KVM machines at OVH's proxmox please read this:
http://www.proxmox.com/forum/showthread.php?p=8216
http://help.ovh.co.uk/Proxmox
Click to expand...

We work quite close with OVH now and the new default Proxmox VE installation from OVH will use LVM soon (if you want LVM now, you can change this easily by hand booting the rescue system, not vKVM), go live is soon.

This means if you order a dedicated server at OVH you will got a quite useful standard Proxmox VE setup. you can also use the default bridge setup for KVM guests as OVH adapted their network routers - you just have to tell the routers which MAC so you use in your KVM guest.

I recommend the following additional options:
- Add the Cisco Firewall
- Add the optional hardware raid controller (if not already included)
 
thanks Tom for your fast answer :)
It is very good that you do it together !!!
all sides will profit from this.

...Well yes we could just move all data to LVM in rescue mode
but the issue is that we are not sure what OVH changed maybe LVM is the only thing but nones now :(
that is why we decided to make REAL proxmoxs from YOUR iso and than just fix boot manager in rescue mode. ugly but works for now...

many many thanks again.
Looking forward for new Proxmox and OVH cooperation.
all best
aNeutrino
 
tom said:
We work quite close with OVH now and the new default Proxmox VE installation from OVH will use LVM soon (if you want LVM now, you can change this easily by hand booting the rescue system, not vKVM), go live is soon.
Click to expand...
Great news - do we have an ETA on this?

Thanks all for replying.
 
You must log in or register to reply here.
Top Bottom