This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: [PATCH][XEND] Fix HVM Domain Creation When No Vifs C

To: Christian Limpach <Christian.Limpach@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH][XEND] Fix HVM Domain Creation When No Vifs Configured
From: Daniel Stekloff <dsteklof@xxxxxxxxxx>
Date: Thu, 13 Jul 2006 15:53:04 -0700
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ewan Mellor <ewan@xxxxxxxxxxxxx>
Delivery-date: Thu, 13 Jul 2006 15:53:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C0DC81E3.A4C6%Christian.Limpach@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C0DC81E3.A4C6%Christian.Limpach@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 2006-07-13 at 23:04 +0100, Christian Limpach wrote:
> On 13/7/06 10:46, "Daniel Stekloff" <dsteklof@xxxxxxxxxx> wrote:
> > On Thu, 2006-07-13 at 22:32 +0100, Christian Limpach wrote:
> >> Dan,
> >> 
> >>> Currently - with the new qemu code, HVM domain creation will fail if a
> >>> vif isn't configured. Xm-test will not pass sanity tests to run. The new
> >>> qemu expects "-net none", otherwise it defaults to "-net nic -net
> >>> user". 
> >>> 
> >>> This patch simply adds "-net none" to the qemu-dm cmdline if no vifs are
> >>> configured. 
> >>> 
> >>> Please apply this patch or something similar, xm-test is broken for HVM
> >>> testing without it.
> >> 
> >> I've been meaning to look into this.  I think I'd like to take a slightly
> >> different approach:  change the default in qemu to be -net none.
> >> I'll get to it eventually, but if you want to look into providing a patch,
> >> that would be great!
> > 
> > 
> > I thought about that... but shouldn't we keep the number of changes to
> > qemu to a minimum? Why support more and more specific xen changes to
> > qemu than necessary?
> Sure, but this is a very simple and not very intrusive change.
> I think it's preferable to fix things at the source, in this case it's
> clearly qemu having an unreasonable default for our usage model.

Ok, how's this.



Attachment: ioemu-no-nics-default.patch
Description: Text Data

Xen-devel mailing list