On Sat, Oct 23, 2010 at 12:54 AM, Stephen Liu wrote:
> I found it difficult to run a virtualizer in another virtualizer if both
> need hardware support. OpenVZ can run on VBox and vice versa, but not VBox
> on KVM nor KVM on VBox, etc. I tested the former previously.
IIRC, Dustin Kirkland mentioned that it is possible to change a
configuration file to make UEC use QEMU instead of KVM, which would
allow it to work under VirtualBox, albeit fairly slowly.
> Disregarding the warning mentioned previously, I still have following
> problems;
>
> Both cluster and node are running.
>
> On Cluster:-
> $ sudo euca-describe-availability-zones verbose
> EC2_ACCESS_KEY environment variable must be set.
> Connection failed
>
> $ euca-describe-availability-zones verbose
> [Errno 113] No route to host
>
>
> On node:-
> $ sudo tail -f /var/log/eucalyptus/nc.log
> tail: cannot open `/var/log/eucalyptus/nc.log' for reading: No such file or
> directory
>
> $ tail -f /var/log/eucalyptus/nc.log
> tail: cannot open `/var/log/eucalyptus/nc.log' for reading: No such file or
> directory
>
>
> I think I have to find a spare PC to test Ubuntu Enterprise Cloud installing
> Cluster as base OS.
Dustin also has an image that can be 'burned' to a USB stick and then
if you can boot from a USB stick it will run both the node and the
cluster on the same machine, without having to change anything in your
computer. I don't have the URL handy though.
-- Sidnei
--
Ubuntu-cloud mailing list
Ubuntu-cloud@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-cloud
