VB and KVM ripping problems

[allergone]

Hi all, I only recently discovered VB after trying out a few solutions and it looks like the answers to my prayers. I intend to run it as a virtual machine in KVM but i can't get it to rip audio cds. I'm running VB 1.7. KVM is running on ubuntu 10.10. In KVM the host cdrom drive points to /dev/sr0. From the output below it looks to me like everything should be fine (although I wouldn't be an expert http://vortexbox.org/wp-content/forum-smileys/sf-wink.gif) :




[vortexbox.localdomain ~]# cat /var/log/ripit.log
cat: /var/log/ripit.log: No such file or directory
[vortexbox.localdomain ~]# rpm -q vortexbox ripit
vortexbox-1.7-4.fc14.i686
ripit-3.9.0-1.fc14.noarch
[vortexbox.localdomain ~]# ls -l /dev/sr*
brw-rw—- 1 root cdrom 11, 0 Feb 3 22:03 /dev/sr0
[vortexbox.localdomain ~]# ls -l /dev/cd*
lrwxrwxrwx 1 root root 3 Feb 3 22:03 /dev/cdrom -> sr0
[vortexbox.localdomain ~]#





All i get from the rip log on the webmin is :



02/03/2011 22:03:25 - Restarting Auto Ripper...
02/03/2011 22:03:25 - Ripping from /dev/sr0
02/03/2011 22:03:25 - Vendor : QEMU
02/03/2011 22:03:25 - Model : QEMU DVD-ROM
02/03/2011 22:03:26 - Revision : 0.12.

Am i'm trying something that isn't even possible? I have an old piece of junk
I could install VB which would work fine but I have a powerful server that I'd
like to run VB on as a vm too save on energy costs etc

Thanks

[Ron Olsen]

You're running vortexbox-1.7-4; the current version is vortexbox-1.7-15.


One thing I would recommend is to do a GUI "Start Upgrade" to bring your VM up to date. You can also do "yum clean all; yum update" from the command line to


update your VM.


As for the optical drive:


Do you have the cd-info command on your VM? If it's missing, the Auto Ripper


won't work. Install it by



yum install libcdio



and see if that helps.


Also, try inserting a CD and run

/opt/vortexbox/checkcd /dev/sr0
several times. You should eventually get "ready"


when it sees the CD in the drive. Other possible responses are "nodisk" and "notready".


Both checkcd and cd-info need to work for the Auto Ripper to rip CDs.


You can also try to rip CDs from the command line:



service vortexbox stop


ripit



and see if that works.


Turn the Auto Ripper back on by

service vortexbox start

when you're done with this experiment.

[allergone]

Thanks for the reply Ron. I'm in the middle of a gui upgrade right now but i thought i'd print the output of cd-drive which doesn't look good. It's an old enough drive maybe a firmware upgrade is needed?




[vortexbox.localdomain ~]# cd-drive
cd-drive version 0.82 i386-redhat-linux-gnu
Copyright (c) 2003, 2004, 2005, 2007, 2008 R. Bernstein
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
The driver selected is GNU/Linux
The default device for this driver is /dev/cdrom

Drivers available...
GNU/Linux ioctl and MMC driver
cdrdao (TOC) disk image driver
bin/cuesheet disk image driver
Nero NRG disk image driver

CD-ROM drive supports some nonstandard or degenerate set of MMC

Drive: /dev/cdrom
Vendor : QEMU
Model : QEMU DVD-ROM
Revision : 0.12
Profile List Feature
Read only DVD

Error in getting drive hardware properties
Error in getting drive reading properties
Error in getting drive writing properties

CD-ROM drive supports some nonstandard or degenerate set of MMC

Drive: /dev/sr0
Vendor : QEMU
Model : QEMU DVD-ROM
Revision : 0.12
Profile List Feature
Read only DVD

Error in getting drive hardware properties
Error in getting drive reading properties
Error in getting drive writing properties

[vortexbox.localdomain ~]#

[Ron Olsen]

Please reread my last post; I edited it quite a bit since you last looked at it.


It looks as if cd-drive is seeing the drive, which is good, but it's not getting the drive


properties, which is bad.


See if /opt/vortexbox/checkcd /dev/sr0 and cd-info work, and that you can run ripit from the command line and rip a CD. If all this works, then you should be able to use the Auto Ripper to rip CDs. If not, report the errors you get.

[allergone]

Here is what i get:



[vortexbox.localdomain ~]# /opt/vortexbox/checkcd /dev/sr0
nodisk[vortexbox.localdomai
[vortexbox.localdomain ~]# ripit



RipIT version 3.9.0.



Process summary:
----------------
Could not detect CD device! The default /dev/cdrom device will be used.
Track tags will be analyzed for VA style.
Playlist (m3u) file will be written.
CD will be ejected when finished.


Please insert an audio CD!
^C
[vortexbox.localdomain ~]# cd-info
cd-info version 0.82 i386-redhat-linux-gnu
Copyright (c) 2003, 2004, 2005, 2007, 2008 R. Bernstein
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
CD location : /dev/cdrom
CD driver name: GNU/Linux
access mode: ioctl

Vendor : QEMU
Model : QEMU DVD-ROM
Revision : 0.12
Error in getting drive hardware properties
Error in getting drive reading properties
Error in getting drive writing properties
__________________________________

Disc mode is listed as: Error in getting information
++ WARN: error in ioctl CDROMREADTOCHDR: No medium found

cd-info: Can't get first track number. I give up.
[vortexbox.localdomain ~]#






Ripit just hangs at "Please entar an Audio CD"

[Ron Olsen]

Not good. checkcd is getting "nodisk", so it's not seeing the CD in the drive. cd-info is getting errors retrieving drive info, and can't read the CD in the drive. ripit isn't seeing the CD either.


Looks as if KVM isn't able to connect your real optical drive to the VM /dev/sr0 properly. Maybe there are some KVM drivers that you need for the drive. I'd start asking questions in a KVM forum if there is one. But for now, looks as if you're out of luck trying to rip a CD with the VM inside KVM.


Have you tried using VMware as a virtual machine platform? That may work better than KVM. A while back, I was able to use VMware on Gentoo Linux to set up a VortexBox virtual machine and use the optical drive to rip CDs; see


http://vortexbox.org/forum/gen.....-supported (http://vortexbox.org/forum/general/vortexbox-in-virtualbox-ripping-not-supported)

[allergone]

Hi Ron, many thanks for helping me troubleshoot this issue at the very least I learned a bit about troubleshooting cdrom drives from the command line so I really appreciate it. As for your suggestions, well firstly i think i'll build a dedicated machine with VB just for the purpose of getting all these cds out of my hair before the better half runs me out of the house :)


That will give me a bit of time to work out the issue with kvm. I think I'll stick with KVM as I believe it has great promise and I actually enjoy using it. That wouldn't have been my experience with VMware at all. Virtualbox is nice but not what I'm looking for either.


Time to go and bother someone on ta kvm forum! If they're half as helpful as you've been I should be fine. Many thanks again!

[Ron Olsen]

Good luck getting KVM to properly handle your optical drive. I know VMware can do this; VirtualBox cannot.





I've migrated from an old Pentium 4 machine running Gentoo Linux and Windows to a new Mac Pro, and have found that Parallels ( http://www.parallels.com/ ) on Mac OS X is far and away the best virtual machine manager I've ever used. I'm using it to run VB 1.7, Windows 7, and Fedora 14 VMs. Flawless performance.


No dicking around to get my Mac Pro optical drives to work with the VB VM. Just ripped a CD on the VB VM and am playing it back through my Mac Pro speakers using VortexBox Player. Even have remote access to the VMs from my iPad!


Mac OS X is built on Unix, so a Unix/Linux geek like me is happy using the Mac OS X command line -- just like being on Linux. Don't really miss my Gentoo Linux system at all.


Not much use to you on Ubuntu, but if you're ever thinking about upgrading to new hardware, I highly recommend a Mac. http://vortexbox.org/wp-content/forum-smileys/sf-smile.gif