From owner-freebsd-virtualization@freebsd.org Sun Jun 11 09:51:37 2017 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 D983FC7838A for ; Sun, 11 Jun 2017 09:51:37 +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 7828A856DC for ; Sun, 11 Jun 2017 09:51:37 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (mh0.gentlemail.de [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id v5B9pYMp079619; Sun, 11 Jun 2017 11:51:34 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 1CF20F76; Sun, 11 Jun 2017 11:51:34 +0200 (CEST) Message-ID: <593D1299.3030402@omnilan.de> Date: Sun, 11 Jun 2017 11:51:21 +0200 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: Anish CC: "freebsd-virtualization@freebsd.org" Subject: Re: PCIe passthrough really that expensive? References: <59383F5C.8020801@omnilan.de> <593A5AB1.7090301@omnilan.de> In-Reply-To: <593A5AB1.7090301@omnilan.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Sun, 11 Jun 2017 11:51:34 +0200 (CEST) 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 Jun 2017 09:51:37 -0000 Bezüglich Harry Schmalzbauer's Nachricht vom 09.06.2017 10:22 (localtime): > Bezüglich Anish's Nachricht vom 08.06.2017 14:35 (localtime): >> Hi Harry, >>> I thought I'd save these expensive VM_Exits by using the passthru path. >> Completely wrong, is it? >> >> It depends on which processor you are using. For example APICv was >> introduced in IvyBridge which enabled h/w assisted localAPIC rather than >> using s/w emulated, bhyve supports it on Intel processors. … > I'm still usign IvyBridge (E3v2) with this "new" machine, but haven't > ever heard/thought about APCIv! It seems APICv is available on IvyBridge-EP (Xeon E5/E7v2) only, not for E3v2 :-( Furthermore, if I didn't miss anything in the datasheets, no currently available E3 Xeon offers local APIC virtualization. Can somebody of the xperts confirm that? … >> Can you run a simple experiment, assign pptdev interrupts to core that's >> not running guest/vcpu? This will reduce #VMEXIT on vcpu which we know >> is expensive. > Interesting approach. But I have no idea how I should assign a PCIe > specific core to a PCIe dev. Is it pptdev specific? The tunables in > device.hints(5) can't be used for that, can they? I wasn't able to find out how to do that. Any hints highly appreciated! -harry From owner-freebsd-virtualization@freebsd.org Sun Jun 11 10:37:32 2017 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 41B6DC78CD3; Sun, 11 Jun 2017 10:37:32 +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 C5F4C9D2; Sun, 11 Jun 2017 10:37:31 +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 v5BAbTel080220; Sun, 11 Jun 2017 12:37:30 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id B8AD3F8F; Sun, 11 Jun 2017 12:37:29 +0200 (CEST) Message-ID: <593D1D5C.907@omnilan.de> Date: Sun, 11 Jun 2017 12:37:16 +0200 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-stable@freebsd.org, FreeBSD virtualization Subject: panic: Memory modified after free in zio_create, passthru in use [Was: 11.1-pre runtime Undefined symbol "xdr_accepted_reply" /lib/libc.so.7] References: <59369A15.2010901@omnilan.de> In-Reply-To: <59369A15.2010901@omnilan.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Sun, 11 Jun 2017 12:37:30 +0200 (CEST) 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 Jun 2017 10:37:32 -0000 Bezüglich Harry Schmalzbauer's Nachricht vom 06.06.2017 14:03 (localtime): > Hello, > > suddenly, I'm getting this error: > /lib/libc.so.7: Undefined symbol "xdr_accepted_reply" > > Very mysterious: It showed up on a running system, which worked > flawlessly for some hours. And that host has root-fs (/) mounted > readonly from a memorydisk. So to my understanding, it's completely > impossible that /lib/libc.so.7 is corrupted since last boot. > > I'm completely out of ideas what could cause this strange error during > "normal" operation. > > Normal operation in this case is serving as a bhyve test machine. > I first noticed that error after one guest - with passthru device > attached - was shut down. > > My suspicion is some undiscovered passthru interference... Since I > noticed one other _very_ strange passthru-effect: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215740 Hello, this time I caught a panic with a debuging kernel under 11.1-BETA1, which again occured after shuting down a VM which had ppt in use: cpuid = 5 KDB: stack backtrace: #0 0xffffffff805bf327 at kdb_backtrace+0x67 #1 0xffffffff8057f266 at vpanic+0x186 #2 0xffffffff8057f2e3 at panic+0x43 #3 0xffffffff8082eaeb at trash_ctor+0x4b #4 0xffffffff8082aaec at uma_zalloc_arg+0x52c #5 0xffffffff813b54a6 at zio_add_child+0x26 #6 0xffffffff813b5a05 at zio_create+0x385 #7 0xffffffff813b6de2 at zio_vdev_child_io+0x232 #8 0xffffffff81396be0 at vdev_mirror_io_start+0x370 #9 0xffffffff813bc629 at zio_vdev_io_start+0x4a9 #10 0xffffffff813b76bc at zio_execute+0x36c #11 0xffffffff813b6868 at zio_nowait+0xb8 #12 0xffffffff81396bec at vdev_mirror_io_start+0x37c #13 0xffffffff813bc383 at zio_vdev_io_start+0x203 #14 0xffffffff813b76bc at zio_execute+0x36c #15 0xffffffff805d10dd at taskqueue_run_locked+0x13d #16 0xffffffff805d1e78 at taskqueue_thread_loop+0x88 #17 0xffffffff80543844 at fork_exit+0x84 #0 doadump (textdump=) at pcpu.h:222 #1 0xffffffff8057ece0 in kern_reboot (howto=260) at /usr/local/share/deploy-tools/RELENG_11/src/sys/kern/kern_shutdown.c:366 #2 0xffffffff8057f2a0 in vpanic (fmt=, ap=) at /usr/local/share/deploy-tools/RELENG_11/src/sys/kern/kern_shutdown.c:759 #3 0xffffffff8057f2e3 in panic (fmt=) at /usr/local/share/deploy-tools/RELENG_11/src/sys/kern/kern_shutdown.c:690 #4 0xffffffff8082eaeb in trash_ctor (mem=, size=, arg=, flags=) at /usr/local/share/deploy-tools/RELENG_11/src/sys/vm/uma_dbg.c:80 #5 0xffffffff8082aaec in uma_zalloc_arg (zone=0xfffff8001febc680, udata=0xfffff8001ad5f340, flags=) at /usr/local/share/deploy-tools/RELENG_11/src/sys/vm/uma_core.c:2152 #6 0xffffffff813b54a6 in zio_add_child (pio=0xfffff8026f350b88, cio=0xfffff8002478b7b0) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:460 #7 0xffffffff813b5a05 in zio_create (pio=0xfffff8026f350b88, spa=, txg=433989, bp=, data=0xfffffe0058afa000, size=1024, type=, priority=ZIO_PRIORITY_ASYNC_WRITE, flags=, vd=, offset=, zb=, pipeline=) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:690 #8 0xffffffff813b6de2 in zio_vdev_child_io (pio=0xfffff8026f350b88, bp=, vd=, offset=325398016, data=, size=1024, type=, flags=1048704, done=) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1141 #9 0xffffffff81396be0 in vdev_mirror_io_start (zio=0xfffff8026f350b88) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_mirror.c:488 #10 0xffffffff813bc629 in zio_vdev_io_start (zio=0xfffff8026f350b88) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:3143 #11 0xffffffff813b76bc in zio_execute (zio=) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1681 #12 0xffffffff813b6868 in zio_nowait (zio=0xfffff8026f350b88) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1739 #13 0xffffffff81396bec in vdev_mirror_io_start (zio=0xfffff8026f7a7b88) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_mirror.c:488 #14 0xffffffff813bc383 in zio_vdev_io_start (zio=0xfffff8026f7a7b88) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:3021 #15 0xffffffff813b76bc in zio_execute (zio=) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1681 #16 0xffffffff805d10dd in taskqueue_run_locked (queue=0xfffff8001ab5a700) at /usr/local/share/deploy-tools/RELENG_11/src/sys/kern/subr_taskqueue.c:454 #17 0xffffffff805d1e78 in taskqueue_thread_loop (arg=) at /usr/local/share/deploy-tools/RELENG_11/src/sys/kern/subr_taskqueue.c:741 #18 0xffffffff80543844 in fork_exit (callout=0xffffffff805d1df0 , arg=0xfffff8001aa90720, frame=0xfffffe043f609ac0) at /usr/local/share/deploy-tools/RELENG_11/src/sys/kern/kern_fork.c:1042 #19 0xffffffff808598ae in fork_trampoline () at /usr/local/share/deploy-tools/RELENG_11/src/sys/amd64/amd64/exception.S:611 #20 0x0000000000000000 in ?? () This machine is usually rock solid, but shows most strange errors each time I utilize "passthru" with bhyve. Besides runngin a debug kernel, I don't know how to help tracking this down. I can imagine that above quoted PR and the unexplainable »lib/libc.so.7: Undefined symbol "xdr_accepted_reply"« error all have the same undiscovered cause, which shows up as soon as byhve and passtrhu are involved. Please, can anybody of the xperts add a comment? Thanks, -harry From owner-freebsd-virtualization@freebsd.org Sun Jun 11 10:56:48 2017 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 59E66C793C2 for ; Sun, 11 Jun 2017 10:56:48 +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 46BC0152E for ; Sun, 11 Jun 2017 10:56: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 v5BAumk4024447 for ; Sun, 11 Jun 2017 10:56:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 215740] [bhyve] utilizing passthru breaks raw device usage with virtio-blk | ahci-hd Date: Sun, 11 Jun 2017 10:56:48 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: bugzilla.freebsd@omnilan.de 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: Sun, 11 Jun 2017 10:56:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215740 --- Comment #7 from Harald Schmalzbauer --- Is there anybody who has checked whether the steps to reproduce show the reported results? Meaning, is there anybody who can confirm correct behavio= ur in that case? I observed many more, at first sight completely unrelated strange errors, b= ut all show up as soon as one condition is true: shutting down a bhyve-guest w= hich had ppt in use. Latest example: panic: Memory modified after free 0xfffff8002486a030(48) val=3D0 @ 0xfffff8002486a030 cpuid =3D 5 KDB: stack backtrace: #0 0xffffffff805bf327 at kdb_backtrace+0x67 #1 0xffffffff8057f266 at vpanic+0x186 #2 0xffffffff8057f2e3 at panic+0x43 #3 0xffffffff8082eaeb at trash_ctor+0x4b #4 0xffffffff8082aaec at uma_zalloc_arg+0x52c #5 0xffffffff813b54a6 at zio_add_child+0x26 #6 0xffffffff813b5a05 at zio_create+0x385 #7 0xffffffff813b6de2 at zio_vdev_child_io+0x232 #8 0xffffffff81396be0 at vdev_mirror_io_start+0x370 #9 0xffffffff813bc629 at zio_vdev_io_start+0x4a9 #10 0xffffffff813b76bc at zio_execute+0x36c #11 0xffffffff813b6868 at zio_nowait+0xb8 #12 0xffffffff81396bec at vdev_mirror_io_start+0x37c #13 0xffffffff813bc383 at zio_vdev_io_start+0x203 #14 0xffffffff813b76bc at zio_execute+0x36c #15 0xffffffff805d10dd at taskqueue_run_locked+0x13d #16 0xffffffff805d1e78 at taskqueue_thread_loop+0x88 #17 0xffffffff80543844 at fork_exit+0x84 #0 doadump (textdump=3D) at pcpu.h:222 #1 0xffffffff8057ece0 in kern_reboot (howto=3D260) at /usr/local/share/deploy-tools/RELENG_11/src/sys/kern/kern_shutdown.c:366 #2 0xffffffff8057f2a0 in vpanic (fmt=3D, ap=3D) at /usr/local/share/deploy-tools/RELENG_11/src/sys/kern/kern_shutdown.c= :759 #3 0xffffffff8057f2e3 in panic (fmt=3D) at /usr/local/share/deploy-tools/RELENG_11/src/sys/kern/kern_shutdown.c:690 #4 0xffffffff8082eaeb in trash_ctor (mem=3D, size=3D<= value optimized out>, arg=3D, flags=3D) at /usr/local/share/deploy-tools/RELENG_11/src/sys/vm/uma_dbg.c:80 #5 0xffffffff8082aaec in uma_zalloc_arg (zone=3D0xfffff8001febc680, udata=3D0xfffff8001ad5f340, flags=3D) at /usr/local/share/deploy-tools/RELENG_11/src/sys/vm/uma_core.c:2152 #6 0xffffffff813b54a6 in zio_add_child (pio=3D0xfffff8026f350b88, cio=3D0xfffff8002478b7b0) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/ut= s/common/fs/zfs/zio.c:460 #7 0xffffffff813b5a05 in zio_create (pio=3D0xfffff8026f350b88, spa=3D, txg=3D433989, bp=3D, data=3D0xfffffe00= 58afa000,=20 size=3D1024, type=3D, priority=3DZIO_PRIORITY_ASYN= C_WRITE, flags=3D, vd=3D,=20 offset=3D, zb=3D, pipeline=3D= ) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/ut= s/common/fs/zfs/zio.c:690 #8 0xffffffff813b6de2 in zio_vdev_child_io (pio=3D0xfffff8026f350b88, bp= =3D, vd=3D, offset=3D325398016,=20 data=3D, size=3D1024, type=3D, flags=3D1048704, done=3D) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/ut= s/common/fs/zfs/zio.c:1141 #9 0xffffffff81396be0 in vdev_mirror_io_start (zio=3D0xfffff8026f350b88) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/ut= s/common/fs/zfs/vdev_mirror.c:488 #10 0xffffffff813bc629 in zio_vdev_io_start (zio=3D0xfffff8026f350b88) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/ut= s/common/fs/zfs/zio.c:3143 #11 0xffffffff813b76bc in zio_execute (zio=3D) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/ut= s/common/fs/zfs/zio.c:1681 #12 0xffffffff813b6868 in zio_nowait (zio=3D0xfffff8026f350b88) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/ut= s/common/fs/zfs/zio.c:1739 #13 0xffffffff81396bec in vdev_mirror_io_start (zio=3D0xfffff8026f7a7b88) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/ut= s/common/fs/zfs/vdev_mirror.c:488 #14 0xffffffff813bc383 in zio_vdev_io_start (zio=3D0xfffff8026f7a7b88) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/ut= s/common/fs/zfs/zio.c:3021 #15 0xffffffff813b76bc in zio_execute (zio=3D) at /usr/local/share/deploy-tools/RELENG_11/src/sys/cddl/contrib/opensolaris/ut= s/common/fs/zfs/zio.c:1681 #16 0xffffffff805d10dd in taskqueue_run_locked (queue=3D0xfffff8001ab5a700)= at /usr/local/share/deploy-tools/RELENG_11/src/sys/kern/subr_taskqueue.c:454 #17 0xffffffff805d1e78 in taskqueue_thread_loop (arg=3D) at /usr/local/share/deploy-tools/RELENG_11/src/sys/kern/subr_taskqueue.c:741 #18 0xffffffff80543844 in fork_exit (callout=3D0xffffffff805d1df0 , arg=3D0xfffff8001aa90720, frame=3D0xfffffe043f609a= c0) at /usr/local/share/deploy-tools/RELENG_11/src/sys/kern/kern_fork.c:1042 #19 0xffffffff808598ae in fork_trampoline () at /usr/local/share/deploy-tools/RELENG_11/src/sys/amd64/amd64/exception.S:611 #20 0x0000000000000000 in ?? () I consider this as a severe problem, which shouldn't exist in 11.1-RELEASE. If nobody can prove my findings wrong, using passthru should be disabled in RELENG_11_1 until it can be ruled out as source of these strange problems (= some form of memory corruption). Thanks, -harry --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Sun Jun 11 21:00:09 2017 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 18227B949F9 for ; Sun, 11 Jun 2017 21:00:09 +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 E84C0765AA for ; Sun, 11 Jun 2017 21:00:08 +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 v5BL01wl064872 for ; Sun, 11 Jun 2017 21:00:08 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201706112100.v5BL01wl064872@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 Jun 2017 21:00:08 +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 Jun 2017 21:00:09 -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 | 212820 | FreeBSD 10-STABLE from latest HEAD and 11-RELEASE 1 problems total for which you should take action. From owner-freebsd-virtualization@freebsd.org Mon Jun 12 09:16:40 2017 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 DEC02BF7A13 for ; Mon, 12 Jun 2017 09:16:40 +0000 (UTC) (envelope-from vvelox@vvelox.net) Received: from vulpes.vvelox.net (vulpes.vvelox.net [96.95.67.25]) by mx1.freebsd.org (Postfix) with ESMTP id B498A3B80 for ; Mon, 12 Jun 2017 09:16:40 +0000 (UTC) (envelope-from vvelox@vvelox.net) Received: from vvelox.net (localhost [127.0.0.1]) (Authenticated sender: kitsune) by vulpes.vvelox.net (Postfix) with ESMTPA id C57832199DA7 for ; Mon, 12 Jun 2017 04:16:33 -0500 (CDT) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 12 Jun 2017 04:16:33 -0500 From: "Zane C. B-H." To: freebsd-virtualization@freebsd.org Subject: VNC stuff Message-ID: X-Sender: vvelox@vvelox.net User-Agent: Roundcube Webmail/1.3-beta 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 Jun 2017 09:16:41 -0000 Any idea when the RFB/VNC stuff is going to be hitting 11-STABLE if ever? From owner-freebsd-virtualization@freebsd.org Mon Jun 12 09:26:00 2017 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 090C6BF7E80 for ; Mon, 12 Jun 2017 09:26:00 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from mail-ot0-x229.google.com (mail-ot0-x229.google.com [IPv6:2607:f8b0:4003:c0f::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 C0C7864144 for ; Mon, 12 Jun 2017 09:25:59 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: by mail-ot0-x229.google.com with SMTP id k4so63322209otd.0 for ; Mon, 12 Jun 2017 02:25:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=c2GJTKkwAmjXIOCTqZzSeNd4g7X7mYwxvWgT45X5hr0=; b=KDhWjDYBgCWNDV9yPutbT+fXXWcV4wphkvo+TS2wDtwpc7P2GDrobUkRwr5Dn1OjAW q04L03DDmbIjSSvjCNrnZ3UDlM2Ybyu58ptOoMbR6++0/UNDvu9WO7L+mnDYSQKxsN/8 vndsLhQ/hM0tlV92CiU7TxyhRuZYC1Go2WFpamT0/iAwoX1yUAWlf5ugG5PnN9GLwhp3 +1ufLtGskVepTp+rM3fLPzSgYGos6kuVKlwF0KP1ZRPKhxLdOAtopmjweeViWPrCL5I2 Q/ElZ65nO4yY1J+uxse2Wds20e/cfDP8gaUciahFWuwakzzD9TNju+48Fnz5fU6vQ/mZ cUsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=c2GJTKkwAmjXIOCTqZzSeNd4g7X7mYwxvWgT45X5hr0=; b=XcrRPnNljDEoBKD+ajYZCbhy/0r5tRVl3rTH49f7PunznK+FfgPSBxAgp8Pre/Ocky aSD01iuLKL6KdJh/yMKmPNbAImUFs+ho2pmPvYLVwNZVVCbdtS+pNQ8idovXDJdFm0uV fb+lb+pph19VDZ21M/pZRuJ4QlWQcVRZ3blCpZCf0VRQe0Ko7ZeuND4pPTLwqiFFHQ7T AmZ2Tip186AnUAcXsIpRP7/79ynh65ou45VF4hOjYJr6AEMw82jC651bW7ovMezwUbQK kxyVS0o4lwD0q+aWPjrSVP/mpc7uh6oiDGo90+JQM6uO6Re+RMv1Uwutc0Idi/dYrJG3 x4Dg== X-Gm-Message-State: AKS2vOx4YScSIrLp1YA5SJCPKd18Ke05R+FaNH7YAMKbUXSGYZUcttlY P3Tt1u4dqVFOQJRT+0K+Lwzst06s9w== X-Received: by 10.157.14.137 with SMTP id 9mr18419330otj.208.1497259559002; Mon, 12 Jun 2017 02:25:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.48.71 with HTTP; Mon, 12 Jun 2017 02:25:58 -0700 (PDT) Reply-To: araujo@freebsd.org In-Reply-To: References: From: Marcelo Araujo Date: Mon, 12 Jun 2017 17:25:58 +0800 Message-ID: Subject: Re: VNC stuff To: "Zane C. B-H." Cc: freebsd-virtualization@freebsd.org 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: Mon, 12 Jun 2017 09:26:00 -0000 Hi Zane, Are you talking about the authentication? If yes, probably it will land there right after the RELEASE. Br, 2017-06-12 17:16 GMT+08:00 Zane C. B-H. : > Any idea when the RFB/VNC stuff is going to be hitting 11-STABLE if ever? > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubs > cribe@freebsd.org" > -- -- Marcelo Araujo (__)araujo@FreeBSD.org \\\'',)http://www.FreeBSD.org \/ \ ^ Power To Server. .\. /_) From owner-freebsd-virtualization@freebsd.org Mon Jun 12 09:40:51 2017 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 1003EBF81D9; Mon, 12 Jun 2017 09:40:51 +0000 (UTC) (envelope-from v.velox@vvelox.net) Received: from vulpes.vvelox.net (vulpes.vvelox.net [96.95.67.25]) by mx1.freebsd.org (Postfix) with ESMTP id E8BDA64664; Mon, 12 Jun 2017 09:40:50 +0000 (UTC) (envelope-from v.velox@vvelox.net) Received: from vvelox.net (localhost [127.0.0.1]) (Authenticated sender: kitsune) by vulpes.vvelox.net (Postfix) with ESMTPA id AB9792199E77; Mon, 12 Jun 2017 04:40:48 -0500 (CDT) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 12 Jun 2017 04:40:48 -0500 From: "Zane C. B-H." To: araujo@freebsd.org Cc: freebsd-virtualization@freebsd.org, owner-freebsd-virtualization@freebsd.org Subject: Re: VNC stuff In-Reply-To: References: Message-ID: X-Sender: v.velox@vvelox.net User-Agent: Roundcube Webmail/1.3-beta 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 Jun 2017 09:40:51 -0000 Hoi! I assume that means the VNC/fbuf stuff as well? Not seeing that that currently in 11-STABLE. Thanks. :) On 2017-06-12 04:25, Marcelo Araujo wrote: > Hi Zane, > > Are you talking about the authentication? > If yes, probably it will land there right after the RELEASE. > > > Br, > > 2017-06-12 17:16 GMT+08:00 Zane C. B-H. : > >> Any idea when the RFB/VNC stuff is going to be hitting 11-STABLE if >> ever? From owner-freebsd-virtualization@freebsd.org Mon Jun 12 14:49:35 2017 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 6DE9ABFDFF2 for ; Mon, 12 Jun 2017 14:49:35 +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 2C92771F4B for ; Mon, 12 Jun 2017 14:49:34 +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 EF81320ADBE0 for ; Tue, 13 Jun 2017 00:39:31 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id E3040281233 for ; Tue, 13 Jun 2017 00:39:31 +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 uMGSwCUWHon9 for ; Tue, 13 Jun 2017 00:39:31 +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 447BC2804DF; Tue, 13 Jun 2017 00:39:29 +1000 (AEST) Subject: Re: VNC stuff To: "Zane C. B-H." Cc: araujo@freebsd.org, owner-freebsd-virtualization@freebsd.org, freebsd-virtualization@freebsd.org References: From: Peter Grehan Message-ID: Date: Mon, 12 Jun 2017 07:39:25 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=XKlAcUpE c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=5eVCmCvhg37cu/pjidAGzw==:17 a=IkcTkHD0fZMA:10 a=LWSFodeU3zMA:10 a=6I5d2MoRAAAA:8 a=7dGCqm2WSGaXWDJ6Hn8A:9 a=QEXdDO2ut3YA: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: Mon, 12 Jun 2017 14:49:35 -0000 Hi Zane, > I assume that means the VNC/fbuf stuff as well? Not seeing that that > currently in 11-STABLE. Sure you don't mean 10-STABLE ? The uefi graphics code was committed 11 months ago: https://svnweb.freebsd.org/base/stable/11/usr.sbin/bhyve/pci_fbuf.c?view=log later, Peter. From owner-freebsd-virtualization@freebsd.org Mon Jun 12 17:24:40 2017 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 82B24C08C2A for ; Mon, 12 Jun 2017 17:24:40 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 0D5E177045; Mon, 12 Jun 2017 17:24:39 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id v5CGvvH3052365; Mon, 12 Jun 2017 09:57:57 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id v5CGvvq2052364; Mon, 12 Jun 2017 09:57:57 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201706121657.v5CGvvq2052364@pdx.rh.CN85.dnsmgr.net> Subject: Re: VNC stuff In-Reply-To: To: Peter Grehan Date: Mon, 12 Jun 2017 09:57:57 -0700 (PDT) CC: "Zane C. B-H." , freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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 Jun 2017 17:24:40 -0000 Hello Peter, and others, > Hi Zane, > > > I assume that means the VNC/fbuf stuff as well? Not seeing that that > > currently in 11-STABLE. > > Sure you don't mean 10-STABLE ? The uefi graphics code was committed > 11 months ago: > > > https://svnweb.freebsd.org/base/stable/11/usr.sbin/bhyve/pci_fbuf.c?view=log > > later, Do we want the VNC/Auth fix (once cleaned up for Coverty issues) in the 11.1 release? Doesnt this allow a lot more clients to connect to the fb? Or is it only a few clients that are being pendandic about using a questionable authentication means? > Peter. Cheers, -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Mon Jun 12 17:30:13 2017 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 B13C3C08CF7; Mon, 12 Jun 2017 17:30:13 +0000 (UTC) (envelope-from v.velox@vvelox.net) Received: from vulpes.vvelox.net (vulpes.vvelox.net [96.95.67.25]) by mx1.freebsd.org (Postfix) with ESMTP id 932F57722F; Mon, 12 Jun 2017 17:30:13 +0000 (UTC) (envelope-from v.velox@vvelox.net) Received: from vvelox.net (localhost [127.0.0.1]) (Authenticated sender: kitsune) by vulpes.vvelox.net (Postfix) with ESMTPA id E76292199EA5; Mon, 12 Jun 2017 12:30:11 -0500 (CDT) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 12 Jun 2017 12:30:11 -0500 From: "Zane C. B-H." To: Peter Grehan Cc: araujo@freebsd.org, owner-freebsd-virtualization@freebsd.org, freebsd-virtualization@freebsd.org Subject: Re: VNC stuff In-Reply-To: References: Message-ID: <8a797ee3bd6eca4c959815cea777ca1f@vvelox.net> X-Sender: v.velox@vvelox.net User-Agent: Roundcube Webmail/1.3-beta 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 Jun 2017 17:30:13 -0000 On 2017-06-12 09:39, Peter Grehan wrote: > Hi Zane, > >> I assume that means the VNC/fbuf stuff as well? Not seeing that that >> currently in 11-STABLE. > > Sure you don't mean 10-STABLE ? The uefi graphics code was committed > 11 months ago: > > > https://svnweb.freebsd.org/base/stable/11/usr.sbin/bhyve/pci_fbuf.c?view=log Hmm... interesting. Not seeing that at all mentioned in the man for bhyve. Yeah, now that you mention it, I am seeing the file there. From owner-freebsd-virtualization@freebsd.org Mon Jun 12 18:10:48 2017 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 B33C4C097A9 for ; Mon, 12 Jun 2017 18:10:48 +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 72629788CF for ; Mon, 12 Jun 2017 18:10:48 +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 AEBDF2040938 for ; Tue, 13 Jun 2017 04:10:46 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id A1BB8280996 for ; Tue, 13 Jun 2017 04:10:46 +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 j14CFr01AJHa for ; Tue, 13 Jun 2017 04:10:46 +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 9B4E02804DF; Tue, 13 Jun 2017 04:10:44 +1000 (AEST) Subject: Re: VNC stuff To: "Rodney W. Grimes" Cc: "Zane C. B-H." , freebsd-virtualization@freebsd.org References: <201706121657.v5CGvvq2052364@pdx.rh.CN85.dnsmgr.net> From: Peter Grehan Message-ID: <6c78dc09-bfa1-71fa-65cf-7963e100a550@freebsd.org> Date: Mon, 12 Jun 2017 11:10:42 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <201706121657.v5CGvvq2052364@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=XKlAcUpE c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=mwgbnDbW7alINpy3vhoKyg==:17 a=IkcTkHD0fZMA:10 a=LWSFodeU3zMA:10 a=QTjg61UZKFFiYHvOU78A:9 a=QEXdDO2ut3YA: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: Mon, 12 Jun 2017 18:10:48 -0000 Hi Rod, > Do we want the VNC/Auth fix (once cleaned up for Coverty issues) in > the 11.1 release? > > Doesnt this allow a lot more clients to connect to the fb? > > Or is it only a few clients that are being pendandic about > using a questionable authentication means? The main one is the OSX built-in client where vnc-auth is mandatory, but that also requires rfb version 3.3 support in the bhyve server (admittedly minor, but probably not in time for 11.1). later, Peter. From owner-freebsd-virtualization@freebsd.org Mon Jun 12 21:52:27 2017 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 2C732C792C7 for ; Mon, 12 Jun 2017 21:52:27 +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 C192181378 for ; Mon, 12 Jun 2017 21:52:26 +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 v5CLqPxF014687 for ; Mon, 12 Jun 2017 23:52:25 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id E6E086EB; Mon, 12 Jun 2017 23:52:24 +0200 (CEST) Message-ID: <593F0D0C.6080901@omnilan.de> Date: Mon, 12 Jun 2017 23:52:12 +0200 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: Re: VNC stuff References: <8a797ee3bd6eca4c959815cea777ca1f@vvelox.net> In-Reply-To: <8a797ee3bd6eca4c959815cea777ca1f@vvelox.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Mon, 12 Jun 2017 23:52:25 +0200 (CEST) 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: Mon, 12 Jun 2017 21:52:27 -0000 Bezüglich Zane C. B-H.'s Nachricht vom 12.06.2017 19:30 (localtime): > On 2017-06-12 09:39, Peter Grehan wrote: >> Hi Zane, >> >>> I assume that means the VNC/fbuf stuff as well? Not seeing that that >>> currently in 11-STABLE. >> >> Sure you don't mean 10-STABLE ? The uefi graphics code was committed >> 11 months ago: >> >> >> https://svnweb.freebsd.org/base/stable/11/usr.sbin/bhyve/pci_fbuf.c?view=log >> > > Hmm... interesting. Not seeing that at all mentioned in the man for > bhyve. True. MFCing r302504-317777 for usr.sbin/bhyve/bhyve.8 would document the precious bhyve(8) development progress for upcoming 11.1 users. -harry From owner-freebsd-virtualization@freebsd.org Tue Jun 13 01:02:09 2017 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 9FD82D880F6 for ; Tue, 13 Jun 2017 01:02:09 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 6A2882438 for ; Tue, 13 Jun 2017 01:02:08 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id v5D127R9053950; Mon, 12 Jun 2017 18:02:07 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id v5D125Xm053949; Mon, 12 Jun 2017 18:02:05 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201706130102.v5D125Xm053949@pdx.rh.CN85.dnsmgr.net> Subject: Re: VNC stuff In-Reply-To: <593F0D0C.6080901@omnilan.de> To: Harry Schmalzbauer Date: Mon, 12 Jun 2017 18:02:05 -0700 (PDT) CC: freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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 Jun 2017 01:02:09 -0000 [ Charset ISO-8859-1 unsupported, converting... ] > Bez?glich Zane C. B-H.'s Nachricht vom 12.06.2017 19:30 (localtime): > > On 2017-06-12 09:39, Peter Grehan wrote: > >> Hi Zane, > >> > >>> I assume that means the VNC/fbuf stuff as well? Not seeing that that > >>> currently in 11-STABLE. > >> > >> Sure you don't mean 10-STABLE ? The uefi graphics code was committed > >> 11 months ago: > >> > >> > >> https://svnweb.freebsd.org/base/stable/11/usr.sbin/bhyve/pci_fbuf.c?view=log > >> > > > > Hmm... interesting. Not seeing that at all mentioned in the man for > > bhyve. > > True. > MFCing r302504-317777 for usr.sbin/bhyve/bhyve.8 would document the > precious bhyve(8) development progress for upcoming 11.1 users. I think you meant r302504,r317777. r302504 is not likely to be MFC'ed at this time, this is the e1000 driver and man page. This code has known issues at this time and is an action item list on the bhyve developers work list. r317777 should be MFC'ed asap. Peter, could you please do an RFa to re@ to have R317777 MFC'ed? We have 3 days left before 11.1B2. If you want me to follow up on that just send me back a direct mentor approval and I'll do the RE and MFC work to get this in tree. If you think we should go ahead and pull the usable, but known problematic E1000 driver over mention that as well. Thanks, -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Tue Jun 13 04:13:18 2017 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 B63C5D8D01A for ; Tue, 13 Jun 2017 04:13:18 +0000 (UTC) (envelope-from akgupt3@gmail.com) Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (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 7E023684B8 for ; Tue, 13 Jun 2017 04:13:18 +0000 (UTC) (envelope-from akgupt3@gmail.com) Received: by mail-qt0-x22c.google.com with SMTP id u19so154605125qta.3 for ; Mon, 12 Jun 2017 21:13:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/AUGoSxDfv7u4+EoYLuGdNnjus2Cwg88M+/g7yBlhvE=; b=JWImGfApiIEP5r/Zmt9EzfcUXsx1SjaJtoSR8YfcmtqL85QfipYCwpIhDo/ttu3+a4 q87y0ROldKQEBDy/vqO3VVD+kGSythAY4e9ywYmi6GpsX05k3+Qjo5/qGtAdzml7XtFM tc3p3QQoTfONO6NqyWyLLypUmUyhFiXo+N6ZAuhaqFXy4Y5zcdX0l1eTTnqH7xDnn32/ fRuoHeRSKW7iRN6mzH00oMkrodQt4y8ND6J3VebHYjZXI4IU8ROVwB2c+QlEWGhZ2pN1 cm+zbNEq8tspyIPsd1qKHHBW1xCbKiVVDjH4Abg2Dix2mbazKiNTEsmDEOBGY/0LXXF4 s+MA== 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=/AUGoSxDfv7u4+EoYLuGdNnjus2Cwg88M+/g7yBlhvE=; b=dWYyMPe9lmkGWPyJZIBJAVB4prHjMZ7QjJOz9bT1dVK4yabVVlA2C/2pPJt/2lO3eR VPEBRvvzG+MQ7OzTjhELiS6FUgMRkLKsM4znGhV9RAtMDnEH6yb9gmE4/2ZO8txauGHm EZw2IOCo9VcevkVMmnTCgpZaavIlvUJOEjvwn6vIbCMM/SNrk8u3+64WQr8H914Faphq jSGjZen+jwcUPK2YopR715e58n/XcQtc2SZnmXvvqSpq2gwBvis9KR//epx3I/80PMJW VF8bsPyDNMOcjMBYnGJAsO7neFVsdbvkdQoZ1MPFz7oJf4/TmIyGHp2oPr4o9W61K8Z3 Rozw== X-Gm-Message-State: AODbwcAgLhqQ8uI3X/2gkVOkyoTf1d4IbRzMVzDXSVXXmz3dv3k0Fu6v Axqs/gfTJ3XSCupTti4hwqshqcY+qBWK X-Received: by 10.237.43.227 with SMTP id e90mr55732359qtd.103.1497327197432; Mon, 12 Jun 2017 21:13:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.181.203 with HTTP; Mon, 12 Jun 2017 21:13:16 -0700 (PDT) In-Reply-To: <593D1299.3030402@omnilan.de> References: <59383F5C.8020801@omnilan.de> <593A5AB1.7090301@omnilan.de> <593D1299.3030402@omnilan.de> From: Anish Date: Mon, 12 Jun 2017 21:13:16 -0700 Message-ID: Subject: Re: PCIe passthrough really that expensive? To: Harry Schmalzbauer Cc: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 Jun 2017 04:13:18 -0000 Hi Harry, >Any hints highly appreciated! In my setup, I have dual port Intel GigE, one assigned to host and other one is used by guest root@svmhost:~ # pciconf -l |grep ppt ... ppt2@pci0:2:0:0: class=3D0x020000 card=3D0x125e8086 chip=3D0x105e8086 rev= =3D0x06 hdr=3D0x00 root@svmhost:~ # This show up as 'em0' in BSD guest with 2 vcpus. root@bsdguest:~ # pciconf -l |grep em0 em0@pci0:0:21:0: class=3D0x020000 card=3D0x125e8086 chip=3D0x105e808= 6 rev=3D0x06 hdr=3D0x00 root@bsdguest:~ # Once guest is booted, ppt2 will claim interrupt resources, in this case just 1 interrupt line #265 root@svmhost:~ # vmstat -i interrupt total rate ... irq263: em0:irq0 1028705 634 .. irq265: ppt2 1041187 641 Total 2835121 1747 Now use cpuset to route IRQ#265 to say core 0 $cpuset -l 0 -x 265 Again use cpuset to force VM[PID 1222] to run on all core except #0 root@svmhost:~ # ps PID TT STAT TIME COMMAND .... 1222 1 I+ 5:59.45 bhyve: vm1 (bhyve) VM can run on all cores except #0. $ cpuset -l 1-3 -p 1222 You can monitor guest due to interrupts using $root@svmhost:~ # bhyvectl --get-stats --vm=3D --cpu=3D | gr= ep external vm exits due to external interrupt 27273 root@svmhost:~ # Regards, Anish On Sun, Jun 11, 2017 at 2:51 AM, Harry Schmalzbauer wrote: > Bez=C3=BCglich Harry Schmalzbauer's Nachricht vom 09.06.2017 10:22 (loca= ltime): > > Bez=C3=BCglich Anish's Nachricht vom 08.06.2017 14:35 (localtime): > >> Hi Harry, > >>> I thought I'd save these expensive VM_Exits by using the passthru pat= h. > >> Completely wrong, is it? > >> > >> It depends on which processor you are using. For example APICv was > >> introduced in IvyBridge which enabled h/w assisted localAPIC rather th= an > >> using s/w emulated, bhyve supports it on Intel processors. > =E2=80=A6 > > I'm still usign IvyBridge (E3v2) with this "new" machine, but haven't > > ever heard/thought about APCIv! > > It seems APICv is available on IvyBridge-EP (Xeon E5/E7v2) only, not for > E3v2 :-( > Furthermore, if I didn't miss anything in the datasheets, no currently > available E3 Xeon offers local APIC virtualization. Can somebody of the > xperts confirm that? > > > =E2=80=A6 > >> Can you run a simple experiment, assign pptdev interrupts to core that= 's > >> not running guest/vcpu? This will reduce #VMEXIT on vcpu which we know > >> is expensive. > > Interesting approach. But I have no idea how I should assign a PCIe > > specific core to a PCIe dev. Is it pptdev specific? The tunables in > > device.hints(5) can't be used for that, can they? > > I wasn't able to find out how to do that. > Any hints highly appreciated! > > -harry > > From owner-freebsd-virtualization@freebsd.org Tue Jun 13 04:39:55 2017 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 1A06FD8D5B6 for ; Tue, 13 Jun 2017 04:39:55 +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 CDF8E68C54 for ; Tue, 13 Jun 2017 04:39:54 +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 41DFB2052E01 for ; Tue, 13 Jun 2017 14:39:52 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 3A834280A04 for ; Tue, 13 Jun 2017 14:39:52 +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 jndT5Vj4xYRi for ; Tue, 13 Jun 2017 14:39:52 +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 9E5A6280983; Tue, 13 Jun 2017 14:39:49 +1000 (AEST) Subject: Re: VNC stuff To: "Rodney W. Grimes" Cc: freebsd-virtualization@freebsd.org References: <201706130102.v5D125Xm053949@pdx.rh.CN85.dnsmgr.net> From: Peter Grehan Message-ID: Date: Mon, 12 Jun 2017 21:39:48 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <201706130102.v5D125Xm053949@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=XKlAcUpE c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=5eVCmCvhg37cu/pjidAGzw==:17 a=IkcTkHD0fZMA:10 a=LWSFodeU3zMA:10 a=PUo0EWuEPL4cjm240qoA:9 a=QEXdDO2ut3YA: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 Jun 2017 04:39:55 -0000 Hi Rod, > r302504 is not likely to be MFC'ed at this time, this is the e1000 driver > and man page. This code has known issues at this time and is an action > item list on the bhyve developers work list. The e1000 driver was MFC'd 11 months ago. The issues are currently only with Windows - it works fine with Linux/*BSD/Solaris. I'm hoping that the Windows issue can be fixed before 11.1. > Peter, could you please do an RFa to re@ to have R317777 MFC'ed? We > have 3 days left before 11.1B2. If you want me to follow up on that > just send me back a direct mentor approval and I'll do the RE and > MFC work to get this in tree. I'll get in touch offline on this. later, Peter. From owner-freebsd-virtualization@freebsd.org Tue Jun 13 08:01:45 2017 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 51E46B95076 for ; Tue, 13 Jun 2017 08:01:45 +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 E268671F02 for ; Tue, 13 Jun 2017 08:01:44 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [78.138.80.135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id v5D81f8R028738; Tue, 13 Jun 2017 10:01:41 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id D49E38F2; Tue, 13 Jun 2017 10:01:40 +0200 (CEST) Message-ID: <593F9BD7.4010308@omnilan.de> Date: Tue, 13 Jun 2017 10:01:27 +0200 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: "Rodney W. Grimes" CC: freebsd-virtualization@freebsd.org Subject: Re: VNC stuff References: <201706130102.v5D125Xm053949@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <201706130102.v5D125Xm053949@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Greylist: ACL 129 matched, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [78.138.80.130]); Tue, 13 Jun 2017 10:01:41 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: 78.138.80.135; 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: Tue, 13 Jun 2017 08:01:45 -0000 Bezüglich Rodney W. Grimes's Nachricht vom 13.06.2017 03:02 (localtime): > [ Charset ISO-8859-1 unsupported, converting... ] >> Bez?glich Zane C. B-H.'s Nachricht vom 12.06.2017 19:30 (localtime): >>> On 2017-06-12 09:39, Peter Grehan wrote: >>>> Hi Zane, >>>> >>>>> I assume that means the VNC/fbuf stuff as well? Not seeing that that >>>>> currently in 11-STABLE. >>>> >>>> Sure you don't mean 10-STABLE ? The uefi graphics code was committed >>>> 11 months ago: >>>> >>>> >>>> https://svnweb.freebsd.org/base/stable/11/usr.sbin/bhyve/pci_fbuf.c?view=log >>>> >>> >>> Hmm... interesting. Not seeing that at all mentioned in the man for >>> bhyve. >> >> True. >> MFCing r302504-317777 for usr.sbin/bhyve/bhyve.8 would document the >> precious bhyve(8) development progress for upcoming 11.1 users. > > I think you meant r302504,r317777. > > r302504 is not likely to be MFC'ed at this time, this is the e1000 driver > and man page. This code has known issues at this time and is an action > item list on the bhyve developers work list. I can confirm that the 302504 MFC (r304424) works with BSD guests. Also the man page correctly was included in the MFC – my fault. But I just checked these, which needs MFC: 307517,314342,316357,317545 and the already mentioned > r317777 should be MFC'ed asap. Thanks, -harry From owner-freebsd-virtualization@freebsd.org Tue Jun 13 08:06:59 2017 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 23BEEB952C4 for ; Tue, 13 Jun 2017 08:06:59 +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 AFFDD720E7; Tue, 13 Jun 2017 08:06:58 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [78.138.80.135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id v5D86uTg028848; Tue, 13 Jun 2017 10:06:56 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id A29448F8; Tue, 13 Jun 2017 10:06:56 +0200 (CEST) Message-ID: <593F9D13.6040604@omnilan.de> Date: Tue, 13 Jun 2017 10:06:43 +0200 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: Peter Grehan CC: "Rodney W. Grimes" , freebsd-virtualization@freebsd.org Subject: Re: VNC stuff References: <201706130102.v5D125Xm053949@pdx.rh.CN85.dnsmgr.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: ACL 129 matched, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [78.138.80.130]); Tue, 13 Jun 2017 10:06:56 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: 78.138.80.135; 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: Tue, 13 Jun 2017 08:06:59 -0000 Bezüglich Peter Grehan's Nachricht vom 13.06.2017 06:39 (localtime): > Hi Rod, > >> r302504 is not likely to be MFC'ed at this time, this is the e1000 >> driver >> and man page. This code has known issues at this time and is an action >> item list on the bhyve developers work list. > > The e1000 driver was MFC'd 11 months ago. The issues are currently > only with Windows - it works fine with Linux/*BSD/Solaris. I'm hoping > that the Windows issue can be fixed before 11.1. While we're at issues: virtio-net as one unresolved: [bhyve] utilizing virtio-net truncates jumbo frames at 4084 bytes length https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215737 Most likely this won't be able to fix in time for 11.1, but I wanted to point out, since users depending on jumbo frame to/from the guest, are forced to use the e1000, and if there are problems with different guests, there's no more option left for them. Thanks, -harry From owner-freebsd-virtualization@freebsd.org Tue Jun 13 16:30:38 2017 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 DB358BF8FF2 for ; Tue, 13 Jun 2017 16:30:38 +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 7A63F823C5 for ; Tue, 13 Jun 2017 16:30:38 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (mh0.gentlemail.de [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id v5DGUaHZ043080; Tue, 13 Jun 2017 18:30:36 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id CC04BB3A; Tue, 13 Jun 2017 18:30:35 +0200 (CEST) Message-ID: <5940131E.8020604@omnilan.de> Date: Tue, 13 Jun 2017 18:30:22 +0200 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: Anish CC: "freebsd-virtualization@freebsd.org" Subject: Re: PCIe passthrough really that expensive? References: <59383F5C.8020801@omnilan.de> <593A5AB1.7090301@omnilan.de> <593D1299.3030402@omnilan.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Tue, 13 Jun 2017 18:30:36 +0200 (CEST) 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: Tue, 13 Jun 2017 16:30:38 -0000 Bezüglich Anish's Nachricht vom 13.06.2017 06:13 (localtime): > Hi Harry, >>Any hints highly appreciated! … > > Now use cpuset to route IRQ#265 to say core 0 > > $cpuset -l 0 -x 265 > > Again use cpuset to force VM[PID 1222] to run on all core except #0 > > root@svmhost:~ # ps > > PID TT STAT TIME COMMAND > > .... > > 1222 1 I+ 5:59.45 bhyve: vm1 (bhyve) > > > VM can run on all cores except #0. > > $ cpuset -l 1-3 -p 1222 > > > You can monitor guest due to interrupts using > > $root@svmhost:~ # bhyvectl --get-stats --vm= --cpu= | > grep external > > vm exits due to external interrupt 27273 > > root@svmhost:~ # Thank you very much for that detailed explanation. I didn't thought that cpuset(1) could also pin IRQ (handlers?) to specific cpus. In my case, I couldn't get a noticable difference. Since I have hyperthreading enabled on a single-socket quad core, I pinned cpu2+3 to the bhyve pid (2vCPUs) and for testing copied two times the same 8GB file ofer NFS, while having ppt's IRQ handler pinned to CPU1, CPU4, CPU3 and CPU2. So two times different hostCPUs than guest uses and two times the same. I couldn't see any load nor performance difference and similar 'vm exits due to external interrupt' count groth. To name numbers: 1st CPU had about 40k "vm exits due to external interrupt" per 8GP transfer, the other vCPU ~160k "vm exits due to external interrupt". Like mentioned, different host-CPU-pinning didn't influence that noticable. Thanks four this lesson! -harry From owner-freebsd-virtualization@freebsd.org Tue Jun 13 20:45:02 2017 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 1E251BFE426 for ; Tue, 13 Jun 2017 20:45:02 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 EB543677F6 for ; Tue, 13 Jun 2017 20:45:01 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id v5DKj0b4058057; Tue, 13 Jun 2017 13:45:00 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id v5DKixjb058056; Tue, 13 Jun 2017 13:44:59 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201706132044.v5DKixjb058056@pdx.rh.CN85.dnsmgr.net> Subject: Re: VNC stuff In-Reply-To: <593F9BD7.4010308@omnilan.de> To: Harry Schmalzbauer Date: Tue, 13 Jun 2017 13:44:59 -0700 (PDT) CC: freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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 Jun 2017 20:45:02 -0000 [ Charset windows-1252 unsupported, converting... ] > Bez?glich Rodney W. Grimes's Nachricht vom 13.06.2017 03:02 (localtime): > > [ Charset ISO-8859-1 unsupported, converting... ] > >> Bez?glich Zane C. B-H.'s Nachricht vom 12.06.2017 19:30 (localtime): > >>> On 2017-06-12 09:39, Peter Grehan wrote: > >>>> Hi Zane, > >>>> > >>>>> I assume that means the VNC/fbuf stuff as well? Not seeing that that > >>>>> currently in 11-STABLE. > >>>> > >>>> Sure you don't mean 10-STABLE ? The uefi graphics code was committed > >>>> 11 months ago: > >>>> > >>>> > >>>> https://svnweb.freebsd.org/base/stable/11/usr.sbin/bhyve/pci_fbuf.c?view=log > >>>> > >>> > >>> Hmm... interesting. Not seeing that at all mentioned in the man for > >>> bhyve. > >> > >> True. > >> MFCing r302504-317777 for usr.sbin/bhyve/bhyve.8 would document the > >> precious bhyve(8) development progress for upcoming 11.1 users. > > > > I think you meant r302504,r317777. > > > > r302504 is not likely to be MFC'ed at this time, this is the e1000 driver > > and man page. This code has known issues at this time and is an action > > item list on the bhyve developers work list. > > I can confirm that the 302504 MFC (r304424) works with BSD guests. > Also the man page correctly was included in the MFC ? my fault. > > But I just checked these, which needs MFC: > 307517,314342,316357,317545 and the already mentioned > > > r317777 should be MFC'ed asap. I have this sitting ready for MFC commit, waiting on mentor approval from grehan, and then to re@ for frozen -stable merge approval -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Tue Jun 13 22:40:41 2017 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 6CCE5C0838B for ; Tue, 13 Jun 2017 22:40:41 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 48E6C6ECD1 for ; Tue, 13 Jun 2017 22:40:40 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id v5DMedE0058623; Tue, 13 Jun 2017 15:40:39 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id v5DMedF6058622; Tue, 13 Jun 2017 15:40:39 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201706132240.v5DMedF6058622@pdx.rh.CN85.dnsmgr.net> Subject: Re: VNC stuff In-Reply-To: <593F9BD7.4010308@omnilan.de> To: Harry Schmalzbauer Date: Tue, 13 Jun 2017 15:40:39 -0700 (PDT) CC: freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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 Jun 2017 22:40:41 -0000 > Bez?glich Rodney W. Grimes's Nachricht vom 13.06.2017 03:02 (localtime): > > [ Charset ISO-8859-1 unsupported, converting... ] > >> Bez?glich Zane C. B-H.'s Nachricht vom 12.06.2017 19:30 (localtime): > >>> On 2017-06-12 09:39, Peter Grehan wrote: > >>>> Hi Zane, > >>>> > >>>>> I assume that means the VNC/fbuf stuff as well? Not seeing that that > >>>>> currently in 11-STABLE. > >>>> > >>>> Sure you don't mean 10-STABLE ? The uefi graphics code was committed > >>>> 11 months ago: > >>>> > >>>> > >>>> https://svnweb.freebsd.org/base/stable/11/usr.sbin/bhyve/pci_fbuf.c?view=log > >>>> > >>> > >>> Hmm... interesting. Not seeing that at all mentioned in the man for > >>> bhyve. > >> > >> True. > >> MFCing r302504-317777 for usr.sbin/bhyve/bhyve.8 would document the > >> precious bhyve(8) development progress for upcoming 11.1 users. > > > > I think you meant r302504,r317777. > > > > r302504 is not likely to be MFC'ed at this time, this is the e1000 driver > > and man page. This code has known issues at this time and is an action > > item list on the bhyve developers work list. > > I can confirm that the 302504 MFC (r304424) works with BSD guests. > Also the man page correctly was included in the MFC ? my fault. > > But I just checked these, which needs MFC: > 307517,314342,316357,317545 and the already mentioned > > > r317777 should be MFC'ed asap. These 5 are now merged to 11-stable. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Wed Jun 14 00:41:43 2017 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 6D5D4C0AA43 for ; Wed, 14 Jun 2017 00:41:43 +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 5BB01728F0 for ; Wed, 14 Jun 2017 00:41:43 +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 v5E0fhbK046035 for ; Wed, 14 Jun 2017 00:41:43 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 219973] [Hyper-V] storvsc message appears on Gen2 vm Date: Wed, 14 Jun 2017 00:41:43 +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 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: 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 Jun 2017 00:41:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219973 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- 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 Wed Jun 14 10:54:22 2017 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 F2E05D8AD86 for ; Wed, 14 Jun 2017 10:54:21 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (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 B65A382FA3 for ; Wed, 14 Jun 2017 10:54:21 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dL5wJ-000KRY-TA for freebsd-virtualization@freebsd.org; Wed, 14 Jun 2017 11:54:19 +0100 Date: Wed, 14 Jun 2017 11:54:19 +0100 From: Gary Palmer To: freebsd-virtualization@freebsd.org Subject: VBox 5 getting window height wrong Message-ID: <20170614105419.GB74033@in-addr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false 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 Jun 2017 10:54:22 -0000 Hi, Ever since upgrading from vbox 4 (which had occasional window placement or size issues, but nothing serious), vbox 5 has consistently had a problem where on starting a VM the window height is always reset to a fraction of what it should be. If I size the window properly by hand, and then select View -> Adjust Window Size it goes back to the wrong size again. Anyone else seen this? With Win10 it's worse - unless I maximise the window it keeps getting reset to the wrong height, I think by communication with the additions installed in the client. virtualbox-ose-5.1.22_1 General-purpose full virtualizer for x86 hardware virtualbox-ose-kmod-5.1.22 VirtualBox kernel module for FreeBSD 10.3-RELEASE-p18 Thanks, Gary P.S. Please keep me on CC as I am not subscribed to this list From owner-freebsd-virtualization@freebsd.org Thu Jun 15 11:08:25 2017 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 1B46FD87762 for ; Thu, 15 Jun 2017 11:08:25 +0000 (UTC) (envelope-from tetragir@fastmail.fm) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (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 D3F9C715DB; Thu, 15 Jun 2017 11:08:24 +0000 (UTC) (envelope-from tetragir@fastmail.fm) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 8291420A33; Thu, 15 Jun 2017 07:08:23 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 15 Jun 2017 07:08:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=Nyl+x6+79sW5hPxluD lzs1iZVV9C6GznweQK8L7PTB0=; b=EbcZu3US4541DtrUmtRPbTkAQOO871yRCE T75JEHNLkpx0VGU/LdliuG+/CFKGwq9Rm+Ma0Sp42x9+93cZmsw3syc0bKLj49dI +wkyuj24Jh1C/D8i0dbQYcULDmmzccYXmMWSuQYc8WaTKzuKTIwgksOP9vq7UH1Q YDp/1Y6U6W/GR+WE+hhPl+OBMwzccXTdUrB1G00M8stFKF24um6+JoY++OG5JNRc htoVHvbC+y3OZRTMJb924csFVXE65EIgYo9ZnM1E6+zekw8ZWE4nwQvjQYwEiDYt fcqa+xxMO9aLVb7i8D+OtKLtGPrplfen1wOyf5f4suZkPvIjCL7Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=Nyl+x6+79sW5hPxluDlzs1iZVV9C6GznweQK8L7PTB0=; b=IPNCrsYG g02kCxozUQ7pIT6zfV8LXpYltdiSDxpRlXPEw4rvI6WGZbJPyXtEFmw+HX/pI4/k TrjaFw1JhkP3fTCgeHpmTNJrgj/m6bRk3NSVEwRcyXLzJtX+GUs/JyEgie8PyYH4 SBTTm5hxTebQmfiq+Z8lJgKCNNpGb63a39G6YVo6W0rTeZvifhXZD03owN9c9cTf bmfaTgIto2GqCL0k4m44POv5gOaf5nzvohGaF82yr/VK/AJS4V4kX8nzm/fAZnGi YG9GxldGCa0uYavXGDa60Eka5G5r+Jck3CHEm1MZMqpFGTlT9/9mYo08R9Phrw+f G3odtywhJ7exnA== X-ME-Sender: X-Sasl-enc: ngzv1yvS6Z9GyFDF/+lK8Az93oLxKbK5B44QI6wqaPnx 1497524902 Received: from repa.tetragir.local (hsvpn23b.hotsplots.net [176.74.57.165]) by mail.messagingengine.com (Postfix) with ESMTPA id 79C747E800; Thu, 15 Jun 2017 07:08:22 -0400 (EDT) Message-ID: <1497524900.6640.1.camel@fastmail.fm> Subject: Re: VBox 5 getting window height wrong From: Daniel Tihanyi To: freebsd-virtualization@freebsd.org Cc: Gary Palmer Date: Thu, 15 Jun 2017 13:08:20 +0200 In-Reply-To: <20170614105419.GB74033@in-addr.com> References: <20170614105419.GB74033@in-addr.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6 (3.22.6-2.fc25) Mime-Version: 1.0 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: Thu, 15 Jun 2017 11:08:25 -0000 Hi, Do you have the right version of Guest Additions installed on your guests? I also have Windows 10 as a VM in VirtualBox (though it's FreeBSD 11), but it works for me without any problems. Daniel Tihanyi On Wed, 2017-06-14 at 11:54 +0100, Gary Palmer wrote: > Hi, > > Ever since upgrading from vbox 4 (which had occasional window placement > or size issues, but nothing serious), vbox 5 has consistently had a problem > where on starting a VM the window height is always reset to a fraction of > what it should be. If I size the window properly by hand, and then select > View -> Adjust Window Size it goes back to the wrong size again. > > Anyone else seen this? > > With Win10 it's worse - unless I maximise the window it keeps getting reset > to the wrong height, I think by communication with the additions installed > in the client. > > virtualbox-ose-5.1.22_1 General-purpose full virtualizer for x86 hardware > virtualbox-ose-kmod-5.1.22 VirtualBox kernel module for FreeBSD > > 10.3-RELEASE-p18 > > Thanks, > > Gary > > P.S. Please keep me on CC as I am not subscribed to this list > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" From owner-freebsd-virtualization@freebsd.org Thu Jun 15 15:01:55 2017 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 6B941D8C240 for ; Thu, 15 Jun 2017 15:01:55 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (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 37134781A7; Thu, 15 Jun 2017 15:01:55 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dLWHQ-00026l-44; Thu, 15 Jun 2017 16:01:52 +0100 Date: Thu, 15 Jun 2017 16:01:51 +0100 From: Gary Palmer To: Daniel Tihanyi Cc: freebsd-virtualization@freebsd.org, vbox@freebsd.org Subject: Re: VBox 5 getting window height wrong Message-ID: <20170615150151.GC74033@in-addr.com> References: <20170614105419.GB74033@in-addr.com> <1497524900.6640.1.camel@fastmail.fm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1497524900.6640.1.camel@fastmail.fm> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false 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 Jun 2017 15:01:55 -0000 [ add cc of vbox@freebsd.org which is a better list for this I think ] Hi, Updating to the correct Guest Additions doesn't fix the issue. Whether GA is installed or not doesn't seem to make much difference to this problem I've also changed from QT4 (which I was using) to QT5 with no change Thanks, Gary On Thu, Jun 15, 2017 at 01:08:20PM +0200, Daniel Tihanyi wrote: > Hi, > > Do you have the right version of Guest Additions installed on your > guests? I also have Windows 10 as a VM in VirtualBox (though it's > FreeBSD 11), but it works for me without any problems. > > Daniel Tihanyi > > On Wed, 2017-06-14 at 11:54 +0100, Gary Palmer wrote: > > Hi, > > > > Ever since upgrading from vbox 4 (which had occasional window placement > > or size issues, but nothing serious), vbox 5 has consistently had a problem > > where on starting a VM the window height is always reset to a fraction of > > what it should be. If I size the window properly by hand, and then select > > View -> Adjust Window Size it goes back to the wrong size again. > > > > Anyone else seen this? > > > > With Win10 it's worse - unless I maximise the window it keeps getting reset > > to the wrong height, I think by communication with the additions installed > > in the client. > > > > virtualbox-ose-5.1.22_1 General-purpose full virtualizer for x86 hardware > > virtualbox-ose-kmod-5.1.22 VirtualBox kernel module for FreeBSD > > > > 10.3-RELEASE-p18 > > > > Thanks, > > > > Gary > > > > P.S. Please keep me on CC as I am not subscribed to this list > > _______________________________________________ > > freebsd-virtualization@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" > From owner-freebsd-virtualization@freebsd.org Thu Jun 15 15:59:32 2017 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 9243CD8D11C for ; Thu, 15 Jun 2017 15:59:32 +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 7F51D79F3E for ; Thu, 15 Jun 2017 15:59:32 +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 v5FFxV37064505 for ; Thu, 15 Jun 2017 15:59:32 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 213814] AWS/EC2: no egress traffic stats on ixv(4) xn(4) Date: Thu, 15 Jun 2017 15:59:31 +0000 X-Bugzilla-Reason: CC 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: IntelNetworking, needs-qa, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jeffrey.e.pieper@intel.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? X-Bugzilla-Changed-Fields: cc 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: Thu, 15 Jun 2017 15:59:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213814 Jeff Pieper changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffrey.e.pieper@intel.com --- Comment #12 from Jeff Pieper --- This is fixed in https://reviews.freebsd.org/D11058 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Thu Jun 15 16:16:59 2017 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 D1BE5D8D623 for ; Thu, 15 Jun 2017 16:16:59 +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 BF0CD7A97E for ; Thu, 15 Jun 2017 16:16:59 +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 v5FGGwQW026594 for ; Thu, 15 Jun 2017 16:16:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 219672] vmxnet3: with LRO enabled under FreeBSD 11 as a router, outgoing speed of forwarded traffic becomes slower Date: Thu, 15 Jun 2017 16:16:59 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mp@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: Thu, 15 Jun 2017 16:16:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219672 --- Comment #5 from Mark Peek --- Maxim, were you able to run the experiments, discuss with the pfSense team, and/or confirm the conclusions I added in comment #3? Just looking to see if this bug (and the linked VMware bug) can be closed out. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Thu Jun 15 17:05:07 2017 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 75E03D8E273 for ; Thu, 15 Jun 2017 17:05:07 +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 1590E7C083 for ; Thu, 15 Jun 2017 17:05:06 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (mh0.gentlemail.de [78.138.80.135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id v5FH54cS084167; Thu, 15 Jun 2017 19:05:04 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id A087E193; Thu, 15 Jun 2017 19:05:04 +0200 (CEST) Message-ID: <5942BE33.1040003@omnilan.de> Date: Thu, 15 Jun 2017 19:04:51 +0200 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: "Rodney W. Grimes" CC: freebsd-virtualization@freebsd.org Subject: bhyve.8 referencing non-existing vmm.4 [Was: Re: VNC stuff] References: <201706132240.v5DMedF6058622@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <201706132240.v5DMedF6058622@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Greylist: ACL 129 matched, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [78.138.80.130]); Thu, 15 Jun 2017 19:05:05 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: 78.138.80.135; 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: Thu, 15 Jun 2017 17:05:07 -0000 Bezüglich Rodney W. Grimes's Nachricht vom 14.06.2017 00:40 (localtime): … >> I can confirm that the 302504 MFC (r304424) works with BSD guests. >> Also the man page correctly was included in the MFC ? my fault. >> >> But I just checked these, which needs MFC: >> 307517,314342,316357,317545 and the already mentioned >> >>> r317777 should be MFC'ed asap. > > These 5 are now merged to 11-stable. Great, thanks. Unfortunately I forgot about the reference to vmm(4) in bhyve.8. There is no vmm.4, is/was there? Thanks, -harry From owner-freebsd-virtualization@freebsd.org Thu Jun 15 17:05:35 2017 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 932EDD8E2B2 for ; Thu, 15 Jun 2017 17:05:35 +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 806757C0E9 for ; Thu, 15 Jun 2017 17:05:35 +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 v5FH5ZC3052170 for ; Thu, 15 Jun 2017 17:05:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 219672] vmxnet3: with LRO enabled under FreeBSD 11 as a router, outgoing speed of forwarded traffic becomes slower Date: Thu, 15 Jun 2017 17:05:35 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: max@ritlabs.com 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: Thu, 15 Jun 2017 17:05:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219672 --- Comment #6 from Maxim Masiutin --- I agree with your conclusions, but I didn't make the tests that you have suggested : (1. see good performance with LRO turned on and scp a large fil= e to the appliance and 2. see ICMP "need to frag" with LRO turned on and scp to a machine on the remote side.) Since when I use pfSense as a router, and when I ran speed tests on virtual machines that used pfSense as a router, and download speed almost didn't suffer, but upload speed dropped from around 400 MBps to around 0.5 MBps, I suspect that your conclusions are correct. So I agree with you that it was a misconfiguration, not a bug. But I didn't make the tests that you have suggested. I have contacted pfSense developers and asked them to change the notice in = the configuration panel in pfSense. Currently, there is a notice saying that LR= O is disabled by default because "most drivers have bugs". I have asked them to change this to "LRO should only be enabled on an end point". I am sure that= the description of the LRO user interface was the cause of all problems that mi= sled me. I will watch future versions of pfSense and will remind them if they won't change the notice. Don't get me wrong, I'm just a simple user, not a professional sysadmin, and I'm not skilled enough, for example, to see ICMP "need to frag" with LRO tu= rned on and scp to a machine on the remote side. I would have suggested to close this bugtracker entry. Thank you very much again for your help. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Thu Jun 15 17:14:15 2017 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 0863DD8E628 for ; Thu, 15 Jun 2017 17:14:15 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 E1FA97C62A for ; Thu, 15 Jun 2017 17:14:14 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id v5FHEDg7067619; Thu, 15 Jun 2017 10:14:13 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id v5FHEDDp067618; Thu, 15 Jun 2017 10:14:13 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201706151714.v5FHEDDp067618@pdx.rh.CN85.dnsmgr.net> Subject: Re: bhyve.8 referencing non-existing vmm.4 [Was: Re: VNC stuff] In-Reply-To: <5942BE33.1040003@omnilan.de> To: Harry Schmalzbauer Date: Thu, 15 Jun 2017 10:14:13 -0700 (PDT) CC: freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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 Jun 2017 17:14:15 -0000 [ Charset windows-1252 unsupported, converting... ] > Bez?glich Rodney W. Grimes's Nachricht vom 14.06.2017 00:40 (localtime): > > ? > >> I can confirm that the 302504 MFC (r304424) works with BSD guests. > >> Also the man page correctly was included in the MFC ? my fault. > >> > >> But I just checked these, which needs MFC: > >> 307517,314342,316357,317545 and the already mentioned > >> > >>> r317777 should be MFC'ed asap. > > > > These 5 are now merged to 11-stable. > > Great, thanks. > Unfortunately I forgot about the reference to vmm(4) in bhyve.8. > There is no vmm.4, is/was there? The vmm(4) page is uncommited WIP. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Fri Jun 16 01:50:31 2017 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 E2934BF3963 for ; Fri, 16 Jun 2017 01:50: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 CF95867AB0 for ; Fri, 16 Jun 2017 01:50: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 v5G1oUHc051267 for ; Fri, 16 Jun 2017 01:50:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 213814] AWS/EC2: no egress traffic stats on ixv(4) xn(4) Date: Fri, 16 Jun 2017 01:50:31 +0000 X-Bugzilla-Reason: CC 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: IntelNetworking, needs-qa, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? X-Bugzilla-Changed-Fields: bug_file_loc cc 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 Jun 2017 01:50:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213814 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://reviews.freebsd.org | |/D11058 CC| |re@FreeBSD.org --- Comment #13 from Kubilay Kocak --- CC release engineering for 11.1-RELEASE --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Fri Jun 16 15:10:34 2017 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 DECE1C3116A; Fri, 16 Jun 2017 15:10:34 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (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 AB29683901; Fri, 16 Jun 2017 15:10:34 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dLstL-000Fju-M6; Fri, 16 Jun 2017 16:10:31 +0100 Date: Fri, 16 Jun 2017 16:10:31 +0100 From: Gary Palmer To: emulation@freebsd.org, freebsd-virtualization@freebsd.org Subject: Re: VBox 5 getting window height wrong Message-ID: <20170616151031.GD74033@in-addr.com> References: <20170614105419.GB74033@in-addr.com> <1497524900.6640.1.camel@fastmail.fm> <20170615150151.GC74033@in-addr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170615150151.GC74033@in-addr.com> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false 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 Jun 2017 15:10:35 -0000 After a bit of digging, I've commented out two lines in src/VBox/Frontends/VirtualBox/src/runtime/normal/UIMachineWindowNormal.cpp that call VBoxGlobal::normalizeGeometry. That stops client windows from becoming midgets. Looking further into the logs it looks like VBox gets told my desktop is 5 pixels high (!) 00:00:00.525738 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 0 work area is actually resized to: 0x599 x 1920x5 and then sends a setGeometry() request with height set to -26. If I get time I'll try and figure out Whisky Tango Foxtrot On Thu, Jun 15, 2017 at 04:01:51PM +0100, Gary Palmer wrote: > > [ add cc of vbox@freebsd.org which is a better list for this I think ] > > Hi, > > Updating to the correct Guest Additions doesn't fix the issue. Whether > GA is installed or not doesn't seem to make much difference to this problem > > I've also changed from QT4 (which I was using) to QT5 with no change > > Thanks, > > Gary > > On Thu, Jun 15, 2017 at 01:08:20PM +0200, Daniel Tihanyi wrote: > > Hi, > > > > Do you have the right version of Guest Additions installed on your > > guests? I also have Windows 10 as a VM in VirtualBox (though it's > > FreeBSD 11), but it works for me without any problems. > > > > Daniel Tihanyi > > > > On Wed, 2017-06-14 at 11:54 +0100, Gary Palmer wrote: > > > Hi, > > > > > > Ever since upgrading from vbox 4 (which had occasional window placement > > > or size issues, but nothing serious), vbox 5 has consistently had a problem > > > where on starting a VM the window height is always reset to a fraction of > > > what it should be. If I size the window properly by hand, and then select > > > View -> Adjust Window Size it goes back to the wrong size again. > > > > > > Anyone else seen this? > > > > > > With Win10 it's worse - unless I maximise the window it keeps getting reset > > > to the wrong height, I think by communication with the additions installed > > > in the client. > > > > > > virtualbox-ose-5.1.22_1 General-purpose full virtualizer for x86 hardware > > > virtualbox-ose-kmod-5.1.22 VirtualBox kernel module for FreeBSD > > > > > > 10.3-RELEASE-p18 > > > > > > Thanks, > > > > > > Gary > > > > > > P.S. Please keep me on CC as I am not subscribed to this list > > > _______________________________________________ > > > freebsd-virtualization@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > > > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-emulation@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-emulation > To unsubscribe, send any mail to "freebsd-emulation-unsubscribe@freebsd.org" >