Port-xen archive

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

Re: Getting Xen to go along with LVM

On Mon, Nov 9, 2009 at 11:25 PM, Jean-Yves Migeon
<jeanyves.migeon%free.fr@localhost> wrote:
> Manuel Bouyer wrote:
>> On Mon, Nov 09, 2009 at 06:48:21PM +0000, Hugo Silva wrote:
>>> [...]
>>> dmesg:
>>> xbdback backend/vbd/1/1: can't DIOCGPART device 0xa901: 12
>>> Â Â Â Â Â Â Â Â Â // <------- ?
>> OK, that's the problem. Maybe xbdback should try DIOCGDISKINFO
>> in this case. Sorry, I can't look at a patch right now ...
> proplib(3) things are obscure to me. IIUC, the VOP_IOCTL() for the devmapper
> associated to DIOCGDISKINFO returns an externalized form of the disk-info
> prop_dictionary_t, namely, a struct plistref.
> I can't manage to find how I can get the "block-count" key out of it. I
> would need some kind of prop_dictionary_internalize, to turn this
> externalized form into a proplib object.
> Attached is an ugly patch, untested. Caution, applying it will render all
> disklabel-based partitions unsuitable for xbd backend as is, it replaces the
> DIOCGPART ioctl() with the DIOCGDISKINFO one. It is likely that it will
> panic() the dom0 as well upon domU create.

I think that we need to replace DIOCGWEDGEINFO with DIOCGDISKINFO.
This way we will have old DIOCGPART working and all new
disk/pseudo-disk devices have to support DIOCGDISKINFO.




Home | Main Index | Thread Index | Old Index