On 10/14/2011 02:22 AM, Pekka Enberg wrote: > On Thu, Oct 13, 2011 at 7:52 PM, Ingo Molnar <mingo@xxxxxxx> wrote: >>>> Btw., will 'kvm run' select the last-created rootfs by default? >>> >>> No, it runs rootfs that's named 'default'. We can change that but >>> I'm not completely convinced running that last-created rootfs is >>> the right thing to do here. Hmm. >> >> I'm not convinced either - just wanted to raise the issue. > > Right. So 'kvm run' is supposed to setup and launch a 'default' rootfs > if no rootfs is specified. > >> Also, i raised this in the other thread, why not use .kvmtool of the >> current directory? That way it's cwd local like Git and perf. A 'kvm >> run' (union?) mount the cwd or so - so this would be a natural >> equivalent to chroot. The $HOME/.kvmtool is a Qemu-ish global >> workflow. > > Yeah, that definitely makes sense. 'kvm setup rootfs' wouldn't create > rootfs under $HOME/.kvmtool/rootfs but under $(PWD)/rootfs. I also think $(PWD)/rootfs is much better than $HOME/.kvmtool/rootfs. I think 'kvm setup $absolute_rootfs_path' make sense as well. > I guess we'll lose the ability to 'kvm list' all available rootfs > directories, though? User can create and put the rootfs directories where he/she likes. We do not need to track where the rootfs directories is, thus we do not need to 'kvm list' them. -- Asias He -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
