From owner-freebsd-xen@freebsd.org Mon Aug 31 14:59:21 2020 Return-Path: Delivered-To: freebsd-xen@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2CA4C3C3F11 for ; Mon, 31 Aug 2020 14:59:21 +0000 (UTC) (envelope-from buhrow@nfbcal.org) Received: from nfbcal.org (ns.NFBCAL.ORG [157.22.230.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "nfbcal.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BgCyv65psz4c0h for ; Mon, 31 Aug 2020 14:59:19 +0000 (UTC) (envelope-from buhrow@nfbcal.org) Received: from nfbcal.org (localhost [127.0.0.1]) by nfbcal.org (8.15.2/8.14.1-NFBNETBSD) with ESMTPS id 07VExEJI024451 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 31 Aug 2020 07:59:14 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.97.3 at lothlorien.nfbcal.org Received: (from buhrow@localhost) by nfbcal.org (8.15.2/8.12.11) id 07VExDnt001452; Mon, 31 Aug 2020 07:59:13 -0700 (PDT) Message-Id: <202008311459.07VExDnt001452@nfbcal.org> From: Brian Buhrow Date: Mon, 31 Aug 2020 07:59:13 -0700 In-Reply-To: <20200831075009.GE734@Air-de-Roger> X-Mailer: Mail User's Shell (7.2.6 beta(4.pl1)+dynamic 20000103) To: Roger Pau =?utf-8?B?TW9ubsOp?= Subject: Re: The vnclisten parameter is ignored with hvm domains under xen-4.12.1 and FreeBSD-12.0 Cc: , buhrow@nfbcal.org X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nfbcal.org [127.0.0.1]); Mon, 31 Aug 2020 07:59:14 -0700 (PDT) X-Rspamd-Queue-Id: 4BgCyv65psz4c0h X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of buhrow@nfbcal.org designates 157.22.230.125 as permitted sender) smtp.mailfrom=buhrow@nfbcal.org X-Spamd-Result: default: False [-2.86 / 15.00]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.02)[-1.020]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:ns.nfbcal.org]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nfbcal.org]; NEURAL_HAM_LONG(-0.99)[-0.988]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.55)[-0.551]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7091, ipnet:157.22.0.0/16, country:US]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-xen]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Aug 2020 14:59:21 -0000 hello Roger. Yes, I think an improvement to the xl.cfg man page would be helpful. Your additional notes clarifying my message are also useful in helping to craft what that modified man page might look like. In particular, the section of the man page that says that vnc parameters wil be picked up by hvm guests implies that they'll be picked up from within the vfb spec. that's simply not the case. And, as you point out, it's possible, though not probable, to have both an emulated graphics card on an hvm guest and a pv graphics card on a hvm guest, both potentially sending their vnc output to different IP addresses. That's not at all clear from the man page as I read it. I'll try to come up with some potential language and send it along to you and this list. If you think it helps, then it could be submitted as an upstream patch. -thanks -Brian On Aug 31, 9:55am, Roger Pau =?utf-8?B?TW9ubsOp?= wrote: } Subject: Re: The vnclisten parameter is ignored with hvm domains under xen } On Fri, Aug 28, 2020 at 02:11:07PM -0700, Brian Buhrow wrote: } > hello Roger. thanks for the quick reply. I think, after a careful } > read of the xl.cfg man page plus a careful reading of the xen-tools source } > code, I've figured out the issue. I'm sending the solution here so folks } > will have it in the future. } > } > If one is configuring an hvm guest, any vfb specifications in the domain } > configuration are ignored. } } Let me clarify this a bit. vfb is a para-virtualized frame buffer, so } it needs a specific Xen vfb driver in the guest for it to be able to } use the device (ie: it's not an emulated graphics card). } } > Instead, the parameters that normally get placed } > in a vfb stanza must be placed as top level configuration items. For } > example: } > } > For a PV guest: } > vfb = [ 'vnc=1,vnclisten=10.14.200.200' ] } > } > Translates to, for an hvm guest: } > } > vnc = 1 } > vnclisten = "10.14.200.200" } } OTOH, the global vnc parameter is indeed exclusive to HVM guests and } is related to the emulated graphics card device. } } You could have a HVM guest making use of both the emulated graphics } card (the global vnc parameter) and nmultiple para-virtualized vfb } framebuffers, but those would be different outputs (like having more } than one graphics card on a physical box). } } You cannot however make use of the global vnc parameter for PV guests, } as they have no emulated graphics card. } } > } > The xl.cfg man page doesn't say that in order for the vnc parameters to be } > picked up for hvm guests with emulated graphics cards, those parameters } > need to be specified as top level parameters in the config file. It took } > reading the source code of the xen-tools xl code to figure that out. } } Sorry, I understand this is quite confusing. Do you think the man page } could be modified to make this easier to understand and create less } confusion? } } I'm quite sure the community would be happy to take a patch in order } to clarify stuff. } } Thanks, Roger. >-- End of excerpt from Roger Pau =?utf-8?B?TW9ubsOp?=