On Aug 11, 2015, at 9:12 AM, Deepak Sharma <deeky.sha...@gmail.com> wrote:
> But when I tried to run it from the command line it didn't worked out > but an error occurred. Just to check what really the error is I > installed GUI in it and checked for an error. It said 64 bit is not > compatible. Inside VM when I clicked on "New" (for creating new disk) > then only 32 bit options were present and none of the options were 64 > bit. It sounds like you created a 32-bit VM and were trying to run a 64-bit VDI. > In order to cross check whether 64 bit error exists in freebsd too or > not I moved to freebsd and followed the same i.e installed freebsd and > then inside it VM and then tried to run .vdi file inside it. I > installed VM through pkg as ports throws make error. Inside freebsd I > installed VM version 4.3.30 and tried to run .vdi from command line > but didn't succeed much:-/. Just to check what error I'm getting I > installed GUI and got the same result i.e 64 bit ubuntu is not present > in the list. Even though I tried to run Ubuntu Server ISO (64 bit) > inside VM but same result. Potentially a ditto issue if you installed a 32-bit FreeBSD server. You need to confirm that everything you are running is 64-bit if you created a 64-bit image OR create a 32-bit image (which would be fine for this). > I downloaded Ubuntu Sever 14.04 LTS (32 bit) and installed all the > necessary things that are required to run OGV and tested it. From > single guest to host it works perfectly. But when I tested that VM > inside VM I produce following error : No image/error message came through the mailing list. If you embedded an image, I suggest posting it to an image pastegin (e.g., imgur) and just including a link. > In order to run it from command line I installed phpvirtualmachine, > apache2 and php5 so that I can upload .vdi file directly from host > browser. But whenever I run it (.vdi file inside VM) it runs upto GRUB > and after that blank screen occurs. Same is the case inside freeBSD's > VM. You need to boot grub and/or linux in verbose mode so you can see what’s actually happening. There’s no way to know what a blank screen after grub means without more info. > Now, I am thinking to shift .vdi file directly .bzy server and run > there. I am just eagerly waiting to see OGV running successfully. The fact that you haven’t been able to boot the image headless is not a good sign. :) Keep at it — the first thing to confirm is whether the VDI you created and the environment contained therein is 32-bit or 64-bit. Once you confirm that, you should get remote login working locally, so you can ssh into the VDI environment. If you can do that, then it should be a simple matter of installing the right version of VBox on the server and logging in remotely. You should avoid using or installing a GUI so you can better understand what is really going on and learn how to inspect/control the environment with command-line methods — that is how it will be run too. Cheers! Sean ------------------------------------------------------------------------------ _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
