Thank you to all three of you for your time for me. I downloaded the following file for guest os:

http://releases.ubuntu.com/12.04/ubu...ktop-amd64.iso

and wanted to install it inside vmware player. Got the following error message:

"This virtual machine is configured for 64-bit guest opeating systems. However, 64-bit operation is not possible. This host supports Intel VT-X, but Intel VT-x is disabled."

I found the solution to this on my own. It is here:

https://communities.vmware.com/message/2451618

As explanation says, I did F1 when restarting, found Security tab but here is where my hopes ended. There is NO "System Security" anywhere, neither "VT-x" anywhere. Under Security tab I only see the following:

hardware password manager
current setting
administrator password
power-on password
set administrator password
set power-on password
allow flashing bio to a preview version
require admin password when flashing
require POP on restart
smart usb protection
require administrator pass for F12 boot
hard disk password
fingerprint setup
tcg feature setup
system event log
secure boot
network offline locker setup
configuration change detection

It maybe under systemconfiguration tab svm support enable/disable

Ok so basically I did a lot. The guest os of Ubuntu 64bit was successfully installed. Even managed to do upgrades that took a lot of time. Did some google research but it worked. However there are still following problems:

1. When opening Virtual Machine (installed guest os), I get the following error which doesn't prevent guest os from loading but it is still annoying:

"[ 8.597826] piix4_smbus 0000:00:07.3: Host SMBus controller not enabled"

2. On the following path of windows 8.1:

C:\Users\USERNAME\Documents\VirtualMachines\Ubuntu

I have some vmdk files. Those are 6 named "Ubuntu-s001" up to "Ubuntu-s006". They are very large sizes and I want to get rid of them as much as possible. Which ones can I delete and which one(s), if any, must I keep?

3. Sometimes (yes, not always) I am getting along previously (in this message) mentioned error also the following error:

"[ 15.364389] systemd-udevd[631]: '/usr/sbin/alsactl -E HOME=/var/run/alsa restore 0' [1019] terminated by signal 70 (Unknown signal 70)"

4. Problem with by far highest severity:

From the URL http://openach.com/content/introduci...nach-appliance

I chose Hyper-V Virtual Machine Image - The Originator 1.1 and it didn't work. Then, since I am using VMWARE player with linux ubuntu 64-bit finally successfully installed, I obviously tried also VMware Virtual Machine Image - The Originator 1.1. Unrared the .vmdk file and now im getting, obviously within vmware player (inside ubuntu guest os) the error message:

"Could not display File.vmdk The file is of an unknown type"

If I rename vmdk file to iso (renaming extension within filename) then when i try to open that iso only window Image Burning Setup is shown and when choosing destination path, nothing works because under Select A Disc To Write To always say "No disc available" and then in the same window but below also says "Please replace the disc with supposted CD or DVD".

I think the next step is to try to learn how to mount image within linux ubuntu within vmware player corretly since I assume I am doing something wrong. Right clicking and choosing Open With Disk Image Mounter doesn't work, neither for vmdk nor for iso extension (same file) because nothing happens BUT it could be possible (even is windows is same) that nothing is supposted to pop up, instead I should try to search for "something mounted" on my own. However in Linux ubuntu there is no "My Computer" as it is in windows, and searching for WHERE was "something mounted" exceeds my ubuntu knowledge. Tried every button on left handy vertical taskbar and didn't find anything. Im still assuming I am getting error message bolded above because I don't know how to mount correctly and how to use mounted file. There is also secondary instruction what could be done to mount correctly:

http://www.tech-recipes.com/rx/2747/...unt_iso_files/

but there is no way I could do in light years what is being shown on this page on 7 steps.



I spent entire weekend working on this. Im Not saying I wasted it. Didn't because I managed to install guest os just fine but now those four problems are very complicated.

1. That is just a warning, ignore it.
2. These large files are the virtual harddisk of the virtual machine you installed Ubuntu on. Deleting one or more will make the installation inoperable.
3. That message indicates that the Ubuntu installation was not able to restore the previous volume setting of the virtual soundcard. Without proper investigation it is impossible to find the reason for that, I recommend to open a separate thread about this topic (if you still want, after reading my answer to point 4).
4. The .vmdk file is also a virtual harddisk, it has to be opened with VMware Player, not the OS installed inside. From what I get from that website, the software you want to use comes as appliance, not as separately installable software. This means that the software comes with its own operating system. If we would have known that before you could have saved all the time and hassle installing Ubuntu first, this seems to be not necessary at all, all you had to do was importing the appliance to VMware Player. So, indeed, you can say that time was wasted (if you don't count that you know have learned how to install Ubuntu to a virtual machine).

Regarding 4: Whenever you will have some available time, could you please describe more what do you mean with "it has to be opened with vmware player"? I know you are saying I should NOT open it or try to mount it within guest os. Knowing this isn't enough. How am I supposted to open it with vmware player as you said? Which option on main vmware player screen?

"Create a new virtual machine" ? If yes, this option with VMDK doesn't work and you said VMDK extension should work. It is requesting ISO. I tried ISO (renamed extension from VMDK to ISO directly in filename) but within New Virtual Machine Wizard, it says "Could not detect which operating system is in this disc image. You will need to specify which operating system will be installed."

The problem is that I installed it already. Why it would need to be installed again is beyond my understanding. I tried to click Next with opinion similar to "i installed it so it should recognize installed one". Then I chose installed guest os and version and clicked Next. But in the next window I saw the same annoying part of this New Virtual Machine Wizard as previous time (referring to the field Virtual Machine Name which indicated another guest os [not installed/mounted wanted software] will be installed) installing the actual guest os and not the software.

"Open a virtual machine" ? If yes, this option doesn't work with neither VMDK nor ISO.

The zip-file you downloaded should also contain a .vmx file, which contains the description of the appliance for VMware. Try to open that instead, using the "Open a Virtual Machine" option.

there is no VMX file anywhere. I would have tried it if there was one.

I will download the file and have a look at it, but this can take some time, I am on a slow connection currently.

Ok thanks. I was downloading only VMware Virtual Machine Image - The Originator 1.1 and Hyper-V Virtual Machine Image - The Originator 1.1. If I should try also either of other three mentioned on the link, even if i have vmware player, let me know.

OK, so the OpenACH people made the decision to distribute their software as disk image instead of a complete VM, but that shouldn't be a problem.
I don't use VMware, but this is how it should work:
- Create a new virtual machine and tell it that you want to install the operating system later.
- When asked about the harddisk, don't create one, but tell it to use the downloaded .vmdk file instead. If that is not possible create a small harddisk image, delete it later in the hardware settings dialog for the VM and add the downloaded .vmdk disk image.
- When you now start the VM you should see a starting Ubuntu system and you can follow the instructions on the website to complete the installation.
- After that, complain to the developers about this really odd distribution strategy.

Another possiblity is to go into the hardware settings for the ubuntu install and add the vmdk disk image as a second hard drive. Then boot Ubuntu, open a terminal to run sudo update-grub to be able to boot the second drive.

tobisgd: I have the option to install os (it is installed already!) later but Im NOT asked about harddisk, therefore don't have the option to NOT create one. I uploaded the screenshot of different steps here: http://s10.postimg.org/536dupgh5/vm111.jpg You mentioned alternative option to create small harddisc image: There is no button to add VMDK file extension anywhere in Hardware settings, not even in "Open a virtual machine". Additionally even if it was, if I deleted just created small harddisc, why would I be creating one then? Just for removal purpose? So since, as shown on screenshot, I am not able to NOT create harddisk, I cannot go to third step of your instruction in your latest post.

colorpurple: I also did different screenshot for you according to your reply: http://s21.postimg.org/whm0pn5hj/vm222.jpg You told me I need to add a second hard drive. So clicking "Hard Disk (SCSI)" and then button "ADD" and then I choose Hard Disk\Next\SCSI\Next. But here, on the next page of same window (NOT shown on screenshot), I have to choose (?):

create a new virtual disk
use an existing virtual disk
use a physical disk (for advanced users)

which one? Since you said a SECOND hard drive, I would assume the correct choice is "create a new virtual disk". To run Ubuntu I know I just click on "Play virtual machine" on the main vmware player's interface but how am I supposted to open a terminal? Since you followed this step with next step, typing a command, i assume it is something like Command Prompt in windows but not sure how would I access terminal WITHIN guest os? And what is this:

Any reason you're tied to VMware? I don't use it very often (I avoid it as much as possible) so I don't know if it's possible or if so how, but I see they offer a VirtualBox image instead. Setting that up is very easy, in the 5th step on your image there's another option called "use an existing drive" or similar that lets you specify the drive file and boot it up instead of creating a new one.

use an existing virtual disk

colorpurple I typed the command you mentioned in so called Terminal (googled how to access it), after verifying the command with password (since noone told me password won't be shown as BEING TYPED, i had to do additional task and google even this issue) this is what I got - the quoted text:

"Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-3.13.0-48-generic
Found initrd image: /boot/initrd.img-3.13.0-48-generic
Found linux image: /boot/vmlinuz-3.13.0-32-generic
Found initrd image: /boot/initrd.img-3.13.0-32-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
done
username@ubuntu:~$"

and what am I supposted to do now?