If you look on the VM host at the deployment.0 file
and the actual syntax of the kvm command that is being
called by libvirt, you should be able to figure out
what opennebula is trying to do.
What does the network section of your template say?
How is your onevnet configured?
Steve Timm
On Mon,
Hi,
On Mon, 2011-04-18 at 15:31 +0200, Idafen Santana Pérez wrote:
> interfaces (ifconfig -a): lo and eth1. But when I run the VM with
> opennebula (onevm create template.one) with the same VM image as
> before, it shows lo and eth2, and I have no clue about this behaviour.
https://help.ubuntu.com
Hi,
I have been working on it and I have "found" the problem. The thing is
that ONE is somehow changing the network interfaces of the VM
machines. When I register a VM image (oneimage register file.img) and
run it with KVM (kvm -hda ONE_LOCATION/var/image/imageId) it shows 2
interfaces (ifconfig -
Same problem for me. I can run a Ubuntu image, but i cannot access it
with ssh or even ping to it. I can access it by using virt-manager,
and it is running ok, but the network interfaces are down and their
name change every time I run a new image (eth1, eth2, ...), so I can't
configure it.
Thanks
Hello, Guys:
Currently I am doing some experiments with Opennebula, which is a
cloud management platform.
I have two computers, one is opennebula management node (Ubuntu Desktop 10.10);
the other one is opennebula worker node (Ubuntu Desktop 10.10 + KVM).
>From the Opennebula website, I downloade
