Re: Booting Nested KVM

[Kashyap Chamarthy <kchamart@redhat.com>]

[Sorre for the late response -- I was away for the last week or so.]

On Sat, Mar 26, 2016 at 01:26:20PM -0400, Jacob Abraham Graff wrote:
> Thanks for the responses! Unfortunately, I'm still getting problems.
> After using virsh net-edit, I attempted to virt-install, and still got
> the same error. When I run 'virsh net-start default', I get this
> error:
> 
> error: Failed to start network default
> error: failed to add iptables rule to allow DHCP requests from 'virbr0'

I don't see any such errors as test on latest stable release
libvirt-1.3.2-3.fc23.x86_64.  Given that you say you've looked up few
things, I'd assume you've tried (a) ensuring `firewalld` is running; (b)
have 'iptables' package installed.
 
> None of the solutions I have found on Google have a fix for this. Any
> ideas?

[...]

> > I think his problem is that he has 192.168.122.0/24 configured on
> > both host and guest for the default libvirt network.  Jacob, to fix
> > this you need to do "virsh net-edit default" (as root) and change
> > the occurrences of 122 to another number such as 123.

If that's really the case, then upstream libvirt has fixed[1] the
default network conflicts.  I remember testing the very same case[2] of
avoiding default network conflicts for nested virtualization -- using
the said fix[1] avoids it.  It is available in version libvirt-1.2.8 or
above.


[1] http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=5f719596 --
    network: try to eliminate default network conflict during package
    install
[2] http://kashyapc.com/2014/09/16/libvirt-default-network-conflicts-not-anymore/

-- 
/kashyap