From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: Booting Nested KVM Date: Fri, 25 Mar 2016 11:05:17 +0100 Message-ID: <56F50D5D.4070906@redhat.com> References: <20160325073340.GB32063@tesla.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: Andrew McMahon Grant , Jintack Lim , kvm@vger.kernel.org To: Kashyap Chamarthy , Jacob Abraham Graff Return-path: Received: from mail-wm0-f68.google.com ([74.125.82.68]:34132 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751904AbcCYKFZ (ORCPT ); Fri, 25 Mar 2016 06:05:25 -0400 Received: by mail-wm0-f68.google.com with SMTP id p65so3167894wmp.1 for ; Fri, 25 Mar 2016 03:05:24 -0700 (PDT) In-Reply-To: <20160325073340.GB32063@tesla.redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 25/03/2016 08:33, Kashyap Chamarthy wrote: >> > We receive the error message >> > >> > Could not start virtual network default > It seems like you don't have the default libvirt network active. If it > were active, you'd see something like: > > $ virsh net-list > Name State Autostart Persistent > ---------------------------------------------------------- > default active yes yes 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. Paolo