Re: [Xen-devel] [PATCH 28 of 29 RFC] libxl: add libxl__find_free_vdev

[Roger Pau Monnà <roger.pau@xxxxxxxxxxxxx>]

2012/2/15 Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>:
> Roger Pau Monnà writes ("Re: [Xen-devel] [PATCH 28 of 29 RFC] libxl: add 
> libxl__find_free_vdev"):
>> The main purpose of this series is to separate the control code from
>> the device code (make xl able to plug devices from a domain different
>> than dom0). Since the root image might not be stored on the dom0, we
>> need to be able to make this image available to the dom0 somehow, to
>> extract the kernel and ramdisk. One option is to execute pygrub from
>> the device domain, the other option is to plug the domU hard drive to
>> the dom0, run the bootloader to extract the kernel/initrd and unplug
>> the hd.
>
> Wow. ÂSo this relies on a frontend in dom0 ?

Yes, that's been discussed before, and seemed like the way to go:

http://lists.xen.org/archives/html/xen-devel/2012-01/msg02663.html
http://lists.xen.org/archives/html/xen-devel/2012-01/msg02761.html

I've been playing with this implementation and seems to work ok.

> I think for now it might be wise to simply expect the kernel/ramdisk
> to exist as files in dom0 somewhere.

Well, that is already archived using kernel and ramdisk parameters in
configuration file right?

> Ian.

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