From owner-freebsd-virtualization@freebsd.org Sun Dec 11 07:06:15 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1205AC701D2 for ; Sun, 11 Dec 2016 07:06:15 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id C8A2D287 for ; Sun, 11 Dec 2016 07:06:14 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au [203.13.68.150]) by alto.onthenet.com.au (Postfix) with ESMTPS id D31FA20AE991 for ; Sun, 11 Dec 2016 17:05:48 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id CACC82809D3 for ; Sun, 11 Dec 2016 17:05:48 +1000 (AEST) X-Amavis-Modified: Mail body modified (using disclaimer) - iredmail.onthenet.com.au Received: from iredmail.onthenet.com.au ([127.0.0.1]) by localhost (iredmail.onthenet.com.au [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Qv-tFu9sFaBd for ; Sun, 11 Dec 2016 17:05:48 +1000 (AEST) Received: from Peters-MacBook-Pro-2.local (c-67-180-92-13.hsd1.ca.comcast.net [67.180.92.13]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id 47D5D280996; Sun, 11 Dec 2016 17:05:46 +1000 (AEST) Subject: Re: Execute VMXON again without setting CR4.VMXE to 1 To: "Shen, Zhuojia" References: Cc: "freebsd-virtualization@freebsd.org" From: Peter Grehan Message-ID: <97006289-6009-d16b-ade4-b70716038d23@freebsd.org> Date: Sat, 10 Dec 2016 23:06:01 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=YJDv8VOx c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=5eVCmCvhg37cu/pjidAGzw==:17 a=N659UExz7-8A:10 a=n5n_aSjo0skA:10 a=Y-EksX5Qq8rZYlfHvRIA:9 a=pILNOxqGKmIA:10 wl=host:3 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 11 Dec 2016 07:06:15 -0000 Hi, > I believe I have found a bug in the BHyVe VMX implementation for > Intel platform. Following is the details. > > In sys/amd64/vmm/intel/vmx.c, there are three functions, vmx_enable > (line 500), vmx_disable (line 462), and vmx_restore (line 522), which > respectively enable, disable, and restore VMX on the current > processor. There is also a file scope integer array vmxon_enabled > (line 122) which keeps a record whether VMX on each processor is > enabled. > > I noticed that in function vmx_enable, the kernel sets CR4.VMXE to 1, > executes the VMXON instruction, and then sets the corresponding cell > in vmxon_enabled to 1. That is fine. However, in function > vmx_disable, the kernel executes VMXOFF, clears CR4.VMXE back to 0, > but does not clear the corresponding cell in vmxon_enabled back to 0. > This will cause a problem when the function vmx_restore is called, in > which the kernel executes VMXON again if that the corresponding cell > in that array is 1. That is, it will execute VMXON without CR4.VMXE > being set. > > Of course, that is only my understanding of the way how these > functions will be called. If I am wrong, could anyone of you please > advise me how this works? Thanks. vmx_disable is currently only called on vmm module unload, so vmx_restore/vmx_enable can never be called again after that. later, Peter. From owner-freebsd-virtualization@freebsd.org Sun Dec 11 07:20:34 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 412C2C7060B for ; Sun, 11 Dec 2016 07:20:34 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 03C939C9 for ; Sun, 11 Dec 2016 07:20:33 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au [203.13.68.150]) by alto.onthenet.com.au (Postfix) with ESMTPS id 272362126636 for ; Sun, 11 Dec 2016 17:20:14 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 1DB0F280996 for ; Sun, 11 Dec 2016 17:20:14 +1000 (AEST) X-Amavis-Modified: Mail body modified (using disclaimer) - iredmail.onthenet.com.au Received: from iredmail.onthenet.com.au ([127.0.0.1]) by localhost (iredmail.onthenet.com.au [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id hFWPKTloKZlY for ; Sun, 11 Dec 2016 17:20:14 +1000 (AEST) Received: from Peters-MacBook-Pro-2.local (c-67-180-92-13.hsd1.ca.comcast.net [67.180.92.13]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id 57A4C280502; Sun, 11 Dec 2016 17:20:12 +1000 (AEST) Subject: Re: Debian 8 CPU stall To: Rajil Saraswat References: <9c9e83a5-16c6-0ab5-0ac4-af0a54430706@freebsd.org> <6cff5bf2-9654-8627-83c4-6ab48ee763b5@gmail.com> From: Peter Grehan Cc: freebsd-virtualization@FreeBSD.org Message-ID: <56863fec-d8f8-2601-811f-511cd199e82f@freebsd.org> Date: Sat, 10 Dec 2016 23:20:28 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <6cff5bf2-9654-8627-83c4-6ab48ee763b5@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=YJDv8VOx c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=5eVCmCvhg37cu/pjidAGzw==:17 a=N659UExz7-8A:10 a=n5n_aSjo0skA:10 a=MK8az4FAIlLI1K8yN9IA:9 a=pILNOxqGKmIA:10 wl=host:3 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 11 Dec 2016 07:20:34 -0000 Hi Rajil, > No the system is not oversubscribed. I have a 11 vCPU (1 on debian and 1 > on ubuntu) on a 24 core machine. The debian jail is running x2go and an > ssh server for remote access, so the I/O shouldnt be an issue. The > ubuntu jail doesnt give out any warning messages though. ... > I use vm-bhyve for managing the jails which looks like this for debian8: > > guest="linux" > loader="grub" > cpu=1 > memory=2048M > network0_type="virtio-net" > network0_switch="lannetwork" > disk0_type="virtio-blk" > disk0_name="/dev/zvol/vmpool/os2" > disk0_dev="custom" > passthru0="2/0/0" > passthru1="2/0/1" Looks like a possibly lost interrupt. Can you check to see if this system is using APIC virtualization ? # sysctl -a hw.vmm.vmx.cap ... hw.vmm.vmx.cap.posted_interrupts: 1 hw.vmm.vmx.cap.virtual_interrupt_delivery: 1 (these will be zero if APIC virtualization not in use) If so, one thing to try is disabling these and see if that helps. This can be done by setting the tunable hw.vmm.vmx.use_apic_vid to 1 (e.g. in /boot/loader.conf, or unloading vmm.ko, setting the value with kenv, and the reloading vmm.ko) later, Peter. From owner-freebsd-virtualization@freebsd.org Sun Dec 11 15:27:30 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2272BC72979 for ; Sun, 11 Dec 2016 15:27:30 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: from mail-pg0-x235.google.com (mail-pg0-x235.google.com [IPv6:2607:f8b0:400e:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E4AEA821 for ; Sun, 11 Dec 2016 15:27:29 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: by mail-pg0-x235.google.com with SMTP id p66so25864719pga.2 for ; Sun, 11 Dec 2016 07:27:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:references:cc:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=yX2XuUKjhnBVBFGyf9VENQ8CdL8iX0OOotL8grwiyRI=; b=V/VOl/2fDXHt7gv5t9x/3yu9tLy2d+4rmeGlFhaUjUmoSDqNj7J9OukjVhgBXwKhZV V7Ncv2jOgfzSuOC/vkNguNq0kNIl0QDHvZIE/cLKi8kjfkXjS7czrPMriFrkkaSiB8qV sRd6MlMrA/UrgV6u8lfGw6+48p8Z94EMf44Y9GgZPRGT1YKuuhXb5kaokiGXJvvhO/yi g2fjL75e/ZnwH3Mr/sZTqifeOhyTHa0hQy7rdmTb1J8I1Tgug/gkT6y5TstUwWudeM4I ktKZMxbXmS+lqCjTcGUrdvFxrWe63hEk8Tdg1UjwIioPPkxmo8p8iQsS3vUyUbZARG81 6FBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=yX2XuUKjhnBVBFGyf9VENQ8CdL8iX0OOotL8grwiyRI=; b=Pk8/e45sAbyqCFiMrt0+LM36QMKUud5Yd5w0HkMuecq0K9dczeucjZRALMkH120Ld/ bvznFAKgeln+VLHOwlvAhfhEx5IirvAzN7eh/ufFGztnugROf0Au5H6GDAX9KrTw7llt mzdPgtLIltp0Kf14pBlUQ2A3McLFCLnetTxGjxfu2naQTBHMDNnW+pUTu13clvC+j4Wx 9gM2iSGUVibDB60fMpjCNGW40tJk7BTPsnUD94lWyNMrjxQJ4LlI8A3OsmtgzfQxIw2J pi78FXQza5v/C2L1BQ6X1sWBGbb1sm15tn/K/DF1F7lXG7KNRFGWgwJJ1hGDZge+zT7j X/4g== X-Gm-Message-State: AKaTC01Fao4BXrEWkexqUkxb2MWJ7SrZuI2kfXfQreTwdDMAgq558uClJLgb/yWSnkdEHw== X-Received: by 10.99.55.79 with SMTP id g15mr160430692pgn.65.1481470049122; Sun, 11 Dec 2016 07:27:29 -0800 (PST) Received: from [172.16.1.38] (c-73-155-87-64.hsd1.tx.comcast.net. [73.155.87.64]) by smtp.gmail.com with ESMTPSA id 65sm70544067pfl.21.2016.12.11.07.27.27 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 11 Dec 2016 07:27:28 -0800 (PST) Subject: Re: Debian 8 CPU stall References: <9c9e83a5-16c6-0ab5-0ac4-af0a54430706@freebsd.org> <6cff5bf2-9654-8627-83c4-6ab48ee763b5@gmail.com> <56863fec-d8f8-2601-811f-511cd199e82f@freebsd.org> Cc: freebsd-virtualization@FreeBSD.org From: Rajil Saraswat Message-ID: Date: Sun, 11 Dec 2016 09:27:23 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <56863fec-d8f8-2601-811f-511cd199e82f@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 11 Dec 2016 15:27:30 -0000 On 12/11/2016 01:20 AM, Peter Grehan wrote: > Looks like a possibly lost interrupt. > > Can you check to see if this system is using APIC virtualization ? > > # sysctl -a hw.vmm.vmx.cap > ... > hw.vmm.vmx.cap.posted_interrupts: 1 > hw.vmm.vmx.cap.virtual_interrupt_delivery: 1 > > (these will be zero if APIC virtualization not in use) > > If so, one thing to try is disabling these and see if that helps. > This can be done by setting the tunable hw.vmm.vmx.use_apic_vid to 1 > (e.g. in /boot/loader.conf, or unloading vmm.ko, setting the value > with kenv, and the reloading vmm.ko) > > later, > > Peter. > > I don't seem to have that sysctl on my system. Should i create one? # sysctl -a |grep vmm kern.proc_vmmap_skip_resident_count: 0 kern.coredump_pack_vmmapinfo: 1 hw.vmm.npt.pmap_flags: 0 hw.vmm.svm.num_asids: 0 hw.vmm.svm.disable_npf_assist: 0 hw.vmm.svm.features: 4294967295 hw.vmm.svm.vmcb_clean: 959 hw.vmm.vmx.vpid_alloc_failed: 0 hw.vmm.vmx.posted_interrupt_vector: 252 hw.vmm.vmx.cap.posted_interrupts: 1 hw.vmm.vmx.cap.virtual_interrupt_delivery: 1 hw.vmm.vmx.cap.invpcid: 1 hw.vmm.vmx.cap.monitor_trap: 1 hw.vmm.vmx.cap.unrestricted_guest: 1 hw.vmm.vmx.cap.pause_exit: 1 hw.vmm.vmx.cap.halt_exit: 1 hw.vmm.vmx.initialized: 1 hw.vmm.vmx.cr4_zeros_mask: 18446744073705920512 hw.vmm.vmx.cr4_ones_mask: 8192 hw.vmm.vmx.cr0_zeros_mask: 18446744071025197056 hw.vmm.vmx.cr0_ones_mask: 32 hw.vmm.ept.pmap_flags: 1531 hw.vmm.vrtc.flag_broken_time: 1 hw.vmm.ppt.devices: 2 hw.vmm.iommu.initialized: 1 hw.vmm.bhyve_xcpuids: 72 hw.vmm.topology.cpuid_leaf_b: 1 hw.vmm.topology.cores_per_package: 1 hw.vmm.topology.threads_per_core: 1 hw.vmm.create: beavis hw.vmm.destroy: beavis hw.vmm.force_iommu: 0 hw.vmm.trace_guest_exceptions: 0 hw.vmm.ipinum: 251 hw.vmm.halt_detection: 1 Thanks, Rajil From owner-freebsd-virtualization@freebsd.org Sun Dec 11 17:11:26 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A74F8C72BA4 for ; Sun, 11 Dec 2016 17:11:26 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 68DEAE74 for ; Sun, 11 Dec 2016 17:11:26 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au [203.13.68.150]) by alto.onthenet.com.au (Postfix) with ESMTPS id DEE1520AE974 for ; Mon, 12 Dec 2016 03:11:05 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id D01E4280999 for ; Mon, 12 Dec 2016 03:11:05 +1000 (AEST) X-Amavis-Modified: Mail body modified (using disclaimer) - iredmail.onthenet.com.au Received: from iredmail.onthenet.com.au ([127.0.0.1]) by localhost (iredmail.onthenet.com.au [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id xk1DuffrKoDh for ; Mon, 12 Dec 2016 03:11:05 +1000 (AEST) Received: from Peters-MacBook-Pro-2.local (c-67-180-92-13.hsd1.ca.comcast.net [67.180.92.13]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id 257DD2808F7; Mon, 12 Dec 2016 03:11:03 +1000 (AEST) Subject: Re: Debian 8 CPU stall To: Rajil Saraswat References: <9c9e83a5-16c6-0ab5-0ac4-af0a54430706@freebsd.org> <6cff5bf2-9654-8627-83c4-6ab48ee763b5@gmail.com> <56863fec-d8f8-2601-811f-511cd199e82f@freebsd.org> Cc: freebsd-virtualization@FreeBSD.org From: Peter Grehan Message-ID: <131518ab-c3fc-6509-ba24-08b5c32cddd5@freebsd.org> Date: Sun, 11 Dec 2016 09:11:18 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=YJDv8VOx c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=5eVCmCvhg37cu/pjidAGzw==:17 a=N659UExz7-8A:10 a=n5n_aSjo0skA:10 a=fs8nlc1NudZ2wVvRe4oA:9 a=pILNOxqGKmIA:10 wl=host:3 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 11 Dec 2016 17:11:26 -0000 Hi Rajil, > I don't seem to have that sysctl on my system. Should i create one? It's there: > # sysctl -a |grep vmm ... > hw.vmm.vmx.cap.posted_interrupts: 1 > hw.vmm.vmx.cap.virtual_interrupt_delivery: 1 The easiest way to disable APIC virtualization is to add this line to /boot/loader.conf and reboot hw.vmm.vmx.use_apic_vid="0" (I got that wrong in the previous email; should have been zero) On a reboot, the above sysctl leaves should be set to 0. later, Peter. From owner-freebsd-virtualization@freebsd.org Sun Dec 11 21:00:31 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 56B40C72630 for ; Sun, 11 Dec 2016 21:00:31 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 324611F25 for ; Sun, 11 Dec 2016 21:00:31 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uBBL012J056066 for ; Sun, 11 Dec 2016 21:00:31 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201612112100.uBBL012J056066@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-virtualization@FreeBSD.org Subject: Problem reports for freebsd-virtualization@FreeBSD.org that need special attention Date: Sun, 11 Dec 2016 21:00:31 +0000 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 11 Dec 2016 21:00:31 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 212711 | [typo] bhyve: virtio-rnd PCI ID doesn't match vio New | 212820 | FreeBSD 10-STABLE from latest HEAD and 11-RELEASE 2 problems total for which you should take action. From owner-freebsd-virtualization@freebsd.org Sun Dec 11 21:01:35 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97857C72BF9 for ; Sun, 11 Dec 2016 21:01:35 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 324296E6 for ; Sun, 11 Dec 2016 21:01:35 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id uBBL1VcU089224 for ; Sun, 11 Dec 2016 22:01:31 +0100 (CET) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 59229EFB; Sun, 11 Dec 2016 22:01:31 +0100 (CET) Message-ID: <584DBEAA.1080502@omnilan.de> Date: Sun, 11 Dec 2016 22:01:30 +0100 From: Harry Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: Unhandled ps2 keyboard keysym with UEFI-edk2-bootrom and bhyve(8) Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Sun, 11 Dec 2016 22:01:31 +0100 (CET) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 11 Dec 2016 21:01:35 -0000 Dear all, booting guests with uefi-edk2 bootrom works great, thanks for that great support! Unfortunately the VNC part seems to have keyscan problems: Unhandled ps2 keyboard keysym 0xc4 Unhandled ps2 keyboard keysym 0xf6 Unhandled ps2 keyboard keysym 0xff7f Just to list a view... The really unfortunate problem is that some characters are completely missing, while others are just shifted (involving even meta keys). I haven't found any rule yet, it looks like a mixture of en-US and de-DE layout. Most unfortunate, I can't login because of the missing characters :-( So close yet so far... I haven't really looked into EDKII but saw that BhyvePkg/ (of sysutils/uefi-edk2-bhyve) doesn't include filesystem support. But what I'm really wondering about is how to influence boot order e.g. If I boot into the EFI shell (edk2-bootrom guest) and return with exit into the uefi firmware setup (still edk2-bootrom), I can select what to boot with the boot manager (also MBR booting via CSM works great, thanks thanks thanks!), and I can also save the settings, but they are lost if bhyve(8) terminates. There's /dev/vmm.io/host-bootrom, which I don't understand yet, but probably that's a way to feed the firmware? Thanks for any hints, -harry P.S.: Please set me CC, I'm not subscribed to virtualization From owner-freebsd-virtualization@freebsd.org Sun Dec 11 23:31:02 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49588C737E2 for ; Sun, 11 Dec 2016 23:31:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 38CF016BD for ; Sun, 11 Dec 2016 23:31:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uBBNV1eS045064 for ; Sun, 11 Dec 2016 23:31:02 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 215235] Can't use iSCSI targets on AWS storage gateway Date: Sun, 11 Dec 2016 23:31:02 +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: 10.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 11 Dec 2016 23:31:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215235 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- CC|freebsd-amd64@FreeBSD.org | Assignee|freebsd-bugs@FreeBSD.org |freebsd-virtualization@Free | |BSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Dec 12 12:27:46 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8BCF8C736F6 for ; Mon, 12 Dec 2016 12:27:46 +0000 (UTC) (envelope-from ian.campbell@docker.com) Received: from mail-wj0-x22f.google.com (mail-wj0-x22f.google.com [IPv6:2a00:1450:400c:c01::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C0A4EB7 for ; Mon, 12 Dec 2016 12:27:46 +0000 (UTC) (envelope-from ian.campbell@docker.com) Received: by mail-wj0-x22f.google.com with SMTP id tk12so70349623wjb.3 for ; Mon, 12 Dec 2016 04:27:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=docker.com; s=google; h=mime-version:from:date:message-id:subject:to:cc; bh=grAdJj/7HVPQ7EBpC0VnIxhqJnL7hL6fveShgVVnYrY=; b=D7ZXdgOxgz2CEEqw2jkwYhfS8F9Wu15wBYN+tavaXeCqrlgsWRj74yJla0CWinx64Z r2ZZJ7+oQCGx2J9pt4/98ni2W8XOfZg4MyvTO+vtUGPYZ1s2wfUsBIvWVqUbwstFxQ0g lKmL9eP6KC4g4sYX9N8Ugt/7GiBYC0erhIS0M= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=grAdJj/7HVPQ7EBpC0VnIxhqJnL7hL6fveShgVVnYrY=; b=ZpG5obizoG1e3G4pIdpRGuj/6+QEKy7EFM62h5ZaQLAKa/VN4z4NlPwfAJMFItFtzn ohv9wsV3ZXQ238VyPVhPSHtU36nzfm4Xo6EMX6bS9VDUOv4rf0nNhUSUa+Nx6tsLgksM pF58cA9tiXom25aLQvcR6lHtqM2fZnMvv0QcxNAPQwEPr0M3GAUV+/siyEz8tdi7uUMw 6mssUEt5F3P53K4LwZCetFndYBf/pmXW7+V0unAquFQySTFf5uicrcrIttsFelQJTe9G 1/BQ1UMw+P/c0vwcltAc3P0LPbtW6+gZMIsm1HZPcbBxM7ZczETUEbEcKL7WFQBznAG3 Snzw== X-Gm-Message-State: AKaTC034zFOp51ZMYtQQSj8d2KllnkCWjOfPzvBDc2sQq1NYBO6UbuTE/LlCtnsI92DIyvl0X8osQv+nuDR5iwhw X-Received: by 10.194.105.228 with SMTP id gp4mr59936237wjb.208.1481545664247; Mon, 12 Dec 2016 04:27:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.107.231 with HTTP; Mon, 12 Dec 2016 04:27:43 -0800 (PST) From: Ian Campbell Date: Mon, 12 Dec 2016 12:27:43 +0000 Message-ID: Subject: Query about bhyve's blockif_cancel and the signalling mechanisms To: freebsd-virtualization@freebsd.org Cc: anil@recoil.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Mon, 12 Dec 2016 12:27:46 -0000 Hello, Recently I've been investigating a blk io hang/deadlock[0] in Hyperkit (a bhyve derived hypervisor for Mac's using the OSX Hypervisor framework). While I think I understand that issue (TL;DR: OSX kevent EVFILT_SIGNAL does not receive signals directed to specific threads rather than entire processes, which is different from FreeBSD where it does) there are some aspects of the code which I'm unsure about the mechanisms by which they work on FreeBSD. To recap my understanding of the mechanisms at work (glossing over the queue handling and condvars involved etc), the bhyve block_if infrastructure registers a callback for SIGCONT with the mevent subsystem, which is a kevent/kqueue thing which delivers events to the main thread (mevent_dispatch is the last thing in main()) it also sets SIGCONT to SIG_IGN. When a disk controller device model wants to cancel a block request (e.g. in ahci_port_stop) it calls blockif_cancel which sends a SIGCONT to the blkio thread which has claimed the request, notionally to kick it out of whatever blocking system call it is in and cause it to return an error to the device model. The signal handler callback (in the mevent thread) then kicks the thread which sent the signal to indicate completion of the cancellation. I go in to some more detail of how I think things work in [0] but that's the gist of it. The main thing I do not follow is whether or not the blkio thread is actually interrupted at all when the signal has been configured to be delivered via the kevent/kqueue mechanisms to a 3rd unrelated thread. I've dug around in the FreeBSD kevent and signal man pages but I cannot find any part which describes anything of the semantics which bhyve seems to be relying on (which seems to be that the system call in the target thread will return EINTR at some point before the thread which is "handling" the signal via kevent/kqueue sees that event). Have I missed something here or is bhyve relying on some subtle underlying semantics? I have a secondary concern which is what happens if the IO thread is on its way to making a blocking system call in blockif_proc but has not actually done so when the signal is delivered. It seems like it would simply carry on and make the blocking call with perhaps unexpected consequences (i/o getting wedged, perhaps only until a second reset attempt). I've not actually seen this happening though and there's a chance I'm simply over thinking things after staring at them for so long! I should say that I've mostly been looking at the hyperkit code here but AFAICT it has not diverged in any relevant ways from the bhyve code (although it might now have to in the future given the differing semantics of EVFILT_SIGNAL on OSX). Thanks, Ian. [0] https://github.com/docker/hyperkit/issues/94 From owner-freebsd-virtualization@freebsd.org Tue Dec 13 01:20:25 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1C85AC74B1B; Tue, 13 Dec 2016 01:20:25 +0000 (UTC) (envelope-from javocado@gmail.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BD7321D86; Tue, 13 Dec 2016 01:20:24 +0000 (UTC) (envelope-from javocado@gmail.com) Received: by mail-wm0-x229.google.com with SMTP id a197so87424807wmd.0; Mon, 12 Dec 2016 17:20:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=ks5P72YneuHYn5HRAzWlTvlPEI4cfDr1xsM7fBaghwQ=; b=XrZYRe8AsrdpHn6ssu6xKdbY2Cadb0hREIFkxI6Qgi17+qnAT40KDrkaqvwGr4+umi xf9Sk3rc502vu04Xlu4Q2nbV1fpOKxF5dJvqX1ClZ6Wru/qi27gQ6j1FNs7sMFqQd0TW dvT+1S5qjT8zwLV96Vh/oUQWS2kxrwhxGShYD93nM6b/D9/iouu5sVXEHxKxRZfJeX90 /yo+Vd0zsrPgHepyTq+mib7X5IT7hTNq658J6doCVwzolHuLkA0nrMNUujEB13vG5kzC NI63Eqnucba1QIewAtuhsLFafIdPkXAWNhy6nPim9BH0nJ1jSXc3388/gBzbYwDZD2Nc W0aw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=ks5P72YneuHYn5HRAzWlTvlPEI4cfDr1xsM7fBaghwQ=; b=LUHdUH/NYY5TOVSd/moljcaSHYwHURY0rw1BS8FHKPsIpAJtPb7XUMC0ZCNrl2suRV csJQvE2I+O3LYVTt+TV1oG/3IznpM48CY2XRDl4xLoFPU7NzysF/nnul86ReNWWhCCFz O2uz/9e7g/syWrwm9Xz6hy+r0hoJ76HjlhfAOg554xM0nGU6bjnWFj7uApj/SaYpcoIM waky9PqJy8ZRPSlj9GCz+gVksw0ZOk696tvszBa5JRaeQqkNElBXTP/iBCDOslkrV7/7 AgPKeIAZfGrEPGfowax89X0qImI+5g5srmpc6Hj34pLQGKk8sADOdsGNESndiQRLg7QI vF2Q== X-Gm-Message-State: AKaTC00qxDcq8AizXXUhxeda18PYykcQy+GWHBierxDmTGQfuJouQq/E7m/UW/IfNXmUaucpwO0fLo+arFuLig== X-Received: by 10.46.77.17 with SMTP id a17mr40522055ljb.34.1481592021762; Mon, 12 Dec 2016 17:20:21 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.25.165 with HTTP; Mon, 12 Dec 2016 17:20:21 -0800 (PST) From: javocado Date: Mon, 12 Dec 2016 17:20:21 -0800 Message-ID: Subject: Re-sparse a file-backed IO device + zfs To: freebsd-virtualization@freebsd.org, freebsd-questions@freebsd.org, FreeBSD Filesystems Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Tue, 13 Dec 2016 01:20:25 -0000 Hi, I'm setting up a bhyve wherein: host # truncate -s 1T vol.file host # du -ah vol.file 200K vol.file host # /usr/sbin/bhyve ... -s 4,ahci-hd,vol.file ... Then inside the bhyve I create a zpool (ada0 = vol.file): bhyve # zpool create -O devices=off -O atime=off -O compression=on -m /mnt/data1 data1 ada0 And I put a bunch of stuff in the zpool ... and the vol.file grows in size: host # du -ah vol.file 100G vol.file Then I remove the files from the zpool and the zpool usage returns to 0 but of course the vol.file size does not shrink, the data is still there (but not referenced?) Normally I'd just write zeros to a file inside the zpool until the pool fills up, then maybe cp --sparse vol.file for good measure, but with compression on in the zpool the zeroing doesn't really fill up space or seem to overwrite anything. In my testing the zero file grew larger than 100G with no change to vol.file I did not let it run forever, however. Any other ideas how to scrub off or clear out deleted data from a zpool and/or this kind of file-backed device? From owner-freebsd-virtualization@freebsd.org Tue Dec 13 01:25:22 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B6CDBC74FB8 for ; Tue, 13 Dec 2016 01:25:22 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 70B10360 for ; Tue, 13 Dec 2016 01:25:22 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-qt0-x235.google.com with SMTP id c47so93749366qtc.2 for ; Mon, 12 Dec 2016 17:25:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Z3BWObFzyIeKTSrXcM227IZWryAiGZu/YM2FEOe0isY=; b=uatTZEL8zukKy4INkDUSWLfERUUjMdVhh7SMV2hO/EjIXEZAu+I+TLZyAh0bzqBxE1 R7hwN7ObWr7ECBFqR2lx+7bvB0K1x4+86h/v0NM9w6Os/1m/Y032EhxG3epe7AtFjQ6N JM/MSvfd5bcY/PIg5WhfsevXUm8CNyAkk43IfQzmDMHu56nUXXHi+L6pLl8ScJElwqp5 oBvC+2Vtd3U1i57WDqNcD/7ZZDmcxfP0wJhOEXjhQaLe+7YxvtxKAbu22yBrUrYMtTun 4N+JTrpAQZYKrMImyuDtr0hS7ugHVB12AluZvO146ebMkC1VDhOr0mFSmOYkYXnT0f+8 4Hew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Z3BWObFzyIeKTSrXcM227IZWryAiGZu/YM2FEOe0isY=; b=N9jIQ9zIW2NLX8/6NgwwaJYadPiwPnY6s5cFFoSLEuuavLW/0yBZD78jEQFs+XSWTR UHXPrGqJB9sUSLo42Mq39hDpUA5X9wis5qDqNsFHJ46Clq3+OpDxkzl50Fo48Rt2dPZQ yb+4fb75LM/CFkjqAKSJKDf3p95bwJji7FkEUbzOGAcCj0VO0kfsodW8cgCDDy1a+Kx9 zUjiedBoR1x3GkYzMzBcOpsmC9P2+AronYO7jiSECMtc+xOqUzyZXDxU/rlwEWbPdEsd +wekNArRaFhjVltccRQfoP6ET2iexkw55U+FvXpO+IogG2V0upqCvDWmiiQTRwSRQRer YxfQ== X-Gm-Message-State: AKaTC01i1z1IKx56t6cBq550KUKmK6dxr4oqSm4sYPI8XG78ARo5g8prX1LN8NMWXCkXpNmC X-Received: by 10.237.32.205 with SMTP id 71mr93387527qtb.237.1481592321577; Mon, 12 Dec 2016 17:25:21 -0800 (PST) Received: from mutt-hardenedbsd (pool-100-16-218-231.bltmmd.fios.verizon.net. [100.16.218.231]) by smtp.gmail.com with ESMTPSA id v18sm27867220qkb.40.2016.12.12.17.25.20 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 12 Dec 2016 17:25:20 -0800 (PST) Date: Mon, 12 Dec 2016 20:25:18 -0500 From: Shawn Webb To: javocado Cc: freebsd-virtualization@freebsd.org, freebsd-questions@freebsd.org, FreeBSD Filesystems Subject: Re: Re-sparse a file-backed IO device + zfs Message-ID: <20161213012518.GA77233@mutt-hardenedbsd> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD mutt-hardenedbsd 12.0-CURRENT-HBSD FreeBSD 12.0-CURRENT-HBSD X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0x6A84658F52456EEE User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Tue, 13 Dec 2016 01:25:22 -0000 --J/dobhs11T7y2rNN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 12, 2016 at 05:20:21PM -0800, javocado wrote: > Hi, >=20 > I'm setting up a bhyve wherein: >=20 > host # truncate -s 1T vol.file > host # du -ah vol.file > 200K vol.file >=20 > host # /usr/sbin/bhyve ... -s 4,ahci-hd,vol.file ... >=20 > Then inside the bhyve I create a zpool (ada0 =3D vol.file): >=20 > bhyve # zpool create -O devices=3Doff -O atime=3Doff -O compression=3Don= -m > /mnt/data1 data1 ada0 >=20 > And I put a bunch of stuff in the zpool ... and the vol.file grows in siz= e: >=20 > host # du -ah vol.file > 100G vol.file >=20 > Then I remove the files from the zpool and the zpool usage returns to 0 b= ut > of course the vol.file size does not shrink, the data is still there (but > not referenced?) >=20 > Normally I'd just write zeros to a file inside the zpool until the pool > fills up, then maybe cp --sparse vol.file for good measure, but with > compression on in the zpool the zeroing doesn't really fill up space or > seem to overwrite anything. In my testing the zero file grew larger than > 100G with no change to vol.file I did not let it run forever, however. >=20 > Any other ideas how to scrub off or clear out deleted data from a zpool > and/or this kind of file-backed device? Instead of dd'ing /dev/zero, try /dev/random. All zeros compress extremely well, [pseudo-]random data does (or, ideally, should) not. --=20 Shawn Webb Cofounder and Security Engineer HardenedBSD GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --J/dobhs11T7y2rNN Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJYT038AAoJEGqEZY9SRW7u1g0P/impDd7fVDSFcO5i/3wlf8M6 8tUs1sg53pJYSNDtEbIfiSODiJDwaXl4+Kdp7o4WbFP68HCzhHPr/qKB4GTyhSPD CgQRa9Jj90E+B7+/zSTba/b5axa30mfSeoVc0Ma1+id/Yq7J+rVEa951eXGCaE/5 bmkrPnWHilYfdRJLY2npVoVwjC44vxn3f1GlD06rrwTV+JCMaw6f7k6hkuAh9trg UyoCJftEH1hzcpyAWYVS4Wn+t/6bXFICKv+tpwDwm+epVkf6tIKvNNFEYxE+TFik PhTk5+i7Lz/12bR6Vh/hKiYKKxHa2rtYSA49TDBMeInOa5yCGQ6f98/Nz/MKc8d9 LUXUSovnVLZkMVObUK31dPF9TuZESK3SGRUTN6CzDArRIcl63xqRWevuv6Hk46Je vurBhvtN89ROzd/BZ10rISuGv+TlyY5MvykggZ7v1obB7nkukFnGQ3PKwmL2DHP5 h1AMc+NFQOU6ym/qcMVDqX/BBuzFBvkgLzZyOjh5wPNsq1ScuBBYO7yFBBwzcQRl rDLviLKBsUNsjHtOF38evqcbGYl19th92o6q4pWiE6hriO/WnaI6yI5WtfPHV7ta oefL87gBeb98YegBF2cCMmE+e0kulJta8qFZQC5bLcIQoBF8Nk9fBfMHUYiGlBxZ /iLIWlsGHOIQt86ev4Nt =wvAw -----END PGP SIGNATURE----- --J/dobhs11T7y2rNN-- From owner-freebsd-virtualization@freebsd.org Tue Dec 13 05:57:23 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BFE74C74012 for ; Tue, 13 Dec 2016 05:57:23 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 83031339 for ; Tue, 13 Dec 2016 05:57:23 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au [203.13.68.150]) by alto.onthenet.com.au (Postfix) with ESMTPS id 5E8C32126626 for ; Tue, 13 Dec 2016 15:57:04 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 55DEF2809D3 for ; Tue, 13 Dec 2016 15:57:04 +1000 (AEST) X-Amavis-Modified: Mail body modified (using disclaimer) - iredmail.onthenet.com.au Received: from iredmail.onthenet.com.au ([127.0.0.1]) by localhost (iredmail.onthenet.com.au [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id aSGxw6Rd01KU for ; Tue, 13 Dec 2016 15:57:04 +1000 (AEST) Received: from Peters-MacBook-Pro-2.local (c-67-180-92-13.hsd1.ca.comcast.net [67.180.92.13]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id B49D22809CC; Tue, 13 Dec 2016 15:57:02 +1000 (AEST) Subject: Re: Unhandled ps2 keyboard keysym with UEFI-edk2-bootrom and bhyve(8) To: Harry Schmalzbauer References: <584DBEAA.1080502@omnilan.de> Cc: freebsd-virtualization@freebsd.org From: Peter Grehan Message-ID: Date: Mon, 12 Dec 2016 21:57:17 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <584DBEAA.1080502@omnilan.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=YJDv8VOx c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=5eVCmCvhg37cu/pjidAGzw==:17 a=N659UExz7-8A:10 a=n5n_aSjo0skA:10 a=O-Jy8nmuj3cDa4b37KUA:9 a=pILNOxqGKmIA:10 wl=host:3 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Tue, 13 Dec 2016 05:57:23 -0000 Hi Harry, > Unfortunately the VNC part seems to have keyscan problems: > Unhandled ps2 keyboard keysym 0xc4 > Unhandled ps2 keyboard keysym 0xf6 > Unhandled ps2 keyboard keysym 0xff7f > Just to list a view... > > The really unfortunate problem is that some characters are completely > missing, while others are just shifted (involving even meta keys). > I haven't found any rule yet, it looks like a mixture of en-US and de-DE > layout. > Most unfortunate, I can't login because of the missing characters :-( So > close yet so far... Would you be able to list the key mappings that don't work (and also the VNC client you are using) ? > But what I'm really wondering about is how to influence boot order e.g. > > If I boot into the EFI shell (edk2-bootrom guest) and return with exit > into the uefi firmware setup (still edk2-bootrom), I can select what to > boot with the boot manager (also MBR booting via CSM works great, thanks > thanks thanks!), and I can also save the settings, but they are lost if > bhyve(8) terminates. > There's /dev/vmm.io/host-bootrom, which I don't understand yet, but > probably that's a way to feed the firmware? There's a fix for this in progress - the contents of the UEFI NV vars will be saved/restored from a host file. later, Peter. From owner-freebsd-virtualization@freebsd.org Tue Dec 13 06:32:19 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BFF6CC74DA0 for ; Tue, 13 Dec 2016 06:32:19 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 6918415D0 for ; Tue, 13 Dec 2016 06:32:19 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au [203.13.68.150]) by alto.onthenet.com.au (Postfix) with ESMTPS id C423520C1C05 for ; Tue, 13 Dec 2016 16:31:59 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id B6474280502 for ; Tue, 13 Dec 2016 16:31:59 +1000 (AEST) X-Amavis-Modified: Mail body modified (using disclaimer) - iredmail.onthenet.com.au Received: from iredmail.onthenet.com.au ([127.0.0.1]) by localhost (iredmail.onthenet.com.au [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 3_O_WMxwJiOg for ; Tue, 13 Dec 2016 16:31:59 +1000 (AEST) Received: from Peters-MacBook-Pro-2.local (c-67-180-92-13.hsd1.ca.comcast.net [67.180.92.13]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id 6BDCC2809E1; Tue, 13 Dec 2016 16:31:57 +1000 (AEST) Subject: Re: Query about bhyve's blockif_cancel and the signalling mechanisms To: Ian Campbell , Tycho Nightingale References: Cc: freebsd-virtualization@freebsd.org, anil@recoil.org From: Peter Grehan Message-ID: <631f775d-8d61-55ba-1e7b-8ce4fcadcbf3@freebsd.org> Date: Mon, 12 Dec 2016 22:32:11 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=YJDv8VOx c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=5eVCmCvhg37cu/pjidAGzw==:17 a=N659UExz7-8A:10 a=n5n_aSjo0skA:10 a=Goinh_sa6ktK6CdGHDYA:9 a=pILNOxqGKmIA:10 wl=host:3 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Tue, 13 Dec 2016 06:32:19 -0000 Hi Ian, > To recap my understanding of the mechanisms at work (glossing over the > queue handling and condvars involved etc), the bhyve block_if > infrastructure registers a callback for SIGCONT with the mevent > subsystem, which is a kevent/kqueue thing which delivers events to the > main thread (mevent_dispatch is the last thing in main()) it also sets > SIGCONT to SIG_IGN. That's correct. The intent was to have the signal delivered via the kevent callback rather than standard signal delivery. > When a disk controller device model wants to > cancel a block request (e.g. in ahci_port_stop) it calls > blockif_cancel which sends a SIGCONT to the blkio thread which has > claimed the request, notionally to kick it out of whatever blocking > system call it is in and cause it to return an error to the device > model. Yep, that's correct. > The main thing I do not follow is whether or not the blkio thread is > actually interrupted at all when the signal has been configured to be > delivered via the kevent/kqueue mechanisms to a 3rd unrelated thread. It is interrupted on FreeBSD. > I've dug around in the FreeBSD kevent and signal man pages but I > cannot find any part which describes anything of the semantics which > bhyve seems to be relying on (which seems to be that the system call > in the target thread will return EINTR at some point before the thread > which is "handling" the signal via kevent/kqueue sees that event). > > Have I missed something here or is bhyve relying on some subtle > underlying semantics? I didn't think it too FreeBSD-specific - if a thread is blocked in a system call, sending a signal should force it to exit on most Unices. > I have a secondary concern which is what happens if the IO thread is > on its way to making a blocking system call in blockif_proc but has > not actually done so when the signal is delivered. It seems like it > would simply carry on and make the blocking call with perhaps > unexpected consequences (i/o getting wedged, perhaps only until a > second reset attempt). I've not actually seen this happening though > and there's a chance I'm simply over thinking things after staring at > them for so long! I believe this case is handled - I discussed this at length with Tycho when the code was committed a while back. Tycho - any thoughts ? later, Peter. From owner-freebsd-virtualization@freebsd.org Tue Dec 13 07:10:01 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E48EC75786; Tue, 13 Dec 2016 07:10:01 +0000 (UTC) (envelope-from karli.sjoberg@slu.se) Received: from EXCH2-1.slu.se (pop.slu.se [77.235.224.121]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "webmail.slu.se", Issuer "TERENA SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 98966891; Tue, 13 Dec 2016 07:10:00 +0000 (UTC) (envelope-from karli.sjoberg@slu.se) Received: from exch2-4.slu.se (77.235.224.124) by EXCH2-1.slu.se (77.235.224.121) with Microsoft SMTP Server (TLS) id 15.0.1236.3; Tue, 13 Dec 2016 07:54:47 +0100 Received: from exch2-4.slu.se ([fe80::d80d:2775:84ad:c144]) by exch2-4.slu.se ([fe80::d80d:2775:84ad:c144%22]) with mapi id 15.00.1236.000; Tue, 13 Dec 2016 07:54:47 +0100 From: =?utf-8?B?S2FybGkgU2rDtmJlcmc=?= To: javocado CC: "freebsd-questions@freebsd.org" , "freebsd-virtualization@freebsd.org" , FreeBSD Filesystems Subject: Re: Re-sparse a file-backed IO device + zfs Thread-Topic: Re-sparse a file-backed IO device + zfs Thread-Index: AQHSVQ3KGOl7buWA6UuHYaZ3yCwuRA== Date: Tue, 13 Dec 2016 06:54:46 +0000 Message-ID: Accept-Language: sv-SE, en-US Content-Language: sv-SE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Tue, 13 Dec 2016 07:10:01 -0000 DQpEZW4gMTMgZGVjLiAyMDE2IDAyOjIwIHNrcmV2IGphdm9jYWRvIDxqYXZvY2Fkb0BnbWFpbC5j b20+Og0KPg0KPiBIaSwNCj4NCj4gSSdtIHNldHRpbmcgdXAgYSBiaHl2ZSB3aGVyZWluOg0KPg0K PiBob3N0ICMgIHRydW5jYXRlIC1zIDFUIHZvbC5maWxlDQo+IGhvc3QgIyAgZHUgLWFoIHZvbC5m aWxlDQo+IDIwMEsgICAgdm9sLmZpbGUNCj4NCj4gaG9zdCAjICAvdXNyL3NiaW4vYmh5dmUgLi4u IC1zIDQsYWhjaS1oZCx2b2wuZmlsZSAuLi4NCj4NCj4gVGhlbiBpbnNpZGUgdGhlIGJoeXZlIEkg Y3JlYXRlIGEgenBvb2wgKGFkYTAgPSB2b2wuZmlsZSk6DQo+DQo+IGJoeXZlICMgIHpwb29sIGNy ZWF0ZSAtTyBkZXZpY2VzPW9mZiAtTyBhdGltZT1vZmYgLU8gY29tcHJlc3Npb249b24gLW0NCj4g L21udC9kYXRhMSBkYXRhMSBhZGEwDQo+DQo+IEFuZCBJIHB1dCBhIGJ1bmNoIG9mIHN0dWZmIGlu IHRoZSB6cG9vbCAuLi4gYW5kIHRoZSB2b2wuZmlsZSBncm93cyBpbiBzaXplOg0KPg0KPiBob3N0 ICMgIGR1IC1haCB2b2wuZmlsZQ0KPiAxMDBHICAgIHZvbC5maWxlDQo+DQo+IFRoZW4gSSByZW1v dmUgdGhlIGZpbGVzIGZyb20gdGhlIHpwb29sIGFuZCB0aGUgenBvb2wgdXNhZ2UgcmV0dXJucyB0 byAwIGJ1dA0KPiBvZiBjb3Vyc2UgdGhlIHZvbC5maWxlIHNpemUgZG9lcyBub3Qgc2hyaW5rLCB0 aGUgZGF0YSBpcyBzdGlsbCB0aGVyZSAoYnV0DQo+IG5vdCByZWZlcmVuY2VkPykNCj4NCj4gTm9y bWFsbHkgSSdkIGp1c3Qgd3JpdGUgemVyb3MgdG8gYSBmaWxlIGluc2lkZSB0aGUgenBvb2wgdW50 aWwgdGhlIHBvb2wNCj4gZmlsbHMgdXAsIHRoZW4gbWF5YmUgY3AgLS1zcGFyc2Ugdm9sLmZpbGUg Zm9yIGdvb2QgbWVhc3VyZSwgYnV0IHdpdGgNCj4gY29tcHJlc3Npb24gb24gaW4gdGhlIHpwb29s IHRoZSB6ZXJvaW5nIGRvZXNuJ3QgcmVhbGx5IGZpbGwgdXAgc3BhY2Ugb3INCj4gc2VlbSB0byBv dmVyd3JpdGUgYW55dGhpbmcuIEluIG15IHRlc3RpbmcgdGhlIHplcm8gZmlsZSBncmV3IGxhcmdl ciB0aGFuDQo+IDEwMEcgd2l0aCBubyBjaGFuZ2UgdG8gdm9sLmZpbGUgIEkgZGlkIG5vdCBsZXQg aXQgcnVuIGZvcmV2ZXIsIGhvd2V2ZXIuDQo+DQo+IEFueSBvdGhlciBpZGVhcyBob3cgdG8gc2Ny dWIgb2ZmIG9yIGNsZWFyIG91dCBkZWxldGVkIGRhdGEgZnJvbSBhIHpwb29sDQo+IGFuZC9vciB0 aGlzIGtpbmQgb2YgZmlsZS1iYWNrZWQgZGV2aWNlPw0KDQpXb3VsZG4ndCB5b3UgaGF2ZSBuZWVk ZWQgVFJJTSBvbiB0aGUgZGlzayhzKSBpbnNpZGUgdGhlIFZNIGFuZCBpdCB3b3VsZCBoYXZlIHRh a2VuIGNhcmUgb2YgYWxsIHRoaXMgZm9yIHlvdT8NCg0KL0sNCg0KPiBfX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBmcmVlYnNkLWZzQGZyZWVic2Qub3Jn IG1haWxpbmcgbGlzdA0KPiBodHRwczovL2xpc3RzLmZyZWVic2Qub3JnL21haWxtYW4vbGlzdGlu Zm8vZnJlZWJzZC1mcw0KPiBUbyB1bnN1YnNjcmliZSwgc2VuZCBhbnkgbWFpbCB0byAiZnJlZWJz ZC1mcy11bnN1YnNjcmliZUBmcmVlYnNkLm9yZyINCg== From owner-freebsd-virtualization@freebsd.org Tue Dec 13 22:33:01 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 787D4C76015 for ; Tue, 13 Dec 2016 22:33:01 +0000 (UTC) (envelope-from amy@getvoip.click) Received: from m1000.localvisible.com (m1007.localvisible.info [162.248.7.180]) by mx1.freebsd.org (Postfix) with ESMTP id 53FC51946 for ; Tue, 13 Dec 2016 22:33:00 +0000 (UTC) (envelope-from amy@getvoip.click) Received: from m4000.facilitymgmt.link (m4150.ONLINEVALUATOR.COM [185.179.204.52]) by m1000.localvisible.com (Postfix) with ESMTP id 76D501A7533 for ; Tue, 13 Dec 2016 08:02:29 -0800 (PST) Received: from mailerM1.localvisible.info (unknown [212.29.237.165]) by m4000.facilitymgmt.link (Postfix) with ESMTP id E0090269612 for ; Tue, 13 Dec 2016 17:09:27 +0200 (IST) Received: from list.localbizreport.net (unknown [192.168.100.137]) by mailerM1.localvisible.info (Postfix) with ESMTP id EA1EE2FC for ; Tue, 13 Dec 2016 16:51:59 +0200 (IST) To: freebsd-virtualization@freebsd.org Subject: Telephone System Quotes for Charlie's Choice Message-ID: Date: Tue, 13 Dec 2016 12:49:07 +0000 From: "Amy Brown" Reply-To: amy@getvoip.click MIME-Version: 1.0 X-Mailer-LID: 41,41,41 X-Mailer-RecptId: 34790047 X-Mailer-SID: 13917 X-Mailer-Sent-By: 1 Content-Type: text/plain; format=flowed; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Tue, 13 Dec 2016 22:33:01 -0000 Hi, My name is Amy and I’m with GetVoip.click offering Charlie's Choice the best current deals offered by telephone companies. VoIP (Voice Over Internet Protocol) is a technology that utilizes the Internet to make local and International phone calls significantly lowering your communication costs. They are central to maintaining both internal communications between colleagues and providing a consistent external line for your customers. The following information will be needed in order to compose a Quote: Full Name Company Name Phone number Zip Number of users Visit GetVoip.click for a quick no-obligation quote. Best regards, Amy Brown Amy@GetVoip.click www.GetVoip.click http://www.GetVoip.click/default.aspx?c=Charlie's Choice&p=(912) 383-4995&f=&l=&z=31534&e=freebsd-virtualization@freebsd.org&utm_source=is&utm_medium=email&utm_campaign=ZO22 (http://www.GetVoip.click/unsubscribe.aspx?e=freebsd-virtualization@freebsd.org) From owner-freebsd-virtualization@freebsd.org Wed Dec 14 00:06:59 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DFFCDC76CA8 for ; Wed, 14 Dec 2016 00:06:59 +0000 (UTC) (envelope-from tychon@freebsd.org) Received: from sasl.smtp.pobox.com (pb-sasl1.pobox.com [64.147.108.66]) (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 A1537DB0; Wed, 14 Dec 2016 00:06:58 +0000 (UTC) (envelope-from tychon@freebsd.org) Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-sasl1.pobox.com (Postfix) with ESMTP id F14C45186C; Tue, 13 Dec 2016 19:05:16 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=sasl; bh= tmjupcCyxDPoEgNYWP2dhB/Wb08=; b=H5fbP//8oqx9AV8UHxQssKQLO2a6hk1C hpPCNBLDm/vZ4o6z8Xltk15VBRruZ5Pceu8pq0sCB0cxsG1EB/sixgx47zWyyjgY So0TvAQ97QUXOEeM2m4hpMEgAy6He4E5ljhVYS36GbQMm5Inxp6pfMAYSkWWbRKY 7Ztl8sE+jI0= Received: from pb-sasl1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-sasl1.pobox.com (Postfix) with ESMTP id E87EC5186B; Tue, 13 Dec 2016 19:05:16 -0500 (EST) Received: from [10.0.1.5] (unknown [209.6.121.211]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pb-sasl1.pobox.com (Postfix) with ESMTPSA id DE3575186A; Tue, 13 Dec 2016 19:05:15 -0500 (EST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Query about bhyve's blockif_cancel and the signalling mechanisms From: Tycho Nightingale In-Reply-To: <631f775d-8d61-55ba-1e7b-8ce4fcadcbf3@freebsd.org> Date: Tue, 13 Dec 2016 19:05:14 -0500 Cc: Ian Campbell , freebsd-virtualization@freebsd.org, anil@recoil.org Content-Transfer-Encoding: quoted-printable Message-Id: <397B138D-3701-4FB4-A9B3-618CE2624C3C@freebsd.org> References: <631f775d-8d61-55ba-1e7b-8ce4fcadcbf3@freebsd.org> To: Peter Grehan X-Mailer: Apple Mail (2.1878.6) X-Pobox-Relay-ID: FE2CDA74-C190-11E6-84C3-B2316462E9F6-09779102!pb-sasl1.pobox.com X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 14 Dec 2016 00:07:00 -0000 Hi, On Dec 13, 2016, at 1:32 AM, Peter Grehan wrote: > Hi Ian, >=20 >> To recap my understanding of the mechanisms at work (glossing over = the >> queue handling and condvars involved etc), the bhyve block_if >> infrastructure registers a callback for SIGCONT with the mevent >> subsystem, which is a kevent/kqueue thing which delivers events to = the >> main thread (mevent_dispatch is the last thing in main()) it also = sets >> SIGCONT to SIG_IGN. >=20 > That's correct. The intent was to have the signal delivered via the = kevent callback rather than standard signal delivery. >=20 >> When a disk controller device model wants to >> cancel a block request (e.g. in ahci_port_stop) it calls >> blockif_cancel which sends a SIGCONT to the blkio thread which has >> claimed the request, notionally to kick it out of whatever blocking >> system call it is in and cause it to return an error to the device >> model. >=20 > Yep, that's correct. >=20 >> The main thing I do not follow is whether or not the blkio thread is >> actually interrupted at all when the signal has been configured to be >> delivered via the kevent/kqueue mechanisms to a 3rd unrelated thread. >=20 > It is interrupted on FreeBSD. >=20 >> I've dug around in the FreeBSD kevent and signal man pages but I >> cannot find any part which describes anything of the semantics which >> bhyve seems to be relying on (which seems to be that the system call >> in the target thread will return EINTR at some point before the = thread >> which is "handling" the signal via kevent/kqueue sees that event). >>=20 >> Have I missed something here or is bhyve relying on some subtle >> underlying semantics? >=20 > I didn't think it too FreeBSD-specific - if a thread is blocked in a = system call, sending a signal should force it to exit on most Unices. >=20 >> I have a secondary concern which is what happens if the IO thread is >> on its way to making a blocking system call in blockif_proc but has >> not actually done so when the signal is delivered. It seems like it >> would simply carry on and make the blocking call with perhaps >> unexpected consequences (i/o getting wedged, perhaps only until a >> second reset attempt). I've not actually seen this happening though >> and there's a chance I'm simply over thinking things after staring at >> them for so long! >=20 > I believe this case is handled - I discussed this at length with Tycho = when the code was committed a while back. >=20 > Tycho - any thoughts ? ahci_port_stop() is called under the protection the port soft-state lock = so that will stem any further requests from landing in the blockif = queue. That=92s the easy case. As for blockif requests which are queued, those are simply completed. = The ones that are in-flight all have their status set to BST_BUSY when = they are moved from the pending queue to the busy queue just prior to = being sent to blockif_proc(). It=92s therefore possible that an = in-flight request (one on the busy list) has yet to call blockif_proc(), = or is already inside blockif_proc() or has just completed = blockif_proc(). In all cases however BST_BUSY is cleared in = blockif_complete(). The key is therefore that regardless of where the = thread is, blockif_cancel() will continue to issue pthread_kill() until = the request reaches blockif_complete() =97 breaking it out of system = calls as necessary. Does that make sense? Tycho= From owner-freebsd-virtualization@freebsd.org Wed Dec 14 00:34:08 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0D84C743AA; Wed, 14 Dec 2016 00:34:07 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-wj0-x230.google.com (mail-wj0-x230.google.com [IPv6:2a00:1450:400c:c01::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 86FF31C84; Wed, 14 Dec 2016 00:34:07 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-wj0-x230.google.com with SMTP id xy5so6001829wjc.0; Tue, 13 Dec 2016 16:34:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cLJHsTtdEqaW3+fNMrFHwZ1gNVoD5TT9QA3HXXnwFMw=; b=dOwJdcb1CedKBW9Ea/w05pwZ8jeAw+aO4UlXN3foFQBNxmzR+BfYVISp+kD174/YwW C2KO3uF9fJN5ZkzB1+jnBLTSgww9arGNCRSkNa30hOLujxftvieMw2Ww6qBv7WqRBKKu 1jrn9bMgfpoNxWsOEIKK7FGO5Kbb6MGrHIV56YfNZQwZTXA/nSYU9jzQYDIhOW+0ot/S DzSnWVCSd0zg19xx+RmT4sHZzpBIAp1cEjxA3IGS9a1MafVpT3sJTtkRyrIKj9lcGWQB K559XDUrrm1W+5ewzI4fnxeySsDproRfmK2SCEZXrOUrsO5kP4X/gjHQUE7qKLI52eKj h9Lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=cLJHsTtdEqaW3+fNMrFHwZ1gNVoD5TT9QA3HXXnwFMw=; b=SBnCsvUzcTp+hAUveyZR/iVjfrvJDj2Cx/Aiu6x6ECXFiQFZz6lW1hZxFpEYL2jqQb btSRBFXnF/wWYYquDUddh7ZVbhp8qcYl9Zd7w1X4U5v/zZNI7NgOw+AaXnriD9vKH23T c4pC3iRZ6hoF/Oh1JYP3r9v0IDrtjrHfFtA+S3WR4V4NiEm73Q+v5LFsexub0YCmXsgb tjcKH6OjpJgrA0343mbNczymyzy1ERELjHi6oZs+Mfu3NbjE4xbpjfoxyLstEMv4Zv2x U/dlCp7mq2xqqdC5BqfpeyZgqUHaY2ofbXbNchlwX2rh/p/gTAEzeEcszTNCJiOYttc6 teRw== X-Gm-Message-State: AKaTC02+jagxljIXaeH34WthXYU29eXTugjCR/FCAMzVBqLJmojQDbTm4kfReTdXRgvTj2pvOS6+FZPlds2AtA== X-Received: by 10.28.29.23 with SMTP id d23mr4711170wmd.91.1481675645237; Tue, 13 Dec 2016 16:34:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.80.169.195 with HTTP; Tue, 13 Dec 2016 16:34:04 -0800 (PST) In-Reply-To: References: From: Adam Vande More Date: Tue, 13 Dec 2016 18:34:04 -0600 Message-ID: Subject: Re: Re-sparse a file-backed IO device + zfs To: javocado Cc: FreeBSD virtualization , FreeBSD Questions , FreeBSD Filesystems Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 14 Dec 2016 00:34:08 -0000 On Mon, Dec 12, 2016 at 7:20 PM, javocado wrote: > Hi, > > I'm setting up a bhyve wherein: > > host # truncate -s 1T vol.file > host # du -ah vol.file > 200K vol.file > > host # /usr/sbin/bhyve ... -s 4,ahci-hd,vol.file ... > > Then inside the bhyve I create a zpool (ada0 = vol.file): > > bhyve # zpool create -O devices=off -O atime=off -O compression=on -m > /mnt/data1 data1 ada0 > I think there used to be a utility called sparsify. -- Adam From owner-freebsd-virtualization@freebsd.org Wed Dec 14 03:03:49 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 086C8C7650C for ; Wed, 14 Dec 2016 03:03:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 EC1131507 for ; Wed, 14 Dec 2016 03:03:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uBE33me4025706 for ; Wed, 14 Dec 2016 03:03:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 213396] official FreeBSD vm image not runing on openstack Date: Wed, 14 Dec 2016 03:03:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: gjb@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: re@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: dependson 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-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 14 Dec 2016 03:03:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213396 Glen Barber changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |215258 Assignee|freebsd-virtualization@Free |re@FreeBSD.org |BSD.org | Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215258 [Bug 215258] Update openstack.conf options --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Wed Dec 14 11:46:59 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5F06C7690B for ; Wed, 14 Dec 2016 11:46:59 +0000 (UTC) (envelope-from ian.campbell@docker.com) Received: from mail-wj0-x22d.google.com (mail-wj0-x22d.google.com [IPv6:2a00:1450:400c:c01::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F90A17B0 for ; Wed, 14 Dec 2016 11:46:59 +0000 (UTC) (envelope-from ian.campbell@docker.com) Received: by mail-wj0-x22d.google.com with SMTP id tk12so29513363wjb.3 for ; Wed, 14 Dec 2016 03:46:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=docker.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=dGXF6PSFB1U/SOvvGDP/MDPlVEtOjKhlTBTh1qOchDI=; b=OSYaErF6p5Um0ltDI6Dh0Kihi0o2IirFGNVUNuLMLj1BFAFilI55JhFqUN0+XPo7BW zYHWSg4vNCNLxLp/xzOLUsTaYkSORAcJYQWR5jhfuDdTqT1ahJ4bToXtD9YDeHRT3BMT L74qVnsRzAoGtxMDGDPBZdqg9+BHk3XfZelkU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=dGXF6PSFB1U/SOvvGDP/MDPlVEtOjKhlTBTh1qOchDI=; b=f+jqCetH2IAm+VRIUZFaGdaxGGFDOQZi/Hy0ePHntcktcve9JzzKA++K1AjXu3kBl3 4ingqMW/1ZZhNKSBKQBcxFkVScH0ohMebkRswc33cyQQXNTb+eHGVXeHxca7Uq4NxoO1 n+LoNdwFk+8QqmVO118/C4e4H9lszuhzsDeJ/VU9tau9G2MfIMYLoHx+lORLBkkUN23r FqzmHqrSAKTbYQWoCBqGqOE+XGopc1YsjUn32q8VZD8ZSdKo8AKz0V0QPsh2El1FGhvo pWlJoESjX0ID7GAJ5ypG3b5ZlxwxSWsukWyZc0qfhaH/ExHIzttABZL/aMg94uOP9waG 1+ZQ== X-Gm-Message-State: AKaTC01tQqtMrFnewrUwJYk9E9wvPTXY/AG/GuPpKz2H5gp8+MTjjUaki5vajfrxn9eNV5DHAc8UNpfTbKVDtsfT X-Received: by 10.28.133.143 with SMTP id h137mr6556058wmd.58.1481716017211; Wed, 14 Dec 2016 03:46:57 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.107.231 with HTTP; Wed, 14 Dec 2016 03:46:56 -0800 (PST) In-Reply-To: <397B138D-3701-4FB4-A9B3-618CE2624C3C@freebsd.org> References: <631f775d-8d61-55ba-1e7b-8ce4fcadcbf3@freebsd.org> <397B138D-3701-4FB4-A9B3-618CE2624C3C@freebsd.org> From: Ian Campbell Date: Wed, 14 Dec 2016 11:46:56 +0000 Message-ID: Subject: Re: Query about bhyve's blockif_cancel and the signalling mechanisms To: Tycho Nightingale Cc: Peter Grehan , freebsd-virtualization@freebsd.org, Anil Madhavapeddy Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 14 Dec 2016 11:46:59 -0000 On 14 December 2016 at 00:05, Tycho Nightingale wrote: > On Dec 13, 2016, at 1:32 AM, Peter Grehan wrote: >>> I have a secondary concern which is what happens if the IO thread is >>> on its way to making a blocking system call in blockif_proc but has >>> not actually done so when the signal is delivered. It seems like it >>> would simply carry on and make the blocking call with perhaps >>> unexpected consequences (i/o getting wedged, perhaps only until a >>> second reset attempt). I've not actually seen this happening though >>> and there's a chance I'm simply over thinking things after staring at >>> them for so long! >> >> I believe this case is handled - I discussed this at length with Tycho w= hen the code was committed a while back. >> >> Tycho - any thoughts ? > > ahci_port_stop() is called under the protection the port soft-state lock = so that will stem any further requests from landing in the blockif queue. = That=E2=80=99s the easy case. > > As for blockif requests which are queued, those are simply completed. Th= e ones that are in-flight all have their status set to BST_BUSY when they a= re moved from the pending queue to the busy queue just prior to being sent = to blockif_proc(). It=E2=80=99s therefore possible that an in-flight reque= st (one on the busy list) has yet to call blockif_proc(), or is already ins= ide blockif_proc() or has just completed blockif_proc(). In all cases howe= ver BST_BUSY is cleared in blockif_complete(). The key is therefore that r= egardless of where the thread is, blockif_cancel() will continue to issue p= thread_kill() until the request reaches blockif_complete() =E2=80=94 breaki= ng it out of system calls as necessary. > > Does that make sense? Absolutely. Somehow I had read "while (be->be_status =3D=3D BST_BUSY)" as "if (...)", Thanks for setting me straight! Ian. From owner-freebsd-virtualization@freebsd.org Wed Dec 14 12:11:49 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6E743C779B8 for ; Wed, 14 Dec 2016 12:11:49 +0000 (UTC) (envelope-from ian.campbell@docker.com) Received: from mail-wj0-x22f.google.com (mail-wj0-x22f.google.com [IPv6:2a00:1450:400c:c01::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0A1EA1834 for ; Wed, 14 Dec 2016 12:11:49 +0000 (UTC) (envelope-from ian.campbell@docker.com) Received: by mail-wj0-x22f.google.com with SMTP id v7so30607202wjy.2 for ; Wed, 14 Dec 2016 04:11:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=docker.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fAcxnqxYSQ2Zj0U39FjBnB1caJ7EHUhBluTak8gyeEY=; b=EA6KL29T84VgmzsGsh6nEy2AZcHLQnexxNILsyYUhu+WrQifHtkF8IwYnGFZJopBgf Zt+NS/UMoP40HhKmZqkOq6bDZdffBDY2a4xAW66HkJOwsRdiumMGGbjUi/5XtjtPtNBB /+1dVeDDQwB/bftp2NRzl9jpZCvcouj0ihrbs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fAcxnqxYSQ2Zj0U39FjBnB1caJ7EHUhBluTak8gyeEY=; b=VrHV8eJl1NG5e/8lVhKZrjbEkTaTIRo6b8K2UuSBrEykeNKyUn8t16QHhSm/TssuWq QxMWnRTu7RtkGWW2ne7MYXcxsaAA7kQYpa34aXkaOmK23ujp2qVYv750/ZrwdKWxs1qk AvPtoKbDiEAzsIuCXpXQpn3pqlwQfs+zWREReQB2FCt3ahByXLLJnvaNCy/j5R/vDxAD Ti9K4pPl//l4WsUS+cZwyCZny+3c8jFSrhUeQvH6Y6Ad91Z0vE8/OorJEBzlYk0jomYC h+BTBlXESXhlwMeEvKN9ZXylk81VRrgoAcpzXuQ2Jx/2PKo1XufXDBVfL0DqzxZRKlG0 PNkQ== X-Gm-Message-State: AKaTC01DQ2UorCYr24HryJIFXaNTsmRFIh1jHFKzqTIB1i+QWS2RJLv0lj7CaHATccJEdWvVxjXEAO5RqpqWm+Ox X-Received: by 10.28.113.76 with SMTP id m73mr6630209wmc.114.1481717507201; Wed, 14 Dec 2016 04:11:47 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.107.231 with HTTP; Wed, 14 Dec 2016 04:11:46 -0800 (PST) In-Reply-To: <631f775d-8d61-55ba-1e7b-8ce4fcadcbf3@freebsd.org> References: <631f775d-8d61-55ba-1e7b-8ce4fcadcbf3@freebsd.org> From: Ian Campbell Date: Wed, 14 Dec 2016 12:11:46 +0000 Message-ID: Subject: Re: Query about bhyve's blockif_cancel and the signalling mechanisms To: Peter Grehan Cc: Tycho Nightingale , freebsd-virtualization@freebsd.org, Anil Madhavapeddy Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 14 Dec 2016 12:11:49 -0000 On 13 December 2016 at 06:32, Peter Grehan wrote: >> I've dug around in the FreeBSD kevent and signal man pages but I >> cannot find any part which describes anything of the semantics which >> bhyve seems to be relying on (which seems to be that the system call >> in the target thread will return EINTR at some point before the thread >> which is "handling" the signal via kevent/kqueue sees that event). >> >> Have I missed something here or is bhyve relying on some subtle >> underlying semantics? > > > I didn't think it too FreeBSD-specific - if a thread is blocked in a system > call, sending a signal should force it to exit on most Unices. Sure, the thing I was unsure about was whether that was the case when the application has asked for signal delivery via some other mechanism than the traditional asynchronous signal handlers such as kevent. Especially when the signal itself if SIG_IGN'd (as SIGCONT is in bhyve in blockif_init). The attached test tries to mimic what bhyve is doing, it has a blocked io thread and a thread handling kevents, with the signal set to SIG_IGN. A signal is then sent to the io thread. Running it on FreeBSD 11[0] it outputs: main: starting kevent thread main: starting io thread kevent thread: opening kqueue kevent thread: setting up SIGCONT event kevent thread: waiting for SIGCONT event io thread: blocking in read main: sending SIGCONT io thread main: waiting for io thread to complete kevent thread: received SIGCONT event and then blocks indefinitely. The kevent thread has seen the SIGCONT but the read in the io thread has not been interrupted. If I #define USE_HANDLER at the same time as USE_KEVENT then instead I see: main: starting kevent thread kevent thread: opening kqueue main: starting io thread kevent thread: setting up SIGCONT event io thread: blocking in read kevent thread: waiting for SIGCONT event main: sending SIGCONT io thread sigcont: received SIGCONT main: waiting for io thread to complete io thread: Read from pipe returned errno=4: Interrupted system call io thread: exiting main: waiting for kevent thread to complete kevent thread: received SIGCONT event main: all done i.e. the signal is seen by both the kevent thread and the async handler in the io thread, the latter of which causes EINTR from the read. bhyve sets SIGCONT to SIG_IGN so falls into the first case I think. If there is really a bhyve bug here I think it should be fixable with a dummy SIGCONT handler alongside the kevent thread. I think it wouldn't be reliant on a specific ordering of kevent vs async handler invocation due to the while loop on status == BUSY in blockif_cancel which Tycho opened my eyes to earlier. Ian. [0] ftp://ftp.freebsd.org/pub/FreeBSD/releases/VM-IMAGES/11.0-RELEASE/amd64/Latest/FreeBSD-11.0-RELEASE-amd64.qcow2.xz fed to virt-manager. From owner-freebsd-virtualization@freebsd.org Wed Dec 14 18:29:12 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F16D5C76782 for ; Wed, 14 Dec 2016 18:29:12 +0000 (UTC) (envelope-from pkubaj@anongoth.pl) Received: from anongoth.pl (anongoth.pl [88.156.79.165]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "anongoth.pl", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF199799 for ; Wed, 14 Dec 2016 18:29:11 +0000 (UTC) (envelope-from pkubaj@anongoth.pl) Received: from mail (unknown [127.0.1.10]) by anongoth.pl (Postfix) with ESMTP id D083BAF07 for ; Wed, 14 Dec 2016 19:19:21 +0100 (CET) X-Virus-Scanned: amavisd-new at anongoth.pl Received: from anongoth.pl ([127.0.1.10]) by mail (anongoth.pl [127.0.1.10]) (amavisd-new, port 10024) with LMTP id asTB91AqQ2Zy for ; Wed, 14 Dec 2016 19:19:10 +0100 (CET) Received: from anongoth.pl (unknown [46.248.161.165]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: pkubaj) by anongoth.pl (Postfix) with ESMTPSA id 83837AEFC for ; Wed, 14 Dec 2016 19:19:10 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=anongoth.pl; s=ANONGOTH; t=1481739550; bh=fzIinakNUtDMFa39tTiD+k9UhHRKeDgrIuLaqPFGM28=; h=Date:From:To:Subject; b=aNyteob+zB/dWPj9wDz/mfKlcXfMlzvRy1/gV2IxgykAgpxidRYht8+luYvJQUy2W T4pZ0sXuVkwQnec1H6rGL4bsAaTQx8JmSVFI3RaXGUQRtfzxM8g5tYsIzzUb8eQXmn dlVeGJeo+qkrak+d3WtxqCBoQ0+b8FNOxmMiHZaz7Mlxc786MI71IelXE/5Cm3aD5d rLX/oW8ibfuqGOUB26jvciNol5JdPzyyF3oAMcTLR3Yax5LUwKdkWgfPb9oH7vDZyX kCVRMq1bTCnx+tztbN5WWp4KFszDvInTeLR8c+o1CWw057veOy2yfVoO5OGwktEaR4 FbE7J0VVsSxyQ== Date: Wed, 14 Dec 2016 19:19:09 +0100 From: Piotr Kubaj To: freebsd-virtualization@freebsd.org Subject: Booting 9front on bhyve Message-ID: <20161214181909.GA20065@chujemuje> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 14 Dec 2016 18:29:13 -0000 Hi, I want to install 9front in bhyve. The only information I've found about 9front on bhyve is here: https://www.mail-archive.com/search?l=9fans@9fans.net&q=subject:%22Re%5C%3A+%5C%5B9fans%5C%5D+Plan+9+image+for+xhyve%5C%2Fbhyve+hypervisor%5C%2Fvm%5C%3F%22&o=newest&f=1 That's what I actually do - I boot 9front with UEFI enabled. The problem is that when booting with UEFI mode, 9front hangs on https://anongoth.pl/2016-12-14-191343_1920x1080_scrot.png When I enable CSM, I get further, but when I move my mouse, it only randomly moves in the VM (I set up ps2 type). Any idea on this? The OS is FreeBSD 11.0-RELEASE. Please CC, since I'm not subscribed to this list. -- ________________________________________ / Life is a sexually transferred disease \ \ with 100% mortality. / ---------------------------------------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || From owner-freebsd-virtualization@freebsd.org Wed Dec 14 22:32:41 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DD47AC80C41 for ; Wed, 14 Dec 2016 22:32:41 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 9F9F51D5E for ; Wed, 14 Dec 2016 22:32:41 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au [203.13.68.150]) by alto.onthenet.com.au (Postfix) with ESMTPS id 695A92126630 for ; Thu, 15 Dec 2016 08:32:16 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 64CED280A1F for ; Thu, 15 Dec 2016 08:32:16 +1000 (AEST) X-Amavis-Modified: Mail body modified (using disclaimer) - iredmail.onthenet.com.au Received: from iredmail.onthenet.com.au ([127.0.0.1]) by localhost (iredmail.onthenet.com.au [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id F2LTBriOFTMV for ; Thu, 15 Dec 2016 08:32:16 +1000 (AEST) Received: from Peters-MacBook-Pro-2.local (96-82-80-65-static.hfc.comcastbusiness.net [96.82.80.65]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id A4F732809F5; Thu, 15 Dec 2016 08:32:13 +1000 (AEST) Subject: Re: Booting 9front on bhyve To: Piotr Kubaj References: <20161214181909.GA20065@chujemuje> Cc: freebsd-virtualization@freebsd.org From: Peter Grehan Message-ID: <58c8124e-847b-3af9-eef0-faa27a45605a@freebsd.org> Date: Wed, 14 Dec 2016 14:32:29 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20161214181909.GA20065@chujemuje> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=YJDv8VOx c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=mwgbnDbW7alINpy3vhoKyg==:17 a=N659UExz7-8A:10 a=n5n_aSjo0skA:10 a=iVOYtHzJAAAA:8 a=QXwwpPy6wXrVDriAdysA:9 a=pILNOxqGKmIA:10 a=EttwhFvZ3FR2qAco_uTo:22 wl=host:3 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 14 Dec 2016 22:32:42 -0000 Hi Piotr, > That's what I actually do - I boot 9front with UEFI enabled. > > The problem is that when booting with UEFI mode, 9front hangs on > https://anongoth.pl/2016-12-14-191343_1920x1080_scrot.png I managed to get it to boot a bit further. The tip is to not hit return at the [vesa] line - enter any text and then hit return, and it will continue using the UEFI frame buffer. > When I enable CSM, I get further, but when I move my mouse, it only > randomly moves in the VM (I set up ps2 type). > > Any idea on this? Unfortunately hit the same issue on UEFI: the ps2 mouse is pretty much unusable :( later, Peter. From owner-freebsd-virtualization@freebsd.org Wed Dec 14 22:44:38 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A646C80F50 for ; Wed, 14 Dec 2016 22:44:38 +0000 (UTC) (envelope-from pkubaj@anongoth.pl) Received: from anongoth.pl (anongoth.pl [88.156.79.165]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "anongoth.pl", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 25E52620; Wed, 14 Dec 2016 22:44:38 +0000 (UTC) (envelope-from pkubaj@anongoth.pl) Received: from mail (unknown [127.0.1.10]) by anongoth.pl (Postfix) with ESMTP id BE786AFF3; Wed, 14 Dec 2016 23:44:34 +0100 (CET) X-Virus-Scanned: amavisd-new at anongoth.pl Received: from anongoth.pl ([127.0.1.10]) by mail (anongoth.pl [127.0.1.10]) (amavisd-new, port 10024) with LMTP id 3PY-tjXgvd-O; Wed, 14 Dec 2016 23:44:31 +0100 (CET) Received: from anongoth.pl (89-73-21-54.dynamic.chello.pl [89.73.21.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: pkubaj) by anongoth.pl (Postfix) with ESMTPSA id 0F78BAFE5; Wed, 14 Dec 2016 23:44:31 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=anongoth.pl; s=ANONGOTH; t=1481755471; bh=Ec3RqqZuSYX1T1xJ5ybS8ei2aQHaspCh6RXLTFWe1uU=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=iFeo/IV4JcLvOoq7b4p2kNRLd4D23SZ55jd31uSoB0l8+ot3O0H7r5raVJoHpmvCr r6qJCajXb0W2nwC5QxXvR5eFJ9GAB742T6k7hyR2qqACZVAaPOBr5fNhMassxXrFHt aj0jFadLIJHnFmgUeyFtMThopfwHSVooCfIX5QymWoyVHoELtBc4KuespWdbzj2E2x /2wacxLRiqVLtS/AzQdG7wlTGA2lmlEhHJuhtdUBHSvw8GRg9NUmRi0W59D1Z2l0SM LGaKJXG0vkptK71YxaqLGXrgjcvwfJCUo1JHBIkp4tbNCQggf/p7GRRgZneU5uEbgA KUyyh4pCkKozg== Date: Wed, 14 Dec 2016 23:44:29 +0100 From: Piotr Kubaj To: Peter Grehan Cc: freebsd-virtualization@freebsd.org Subject: Re: Booting 9front on bhyve Message-ID: <20161214224429.GA76434@DESKTOP1> References: <20161214181909.GA20065@chujemuje> <58c8124e-847b-3af9-eef0-faa27a45605a@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <58c8124e-847b-3af9-eef0-faa27a45605a@freebsd.org> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Wed, 14 Dec 2016 22:44:38 -0000 Is it possible to use other mouse drivers, ps2intellimouse etc.? On 16-12-14 14:32:29, Peter Grehan wrote: > Hi Piotr, > > > That's what I actually do - I boot 9front with UEFI enabled. > > > > The problem is that when booting with UEFI mode, 9front hangs on > > https://anongoth.pl/2016-12-14-191343_1920x1080_scrot.png > > I managed to get it to boot a bit further. The tip is to not hit return > at the [vesa] line - enter any text and then hit return, and it will > continue using the UEFI frame buffer. > > > When I enable CSM, I get further, but when I move my mouse, it only > > randomly moves in the VM (I set up ps2 type). > > > > Any idea on this? > > Unfortunately hit the same issue on UEFI: the ps2 mouse is pretty much > unusable :( > > later, > > Peter. -- ________________________________________ / A paranoid is a man who knows a little \ | of what's going on. | | | \ -- William S. Burroughs / ---------------------------------------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || From owner-freebsd-virtualization@freebsd.org Thu Dec 15 15:10:22 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 476EAC77396 for ; Thu, 15 Dec 2016 15:10:22 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A9BA0D86 for ; Thu, 15 Dec 2016 15:10:21 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from moby.local ([77.12.92.170]) by mail.gmx.com (mrgmx003 [212.227.17.184]) with ESMTPSA (Nemesis) id 0MCLx3-1cQaEJ0m9p-0098Ra for ; Thu, 15 Dec 2016 16:10:14 +0100 To: freebsd-virtualization@FreeBSD.org From: Nikos Vassiliadis Subject: VIMAGE VS virtualbox-kmod Message-ID: <8996da05-5f3e-dfe4-0555-76c77b86d3ee@gmx.com> Date: Thu, 15 Dec 2016 16:10:06 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:BR8Ay9ugx2SxcDH2HEV/7t8I6wmx41nmVMcMRn4zEzkIg41PxZM aohy0oWXGEz3Fc5NbKpR2Bg97mAyUjB9CnWsNnaEkQXTpM8EPBJD8mXSFAYR1PQkqPJCpcW D9o9RKuX+TH4Ctrdkabm8lCSnXquemXFsi3aFQTJDZ8hmxNeOWLKN4rxi9X+jJUlhl23okl vjZ1bV5BwWT8gqdbg8J3Q== X-UI-Out-Filterresults: notjunk:1;V01:K0:+Z0UiQ4U+A0=:laFk0r9IFgbNW1dfeWdf2t a0FloX5GZ6dWZOTViaZ9SLArrUVeYzM8bnMuqqTwBO6Giev9/ufS2Fch2xCs3mCN4DPrzhfyU 00iNFI41NQ1w7JFH56HWwlaiy59HN57OX3eNi2V43OrfYVM92Ox/1ktlZO0G9rTKbhwIq1VON Sm+IWKcw7/t/Te9SMmZ4HBptNZBbm8uHHHoOTvSAtb9dbj4AWNyxoV+LPyCoxId2SR3iqzr7B ennfZ5QBapg8zPeBApVaJZeLHVGxvv61GA5mXcQ/3dzFXi9sVV11WPcLevObLiZw+tos9roqx bu1Jw0EIkdD7btcA3BUw7z6VxCPxzhyPbSbDcUN9SaZEORH+e+1BAFlTxJ7fKfPczOepoqXBF 1kcQWiIrNBfZPp7+/KwxNLa9rlkvwOJ5xVxDgCu6Fj8efE8RglFU2cXVDlsq0RZmdnM0mn5GT iEr0u2jOtAWDaw9awuwGdHUssnDXePeZDqX69Ftvo2t+VjG5/UXoaaUWH9TeFpGyBgmbc6jE4 IqqCLbtCoslprqeDMTOk8nXAygIWthymG0y32zaPqokSPVtoh2hmWlPRdooS5Yexilh6/0EeJ CIY5RG0F0kGr/H2vp61pmVMfDvCQo8JrBcXqfO+Uf5kaQmjK9wnzIocb0w/Co7mD//cAUBM6n R/ISLwdbKs8uUghikeLAZvS7bz8ys9O/bIUSJifqyJokhKaGFnBAfWEe/f6gyJVZ10cnIF04J 6P+Ni3PK6v4KjvYDJW9CDVBbKrqjd8M8T7+sF/Knv0HinuNhlvl9PJfK8zBf7rFj+F4y1H7O0 V/TjkKl X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Dec 2016 15:10:22 -0000 Hi, From time to time I need to run VirtualBox, not often thanks to bhyve:), but the VirtualBox kernel module needs to be compiled when one uses a VIMAGE-enabled kernel. VirtualBox is quite big and that means several hours of compiling so I'd like to just "pkg install" it. My options are: 1) switch to a GENERIC kernel just to run VBox VMs or 2) compile VBox from ports for my VIMAGE-enabled kernel Does somebody else have a better solution? What other people do? TIA, Nikos PS It'd would be so good if we had a extra pkg for vbox-kmod with vnet support From owner-freebsd-virtualization@freebsd.org Thu Dec 15 15:13:31 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9ACCEC7755F for ; Thu, 15 Dec 2016 15:13:31 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:130:3ffc::401:25]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 603341094 for ; Thu, 15 Dec 2016 15:13:31 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 1BEF725D387C; Thu, 15 Dec 2016 15:13:21 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 6CEE4D1F8DA; Thu, 15 Dec 2016 15:13:20 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id M58tE37mMOkZ; Thu, 15 Dec 2016 15:13:19 +0000 (UTC) Received: from [10.248.108.210] (fresh-tun0-ula.sbone.de [IPv6:fde9:577b:c1a9:4920:2ef0:eeff:fe03:ee34]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 5BB9AD1F8D9; Thu, 15 Dec 2016 15:13:19 +0000 (UTC) From: "Bjoern A. Zeeb" To: "Nikos Vassiliadis" Cc: freebsd-virtualization@FreeBSD.org Subject: Re: VIMAGE VS virtualbox-kmod Date: Thu, 15 Dec 2016 15:13:17 +0000 Message-ID: In-Reply-To: <8996da05-5f3e-dfe4-0555-76c77b86d3ee@gmx.com> References: <8996da05-5f3e-dfe4-0555-76c77b86d3ee@gmx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Mailer: MailMate (2.0BETAr6069) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Dec 2016 15:13:31 -0000 On 15 Dec 2016, at 15:10, Nikos Vassiliadis wrote: > It'd would be so good if we had a extra pkg for vbox-kmod with > vnet support I think that’s your best solution. And possibly not just for vbox-kmod but for all networking kmods? /bz From owner-freebsd-virtualization@freebsd.org Fri Dec 16 00:08:53 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F07D3C8176C for ; Fri, 16 Dec 2016 00:08:53 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (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 D052F98F for ; Fri, 16 Dec 2016 00:08:53 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.88) (envelope-from ) id 1cHg4s-0003wA-Mv for freebsd-virtualization@freebsd.org; Thu, 15 Dec 2016 17:08:46 -0700 Date: Thu, 15 Dec 2016 17:08:46 -0700 From: The Doctor To: freebsd-virtualization@freebsd.org Subject: Debian 8 issue Message-ID: <20161216000846.GA14434@doctor.nl2k.ab.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 16 Dec 2016 00:08:54 -0000 I tried to install Debian 8 as a VM on FreeBSD 11 using the directions fro the Handbook and I get +---------------------+ Installing the base system +----------------------+ | | | 3% | | | | [ 956.283176] BUG: unable to handle kernel paging request at 0000000010020000| | [ 956.284449] IP: [] __blk_bios_map_sg+0x1de/0x400-------+ [ 956.285552] PGD 0 [ 956.285949] Oops: 0000 [#1] SMP [ 956.286578] Modules linked in: dm_mod md_mod xfs libcrc32c jfs crc32c_generic btrfs xor raid6_pq vfat fat ext4 crc16 mbcache jbd2 virtio_blk virtio_net virtio_pci virtio_ring virtio nls_utf8 isofs sg sr_mod cdrom ahci libahci libata scsi_mod [ 956.291000] CPU: 0 PID: 106 Comm: kworker/0:1H Not tainted 3.16.0-4-amd64 #1 Debian 3.16.36-1+deb8u1 [ 956.292578] Hardware name: BHYVE, BIOS 1.00 03/14/2014 [ 956.293501] Workqueue: kblockd blk_mq_run_work_fn [ 956.294347] task: ffff88013ab67370 ti: ffff88013ab68000 task.ti: ffff88013ab68000 [ 956.295642] RIP: 0010:[] [] __blk_bios_map_sg+0x1de/0x400 [ 956.297120] RSP: 0018:ffff88013ab6bcd8 EFLAGS: 00010206 [ 956.297977] RAX: 0000000010020000 RBX: 000000000001d000 RCX: 0000000000000004 [ 956.299122] RDX: 0000000010020001 RSI: ffffea000005b738 RDI: 0000000000000000 [ 956.300268] RBP: ffff88013ab6bd58 R08: ffff8800ad19cd20 R09: 0000000000000025 [ 956.301413] R10: 0000000000000000 R11: 0000000001a22000 R12: 0000000000000000 [ 956.302558] R13: 0000000000001000 R14: 0000000000000004 R15: ffff88013ab6bd68 [ 956.303704] FS: 0000000000000000(0000) GS:ffff88013fc00000(0000) knlGS:0000000000000000 [ 956.305008] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 956.305941] CR2: 0000000010020000 CR3: 000000013ab13000 CR4: 00000000000406f0 [ 956.307099] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 956.308254] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 956.309410] Stack: [ 956.309751] ffff88013ab6bc50 ffff8800ba23cda0 ffff8800ba6d5008 0100000000000010 [ 956.311048] ffff8800ad19cd20 ffff880000000025 0000000000000004 ffffea000005b738 [ 956.312405] 0000000000001000 ffffea000005b738 0000000000001000 ffff8800ba23cc00 [ 956.313693] Call Trace: [ 956.314107] [] ? blk_rq_map_sg+0x2f/0x170 [ 956.315030] [] ? virtio_queue_rq+0x9b/0x240 [virtio_blk] [ 956.316152] [] ? __blk_mq_run_hw_queue+0x1c2/0x320 [ 956.317190] [] ? process_one_work+0x143/0x430 [ 956.318163] [] ? worker_thread+0x113/0x4f0 [ 956.319097] [] ? __schedule+0x2b1/0x6f0 [ 956.319983] [] ? rescuer_thread+0x2d0/0x2d0 [ 956.320924] [] ? kthread+0xbd/0xe0 [ 956.321738] [] ? kthread_create_on_node+0x180/0x180 [ 956.322791] [] ? ret_from_fork+0x58/0x90 [ 956.323691] [] ? kthread_create_on_node+0x180/0x180 [ 956.324816] Code: 3f 44 89 4c 24 28 48 89 4c 24 30 e8 5d 5a 03 00 8b 7c 24 44 48 8b 74 24 38 4c 8b 44 24 20 44 8b 4c 24 28 48 8b 4c 24 30 49 89 07 <48> 8b 10 83 e2 03 40 f6 c6 03 0f 85 b2 01 00 00 48 09 f2 89 78 [ 956.329894] RIP [] __blk_bios_map_sg+0x1de/0x400 [ 956.331058] RSP [ 956.331741] CR2: 0000000010020000 [ 956.332497] ---[ end trace 834b995df25d6fd4 ]--- [ 956.333713] BUG: unable to handle kernel paging request at ffffffffffffffd8 [ 956.334913] IP: [] kthread_data+0xc/0x20 [ 956.335902] PGD 1816067 PUD 1818067 PMD 0 [ 956.336706] Oops: 0000 [#2] SMP [ 956.337341] Modules linked in: dm_mod md_mod xfs libcrc32c jfs crc32c_generic btrfs xor raid6_pq vfat fat ext4 crc16 mbcache jbd2 virtio_blk virtio_net virtio_pci virtio_ring virtio nls_utf8 isofs sg sr_mod cdrom ahci libahci libata scsi_mod [ 956.341845] CPU: 0 PID: 106 Comm: kworker/0:1H Tainted: G D 3.16.0-4-amd64 #1 Debian 3.16.36-1+deb8u1 [ 956.343644] Hardware name: BHYVE, BIOS 1.00 03/14/2014 [ 956.344619] task: ffff88013ab67370 ti: ffff88013ab68000 task.ti: ffff88013ab68000 [ 956.345921] RIP: 0010:[] [] kthread_data+0xc/0x20 [ 956.347333] RSP: 0018:ffff88013ab6b9f0 EFLAGS: 00010002 [ 956.348292] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000000000000c [ 956.349555] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff88013ab67370 [ 956.350810] RBP: ffff88013ab67370 R08: 0000000000000001 R09: 000000000000b981 [ 956.352072] R10: ffffffff81ae0408 R11: 0000000000000000 R12: ffff88013fc12f40 [ 956.353339] R13: 0000000000000000 R14: 0000000000000000 R15: ffff88013ab67370 [ 956.354578] FS: 0000000000000000(0000) GS:ffff88013fc00000(0000) knlGS:0000000000000000 [ 956.356015] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 956.357044] CR2: 0000000000000028 CR3: 00000000ba7d5000 CR4: 00000000000406f0 [ 956.358322] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 956.359605] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 956.360878] Stack: [ 956.361256] ffffffff8108373d ffff88013ab677d0 ffffffff81514abd 0000000000012f40 [ 956.362667] ffff88013ab6bfd8 0000000000012f40 ffff88013ab67370 ffff88013ab679f0 [ 956.364072] ffff88013ab676c8 ffff88013ab67360 ffff88013aebb2b0 ffff88013ab67360 [ 956.365480] Call Trace: [ 956.365936] [] ? wq_worker_sleeping+0xd/0x80 [ 956.366989] [] ? __schedule+0x43d/0x6f0 [ 956.367970] [] ? do_exit+0x6df/0xa70 [ 956.368899] [] ? oops_end+0x97/0xe0 [ 956.369806] [] ? no_context+0x2b2/0x2be [ 956.370786] [] ? __do_page_fault+0x80/0x4f0 [ 956.371828] [] ? virtqueue_add_sgs+0x350/0x5f7 [virtio_ring] [ 956.373128] [] ? cpumask_next_and+0x30/0x40 [ 956.374168] [] ? virtqueue_add_sgs+0x4ac/0x5f7 [virtio_ring] [ 956.375444] [] ? page_fault+0x28/0x30 [ 956.376394] [] ? __blk_bios_map_sg+0x1de/0x400 [ 956.377477] [] ? __blk_bios_map_sg+0x1c3/0x400 [ 956.378558] [] ? blk_rq_map_sg+0x2f/0x170 [ 956.379566] [] ? virtio_queue_rq+0x9b/0x240 [virtio_blk] [ 956.380800] [] ? __blk_mq_run_hw_queue+0x1c2/0x320 [ 956.381937] [] ? process_one_work+0x143/0x430 [ 956.382915] [] ? worker_thread+0x113/0x4f0 [ 956.383847] [] ? __schedule+0x2b1/0x6f0 [ 956.384728] [] ? rescuer_thread+0x2d0/0x2d0 [ 956.385670] [] ? kthread+0xbd/0xe0 [ 956.386489] [] ? kthread_create_on_node+0x180/0x180 [ 956.387543] [] ? ret_from_fork+0x58/0x90 [ 956.388443] [] ? kthread_create_on_node+0x180/0x180 [ 956.389489] Code: 08 04 00 00 48 8b 40 c8 48 c1 e8 02 83 e0 01 c3 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 8b 87 08 04 00 00 <48> 8b 40 d8 c3 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 0f [ 956.394034] RIP [] kthread_data+0xc/0x20 [ 956.394953] RSP [ 956.395522] CR2: ffffffffffffffd8 [ 956.396065] ---[ end trace 834b995df25d6fd5 ]--- [ 956.396809] Fixing recursive fault but reboot is needed! What could the issue be? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Merry Christmas 2016 and Happy New Year 2017 From owner-freebsd-virtualization@freebsd.org Fri Dec 16 06:02:23 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0844C822BB for ; Fri, 16 Dec 2016 06:02:23 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id B4D6B1EAB for ; Fri, 16 Dec 2016 06:02:23 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au [203.13.68.150]) by alto.onthenet.com.au (Postfix) with ESMTPS id 44CB7204044D for ; Fri, 16 Dec 2016 16:01:58 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 3F93F280999 for ; Fri, 16 Dec 2016 16:01:58 +1000 (AEST) X-Amavis-Modified: Mail body modified (using disclaimer) - iredmail.onthenet.com.au Received: from iredmail.onthenet.com.au ([127.0.0.1]) by localhost (iredmail.onthenet.com.au [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id zdNReFLvyD3v for ; Fri, 16 Dec 2016 16:01:58 +1000 (AEST) Received: from Peters-MacBook-Pro-2.local (c-67-180-92-13.hsd1.ca.comcast.net [67.180.92.13]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id C810A2808FF; Fri, 16 Dec 2016 16:01:55 +1000 (AEST) Subject: Re: Debian 8 issue To: The Doctor References: <20161216000846.GA14434@doctor.nl2k.ab.ca> Cc: freebsd-virtualization@freebsd.org From: Peter Grehan Message-ID: <16ce98df-e94b-aa5d-96cf-89169563da94@freebsd.org> Date: Thu, 15 Dec 2016 22:02:12 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20161216000846.GA14434@doctor.nl2k.ab.ca> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=YJDv8VOx c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=5eVCmCvhg37cu/pjidAGzw==:17 a=N659UExz7-8A:10 a=n5n_aSjo0skA:10 a=6I5d2MoRAAAA:8 a=7L0C7lOm3xTyugEVKFwA:9 a=pILNOxqGKmIA:10 a=IjZwj45LgO3ly-622nXo:22 wl=host:3 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 16 Dec 2016 06:02:24 -0000 Hi, > I tried to install Debian 8 as a VM on FreeBSD 11 using the directions fro the Handbook > > and I get ... > | [ 956.283176] BUG: unable to handle kernel paging request at 0000000010020000| | > What could the issue be? This has been brought up previously - see the thread starting at http://docs.FreeBSD.org/cgi/mid.cgi?5553E12F.50506 The workaround as mentioned in that thread is to either use ahci-hd for the disk emulation, or select 'Guided - use entire disk' with virtio-blk. later, Peter. From owner-freebsd-virtualization@freebsd.org Fri Dec 16 09:36:03 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5EE6C772E6 for ; Fri, 16 Dec 2016 09:36:03 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0151D16F6 for ; Fri, 16 Dec 2016 09:36:02 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from moby.local ([95.119.248.123]) by mail.gmx.com (mrgmx103 [212.227.17.174]) with ESMTPSA (Nemesis) id 0LfkJC-1cwtEJ2x7i-00pKCO; Fri, 16 Dec 2016 10:35:53 +0100 Subject: Re: VIMAGE VS virtualbox-kmod To: "Bjoern A. Zeeb" References: <8996da05-5f3e-dfe4-0555-76c77b86d3ee@gmx.com> Cc: freebsd-virtualization@FreeBSD.org From: Nikos Vassiliadis Message-ID: Date: Fri, 16 Dec 2016 10:35:52 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:sY9Q/QUuwHhtOZA0Nsqn2Yej1AONqgwpLN3AUDHoD3A/yCNPygP RMa5Jzh8S0VWmoKIIKHF/eWpg8xMoyR4fT11GyGfRvAYpW+p1+bUPkp38Zh4GIvhEJlTB3v c5c3jfyIzHwqlgh9vc8l3wo0L4pQ8fPV9w8+AKPqx8BS4bOGFmYo5HNbPx+ySabQhsoK3sj 3T+3Lvmhxawtx/ElIDCtA== X-UI-Out-Filterresults: notjunk:1;V01:K0:bXY5uT/BToM=:ckLsRMAX8MMKs1aL1MUmlX 1DdrTJ1LPPlCR7512DnOxbnosbgjMdGf5l3aq5AIJ4e5YZWQNF4BQFaD+xcziwz9T9eibXf1V tDjG4on31Br/PB9272I2RnsE16mWnYE8wphyDi1ugHdvUG3qRDZt1uQZkgEk9DSXyeNyBu2fE BjQqUInvtmRYL30AK8O34ml2MX0DNUYT5P6HPAixKe+D+jmfhGXycONHS2FatfMzhubicwXYE uiBs8jN6+ObGriTfFnPAILh0CsftYUU/dBajT2bBIPv4M4AMVDJrP3phGAQi6/H6Y/CYK6XlZ MDcQksbR6D0gBuPK8akKawy/GhQxMX67pyngoBWdQ9hIpRXXXrcDCnD8v6YODC0i0Y2RvDqND OFMjGr2ta6rEwTqGYt6uP+kkvvKRDMfpUrP/PlkRkqZwV0EGxBwz/WECzVWS1WbwJnJTrICDp fwojq+SdfKtVcCRd7ZIPPwkNYDPvsr8YfdQCjZ21TU+ZAQh8dnBRV3em3Hc2/54lbQRfstU3t NeQgOfgOMXCi3sw5IseJuu3Zy0qlNc4tp1BOrHYd8fay1Uj5Qvz9Tpxp+WYpDyy8oYLvSSE2N 024ejS7Feqkkc00ac9dEO6Tkion5D4Q7lQEPX2aXvhaT+qwk4DRhNx2rpP0LcDopHjBMHZYRl XUDQwMyNV4yoDBra3st7PN2u/9vbkYsKfkRH6L8Q7UyODEobHgoGmo4bdgf9NTWDLLYTYqZc5 orr034ZHvZZ5e44ycBzXibQ2nLwo7Sf3hAa7koaFVtxcMjtYbgPoHnWZI2xG/+xevFM6nWZwo 3LGnycw X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 16 Dec 2016 09:36:03 -0000 On 12/15/16 16:13, Bjoern A. Zeeb wrote: > On 15 Dec 2016, at 15:10, Nikos Vassiliadis wrote: > >> It'd would be so good if we had a extra pkg for vbox-kmod with >> vnet support > > I think that’s your best solution. And possibly not just for vbox-kmod > but for all networking kmods? I tried to create a new port for vbox: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215336 The more general task should be done by a person with actual knowledge of the ports' system. Best, Nikos From owner-freebsd-virtualization@freebsd.org Fri Dec 16 21:11:30 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 673DCC82BDA for ; Fri, 16 Dec 2016 21:11:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 566E0BE1 for ; Fri, 16 Dec 2016 21:11:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uBGLBTuN047606 for ; Fri, 16 Dec 2016 21:11:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 203682] Slow boot under VMware Fusion w/ UEFI firmware and SMP -- until APs are launched Date: Fri, 16 Dec 2016 21:11: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 Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 16 Dec 2016 21:11:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203682 --- Comment #9 from commit-hook@freebsd.org --- A commit references this bug: Author: jhb Date: Fri Dec 16 21:10:38 UTC 2016 New revision: 310177 URL: https://svnweb.freebsd.org/changeset/base/310177 Log: Enable EARLY_AP_STARTUP on amd64 and i386 kernels by default. PR: 199321, 203682 MFC after: 2 months Sponsored by: Netflix Changes: head/sys/amd64/conf/GENERIC head/sys/amd64/conf/MINIMAL head/sys/i386/conf/GENERIC --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Sat Dec 17 01:15:03 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3879BC82899 for ; Sat, 17 Dec 2016 01:15:03 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 060351B05 for ; Sat, 17 Dec 2016 01:15:03 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: by mail-pf0-x232.google.com with SMTP id c4so16417283pfb.1 for ; Fri, 16 Dec 2016 17:15:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:references:to:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=r6vCCjBqIDuly+Ynl6SUa9QA9tl4xQiBZ7wJL3RvmtI=; b=YBqfTv7VwMlK2Ac1qjhHLRrQKk0+PBvD5S5SOo5VWVk4MmCrdTz1fi/U7SWIe/8gFR FN/A3Qt1DAndAcDECWJ2nzwMt0g3JsnS++Q5Vq2im7Rh+abub5ZFv+DVcjlH9Zq2IsZz zmTVfGhj3hr5a4RXieQBX9p2NVCSKVgLR8I5fCTJHdGXkAOSO9MGIgjVqq2RJuCZFEVN km9ZVgl73yfKUic2tu2W9HDxAhFh+EoUkq3tST9qRmBcY6kHVUfTt8jKjwRrCbwY6aXW ruuonK9Ru0V9kXaju00m+tESO0Sse89X7w+E0ojKZKTIiQZ6ttAf4JJS1MPT1uskDOJz BOYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:to:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=r6vCCjBqIDuly+Ynl6SUa9QA9tl4xQiBZ7wJL3RvmtI=; b=HMgo3Di7Gqhaz8FisLF+KJJMCy39Qg2h2WERXkXV8h/9WFKYibHvJ9/tbR2aDrs8HY gbIWZzrWdgT80ZnYh4Jt9p6ukwbvhzRyHPCvjfjN3Fft/aP492cZVrXylaAbZpO1v0Y+ yDA8bkogOO5Bzx5JIiyxhoRbMA6CUPu8NqTgYam0oy8tSaD7YxlrGtRaibEb3+hYmLE5 J+wLxj5onz4hWcq/YM4TW482DweDE55KJtCgDcb8NVrKcJnEbK5/2c6ogZPM55/jJMPd camzzmlsPasCthxLUl3b5oVeNU9czJfNbSxalRBzWDgm3hsHqqh3DYYzjPc+ttOvocOp /m2w== X-Gm-Message-State: AIkVDXITeIKe5GHCE8i1/z7ged25fqAsLWBFt7Aay6N8qm10pfy4gZT5UyE/zi+CrQ80Qg== X-Received: by 10.84.215.137 with SMTP id l9mr6647476pli.21.1481937302334; Fri, 16 Dec 2016 17:15:02 -0800 (PST) Received: from [172.16.1.28] (c-73-155-87-64.hsd1.tx.comcast.net. [73.155.87.64]) by smtp.gmail.com with ESMTPSA id x2sm14370065pfx.65.2016.12.16.17.15.00 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Dec 2016 17:15:01 -0800 (PST) Subject: Re: Debian 8 CPU stall References: <9c9e83a5-16c6-0ab5-0ac4-af0a54430706@freebsd.org> <6cff5bf2-9654-8627-83c4-6ab48ee763b5@gmail.com> <56863fec-d8f8-2601-811f-511cd199e82f@freebsd.org> <131518ab-c3fc-6509-ba24-08b5c32cddd5@freebsd.org> To: freebsd-virtualization@FreeBSD.org From: Rajil Saraswat Message-ID: Date: Fri, 16 Dec 2016 19:14:18 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <131518ab-c3fc-6509-ba24-08b5c32cddd5@freebsd.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Sat, 17 Dec 2016 01:15:03 -0000 On 12/11/2016 11:11 AM, Peter Grehan wrote: > Hi Rajil, > >> I don't seem to have that sysctl on my system. Should i create one? > > It's there: > >> # sysctl -a |grep vmm > ... >> hw.vmm.vmx.cap.posted_interrupts: 1 >> hw.vmm.vmx.cap.virtual_interrupt_delivery: 1 > > The easiest way to disable APIC virtualization is to add this line to > /boot/loader.conf and reboot > > hw.vmm.vmx.use_apic_vid="0" > > (I got that wrong in the previous email; should have been zero) > > On a reboot, the above sysctl leaves should be set to 0. > > later, > > Peter. Hi Peter, This seems to have worked. Even after 5 days of uptime, i dont see the CPU stall messages. It looks like an issue with debian only as my other vm's based off ubuntu and centos did not have those errors. Thanks, Rajil From owner-freebsd-virtualization@freebsd.org Sat Dec 17 01:38:02 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AEB03C83C8A for ; Sat, 17 Dec 2016 01:38:02 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 6D3BED5C for ; Sat, 17 Dec 2016 01:38:02 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au [203.13.68.150]) by alto.onthenet.com.au (Postfix) with ESMTPS id 4E3C320AE98C for ; Sat, 17 Dec 2016 11:37:42 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 46DC52804EA for ; Sat, 17 Dec 2016 11:37:42 +1000 (AEST) X-Amavis-Modified: Mail body modified (using disclaimer) - iredmail.onthenet.com.au Received: from iredmail.onthenet.com.au ([127.0.0.1]) by localhost (iredmail.onthenet.com.au [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id mVy9pkIAS2a7 for ; Sat, 17 Dec 2016 11:37:42 +1000 (AEST) Received: from Peters-MacBook-Pro-2.local (96-82-80-65-static.hfc.comcastbusiness.net [96.82.80.65]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id 99EAB2804DF; Sat, 17 Dec 2016 11:37:40 +1000 (AEST) Subject: Re: Debian 8 CPU stall To: Rajil Saraswat References: <9c9e83a5-16c6-0ab5-0ac4-af0a54430706@freebsd.org> <6cff5bf2-9654-8627-83c4-6ab48ee763b5@gmail.com> <56863fec-d8f8-2601-811f-511cd199e82f@freebsd.org> <131518ab-c3fc-6509-ba24-08b5c32cddd5@freebsd.org> Cc: freebsd-virtualization@FreeBSD.org From: Peter Grehan Message-ID: <002b80bb-d56b-95b8-6249-cf46d0896441@freebsd.org> Date: Fri, 16 Dec 2016 17:37:54 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=YJDv8VOx c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=mwgbnDbW7alINpy3vhoKyg==:17 a=N659UExz7-8A:10 a=n5n_aSjo0skA:10 a=z-kaFTlq7YmkccKTkbAA:9 a=pILNOxqGKmIA:10 wl=host:3 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 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: Sat, 17 Dec 2016 01:38:02 -0000 Hi Rajil, > This seems to have worked. Even after 5 days of uptime, i dont see the > CPU stall messages. It looks like an issue with debian only as my other > vm's based off ubuntu and centos did not have those errors. Thanks very much for testing that out. The problem is certainly narrowed down a lot: Debian 8, single vCPU, APIC virtualization, with multiple PCI passthru ports. That will help a lot with debugging the issue. later, Peter.