I think it would be good if SCSI support can be provided as for web caching it will be good and it's easier to find good servers with SCSI than IDE or SATA. Please consider.

It will be good whit SCSI support so you can run Mikrotik on Vmware ESX
server

we will not support scsi

You can manually change the ESX config file to provide support for IDE discs....

snippet from my running ILM-Router.vmx /Jörgen

we will not support scsi

what about SATA? it's almost impossible to buy a new machine (not parts, the whole machine) now that has IDE boot capabilities, if it even has a IDE controller...

SATA is supported if you select `legacy mode` in your BIOS, and SATA is fully supported in v3

SATA is supported if you select `legacy mode` in your BIOS, and SATA is fully supported in v3

I know legacy mode is supported, but not all boards have a legacy mode...

glad to hear about v3

Hi.
Jörgen,
what version of ESX you are running?
I've been trying to edit config in ESX 3.01 and it was unsuccessfull. It said wrong config when I've tried to add VM.

in vmware there is IDE option available.

that way you can create a raid an virtual machine on top of it and save everything in a virtual file.

on the other hand - if you create RAID for router - that this must be web proxy - i would create separate machine for that. and router to work as transparent router.

Thanks for reply janisk.
Can you tell a bit more about this option? Do you meen I should pay for IDE option to Vmware? Or I have this by default in ESX 3?

hy,

Jörgen, could you give us more information about this IDE setup on ESX ?
I'm running esx 2.5.3, and have tried setting up the ide disk in VM but now when I connect to it with VMware Remote Console it shows an error "This is not a valid Plain IDE disk".

Here is my configuration for this VM:

#!/usr/bin/vmware
config.version = "6"
virtualHW.version = "3"
scsi0.present = "TRUE"
scsi0.virtualDev = "vmxbuslogic"
memsize = "64"
ide0:0.startConnected = "TRUE"
ide0:0.present = "TRUE"
ide0:0.fileName = "/vmfs/esxsas1/Untitled.vmdk"
ide0:0.deviceType = "plainDisk"
floppy0.present = "FALSE"
floppy0.startConnected = "FALSE"
floppy0.fileName = "/dev/fd0"
Ethernet0.present = "TRUE"
Ethernet0.connectionType = "monitor_dev"
Ethernet0.devName = "vmnic0.150"
Ethernet0.networkName = "Adsl"
usb.present = "FALSE"
RemoteDisplay.depth = "16"
displayName = "Router-test"
guestOS = "linux"
checkpoint.cptConfigName = "routertest-805cab8e"
priority.grabbed = "normal"
priority.ungrabbed = "normal"

scsi0:0.present = "FALSE"

draw = "gdi"

Ethernet1.present = "TRUE"
Ethernet1.connectionType = "monitor_dev"
Ethernet1.virtualDev = "vmxnet"
Ethernet1.devName = "vmnic0.2"
Ethernet1.networkName = "CorpLan"

ide1:0.present = "TRUE"
ide1:0.fileName = "/vmfs/esxscsi1/m.iso"
ide1:0.deviceType = "cdrom-image"

ide1:0.startConnected = "TRUE"

i suggest you to recreate IDE drive (if possible)

After changing the path to the disk file from the web interface it shows a different error:
Device ide0:0 is configured as the virtual disk file esxsas1:Untitled.vmdk. This virtual disk was created as a SCSI disk with SCSI geometries. It cannot be used as an IDE disk.

My question is, how to create an IDE disk in esx or import it so that ESX will accept it ?

This is the worst squid configuration I ever tried in mikrotik routeros.In 3.0 beta5 I had pages redirecting by themselves after one hour of uptime !
another thing if you can support multiple hard disk mikrotik will never have better preformance,if you guys are not capable of supporting scsi at least suppory multiple hard disk to load balance the squid requests.thank you

It seems that there are a large number of people who want to run MT in VMWare. And, it also seems that it is not clearly understood as to why.

Some feel that it would be great to just put it in a container on your workstation. But, we have much bigger plans.

We are an Telco Carrier and ISP. We have thousands of PPPoe connections we support and maintain. We want to switch to MT. But, MT is not exactly a carrier class product . . . We need redundancy. We need fast routers which can handle lots of RAM . . . and lots of connections. MT does a great job. But, we need to have a means to automatically recover from failures quickly . . . and scale the connection capacity without bound.

Our solution is to run MT on VMWare. We give MT as much RAM as it will take, and all the disk it wants. We have settled for the default network drivers. And, it all works. And, we can run three or four MT instances on one machine. But, we are still missing vmware-tools and most importantly the vmxnet interface.

With the tools, we would be able to restart containers if and when there is a problem. As well, we can start and stop containers when connection loads exceed the capacity of one, two, or three MT instances. That many MT instances can handle a bunch of PPPoe connections.

So, if anyone would be interested in including vmware-tools and vmxnet as an addition to MT, we would appreciate it greatly. If not, we will keep doing what we are doing. But, it would be easier if we had the interface and tools.

Take care and thanks for the great product. Keep up the good work.

why not ask VM Ware to add Lan interfaces with is legacy supported

Why not use MS VIRTUAL Server it is fully supported and x64 supported