From nobody Fri Aug 18 09:22:58 2023 X-Original-To: freebsd-virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RRxHk4fQdz4qy1S for ; Fri, 18 Aug 2023 09:23:14 +0000 (UTC) (envelope-from meka@tilda.center) Received: from c3po.tilda.center (c3po.tilda.center [108.61.164.129]) (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 mx1.freebsd.org (Postfix) with ESMTPS id 4RRxHj5yTQz3W4n; Fri, 18 Aug 2023 09:23:13 +0000 (UTC) (envelope-from meka@tilda.center) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=tilda.center header.s=c3po header.b=E9kCLlBr; spf=pass (mx1.freebsd.org: domain of meka@tilda.center designates 108.61.164.129 as permitted sender) smtp.mailfrom=meka@tilda.center; dmarc=pass (policy=reject) header.from=tilda.center Received: from [192.168.111.193] (meka.rs [109.93.255.137]) by c3po.tilda.center (Postfix) with ESMTPSA id 6636A2123E; Fri, 18 Aug 2023 11:20:37 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tilda.center; s=c3po; t=1692350438; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=GbtcxEmfjrW+LBq4gYgrvwxg93MH5jqpAX36d6pD8K8=; b=E9kCLlBra6QJrwerGSSmNDC8b1xeuPdOi3bqnUk3h4T3P6DnOUQDP3Mf0wkroI9GLhy416 wzIhomRFMCjgTnDY8ndRhLvwRC0uzNQSxk8Xsij1AjNSiuEhzNg3zzRYT3oVA62+tndkmY ygn0qvyUQKrMtyGqWJ2QwKHCfw1Ng30= Message-ID: <06ae27b6-7a38-ff73-8d9b-70b6be517ccc@tilda.center> Date: Fri, 18 Aug 2023 11:22:58 +0200 List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.14.0 Subject: Re: Sudden need for bhyve TPM Emulation... willing to port swtpm? To: =?UTF-8?Q?Corvin_K=c3=b6hne?= , "freebsd-virtualization@freebsd.org" References: <662af723-de9f-36d9-c960-ef08379ca26e@callfortesting.org> <1d4e6558-0c56-5758-d87e-e9bf4aacc0a5@tilda.center> <85ee3beda055c5bc9fae26c07247fe0cea1458e9.camel@FreeBSD.org> <2f1539fc-f8b2-2ec5-9c68-c60f68e66c0e@tilda.center> <2c1205c0fc48e8c6ac103d3f3ca0c722a7cd3c6e.camel@FreeBSD.org> Content-Language: en-US From: =?UTF-8?Q?Goran_Meki=c4=87?= In-Reply-To: <2c1205c0fc48e8c6ac103d3f3ca0c722a7cd3c6e.camel@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-2.90 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[tilda.center,reject]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[tilda.center:s=c3po]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-virtualization@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; ASN(0.00)[asn:20473, ipnet:108.61.164.0/22, country:US]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[tilda.center:+]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_SOME(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[] X-Spamd-Bar: -- X-Rspamd-Queue-Id: 4RRxHj5yTQz3W4n Hello, There's an update for swtpm and I submitted https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273199. My first question is if phabricator is preferred for this port? I'm OK with submitting it on either place, so whatever is easier. With updated port there's also support for CUSE, which would allow swtpm to be used with pass-through. The problem is that socket and CUSE have problems which I described in upstream issue: https://github.com/stefanberger/swtpm/issues/820. If there are any suggestions how to fix that fuse error, I'd like to hear them and try and fix it. Regards, meka