Yes, I was working from the image that Chris created. I have been trying to get the image over to
ESX for the past couple of hours,
but no one seems to have laid out all of the steps. Now I am stuck. Here is what I did.
First I had to convert the workstation file from IDE to SCSI
1. Used vmware-vdiskmanager on workstation to convert the image into an allocated disk file
Vmware-vdiskmanager -r Freebsd.vmdk -t2 m0n0wall.vmdk
This creates two files:
2. Used vmware-vdiskmanager on workstation to create a dd entry for to add to m0n0wall.vmdk
vmware-vdiskmanager -c -s 262144 -a buslogic -t 1 scsi.vmdk
3. Took the following lines from scsi.vmdk and replace the c/h/s entries in m0n0wall.vmdk
ddb.geometry.cylinders = "123"
ddb.geometry.heads = "64"
ddb.geometry.sectors = "32"
4. ftped the files over to the ESX Server
On the ESX Server
1. Used vmkfstools to convert the hard disk file from workstation/GSX to ESX
vmksftools -i m0n0wall.vmdk vmhba1:0:3:1:m0n0wall-Cdrive.vmdk
Note that vmkfstools throws a warning that says: Disk geometry mismatch. To power on the
virtual machine you should specify scsi<adapter-id>:<target-id>.biosGeometry="123/64/32"
in the configuration file
2. Edited the freebsd.vmx file by adding:
scsi0.present = "TRUE"
scsi0.VirtualDev = "buslogic"
scsi0:0.present = "TRUE"
scsi0:0.name = "MSA01LD03:m0n0wall-Cdrive.vmdk"
3. Saved the file as m0n0wall.vmx
4. Created a freebsd VM with configuration file called m0n0wall-new.vmx
5. Deleted m0n0wall-new.vmx
6. Renamed m0n0wall.vmx to m0n0wall-new.vmx
The good news is that ESX sees the vmdk file as a valid SCSI file with all of the valid information,
but when I try to connect to
the VM to start it, I get the following error:
There was an error connecting to the specified virtual machine. Unexpected response from
vmware-authd: The process exited with an
vmxvmdb: Index name being generated from config file
End of error message
Cannot connect to the remote virtual machine
"root/vmware/freebsd/m0n0wall-new.vmx" on "esx02" at port 902 as user "root".
And I thought that this was going to be easy...
From: Ryan [mailto:dreadlocks at gmail dot com]
Sent: Monday, December 26, 2005 8:00 PM
Cc: Hank Wright; m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] VMware m0n0wall Image
Chris has some premade vmware images on his site,
short story, its not that easy to install in vmware..
On 12/26/05, Kristian Shaw <monowall at wealdclose dot co dot uk> wrote:
> I would probably use something like 'Ghost for Unix' to image the Generic PC
> HD image to a clean VMware machine. You need an FTP server for GFU but the
> whole thing should only take a few minutes.
> ----- Original Message -----
> From: "Hank Wright" <hank at nworks dot com>
> To: <m0n0wall at lists dot m0n0 dot ch>
> Sent: Monday, December 26, 2005 10:58 PM
> Subject: [m0n0wall] VMware m0n0wall Image
> > Hello,
> > I would like to use the m0n0wall in our test environment to act as a
> > firewall between a set of test VMs running on a private network
> > and our corporate network.
> > We are using ESX 2.5. I downloaded the m0n0wall 1.2 HD version of the
> > legacy image. When I loaded it on my ESX Server it would not
> > 'see' the vmdk file so I guessed that it was a workstation vmdk file. I
> > then tried to use vmkfstools on it and the utility failed
> > with: "source disk type must be scsi. 'FreeBSD.vmdk' is an ide disk".
> > I don't have access to P2V so is there any other way to convert the file
> > image from IDE to SCSI so I can get this image to run on
> > ESX 2.5?
> > Hank
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch