I'm using VM Server
This simply CAN'T work.
You need WS6.
Just to complete the lab - made under WKS6:
\- 1 VM windows 2003 server SP2 (VC + iSCSI Target Software)
\- 2 VM ESX Server
ESX Servers are configured via native iSCSI software capability to access dedicated LUN on my Win2K3 Server - this LUN is configured as shared VMFS between ESX hosts.
After VM creation under the first ESX, I am able to migrate (vmotion) the VM to the other ESX (5 ping lost during the guest move)...
I got it to work last night too. Which Windows iSCSI target did you use?
Three cheers and a virtual pat on the back for laddario.
Would have done it myself if it was 30 hours in a day...
Next challenge: VCB backup over iSCSI on your laptop!
I have used Wintarget iSCSI software from String Bean Software . (Light and very simple)
Oups, they have been acquired by Microsoft. So if you need an eval distribution take a look under your favorite peer to peer client )
Its clear that it should work with any iSCSI target software, just dont forget to open firewall on ESX side for iSCSI initiator
Best will be an iSCSI solution under a Linux distribution, but no time to investigate and this is another topic.
\- for VCB I will waiting also for 30 hours per day )
Man : Toshiba
Model : Tecra A7-243
Artikelnummer : PTA71E-071021DU
CPU : Intel Core 2 Duo Processor T7200 2.00 GHz 4 MB L2 cache 667 MHz FSB
RAM : 2GB
BIOS : 5.60-WIN
Works like a charm!
Message was edited by:
firstname.lastname@example.org to shorten the URL
As I have mentioned in my earlier posts I have been trying to get ESX to work as Wkst guest on single core P4 processor PC and despite trying various recomended vmx file settings but it it fails when loading the vmkernel during the boot process.
I get the below error during the startup.
VMware VMkernel authorisation daemon, Warning: date....error:md5 signature mismatch. Running vmkernel built on -Unknown- (vs.vmkload_app built on Sept 26 2006 00:00:01)
When logon to the console I see an error:
Service Console running in fallback mode.
VMWare should definitely consider modifying Workstation to be able to run experimental ESX Hosts. Actually, I would like not only a single host, but the ability to mockup multiple hosts with VMotion, HA, and DRS. These features should be able to use fake LUNS that are just VMDKs on the Workstation's normal SATA/IDE drives.
These features will allow Admins to better understand ESX's functionality (not speed since it is running in Workstation) and how it is far superior to the existing x86 virtualization platforms. Furthermore, it will be easier for Admins to demonstrate these features to management to get a dev project for ESX rolled out to server HW.
If you read through this thread, you'll see that ESX works just fine in a WS6 VM - as long as you have VT support with your CPU. So...you can build out an entire VI-3 environment on one box - if it's a beefy enough box
I'd like to see VMware post a VI-3 Virtual Appliance set (ESX, VC, iSCSI target) complete with everything except a license. You could then use your own license or register for an evaluation license to make it come to life...
Is it also possible to run an ESX 3.01 guest on a ESX 3.01 host?
AFAIK this is not possible
Works fine on a Dell D820 with VT turned on in the BIOS.
will this work with a amd-v cpu (m2a-vm with an x2 3600)?
Ken I agree a 3 appliance set would be nice. But I would do it up differently (ESX1, ESX2, VC) and have the VC guest act as the iSCSI target. That's what I did the second time around. I used StarWind (www.rocketdivision.com) as the Windows Server 2003 iSCSI target (they are offering NFR licenses for this kind of stuff if you search the forums) saved me from running a 4th guest.