[Spce-user] New Community Install

Michael Prokop mprokop at sipwise.com
Thu Nov 5 10:42:34 EST 2015


Hi,

it would be enough if you could take a look at the VM's underlying
vmx configuration file or just drop this to me so I could figure out
the changes your team did.

regards,
-mika-

* Serge S. Yuriev [Thu Nov 05, 2015 at 05:55:57PM +0300]:
> Hi,

> Sorry I don't know what it was exactly :(
> IIRC something like unsupported diskimage version
> And our team didn't remember either..

> On 05/11/15 17:13, Michael Prokop wrote:
> >Hi,

> >is there any chance you might share the fix with us?

> >If we could integrate the proper configuration into our underlying
> >vmware.vmx configuration then we might be able to properly support
> >newer VMWare environments out of the box too.

> >regards,
> >-mika-

> >* Serge S. Yuriev [Thu Nov 05, 2015 at 04:24:19PM +0300]:
> >>Hi,
> >>We started from VMWare image few versions ago (3.6 or so) and also
> >>got some kind of unsupported error but our devops was able to handle
> >>this.
> >>After fixing diskimage system working correctly w/default limits.
> >>On 04/11/15 18:50, Atlanta Man wrote:
> >>>Hi Alex,
> >>>Thanks for your response.
> >>>I did try the VMWare Image first, actually.    First I added it to
> >>>the inventory using the .vmx file.  When I tried starting it
> >>>reported an unsupported disk file definition.  Then I created a new
> >>>machine using the disk drive.  (several attempts).  The system
> >>>would abort for reasons I have not been able to determine.  One
> >>>issue is my VM environment does not have a DHCP server defined.   I
> >>>set the IP statically after the system starts.  I then enter
> >>>commands to stop the firewall. After that the system aborts.  I'm
> >>>puzzled!



> >>>On Wednesday, November 4, 2015 9:53 AM, Henry L. Jones
> >>><henryjones at axxtel.com> wrote:

> >>>Hi Michael,
> >>>Thanks for your response.

> >>>I am running VMWare ESXi 6.0.0 on a Dell PowerEdge R710 server.
> >>>The new VM for SIPWise was defined as2 cpus with 2
> >>>cores,  2 gb memory, 2 NIC cards, Debian x64 with 60gb hard drive.
> >>>The drive was defined new and not initialized.  The ISO was
> >>>installed on a fresh VM. I used the LSI Logic Parallel SCSI
> >>>controller for the virtual disk.
> >>>Thanks
> >>>On Wed, Nov 4, 2015 at 8:22 AM, Michael Prokop <mprokop at sipwise.com
> >>><mailto:mprokop at sipwise.com>> wrote:
> >>>    * Henry L. Jones [Tue Nov 03, 2015 at 12:22:25PM -0500]:
> >>>    > Is anyone having issues when installing SipWise from the iso?  I
> >>>    have tried
> >>>    > versions 4.1.1 and 3.8.3.  In both instances the installation
> >>>    completes
> >>>    > successfully and the system reboots. After the reboot the system
> >>>    reports a
> >>>    > grub error.
> >>>    > Error: fd0 read error
> >>>    > Error: no such disk
> >>>    > Entering rescue mode ...
> >>>    > grub rescue>
> >>>    > When I enter a set I get:
> >>>    > prefix=(ngcp-root)/boot/grub
> >>>    > root=ngcp-root
> >>>    > When I enter ls I get:
> >>>    > (hd0) (fd0)
> >>>    You should also see (hd0,msdos1) + (ngcp-root).
> >>>    > I am installing on a VM environment with a definition of 2 cpus
> >>>    with 2
> >>>    > cores,  2 gb memory, 2 NIC cards, Debian x64 with 60gb hard drive.

> -- 
> Serge S. Yuriev
> Lead VoIP engineer

> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20151105/f48daba9/attachment-0001.asc>


More information about the Spce-user mailing list