From owner-freebsd-virtualization@freebsd.org Thu May 9 06:52:53 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97D29159F109 for ; Thu, 9 May 2019 06:52:53 +0000 (UTC) (envelope-from jo@durchholz.org) Received: from 5.itsy.de (5.itsy.de [188.40.84.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1E8298140E for ; Thu, 9 May 2019 06:52:51 +0000 (UTC) (envelope-from jo@durchholz.org) Received: from [192.168.178.32] (unknown [195.48.33.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by 5.itsy.de (Postfix) with ESMTPSA id 6A9F364029 for ; Thu, 9 May 2019 08:52:43 +0200 (CEST) To: freebsd-virtualization@freebsd.org From: Joachim Durchholz Subject: [maybe OT] Strange behaviour when connecting to serial port of a FreeBSD inside a VM Message-ID: <2c875da4-741b-3601-dd38-b191450497d7@durchholz.org> Date: Thu, 9 May 2019 08:52:42 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 1E8298140E X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.11 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.97)[-0.970,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; IP_SCORE(-0.75)[ipnet: 188.40.0.0/16(-2.01), asn: 24940(-1.73), country: DE(-0.01)]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; DMARC_NA(0.00)[durchholz.org]; MX_GOOD(-0.01)[188.40.84.14.durchholz.org]; NEURAL_HAM_SHORT(-0.28)[-0.278,0]; RCVD_IN_DNSWL_NONE(0.00)[14.84.40.188.list.dnswl.org : 127.0.10.0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:188.40.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 May 2019 06:52:53 -0000 Sorry if this off-topic, please direct me to the correct list. I have FreeBSD running inside a VirtualBox VM, and while FreeBSD boots and works fine and I could successfully hook up a host's domain socket, I don't see output on the socket. SOMETHING is working: Some boot messages are redirected, though to a place that I do not see. I have a shell script that recreates the entire situation from scratch, I can describe everything in excruciating detail - where do I start? Regards, Jo