On Thu, Aug 17, 2006 at 01:02:17AM +0200, Henning Sprang wrote: > ( I start to see that the topic should be different, but it will be > gone soon anyway...)
True. > I have 2 issues with the current implementation: > > I just tried to give "hvm.tmpl" as template, assuming it would take a > file in /etc/xen-tools/. It didn't, but instead the template xm.tmpl > was used. That sounds strange. I tested it with this: xen-create-image --hostname=megan.my.flat --ip=192.168.1.223 --dist=sarge --boot --force --template /etc/xen-tools/foo.tmpl --verbose It correctly used the foo.tmpl file which I'd specified. > For one thing it would be convenient to choose to either give a name > in /etc/xen-tools or, if someone prefers stroing their template > elsehwere, an absolute path (similar to xen xm behaviour). I'm not sure that is a good idea to be honest. xm is a different tool, and all the other options such as specifying a kernel require an absolute path. > Then, if a wrong temple is given, that is a fatal error - a user > should always give a valid template or none, so the default is being > used. Agreed. The code will be updated to ensure a valid template is given or a fatal error. > At least a warning should be given out, but I'd vote for a fatal error > instead. Yes. Steve -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
