Thanks Ben, (thanks for your reply too Bernd) yet that was one of the first things I tried! I tried every iteration of a Solaris device name or mount point I could think of.
I'll try one more time though just for sanity sake when I fire up that enviromnent later today. :-) Based on the qemu docs though and the example usage of the "change cdrom" verbiage in the FAQ, I assumed that qemu just did some kind of mapping so that whatever your host OS was, /dev/cdrom under the guest would map to whatever the true cdrom device was on the Host OS. I also though the "[not inserted]" output from the "info block" command might mean that qemu does not see the cdrom. I'll try one more time using the Solaris device name just to make sure I have tried everything . . . Thx! T. Ben Taylor wrote: >---- "Thomas D. Briglia" <briglia at stanford.edu> wrote: > > >>Hi Folks, >> >>A while back I had a newbie cdrom question and the answer was easily >>found in the FAQ at fabrice.bellard.free.fr and after figuring out how >>to go into the monitor and 'change' the cdrom I was back running. >> >>Well I now have a similar problem yet not having as much luck accessing >>the cdrom even using the "change cdrom /dev/cdrom" monitor command. >> >> > >but /dev/cdrom doesn't mean anything on solaris. > > > >>I am trying to evaluate this Proxy software called Zorp (from balabit >>the folks who make syslog-ng). Zorp comes with a scaled down version of >>Debian Linux re-branded as "ZorpOS". I want to try the initial eval in a >>qemu virtual environment. >> >>The idea is that you basically install "ZorpOS" plus the Zorp Proxy >>'native' onto a system so it is sort of a scaled down 'proxy appliance' >>just supporting the proxy technology. >> >>The installation is two part, you first install the base ZorpOS, then >>upon rebooting it takes you back into a "Configuration Screen" where it >>wants to load the proxy software off the installation cdrom. >> >>The Zorp install utility asks you where you want to load the sw from and >>the default location is "/dev/cdrom". Upon selecting this option though >>you get an error saying the "program was unable to auto-detect a cdrom >>or there is no usable cdrom in the device". >> >>So at this point even if I go into the qemu monitor, issue an "eject >>cdrom" command, then issue the "change cdrom /dev/cdrom" command the >>Zorp install utility still does not see the cdrom device. >> >>I am running qemu on Sol10 x86 and the Zorp cdrom is mounted under >>Solaris as /vol/dev/dsk/c1t0d0/cdrom on mount point /cdrom/cdrom. >> >> > >so do you see anywhere in those devices where /dev/cdrom is appropriate? :-) > >Try /vol/dev/rdsk/c1t0d0/cdrom (notice the *rdsk*) > >Ben > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/qemu-discuss/attachments/20071218/756a5daf/attachment.html>
