SOLVED issues installing 20650 on Hyper-v 2012

[darmock]

Well that was put in for a very specific reason.

A long time ago in a galaxy far far away..........

Digium changed the spec for the make menuconfig so it would only display in a terminal with a resolution greater than standard. (80x25) thus why the switch is included by default. Not sure if they finally fixed this or not as there was a howl of protest by people. We just added the switch and made the problem go away for most. This is why during the setup portion of our installer it actually checks your terminal resolution to ensure it is greater than 80x25 IF you choose to use make menuconfig. If you use the autoconfiguration option it does not need the extra resolution. It was decided to make it mandatory as at the console you have to reboot to change the resolution.

So yes everything has a reason. IF Digium finally came to their senses and removed this requirement then the next ISO can be modified to remove it if not it is there to stay.


Not sure where we will go from here as the ISO is designed for the lowest common denominator and this is not hyper-v users. Interesting that it installs under 20645 and not 20650 as the setting of the console has been there since 20600! So our original premise of centos breaking things (pardon me correcting things) between minor versions is still valid.

Thanks for all your hard work on this...... I will think some to see if there is a solution that will fit into our conceptual framework of reality. For the moment users can simply interrupt the firstboot AFTER the base install and remove the vga= line and then edit out the command in /boot/grub/grub.conf. Let me know if this works and then you could see if make menuconfig will work in an 80x25 screen or perhaps you can set hyper-v to accept the higher screen resolution.


Thanks

Tom

 

[MrBostn]

I'll try it today. Thank you

 

[CSerpent]

I can confirm this works nicely, I changed it to nomodeset and it's booted fine.

 

[MrBostn]

Tee hee. Remove vga=791 from the grub configuration kernel line.

You owe me beer.

Thank you. Worked as stated.

 

[darmock]

I can confirm this works nicely, I changed it to nomodeset and it's booted fine.

Ah forgot we put that in! Good catch.

Tom

 

[atsak]

Well, it's not that hard to work around, and the vga=791 line is all over the net as a suggested "fix" for video issues. So it seems to make sense to have it there because of that. Except that at the same time make menuconfig is "not supported" (so says the install ) so it seems a bit odd to have a setting in to accommodate that particular option. I have no idea what's the better way either so don't know what to suggest, but at least we know what to do. It's just that the hyper v 2012 r2 now supports one to many async replication natively and you can get it for free, so it's a very full featured product that MS isn't charging for (though of course they will at some point figure out a way to charge for it, but so does every other software company out there eventually).

 

[darmock]

We won't support the ENDLESS options that are available in make menuconfig. Perhaps a better way of wording it is that you change anything you support it yourself. However that being said it IS available during the install for folks who want to do it "their" way. Beyond that we are FIRMLY committed to folks going to hell in the way they choose...... we just won't give them support when it breaks...... Remember that the ISO/Install is NOT targeted for advanced linux users.... rather it is the newbs who don't know what linux is......

Tom

 

[ccwtech]

Same issue. I'm trying to find out how to edit that. Not familiar with Grub and Google hasn't been helpful to me this morning.

Update: in case anyone has this issue. Upon boot hit a key to stop autoboot.

1 Select e for edit commands before booting
2 Select kernel
3 e to edit
4 remove VGA=791
5 press enter
6 b to boot

Then, once in, you will want to edit the file /boot/grub/grub.conf to make it stick.

 

[atsak]

Press a to edit the line I find in Centos 6.5.
Once in /etc/grub.conf.

e doesn't work sometimes.

 

[kflorian]

welp....using the installers from here:

http://sourceforge.net/projects/pbxinaflash/files/PIAF-3.6.5-Installer/

I do not even see the "VGA=791" in the kernel line.

(I shoulda learned linux when time was endlessly available)

 

[Support MTC]

it seems that after installing a fresh installation on Hyper-V 2012 CENTOS 6.5 64 bit or 32 bit minimum we reach the point where (yes you must remove the vga=791 line and add nomodeset). After the PIAF installation launches everything works fine until the system begins the actual pbx installation. What I mean is after the password is given and flavors are chosen the install proceeds. The problem occurs on the reboot which when "Applying firewall rules" after asterisk is started on boot the system hangs. I have tried different machines and also both the pre-packages ISO for PIAF and also the downloaded installer for PIAF. both result in the same problem. this is halting us and any help would be immensely helpful. Thanks guys.

 

[atsak]

It is the same problem. The vga=791 line is reappearing in there I will wager. I do not recall how I eventually worked around it other than the instructions above . . . I'd have to try it again.

wardmundy do you think you / I / we could "unofficially" put a Hyper V vhd up somewhere the community could share? There are lots of us using this and it works well for most of us (contrary to what the Freepbx folks say, which is fair enough). We could call it an unsupported type install anyway.

 

[Support MTC]

To further correct the point, i do have a working install that has these parameters:
CENTOS 6.5 i386
Linux pbx.local 2.6.32-431.1.2.0.1.el6.i686 #1 SMP Fri Dec 13 11:45:23 UTC 2013 i686 i686 i386 GNU/Linux
Asterisk 11.8/PIAF Green/INCREDIBLE PBX 11
Freepbx 11

This setup was done on hyper-v a few months back. This was successful. however no when using the latest ISO or doing the downloaded installer method on a minimum install it hangs. After inspecting the boot grub requirement it is completely blank.

I would love to help maintain a location for VHDs that are preconfigured in a working state. I do understand that these drives are rather large and must be used in torrents to distribute it correctly but i am humbled at the experts in the communicity and hope to be guided on this problem and how to incorporate VHDs in distributions from PIAF.

 

[Chris Sweeney]

it seems that after installing a fresh installation on Hyper-V 2012 CENTOS 6.5 64 bit or 32 bit minimum we reach the point where (yes you must remove the vga=791 line and add nomodeset). After the PIAF installation launches everything works fine until the system begins the actual pbx installation. What I mean is after the password is given and flavors are chosen the install proceeds. The problem occurs on the reboot which when "Applying firewall rules" after asterisk is started on boot the system hangs. I have tried different machines and also both the pre-packages ISO for PIAF and also the downloaded installer for PIAF. both result in the same problem. this is halting us and any help would be immensely helpful. Thanks guys.

Have you edited grub.conf after booting into linux to make the change of removing vga=791? Removing it on boot doesn't make the change permanent and you will have the problem again until you edit grub.conf once booted into linux.

 

[Support MTC]

chris sweeny: It looks like the problem is interesting but i was already in the direction early this morning at looking at what might have gone wrong (thank you for the pointer).

Whenever we load the grub editor form the boot menu it was showing everything as blank. Meaning no parameters were stated. After inspecting the file it seems there were some formatting issues as well as the vga=791.

After booting into rescue mode and editing the grub.conf this allowed me to resolve this problem. I would suggest anyone who is having this problem to make sure to double check their grub.conf file at /boot/grub/grub.conf file to ensure that all the proper lines are in the place or removed. i did have to mount the the boot image into CHROOT and then launch the sshd server so i can edit it properly from an external program. for some reason when editing this machine with nano in rescue mode caused some incorrect formatting issues in the grub.conf file. FYI, ensure that you have some way to get into the rescue mode.