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

[Xen-users] Xen 3.1 DVD writer usage


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: afoo <afoo42@xxxxxxxxx>
  • Date: Thu, 7 Feb 2008 16:49:31 +0100
  • Delivery-date: Thu, 07 Feb 2008 07:50:04 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=J681Fd8w0GMdTF5OzlE5oeY2D7F8n/QrOeN3gkRg4/Ph8laEjwLC+TRSOhYd/Jgbh45Bb6LiwfyIokIuin6+90F9uEbLeww74UPEJ4Yla48H45igxrDaO/Vd0BOaT+inqarlLcHeYZS3d1LITNsmwHL7MEymlH6vZtjVovbDAnY=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello list,

I have a problem trying to get my DVD-RAM writer to work for a particular domU
on my Xen 3.1 system. The domU boots fine, xend.log shows createDevice and
DevController entries for the device and xm list --long shows the device, too,
yet I can not access the device from inside the domU. When I try to
mount it, the
following happens:

mount: /dev/hdc is not a valid block device

or a variation thereof, see below.

I tried several things in the domu.cfg file's disk stanza:

'phy:/dev/hda:hda:cdrom,w',
'phy:hda:sdb,w'

and I think every combination thereof (like 'phy:/dev/hda:sdb:cdrom,w'
and so on).
The problem presents itself in the same way every time.

I am using the Xen 3.1 hypervisor from Debian etch backports with a
self-compiled/patched 2.6.18 Linux kernel. I also tried compiling a domU kernel
with everything relevant compiled in. I even tried booting the domU with and
without udev.

Any hints on what I am doing wrong?

Cheers,

Jan

_______________________________________________
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®.