Defect report: cloning ready-for-easy-install machines

[asdfvmw]

I'm not sure if this is the place for this if you want to report a bug and you are not the owner of the licenses but you are working for someone who owns the license and provides you access to the workstations.

These are the steps to reproduce the defect:

Create a VM (in my case XP) and configure it to use Easy Install. Don't power it.

     * At this point a floppy autoinstall image is created in a temp directory and attached to the VM

Clone the VM

Start the original one, let it install

     * At some point through the installation, the floppy is removed

Start the cloned one. It doesn't lunch Easy Install because the workstation didn't generate a specific easy install floppy for this vm.

Another defect:

Create a VM (in my case XP) and configure it to use Easy Install. Don't power it.

     * At this point a floppy autoinstall image is created in a temp directory and attached to the VM

Clone the VM

Start both at once

Again, since the workstation didn't generate a specific easy install floppy for the cloned vm, the cloned vm shows an error on trying to access one of its virtual devices as it's in use

Hope the VMWare guys take a look at this

Kind regards.

[continuum]

Cloning a VM that is prepared for easy-install BEFORE the first start is a strange use-case.
I doubt that VMware engineers even thought of such a scenario as it does not make sense.

If it worked you would create 2 XP VMs with the same serial number and host name which does not sound reasonable at all.

[asdfvmw]

Just aiming to report the defect, every developing company should collect all the clients detect. I know the scenario is very specific, and I also suppose the VMWare developers just didn't thought about it, it's logical. Do you know if the VMWare guys collect feedback from this forum?

[lakshya32]

Hi

Welcome to communities.

Agree with asdfvmw , As all developer developing the sw after the product \design approved

by team and expert-es feedback and few bug from last production ,still developer should keep track of

all customers feedbcak further released and to fulfill end users requirement.

[Stealer0]

I have the same issue.

I need to start a lot of VM installations simultaneously with unique identifiers and custom hardware parameters.

As it requires a lot of manipulation via 'New Virtual Machine' wizard, I thought why not to create one, and before powering on - quickly create the clones?

Mac, bios id and hdd serial gets new identifiers.

However, in that scenario the autoinstall image left missing.

I would copy-paste it manually, but I suppose it carries some unique generated identifiers?