I have another issue here with getting hvm going:

hvm systems seem under some(probably all?) circumstances only be able
to boot when having an absolute path to the physical volume.

However, the value {$image_vbd} seem to be replaced with a physical
disk path relative to /dev.
I can workaround it by hard-coding the first and last part of the disk
(phy and -disk) and only replacing the name value, but so I lose the
possibility to create image or disk based vm's with only one template.

(hmm, maybe I can also script the template a bit?)
Anyway, a image_vbd value that works better would be nice.

Henning


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to