[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 0 of 6] dm-userspace xen integration
On 8/22/06, Dan Smith <danms@xxxxxxxxxx> wrote: CL> This needs to be changed to fail gracefully if the auto* tools are CL> not installed. Is the use of auto* tools absolutely necessary? Since xm-test was accepted with the use of autotools, we did not see any reason why this wouldn't. Well, this is part of the tools build, while xm-test isn't. CL> Could we checkin the generated files as well? I suppose, if that's what you want. It will result in some relatively large patches of apparent garbage every time we make a change to the build system. Yeah, I'm not sure about this. We could do the same we do for the firmware build, i.e. test for the existence of the required tools and if they are not present, then skip the build. CL> Does this work for qemu domains? If so how, if not, what are your CL> plans to make it work for qemu domains? I don't see why it would not work. It just exports a block device, so if a qemu domain can use an LVM or a partition, then this will work. I can get access to an HVM machine and verify. qemu expects to being able to open(2) the name of the file/partition. I guess dm-userspace configures a devicemapper device from the backend script and then has the backend driver use that. This is probably too late for qemu to use it since qemu starts immediately and will try to open it right away. christian _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |