Hey there, Apparently, the error message is saying that virtualization feature is disabled, you can verify it running in the host machine running
$ egrep ‘(vmx|svm)’ /proc/cpuinfo In the other hand, if that computer was provisioned by OpenStack, the Compute node where that instance is hosted has to support nested virtualization which can be enabled the proper kernel module. · https://docs.openstack.org/devstack/latest/guides/devstack-with-nested-kvm.html I haven’t tried to use the scripts isolated (there are plans to document and test that in the future) but maybe this can work $ git clone https://git.onap.org/integration $ mv integration/bootstrap/vagrant-onap/lib /var/onap $ source /var/onap/policy $ init_policy Regards, Victor Morales From: <onap-discuss-boun...@lists.onap.org> on behalf of Viswanath Kumar Skand Priya via onap-discuss <onap-discuss@lists.onap.org> Reply-To: "viswanath.kumarskandpr...@verizon.com" <viswanath.kumarskandpr...@verizon.com> Date: Wednesday, August 16, 2017 at 6:51 AM To: "'DRAGOSH, PAMELA L (PAM)'" <pdrag...@research.att.com>, Atul Shegokar <as00500...@techmahindra.com>, "Guo, Ruijing" <ruijing....@intel.com> Cc: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org> Subject: Re: [onap-discuss] Facing issues with policy setup with Vagrant I’m also facing similar issue. Although, going through Google, I learnt that nested virtualization is not supported. Apparently, I’m running a Ubuntu VM in openstack and I’m trying to use vagrant to power-up V-Box inside that Ubuntu. Is there any much simpler approach to bring up entire policy component in single VM? The READ.ME from http://gerrit.onap.org/r/policy/docker suggest to build individual mvn projects starting from “policy-common-modules”, but I couldn’t see that dir in my cloned repo. Also, https://wiki.onap.org/pages/viewpage.action?pageId=11929334 page explains about building PDP but not entire policy component. Could you somebody from policy team shed some light on development env setup? BR, Viswa From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of DRAGOSH, PAMELA L (PAM) Sent: Wednesday, August 16, 2017 5:13 PM To: Atul Shegokar <as00500...@techmahindra.com>; ruijing....@intel.com Cc: onap-discuss@lists.onap.org Subject: [E] Re: [onap-discuss] Facing issues with policy setup with Vagrant Atul, Sorry that you are having issues. I don’t know what those errors are or where they come from. Perhaps Ruijing could help you, he setup the vagrant for Policy. Not sure if you saw this wiki or if it would help: https://wiki.onap.org/pages/viewpage.action?pageId=11930786<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D11930786&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=9F3pNUkzjE-2v1eTClkRVe_0_NKUnq80ofq4I8oRnFqsXZpLuCtlULKYzwU3QsHo&m=AOFrZt9XLFVYKw8kegDMurnoKluXMlwzETmPN4Ujmnw&s=zKoYP3cS-nwxQ6wKy0SzYG3OpBVBfFlduSzCMTfdeNY&e=> Regards, Pam From: <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>> on behalf of Atul Shegokar <as00500...@techmahindra.com<mailto:as00500...@techmahindra.com>> Date: Wednesday, August 16, 2017 at 4:31 AM To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> Subject: [onap-discuss] Facing issues with policy setup with Vagrant HI team, I am trying to make setup for policy using vagrant. When I try to use vagrant up command, it gives an error saying VT-x is not available (VERR_VMX_NO_VMX). I have already made below checks – 1) VT-x AMD-V rea active in VM. 2) VT-x is enabled in BIOS. 3) Hyper-V is disabled and system rebooted (it was checked earlier). Please guide help, if there are any other possible reasons which are affecting vagrant up command working. Thanks & Regards, Atul Shegokar ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_Disclaimer.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4&m=ET5R9r4L8F5Imk4CVr4NbR9OTOvYMRD4t4Mi7HQEgz4&s=CLCDNXdk40202-s5qN8_DTq69katb1MRglD2cPK24t8&e=> externally http://tim.techmahindra.com/tim/disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__tim.techmahindra.com_tim_disclaimer.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4&m=ET5R9r4L8F5Imk4CVr4NbR9OTOvYMRD4t4Mi7HQEgz4&s=YaRmfmY6xAp4FOAMFzTMYUTDCh2Ca7Kaa_a13uzjNHA&e=> internally within TechMahindra. ============================================================================================================================
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
