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

RE: [Xen-devel] Block device not presented read-only in HVM domain


  • To: "Steve Dobbelstein" <steved@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Thu, 26 Oct 2006 17:39:45 +0100
  • Delivery-date: Thu, 26 Oct 2006 09:40:43 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acb4b1uTAMTBpEkSRu2GuyGoeuNouwArXeHQ
  • Thread-topic: [Xen-devel] Block device not presented read-only in HVM domain

> /dev/vbd-backend/hvm1 is an LVM volume containing a disk image with a
> partition for the root filesystem for the hvm1 domain.
> /dev/vbd-backend/usr is an LVM volume containing a disk image with a
> partition for /usr which is shared read-only across multiple HVM
domains.
> /dev/vbd-disktest/dom1 is an LVM volume that is used as a scratch
disk.
> 
> The /etc/fstab in the HVM domain has the lines:
> 
> /dev/hda1            /                    ext3       acl,user_xattr
> 1 0
> /dev/hdb1            /usr                 ext3       acl,user_xattr
> 1 0
> 
> In the domain I can write to /usr, even though it is supposed to be
shared
> read-only!
> 
> x3850-hvm1:~ # ls -l /usr/bob
> /bin/ls: /usr/bob: No such file or directory
> x3850-hvm1:~ # touch /usr/bob
> x3850-hvm1:~ # ls -l /usr/bob
> -rw-r--r-- 1 root root 0 Oct 25 14:29 /usr/bob
> x3850-hvm1:~ #

You've not using PV drivers, right?
Someone needs to extend qemu-dm to accept and respect a 'read only' flag
associated with a device.

Ian




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


 


Rackspace

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