On Sun, Dec 19, 2010 at 02:16:38PM +0800, Thomas Goirand wrote: > On 12/19/2010 08:48 AM, Vagrant Cascadian wrote: > > On Fri, Dec 10, 2010 at 04:05:19PM +0800, Thomas Goirand wrote:
> What is happening is that in every other distribution, and when you > install Xen from source, there's a /usr/lib/xen containing various tools > and libs that one might need. In Debian, it's made in /usr/lib/xen-4.0 > for example. i think the reason for this is to support multiple concurrant xen installs. > This creates compatibility issues for some software. Fore example, if > you want to create a VM with VT-x feature, you would do: > > kernel = "/usr/lib/xen/boot/hvmloader" > builder = 'hvm' > memory = 512 > device_model='/usr/lib/xen/bin/qemu-dm' > > But in Debian, you are forced into doing: > > kernel = "/usr/lib/xen-4.0/boot/hvmloader" > builder = 'hvm' > memory = 512 > device_model='/usr/lib/xen-4.0/bin/qemu-dm' > > which to me, isn't right. to get that to work, you'd need to have symlinks from /usr/lib/xen/boot to /usr/lib/xen-4.0/boot as well as "bin" and possibly others (possibly using the alternatives system), rather than a symlink from /usr/lib/xen. but i don't think that the symlinks should be handled by xen-qemu-dm, but some other xen related package, if it was to be decided on at all. > But at the end of the day, my thinking is that the symlink creation > should be removed completely, and left to the administrator of the > server. I'm not really sure of that though, and I am open to others view > on this. Please let me know what you think! yes, i think the symlink handling should be removed from xen-qemu-dm. if such a set of symlinks was needed in debian, i'd recommend some sort of xen-default or xen-common package. live well, vagrant -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
