WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Xen 3.1 DVD writer usage

To: afoo <afoo42@xxxxxxxxx>
Subject: Re: [Xen-users] Xen 3.1 DVD writer usage
From: Sadique Puthen <sputhenp@xxxxxxxxxx>
Date: Thu, 07 Feb 2008 23:22:22 +0530
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 07 Feb 2008 09:53:05 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <fda2d4340802070749o10bf5748p9cd0c11bcbe525b@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <fda2d4340802070749o10bf5748p9cd0c11bcbe525b@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.6 (X11/20070926)
afoo wrote:
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'

Fully virt or paravirt? If fully virt try 'phy:/dev/hda,hdb:cdrom,w'

--Sadique

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



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

<Prev in Thread] Current Thread [Next in Thread>