From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by passt.top (Postfix) with ESMTP id 1A3B85A0082 for ; Wed, 11 Jan 2023 19:33:31 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1673462009; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=ASyF6HYpLx1pjgeUkcqhvnIkTPZrrZt846o9XcNzSGE=; b=PVEh75mXQhi7kq1k0qeYQwOI29vfcnuwvPE//Iv1Ps1Zw7T3pwxL6cPCONcqSyFJz6RzQp 8yOm8vZzLu393B0jYrZY/dUAGuOVxKSe+9YC1BlFsQ1I4BsNw4hcO28tv1+Iah1zyO3xKg bBo1vQ2SnoWdOMPcuv5IutX/g/kEmOA= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-558-uxkpLr6mPJKWCZCtSNVR5g-1; Wed, 11 Jan 2023 13:33:28 -0500 X-MC-Unique: uxkpLr6mPJKWCZCtSNVR5g-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id C7C9A3C22745 for ; Wed, 11 Jan 2023 18:33:27 +0000 (UTC) Received: from redhat.com (unknown [10.33.36.119]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9D35440C1141; Wed, 11 Jan 2023 18:33:26 +0000 (UTC) Date: Wed, 11 Jan 2023 18:33:23 +0000 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Laine Stump Subject: Re: [libvirt PATCH 4/9] conf: add passt XML additions to schema Message-ID: References: <20230109041112.368790-1-laine@redhat.com> <20230109041112.368790-5-laine@redhat.com> MIME-Version: 1.0 In-Reply-To: <20230109041112.368790-5-laine@redhat.com> User-Agent: Mutt/2.2.9 (2022-11-12) X-Scanned-By: MIMEDefang 3.1 on 10.11.54.2 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-MailFrom: berrange@redhat.com X-Mailman-Rule-Hits: nonmember-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation Message-ID-Hash: DQLMYH4GM53PYPHYPXDC263PNH3TIW32 X-Message-ID-Hash: DQLMYH4GM53PYPHYPXDC263PNH3TIW32 X-Mailman-Approved-At: Thu, 12 Jan 2023 14:00:24 +0100 CC: libvir-list@redhat.com, sbrivio@redhat.com, passt-dev@passt.top X-Mailman-Version: 3.3.3 Precedence: list Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= List-Id: Development discussion and patches for passt Archived-At: Archived-At: List-Archive: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Sun, Jan 08, 2023 at 11:11:07PM -0500, Laine Stump wrote: > Initial support for network devices using passt (https://passt.top) > for the backend connection will require: > > * new attributes of the subelement: > * "type" that can have the value "passt" (to differentiate from > slirp, because both slirp and passt will use type='user'>) > * "logFile" (a path to a file that passt should use for its logging) > * "upstream" (a netdev name, e.g. "eth0"). IMHO this attribute is inappropriate for .... > * a new subelement (described in more detail later) > > Signed-off-by: Laine Stump > --- > src/conf/schemas/domaincommon.rng | 65 +++++++++++++++++++++++ > tests/qemuxml2argvdata/net-user-passt.xml | 57 ++++++++++++++++++++ > 2 files changed, 122 insertions(+) > create mode 100644 tests/qemuxml2argvdata/net-user-passt.xml > > diff --git a/tests/qemuxml2argvdata/net-user-passt.xml b/tests/qemuxml2argvdata/net-user-passt.xml > new file mode 100644 > index 0000000000..b82eebd089 > --- /dev/null > +++ b/tests/qemuxml2argvdata/net-user-passt.xml > @@ -0,0 +1,57 @@ > + > + QEMUGuest1 > + c7a5fdbd-edaf-9455-926a-d65c16db1809 > + 219136 > + 219136 > + 1 > + > + hvm > + > + > + > + destroy > + restart > + destroy > + > + /usr/bin/qemu-system-x86_64 > + > + > + > + > +
> + > + > + > +
> + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + I don't think that 'upstream' is really describing a property of the backend. This is expressing a traffic routing restriction for the 'user' networking type. IMHO it should probably be using the existing element, that is currently used by the 'direct' networking type. Can we see about fixing this before release. > +
> + > + > + > +