No, but maybe that's not a requirement for him.
Nikhil, I have Grizzly running on 13.04, but I'm also having network
problems (see subject "A Grizzly arping failure"). I'm investigating
these issues today, hopefully with plenty of help from the community.
Maybe the fix I need is similar to the fi
but NAT wont make the VM accessible from outside world ... will it?
Regards,
Pranav
On Fri, May 10, 2013 at 5:16 PM, Nikhil Mittal wrote:
> Nope, assigning a floating IP is not required. The VM can be accessed with
> whatever IP that is assigned as the NAT'ng will take care of that.
>
> On Fri,
Nope, assigning a floating IP is not required. The VM can be accessed with
whatever IP that is assigned as the NAT'ng will take care of that.
On Fri, May 10, 2013 at 4:50 PM, Pranav wrote:
> you need to expose the VM's internal network to an external network by
> allocating it floating IP addres
you need to expose the VM's internal network to an external network by
allocating it floating IP address.
Regards,
Pranav
On Thu, May 9, 2013 at 10:47 PM, Nikhil Mittal wrote:
> I am seeing this email after a long time. Quite recently I tried
> installing Grizzly on Ubuntu 13.04 on x86 64 machi
I am seeing this email after a long time. Quite recently I tried installing
Grizzly on Ubuntu 13.04 on x86 64 machine. It installed fine except that i
am facing some network configuration issues after the VMs start running.
On Fri, Apr 26, 2013 at 12:05 AM, skible.openst...@gmail.com <
skible.open
Hi,
So the ubuntu 13.04 has just been released. Everything is fine except
for the virtualization using KVM.
After installing nova-compute-kvm, nova-compute does not start and this
is what i found in my log file:
Connection to libvirt failed: Failed to connect socket to
'/var/run/libvirt/l
6 matches
Mail list logo
