Virtualization FAQ: Why won’t my virtualization product boot from my OS CD to load my new guest OS?

Many times, admins have complained that they could not access or could not boot a virtual CDROM that was inserted or an ISO file that was mapped.

And so many times, the cause of this issue is just a simply click. To access a virtual CDROM, that CDROM must be connected. If you look at the graphic below, you can see how the device is both connected and connected at power on. Connected devices are connected after the VM boots where as connected at power on devices, are connected before the VM boots. To boot a new OS CD, that CDROM needs to be connected at power on.


Figure 1

Share this article

Receive all the latest articles by email!

Get all articles delivered directly to your mailbox as and when they are released on MSExchange.org! Choose between receiving instant updates with the Real-Time Article Update, or a monthly summary with the Monthly Article Update. Sign up to the MSExchange.org Monthly Newsletter, written by Exchange MVP Henrik Walther, containing news, the hottest tips, Exchange links of the month and much more. Subscribe today and don't miss a thing!



Receive all the latest articles by email!

Receive Real-Time & Monthly VirtualizationAdmin.com article updates in your mailbox. Enter your email below!
Click for Real-Time sample & Monthly sample

Become a VirtualizationAdmin.com member!

Discuss all your Virtualization issues with other experts. Click here to join!

Solution Center

Readers' Choice

What is your preferred Monitoring, Management and Performance solution?