`Still no dice ...<br>root@gazoo ~ # gem install qemu-toolkit<br>Fetching: qemu-toolkit-0.3.1.gem (100%)<br>Successfully installed qemu-toolkit-0.3.1<br>1 gem installed<br>Installing ri documentation for qemu-toolkit-0.3.1...<br>
Installing RDoc documentation for qemu-toolkit-0.3.1...<br>root@gazoo ~ # vmadm create myvm3<br>uninitialized constant QemuToolkit::Vmadm::FileUtils<br>root@gazoo ~ # vmadm start myvm3<br>uninitialized constant QemuToolkit::VM::FileUtils<br>
<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Nov 10, 2012 at 7:11 PM, Kaspar Schiess <span dir="ltr"><<a href="mailto:kaspar.schiess@absurd.li" target="_blank">kaspar.schiess@absurd.li</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Denis,<br>
<div class="im"><br>
> I'm getting the following warning messages after what I believe to be successfully installing as per the instructions:<br>
><br>
> root@gazoo ~ # vmadm create myvm2<br>
> uninitialized constant QemuToolkit::Vmadm::FileUtils<br>
> root@gazoo ~ # vmadm start myvm2<br>
> uninitialized constant QemuToolkit::VM::FileUtils<br>
<br>
</div>You're right, I can reproduce that in some environments. Can you try installing 0.3.1? A simple<br>
<br>
gem install qemu-toolkit<br>
<br>
should do the trick.<br>
<span class="HOEnZb"><font color="#888888"><br>
kaspar<br>
<br>
</font></span></blockquote></div><br></div>
`