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. 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. Anyone ever have a similar problem? I did see similar issues in the FAQ for SUSE Linux where it says: "At the SUSE Linux Boot menu screen, add the boot option: cdromdevice=/dev/hdc Continue with the SUSE Linux boot and installation". I am wondering if I need to do something like this for the ZorpOS? The problem is that when ZorpOS boots up I do not see anyway to escape the boot sequence and give it any boot options. Also at this point in the installation Zorp is not running from a GUI Debian/ZorpOS QEMU window and is just running in non-graphical mode from a small character mode window and I have no way of ''shelling out'' to try to get a shell on the ZorpOS to further troubleshoot. The only other troubleshooting data point I have is that if I go into the qemu monitor and issue the "info block" command I see: cdrom: type=cdrom removable=1 locked=0 [not inserted] Is the "not inserted" anything to worry about? Anyone have any other ideas on stuff to try? Thanks! Regards, Tom
Hi, looks like the CDROM is not attached to your qemu machine. I would suggest to create an ISO image of the CDROM and use the ISO image instead of the real CDROM for qemu, e.g. qemu -cdrom <imagefile> ... Use a dd to from the raw cdrom device to create the ISO file. regards Bernd Thomas D. Briglia 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. > > 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. > > Anyone ever have a similar problem? I did see similar issues in the FAQ > for SUSE Linux where it says: "At the SUSE Linux Boot menu screen, add > the boot option: cdromdevice=/dev/hdc Continue with the SUSE Linux boot > and installation". > > I am wondering if I need to do something like this for the ZorpOS? The > problem is that when ZorpOS boots up I do not see anyway to escape the > boot sequence and give it any boot options. Also at this point in the > installation Zorp is not running from a GUI Debian/ZorpOS QEMU window > and is just running in non-graphical mode from a small character mode > window and I have no way of ''shelling out'' to try to get a shell on the > ZorpOS to further troubleshoot. > > The only other troubleshooting data point I have is that if I go into > the qemu monitor and issue the "info block" command I see: > > cdrom: type=cdrom removable=1 locked=0 [not inserted] > > Is the "not inserted" anything to worry about? Anyone have any other > ideas on stuff to try? > > Thanks! > > Regards, > > Tom > > _______________________________________________ > qemu-discuss mailing list > qemu-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/qemu-discuss > >-- Bernd Schemmer, Frankfurt am Main, Germany http://home.arcor.de/bnsmb/index.html M s temprano que tarde el mundo cambiar . Fidel Castro
---- "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
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>
OK using the raw "/vol" device did not work as you had suggested and as I had found yesterday during my initial attempts. I kept hacking at it though and found that once I killed the Solaris Volume Management daemon and manually mounted the cdrom I was then able to give the raw device /dev/rdsk/c1t0d0s2 to the ZorpOS installer and it likes it! :-) So I guess this has something to with the Volume Manager and ZorpOS (ie: Debian) does not like the automounter device paths? I did not have this problem installing RH Linux under qemu though, during that install I was able to use the automounted device paths no problem when I needed to switch to each cd during the install! Hmmmmmmm! Oh well I am back on track ! :-) Oh and for the record even now that I have it working, "info block" in the monitor still reports "[not inserted]" whatever that means . . . 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/3f7e7207/attachment.html>
---- "Thomas D. Briglia" <briglia at stanford.edu> wrote:> > 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.Note to self: This needs documentation. I hope to expand the Qemu project page with some really cool things I''ve done over the last couple of years so folks can get more use out of it. I have the week off during Christmas, so I''ll probably get to it then.> 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.No, because the cdrom that Solaris presents to Qemu acutally uses the raw device. I actually worked on part of this code with help from Juergen Keil and Mike Riley (from Sun), and it''s been working AFAIK.> I also though the "[not inserted]" output from the "info block" command > might mean that qemu does not see the cdrom.it''s supposed to mean it can''t see the CDROM. In the past, I''m pretty sure this was working.> I''ll try one more time using the Solaris device name just to make sure I > have tried everything . . .Yeah, volmgr really makes this stuff harder than it has to be, but once you get the Solaris way of doing things, volmgr becomes a non-issue. Let me know if you have any problems. Ben