From owner-freebsd-xen@freebsd.org Mon Aug 31 07:55:14 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 552063B8D48 for ; Mon, 31 Aug 2020 07:55:14 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from esa5.hc3370-68.iphmx.com (esa5.hc3370-68.iphmx.com [216.71.155.168]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "esa5.hc3370-68.iphmx.com", Issuer "HydrantID SSL ICA G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Bg2YX4s5Rz4CYL for ; Mon, 31 Aug 2020 07:55:12 +0000 (UTC) (envelope-from roger.pau@citrix.com) IronPort-SDR: WJ+W6ihYW1I1IMWOR692Wc7O0UKb2bCP49lFQWkACiEnfLs9pKLwbcWD+3W4dkCVLgfbze+Zgw ewFOFhafMhppO9SGDwskV8toaUyZNLB5M0BW2h2KLVLFe4RrwIXG98btLpKvoKWIkZV5mTEIAm aAv1vQgYXDGuwt9lucOJ8YN/azZS0W82/vxRovxvZ179sbaxEJf804A9h3Kl3Nv024znAQCrgM +FP9kXgaktEK7CTw6SRVm8PI330XRuFElElT8dSKVPYpwx6ZLXxQnl9mDdLDqNZlblOZIYiRCS Vrw= X-SBRS: 2.7 X-MesageID: 25759882 X-Ironport-Server: esa5.hc3370-68.iphmx.com X-Remote-IP: 162.221.158.21 X-Policy: $RELAYED X-IronPort-AV: E=Sophos;i="5.76,374,1592884800"; d="scan'208";a="25759882" Date: Mon, 31 Aug 2020 09:55:03 +0200 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: Brian Buhrow CC: Subject: Re: The vnclisten parameter is ignored with hvm domains under xen-4.12.1 and FreeBSD-12.0 Message-ID: <20200831075009.GE734@Air-de-Roger> References: <20200828165658.GD734@Air-de-Roger> <202008282111.07SLB7TW001877@nfbcal.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline In-Reply-To: <202008282111.07SLB7TW001877@nfbcal.org> X-ClientProxiedBy: AMSPEX02CAS01.citrite.net (10.69.22.112) To FTLPEX02CL06.citrite.net (10.13.108.179) X-Rspamd-Queue-Id: 4Bg2YX4s5Rz4CYL X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.94 / 15.00]; ARC_NA(0.00)[]; RWL_MAILSPIKE_VERYGOOD(0.00)[216.71.155.168:from]; R_DKIM_ALLOW(-0.20)[citrix.com:s=securemail]; NEURAL_HAM_MEDIUM(-1.00)[-0.997]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+exists:216.71.155.168.spf.hc3370-68.iphmx.com]; NEURAL_HAM_LONG(-1.02)[-1.022]; MIME_GOOD(-0.10)[text/plain]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; DWL_DNSWL_LOW(-1.00)[citrix.com:dkim]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[216.71.155.168:from]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[citrix.com,reject]; DKIM_TRACE(0.00)[citrix.com:+]; NEURAL_HAM_SHORT(-0.72)[-0.723]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:16417, ipnet:216.71.154.0/23, country:US]; MAILMAN_DEST(0.00)[freebsd-xen] 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 07:55:14 -0000 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. 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?= From owner-freebsd-xen@freebsd.org Tue Sep 1 14:50:29 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 B448A3CA966 for ; Tue, 1 Sep 2020 14:50:29 +0000 (UTC) (envelope-from roger.pau@citrix.com) Received: from esa2.hc3370-68.iphmx.com (esa2.hc3370-68.iphmx.com [216.71.145.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "esa2.hc3370-68.iphmx.com", Issuer "HydrantID SSL ICA G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BgqkF01vSz4cRS for ; Tue, 1 Sep 2020 14:50:28 +0000 (UTC) (envelope-from roger.pau@citrix.com) IronPort-SDR: 4m4Ek152ZUrRl5kwSFti1KuuknFTlnNAqVUmfkpKdECysUO93Q0WKxY8CHYHE2FIZXMh5AgLaY jyVgWXInfgfweotHOaPkA5TfmKkHTWCWTIppaEZPAOXlBPP0skebV+aApgE/9GBRHD0xiyyLLT ART1bWOBpuuXUTKK+a72ktTtuKXRkfQxZqrNkEyv0HoHYkBZCg+FovUEfturwIWWAgWQKh8Hvh ixbSUGwD3PIDW/NuSs2yT4SvF9YgtST3g3qIccnmaD7Jmwx3WpCIgE23jvZja0eR7lraVR5F97 EGo= X-SBRS: 2.7 X-MesageID: 25759931 X-Ironport-Server: esa2.hc3370-68.iphmx.com X-Remote-IP: 162.221.158.21 X-Policy: $RELAYED X-IronPort-AV: E=Sophos;i="5.76,379,1592884800"; d="scan'208";a="25759931" Date: Tue, 1 Sep 2020 16:50:18 +0200 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: Brian Buhrow CC: Subject: Re: The vnclisten parameter is ignored with hvm domains under xen-4.12.1 and FreeBSD-12.0 Message-ID: <20200901145018.GK734@Air-de-Roger> References: <20200831075009.GE734@Air-de-Roger> <202008311459.07VExDnt001452@nfbcal.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline In-Reply-To: <202008311459.07VExDnt001452@nfbcal.org> X-ClientProxiedBy: AMSPEX02CAS01.citrite.net (10.69.22.112) To FTLPEX02CL06.citrite.net (10.13.108.179) X-Rspamd-Queue-Id: 4BgqkF01vSz4cRS X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.11 / 15.00]; ARC_NA(0.00)[]; RWL_MAILSPIKE_VERYGOOD(0.00)[216.71.145.153:from]; R_DKIM_ALLOW(-0.20)[citrix.com:s=securemail]; NEURAL_HAM_MEDIUM(-1.03)[-1.034]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+exists:216.71.145.153.spf.hc3370-68.iphmx.com]; NEURAL_HAM_LONG(-1.00)[-1.002]; MIME_GOOD(-0.10)[text/plain]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; DWL_DNSWL_LOW(-1.00)[citrix.com:dkim]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[216.71.145.153:from]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[citrix.com,reject]; DKIM_TRACE(0.00)[citrix.com:+]; NEURAL_HAM_SHORT(-0.88)[-0.878]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:16417, ipnet:216.71.145.0/24, country:US]; MAILMAN_DEST(0.00)[freebsd-xen] 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: Tue, 01 Sep 2020 14:50:29 -0000 On Mon, Aug 31, 2020 at 07:59:13AM -0700, Brian Buhrow wrote: > 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. Sure, I would certainly aim to have this upstream, as I don't carry patches to the Xen packages unless they are backports from upstream commits. If you can provide the adjusted text I can prepare a patch and send upstream, or feel free to do it yourself if you want to :). Thanks, Roger. From owner-freebsd-xen@freebsd.org Tue Sep 1 14:58:50 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 689023CAFA3 for ; Tue, 1 Sep 2020 14:58:50 +0000 (UTC) (envelope-from camryn.reese@techinstallbase.com) Received: from mail-ot1-x333.google.com (mail-ot1-x333.google.com [IPv6:2607:f8b0:4864:20::333]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Bgqvr6J5Nz4dX6 for ; Tue, 1 Sep 2020 14:58:48 +0000 (UTC) (envelope-from camryn.reese@techinstallbase.com) Received: by mail-ot1-x333.google.com with SMTP id g10so1400643otq.9 for ; Tue, 01 Sep 2020 07:58:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=techinstallbase-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:from:date:message-id:subject:to; bh=Uzy56u3JUMWde/aTKy2JY/NxPa/9Fs2BwrA+Hi/8ywQ=; b=aDWBiKZY2BCkH8k9rX/jm6Y+31TyFnsduI2AAuyuOHVGWgsJzlHq8Efg0fEAAJ7R49 XxAc8cPT/igq7A4cwlc/HmRhkTs1QkCtrLBOeXEY2xJSDTI2JFhiQVEmp19jEputppjx 4d/ji613jlcPPkr8MgyDXW5XyM0gBxCAP5wQUCP1Rh0tibOX2C/RQivhX5aR40bGg68l nqkh1xIs8zYoDalKD3pq9N1CFXb721PZ1W/tST7GOp/IQHrRnK/7kLzEVkjcdiuuVA3w tJrMBwZl22ZC8n+irIbY/gMRKEDfqPgerzdMDjIO920slvT4MAej/2ZhIWrrPp3RESJv aoRg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=Uzy56u3JUMWde/aTKy2JY/NxPa/9Fs2BwrA+Hi/8ywQ=; b=INjv42HmI8HYXnI5WBgZsffRSNCQTxqwq3j16g2oql6SHVuTxfN5ImHi0rvtqa9GNq TYXYA4jgIhIjJmhhgw87+S6qr3cxxBWpDYVQOIyJKPkYLaHCBxSmOD2j+hq8GFF2cBNk D0jYNWBRc0atEvS8zFf/fZXrrf4+q8uqO1k5sVN24f7G/BnFPxcPCAnZ2j3aZYpRY/t1 UtgkrHEZoxaqW0Wh7G25pOUG7X/Yll9zpH6px5+kMEarT/5agnArriuGtgAJp4Rsl94Y O+MEwiDT43VRQsEC7oiln2ha4ofknPu3PjkzSLOeAWe7rQHsB9M3l2SgJN9w04DMS5e7 vWKA== X-Gm-Message-State: AOAM533I+zVpLo9d6rnZuuoemNC7rduche2rdmnoJ1R7EjtgDHPtjtKC p7fRlKvBCBahjYbbIqEKk8MhvQWSf+JeSilbefLh9GmhxfApfg== X-Google-Smtp-Source: ABdhPJxXV7HsC5yeHwfc8gV11JJs7qBjHQDagM+ixUHA26kWs2MxSPlPI7hDwcCcbQ+x1dL9t+5XmuWXNoKcT97wKd8= X-Received: by 2002:a9d:3d49:: with SMTP id a67mr1620149otc.361.1598972327324; Tue, 01 Sep 2020 07:58:47 -0700 (PDT) Received: from 1082113268423 named unknown by gmailapi.google.com with HTTPREST; Tue, 1 Sep 2020 14:58:46 +0000 MIME-Version: 1.0 Sender: camryn.reese@techinstallbase.com From: camryn.reese@techinstallbase.com Date: Tue, 1 Sep 2020 14:58:46 +0000 X-Google-Sender-Auth: LIxvbVp8pQH8LaSooPJXriIvV4Y Message-ID: Subject: To: freebsd-xen@freebsd.org X-Rspamd-Queue-Id: 4Bgqvr6J5Nz4dX6 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=techinstallbase-com.20150623.gappssmtp.com header.s=20150623 header.b=aDWBiKZY; dmarc=none; spf=none (mx1.freebsd.org: domain of camryn.reese@techinstallbase.com has no SPF policy when checking 2607:f8b0:4864:20::333) smtp.mailfrom=camryn.reese@techinstallbase.com X-Spamd-Result: default: False [-1.21 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.76)[-0.759]; R_DKIM_ALLOW(-0.20)[techinstallbase-com.20150623.gappssmtp.com:s=20150623]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.99)[-0.992]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-xen@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[techinstallbase.com]; DKIM_TRACE(0.00)[techinstallbase-com.20150623.gappssmtp.com:+]; NEURAL_HAM_SHORT(-0.16)[-0.163]; FROM_NO_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::333:from]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; EMPTY_SUBJECT(1.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-xen] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.33 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: Tue, 01 Sep 2020 14:58:50 -0000 Hi, Are looking for a customer bases of your Competitors Installed Base which you to reach niche target and also helps you to grab new clients for your latest service and products? *We also have an exclusive database of:* 1. Cloud Service Providers- CSPs 2. Independent Software Vendors- ISVs 3. System Integrators- SIs and more 4. Managed Service Providers- MSPs 5. Managed Security Service Providers- MSSPs and more Data can be customized based upon your requirement (e.g. Job title, Verticals, Geography etc.) *Data Fields we provide*: Name, Company's Name, Phone Number, Fax Number, Job Title, Email address, Complete Mailing Address, SIC code, Company revenue, size, Web address etc. Please feel free to get back to me with your target criteria if your criteria is different from the above mentioned applications let me know we have close to 5000+ technology installations. *Best Regards,* *Cynthia Overly* *Marketing Executive* Note: This email is not expected to be a spam. It would be ideal if you acknowledge our conciliatory sentiments and answer in the subject taking with leave off to be expelled from our Mailing list. Why not try it/us out? From owner-freebsd-xen@freebsd.org Sat Sep 5 16:10:31 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 D0E5E3CF7AC for ; Sat, 5 Sep 2020 16:10:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4BkKJl5D1jz4b2b for ; Sat, 5 Sep 2020 16:10:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id B324E3CF7AB; Sat, 5 Sep 2020 16:10:31 +0000 (UTC) Delivered-To: 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 B2E883CF993 for ; Sat, 5 Sep 2020 16:10:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BkKJl4Kq5z4b0V for ; Sat, 5 Sep 2020 16:10:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 7426C2043C for ; Sat, 5 Sep 2020 16:10:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 085GAVhF030297 for ; Sat, 5 Sep 2020 16:10:31 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 085GAVNA030296 for xen@FreeBSD.org; Sat, 5 Sep 2020 16:10:31 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: xen@FreeBSD.org Subject: [Bug 249123] PVH domU not migrating from one XEN host to another Date: Sat, 05 Sep 2020 16:10:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: xen@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Sat, 05 Sep 2020 16:10:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D249123 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |xen@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.=