I try to start MINIX in VmWare, however, there it is stucked in "Started VFS:8 worker thread(s)"
I don't know why? does anyone have the problem?
Normal boot process continues with mounting /dev/c0d0p0s0..2
Q: Can't start?
A: Can. Follow the MINIX step-by-step scenario for VmWare hypervisors
http://wiki.minix3.org/UsersGuide/RunningOnVmware recommends for
Running on VMware
This page describes the process of installing MINIX 3 on VMWare.
1. Preliminaries
Please install VMWare. VMWare binaries can be downloaded from their webpage.
2. Virtual Machine Setup
Before you install Minix 3, you will need to create a new virtual machine configuration. The VM configuration specifies the parameters of your Virtual machine, e.g., how much memory you want the VM to use, how big you want the virtual hard disk to be, etc.
2.1. Create a Virtual Machine -- case: VMware Server
In the main menu of VMware, select New Virtual Machine.
Press Next in the Welcoming Screen.
At the Virtual machine configuration menu, we select Typical.
At the Select a Guest Operating System, select Other and Version Other.
For Virtual Machine Name, write Minix3 (anything would work).
At the Network Type screen, select Use bridged networking.
For Disk Capacity, enter something around 2GBs, although even smaller values would work. That is the size of the virtual partition where Minix will be installed. Tick the Allocate all disk space now.
Pressing Finish will create the Disk Image and the Virtual Machine that we will run.
2.2. Create a Virtual Machine -- case VMware Workstation and VMware Player (version > 3)
In the main menu of VMware, select New Virtual Machine.
At the Wizard, select Typical; and then, press Next.
For the Guest Operating System Installation, select I will install the operating system later; and then, press Next.
At the Select a Guest Operating System, select Other and Version Other.
For Virtual Machine Name, enter Minix3 or some other meaningful name.
At the Specify Disk Capacity, enter 2GBs, which is enough for all packages and sources. You can make it larger if you need to add more source files.
At the Ready to Create Virtual Machine, ensure that Power on this virtual machine after creation is not checked; and then, press Finish.
You will need to edit the memory settings according to your needs. In the Devices section, select the Memory, and adjust the memory accordingly. Note that, in order to run the X Window System on Minix, you need at least 384MB.
2.3. Create a Virtual Machine -- case: VMware Player (version < 3)
If you are using the free VMware Player, you do not have the ability to create new virtual machines. The simplest way around that is to use EasyVMX to create your new (empty) virtual machines.
Choose the Super Simple virtual machine creator at http://www.easyvmx.com/.
Name the machine whatever you want.
Operating System: Other OS (Note: choose the one that is NOT 64-bit).
Choose appropriate memory and storage sizes (e.g., 512 MB Memory and 2GB storage).
Don't worry about the LiveCD ISO, leave that blank (it will be dealt with, later).
Press Create Virtual Machine.
Download the compressed file, and unpack it. It should contain a directory with a bunch of VMware files.
Start VMware Player, choose Open an existing virtual machine, and select the .vmx file in the directory you just unpacked.
Once the virtual machine starts, go to the Devices Menu; and, in the CD/DVD item, choose Connect to Disk Image File (iso). Select the Minix3 ISO that you downloaded from the Minix 3 web-site.
If necessary, reset the machine with Ctrl+R; and, it will boot from the ISO.
2.4. Installation
Assuming you have downloaded and decompressed a MINIX 3 ISO image from the download page, you can mount the ISO file:
Select Minix3 in the Inventory List on the left.
In the Devices section, double-click on CD-ROM.
Select Use ISO Image.
Browse, and select the .iso Minix image that you downloaded earlier.
Then you can follow the normal installation instructions.
When the installation is over, type
shutdown
When you get the d0p0s0> prompt, enter off to shutdown the Virtual Machine.
Related
When I use vm a long time, or started operations with big files in my vm, periodially I get bug: process vmware-vmx.exe never stop disk activity and vm stops responding(or very slow).
Host system: windows 10;
Client (usual): ubuntu 16.04.
That problem happened on different disks (samsung, seagate) and different client systems (various ubuntu).
All disks have alot of free place and don't have bad sectors.
This problem resolved: just update vmware with 12.1.0 to 12.5.2 and in a vm-ubuntu system: etc/fstab swap should not be disabled.
I want to try programming for EFI so I created a VM using virtualbox, checked "enable efi" option and left CD empty.
The efi shell boots how it should but instead of FS0 i only see BLK0, BLK1 etc. Is there any way to have FS without inserting USB disk (which is displayed as FS)?
Edit:
Thanks for your replies. For people who still want to use VB - formatting VB disk with DISKPART using Windows CD solves the problem.
#unixsmurf answer in comments is correct. Your image need file system supported by UEFI. If you can't see fsX in output of map command then it means that non of attached block devices (blkX) contain supported file system. Please create FAT32 partition on your disk, then you will be able to see fsX in map output. To switch between file systems use DOS like syntax command ie. fs0: switch to FS0 file system.
According to UEFI specification 2.5 section 12.3:
EFI encompasses the use of FAT32 for a system partition, and FAT12 or FAT16 for removable
media.
I would suggest to use OVMF (Open Virtual Machine Firmware) directly with QEMU not through VirtualBox. Why ?
Because you can hack OVMF and learn how it works internally, this give you better understanding, VirtualBox hide internals and I'm not sure if it allow firmware replacement
OVMF was developed initially for QEMU and it is adapted by various other virtual machines, because of that there is much more support for OVMF on QEMU then OVMF on VirtualBox
using QEMU also give you ability to emulate your hardware and write drivers/applications in UEFI that use it
I wrote beginners tutorial that help setting up development environment needed for UEFI application development using OVMF.
More about OVMF.
i wrote a cuda program and i am testing it on ubuntu as a virtual machine. the reason for this is i have windows 7, i don't want to install ubuntu as a secondary operating system, and i need to use a linux operating system for testing.
my question is: will the virtual machine limit the gpu resources? So will my cuda code be faster if i run it under my primary operating system than running it on a virtual machine?
I faced a similar task once. What I ended up doing was installing Ubuntu on a 8GB thumb drive with persistent mode enabled.
That gave me 4GB to install CUDA and everything else I needed.
Having a bootable USB stick around can be very useful. I recommend reading this.
Also, this link has some very interesting material if you're looking for other distros.
Unfortunately the virtual machine simulates a graphics device and as such you won't have access to the real GPU. This is because of the way the virtualisation handles multiple VMs accessing the same device - it provides a layer in between to share the real device.
It is possible to get true access to the hardware, but only if you have the right combination of software and hardware, see the SLI Multi-OS site for details.
So you're probably out of luck with the virtualisation route - if you really can't run your app in Windows then you're limited to the following:
Unrealistic: Install Linux instead
Unrealistic: Install Linux alongside (not an option)
Boot into a live CD, you could prepare a disk image with CUDA and mount the image each time
Setup (or beg/borrow) a separate box with Linux and access it remotely
I just heard a talk at NVIDIA's GPU technology conference by a researcher named Xiaohui Cui (Oak Ridge National Laboratory). Among other things, he described accessing GPUs from Virtual machines using something called gVirtuS. He did not create gVirtuS, but described it as an opensource "virtual cuda" driver. See following link:
http://osl.uniparthenope.it/projects/gvirtus/
I have not tried gVirtuS, but sounds like it might do what you want.
As of CUDA 3.1 it's virtualization capabilities are not vivid, so the only usable approach is to run CUDA programs directly on the target HW+SW
Use rCUDA to add a virtual GPU to your VM.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
As you all know, Google-Chrome-OS is released in VMWare Image File, VMDK.
I've downloaded it , however, I couldn't open it with VMWare Work Station and VMWare Player.
Also I've tried to open with Virtual Box in Ubuntu.
Thus, How could I get it?
Create a new Virtual machine in Virtual box,
Select OS type Other and version Other/Unknown
On the Virtual Hard Disk screen, select "Use existing hard disk" and enter the path to the VMDK file.
It should boot your Chrome OS just fine....
BTW Chrome OS goes from VBOX bios screen to login in 7 seconds on my system!!!
This is for vmware workstation 6.5
It is pretty far down.
select Create new virtual machine ->
select custom ->
on compatibility page take defaults ->
check I will install os later
-> click through several pages choosing other for OS, give it a name, make sure it IS NOT in the same folder as the VMDK file. Choose bridged network.
You will now see a screen asking to select disk, select existing virual disk. then browse and select the VMDK file
I was looking for a way to play VMDK files without the vmx file in VMware Player 5 and didn't find any explicit tutorial to do it. So after some time messing around with VMware PLayer 5, it turned out to be pretty simple, but not so intuitive. Here it is:
Create a new virtual machine from VMware Player 5;
There's no need to install an OS, since you already have the VMDK (Virtual Machine Disk);
Set the Virtual Machine to the OS you'll be playing (the one from the VMDK);
After creating the VM with the remaining creation wizard options, go to your VM settings;
There you can remove the existing hard drive and add a new one;
Upon addition of the new hard drive, point it to your existing VMDK file.
And that's it.
If you have problems starting the VM because VMware Player can't lock the VMDK file, rename/delete the dir/files with extension *.lck from the directory where the *.vmdk file is located.
Hope this is helpful.
VMDK is a virtual disk file, what you need is a VMX file. Cruise on over to EasyVMX and have it create one for you, then just replace the VMDK file it gives you with the Cnrome OS one.
EasyVMX is good since VMWare Player has no VM creation stuff in it (at least in version 2, not sure about 3). You had to use one of VMWare's other products to do that.
you can also use vmware-mount from VMwares VDDK (Virtual Disk Development Kit):
http://communities.vmware.com/community/vmtn/developer/forums/vddk
this allows you to mount VMDK files as disk drives in windows or linux
WinMount provides an easiest way to mount VMDK as a virtual disk. You can read or write to the vmdk file without loading the virtual system.
Here shows you how to do: http://www.winmount.com/mount_vmdk.html
For me my vmdk file was accompanied by a vmx file. Opening the vmx file worked for vmware player.
Generally, this is how you open an OS folder containing a bunch of vdmk files on VMware Player.
I've been hearing a lot about about how the new version of VMWare Fusion can run virtual operating systems in "headless mode".
A Google search makes it clear that other virtualisation products also have similar features, however, I have not been able to find a good description of what this actually means? What is happening when you do this?
Headless mode means that the virtual machine is running in the background without any foreground elements visible (like the Vmware Fusion application)
You would have no screen to see running the front end; i.e. the screen/console would not be visible, even though the operating system is running, and would typically have to access the machine via SSH.
For anyone that is interested, you can activate headless mode in VMWare Fusion by running the following command in Terminal.app
defaults write com.vmware.fusion fluxCapacitor -bool YES