The VMware Virtual Hardware drivers injected into the VM upon its creation can conflict with the physical drivers (if the Recovery Point from which the Virtual Export is being created) present in the Operating System. This keeps the initial boot/driver scan from running properly.
NOTE: There may be times when the OS being booted will take a longer time determining its new virtual surroundings. In most cases, waiting for the process is also fruitful, and can be confirmed with a subsequent boot test. We have seen this "longer wait" behavior on new workloads booting for the first time on Hyper-V hypervisors.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center