[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] CDRom and DomU



On Thu, Dec 21, 2006 at 11:23:33AM -0500, Edward Ing wrote:
> That worked.
> 
> Now can I use the DVDRECORDER specification -- or am I pushing my luck.

Not a chance. QEMU only emulates the minimum neccessary of the IDE / ATAPI
spec to get CDROM support working, and even that's slightly dodgy :-)

> On Thu, 2006-21-12 at 15:21 +0000, Daniel P. Berrange wrote:
> > On Thu, Dec 21, 2006 at 12:21:50AM -0500, Edward Ing wrote:
> > > My disk specification is exactly as in the first.
> > > 
> > > disk =
> > > ['phy:/dev/domU/dom1root,hda1,w','phy:/dev/domU/dom1swap,hda2,w','phy:/dev/hdc,hdc,r']
> > > 
> > > However the CDROM is not visible domU
> > 
> > That's because you haven't told Xen that hdc should be exposed as a CDROM
> > device instead of the normal harddisk. Change the config to look like:
> > 
> > disk =
> >  
> > ['phy:/dev/domU/dom1root,hda1,w','phy:/dev/domU/dom1swap,hda2,w','phy:/dev/hdc,hdc:cdrom,r']
> > 
> > Note, the ":cdrom" tag on the end of the target device name.
> > 
> > > ====================
> > > On 11/17/06, jonr@xxxxxxxxxx <jonr@xxxxxxxxxx> wrote:
> > >         disk = ['phy:/dev/hdc,hdc,r']
> > >         
> > >         or
> > >         
> > >         disk = ['tap:aio:cdrom.iso,hdc,r']
> > >         
> > >         cdrom = '/dev/hdc'
> > > You should only need this, not the latter two.
> > 
> > No, 'cdrom = ' is obsolete as of Xen 3.0.3. Instead you need to have :cdrom
> > appended to target device name,


Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.