ISO image in the Shared Datastore.
ISO image in the Shared Datastore.
I Wonder if ISO image located in a Shared Datastore and and used by VM , will not allow the vMotion.
for instance , we have ESX1 and ESX2 they both Share a Datastore that has an iso image. a VM that runs on ESX1 will have that ISO connected to it, will the VM be able to be Migrated successfully ?
Thank you
I Wonder if ISO image located in a Shared Datastore and and used by VM , will not allow the vMotion.
for instance , we have ESX1 and ESX2 they both Share a Datastore that has an iso image. a VM that runs on ESX1 will have that ISO connected to it, will the VM be able to be Migrated successfully ?
Thank you
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It is not recommended to keep ISO attached to VMs in Production!
Install your OS from the ISO and disconnect it.
Install your OS from the ISO and disconnect it.
Why do you need to have the ISO attached? Disconnect the ISO and migrate the VM with vMotion. Then you can connect the ISO back.
ASKER
When ISO is in the shared datastore, the VM will show as it belongs to local Datastore of ESX Host and to the Shared Datastore:
where is the iso ?
something still not correct, some object must be on a local datastore if it states local datastore.
I would check datastore1 for any evidence the VM is still there, or has an item located on the local datastore datastore1.
browse datastore1 and screenshot.
something still not correct, some object must be on a local datastore if it states local datastore.
I would check datastore1 for any evidence the VM is still there, or has an item located on the local datastore datastore1.
browse datastore1 and screenshot.
ASKER
VM was onthe Local DataStore and the iso was on the Shared Datastore connected.
This is why it shows both Datastore... I just restested it again.
This is why it shows both Datastore... I just restested it again.
That explains why it states datastore1 and share-datastore.
Technically for a vMotion the VM needs to be on a share datastore, because ALL the compute can access the share datastore if presented to all hosts.
A host cannot access a VM on another host datastore.
Your VM needs to be on shared datastore for successful vMotion and disconnect iso after use.
Technically for a vMotion the VM needs to be on a share datastore, because ALL the compute can access the share datastore if presented to all hosts.
A host cannot access a VM on another host datastore.
for instance , we have ESX1 and ESX2 they both Share a Datastore that has an iso image. a VM that runs on ESX1 will have that ISO connected to it, will the VM be able to be Migrated successfully ?
Your VM needs to be on shared datastore for successful vMotion and disconnect iso after use.
ASKER
Thank you Guys, this is just testing..
https://kb.vmware.com/s/article/2148813