metron-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zeolla@GMail.com" <zeo...@gmail.com>
Subject Re: errors
Date Tue, 12 Jul 2016 17:59:11 GMT
Hmm, not sure.  My first thought would be to
increase config.vm.boot_timeout like it mentions to some high number.  If
it still hits it, then it may be worth further investigation.  It may be
that the VM you provisioned is just very small/slow.

Jon

On Tue, Jul 12, 2016 at 1:15 PM Tejaswi Palacharla <
Tejaswi.Palacharla@sstech.us> wrote:

>
>
> This is the error
>
> *From:* Zeolla@GMail.com [mailto:zeolla@gmail.com]
> *Sent:* Tuesday, July 12, 2016 12:07 PM
>
>
> *To:* user@metron.incubator.apache.org
> *Subject:* Re: errors
>
>
>
> Can you please provide the text?  That resolution is tough for me to read.
>
>
>
>
> Jon
>
>
>
> On Tue, Jul 12, 2016 at 12:53 PM Tejaswi Palacharla <
> Tejaswi.Palacharla@sstech.us> wrote:
>
> I have got this error if I use this commands.  Wat to do next?
>
>
>
>
>
> *From:* Zeolla@GMail.com [mailto:zeolla@gmail.com]
> *Sent:* Tuesday, July 12, 2016 11:35 AM
>
>
> *To:* user@metron.incubator.apache.org
> *Subject:* Re: errors
>
>
>
> Looks much better now.  Try a vagrant halt then vagrant up.
>
>
>
> On Tue, Jul 12, 2016, 12:27 Tejaswi Palacharla <
> Tejaswi.Palacharla@sstech.us> wrote:
>
> I made the changes and it shows a different error.  Can u check it once?
>
>
>
> *From:* Zeolla@GMail.com [mailto:zeolla@gmail.com]
>
> *Sent:* Tuesday, July 12, 2016 11:07 AM
>
>
> *To:* user@metron.incubator.apache.org
> *Subject:* Re: errors
>
>
>
> I haven't used workstation in a while but I think it is a setting on your
> VM under processor.  Here's a link to how to do it on workstation 8 -
> http://vmwaremine.com/2012/02/03/enable-hardware-virtualization-in-vmware-workstation-8/
>
>
>
> On Tue, Jul 12, 2016 at 12:03 PM Tejaswi Palacharla <
> Tejaswi.Palacharla@sstech.us> wrote:
>
> Vmware workstation 12. Can u give me the steps if possible?
>
>
>
> *From:* Zeolla@GMail.com [mailto:zeolla@gmail.com]
> *Sent:* Tuesday, July 12, 2016 10:57 AM
>
>
> *To:* user@metron.incubator.apache.org
> *Subject:* Re: errors
>
>
>
> If your sandbox machine is a VM, then you need to configure VM nesting at
> the hypervisor level before it will be available within the guest (even
> within the BIOS).  What virtualization product are you using to run your
> sandbox (KVM, VMWare, VirtualBox, etc.)?
>
>
>
> Jon
>
>
>
> On Tue, Jul 12, 2016 at 11:52 AM Tejaswi Palacharla <
> Tejaswi.Palacharla@sstech.us> wrote:
>
> I tried going into bios and changing but virtualization is not present.
>
>
>
> Can u explain me what to do?
>
> Or there any other methods other than this?
>
>
>
> *From:* Zeolla@GMail.com [mailto:zeolla@gmail.com]
> *Sent:* Tuesday, July 12, 2016 10:41 AM
> *To:* user@metron.incubator.apache.org
> *Subject:* Re: errors
>
>
>
> It looks like you're trying to run the full-dev-platform from within a
> VM.  To do this, you need to configure VM nesting (i.e. you need to enable
> the x86 virtualization commands on your sandbox machine).  For how to do
> this with VMWare see https://communities.vmware.com/docs/DOC-8970, for
> more general details regarding x86 virtualization see
> https://en.wikipedia.org/wiki/X86_virtualization.
>
>
>
> Jon
>
>
>
> On Tue, Jul 12, 2016 at 11:35 AM Tejaswi Palacharla <
> Tejaswi.Palacharla@sstech.us> wrote:
>
> Tried to install everything on Horton work sandbox.
>
> Installed ansible, python, vagrant, vbox.
>
> When giving vagrant up we get the following error.
>
>
>
> --
>
> Jon
>
> --
>
> Jon
>
> --
>
> Jon
>
> --
>
> Jon
>
> --
>
> Jon
>
-- 

Jon

Mime
View raw message