William L. Thomson Jr. wrote: > On Mon, 2010-04-19 at 18:52 -0400, Kyle Gonzales wrote: > >> KVM uses QEMU for its toolset. So when leveraging the KVM hypervisor, >> the errors you will see come from the QEMU tools. >> > > I wonder if some of the cdrom behavior is inherited from that. I was > going to say such but wasn't sure. But then with your other post, > describing it being an image, etc restarting the vm after removing the > device. Reminds me of starting qemu at times with and without a cdrom > flag. > > I seem to recall if you start qemu with the cdrom option and no cdrom > present in the drive you will have issues. But it's been a while, and I > am to lazy to confirm such. Though I am using qemu atm for other > things :) > That's pretty much it. Right now you need to tell the VM when it boot whether there is a device available to be considered as a CDROM or not. And if you tell it there is such a device (whether an image or a physical CD) it needs to be there when the VM boots or you will get what Whit saw.
-- Kyle Gonzales [email protected] GPG Key #0x566B435B Read My Tech Blog: http://techiebloggiethingie.blogspot.com/
