From owner-freebsd-virtualization@freebsd.org Sun Feb 4 20:52:12 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9BED2EF0E5D for ; Sun, 4 Feb 2018 20:52:12 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2DA1B71BD6 for ; Sun, 4 Feb 2018 20:52:11 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com ([82.113.183.179]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id w14KRjeD037645 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sun, 4 Feb 2018 20:27:46 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host [82.113.183.179] claimed to be ultrabook.yoonka.com Subject: Re: Xen on FreeBSD 11.1 - Auto creating VMs on boot To: freebsd-virtualization@freebsd.org References: From: Grzegorz Junka Message-ID: <1f68b24a-8e05-3859-9427-ed784cb0d570@gjunka.com> Date: Sun, 4 Feb 2018 20:27:38 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 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, 04 Feb 2018 20:52:12 -0000 On 02/02/2018 17:14, David Salvisberg wrote: > Hello, > > I recently switched from Debian as my Dom0 to FreeBSD to make use of ZFS > without having to rely on zfs-on-linux. The experience has been pretty good > so far, albeit a bit more limited compared to Debian obviously. > > One of the things I haven't been able to figure out is /etc/xen/auto or > rather /usr/local/etc/xen/auto in FreeBSDs case. It doesn't look like Xen > on FreeBSD ships with any of the configuration options for this feature, > possibly due to lack of support for save and restore. > > I don't really need save and restore but auto spawning VMs on boot would be > a nice thing to be able to do without having to write my own rc.d script or > something along those lines. > > Is there a way to make use of the auto creation feature on FreeBSD Xen or > is that feature just missing entirely due to the lack of save/restore > functionality? > > If there is no builtin way, I'd appreciate any recommendations for writing > my own scripts to make sure that they're only being run after Xen has been > fully initialized and is ready for xl create commands. > > Best Regards > > David Salvisberg > Hi David, Unfortunately I don't know the Xen part of the question, but writing your own starting script is quite easy and well documented. A quick google search returns this https://www.freebsd.org/doc/en_US.ISO8859-1/articles/rc-scripting/index.html Good luck GregJ From owner-freebsd-virtualization@freebsd.org Sun Feb 4 23:42:44 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 34BB5EDC590 for ; Sun, 4 Feb 2018 23:42:44 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "bs1.fjl.org.uk", Issuer "bs1.fjl.org.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AE9FE77D6C for ; Sun, 4 Feb 2018 23:42:43 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from [192.168.1.35] (host86-141-21-123.range86-141.btcentralplus.com [86.141.21.123]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id w14NEwLT073051 for ; Sun, 4 Feb 2018 23:14:58 GMT (envelope-from frank2@fjl.co.uk) Subject: Re: Xen on FreeBSD 11.1 - Auto creating VMs on boot To: freebsd-virtualization@freebsd.org References: From: Frank Leonhardt Message-ID: <1251cd71-82b0-7e5e-b4ac-940662eff1b5@fjl.co.uk> Date: Sun, 4 Feb 2018 23:14:59 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 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, 04 Feb 2018 23:42:44 -0000 On 02/02/2018 17:14, David Salvisberg wrote: > Hello, > > I recently switched from Debian as my Dom0 to FreeBSD to make use of ZFS > without having to rely on zfs-on-linux. The experience has been pretty good > so far, albeit a bit more limited compared to Debian obviously. > > One of the things I haven't been able to figure out is /etc/xen/auto or > rather /usr/local/etc/xen/auto in FreeBSDs case. It doesn't look like Xen > on FreeBSD ships with any of the configuration options for this feature, > possibly due to lack of support for save and restore. > > I don't really need save and restore but auto spawning VMs on boot would be > a nice thing to be able to do without having to write my own rc.d script or > something along those lines. > > Is there a way to make use of the auto creation feature on FreeBSD Xen or > is that feature just missing entirely due to the lack of save/restore > functionality? > > If there is no builtin way, I'd appreciate any recommendations for writing > my own scripts to make sure that they're only being run after Xen has been > fully initialized and is ready for xl create commands. > > Best Regards > > David Salvisberg > _______________________________________________ Hi David, I'm not using Xen right now and I'm afraid I can't remember - which means it can't have been an issue. The easy way to kick of something on boot is the traditional "/etc/rc.local" script. Automation "enthusiasts" like to complicate things and are a bit disparaging of this simple way of running whatever you want on startup. The file probably doesn't even exist on your system. So create it. The contents will look something like: cd /usr/something/my-xen-configs xl create somemachine.cfg xl create someothermachine.cfg xl create yetanothermachine.cfg echo All done! This assumes xl is on the search path of the environment when rc.local is run. I never assume, so I'd use the full path to "xl". Avoid unexpected results! This is a normal shell script, so you can do more complex things like: for vm in `ls /usr/something/my-xen-configs` ; do xl create $vm ; done But this is getting dangerously close to automation ;-) Regards, Frank. From owner-freebsd-virtualization@freebsd.org Wed Feb 7 15:01:48 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B6748F0C3E9 for ; Wed, 7 Feb 2018 15:01:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 522EA6D169 for ; Wed, 7 Feb 2018 15:01: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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 7957F2368E for ; Wed, 7 Feb 2018 15:01:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w17F1l3d064191 for ; Wed, 7 Feb 2018 15:01:47 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w17F1lxm064189 for freebsd-virtualization@FreeBSD.org; Wed, 7 Feb 2018 15:01:47 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 225579] CPU usage in top command not matching with VMWare Host's esxtop command's vCPU output Date: Wed, 07 Feb 2018 15:01:47 +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-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.25 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, 07 Feb 2018 15:01:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225579 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 Feb 7 17:16:51 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B9C7F163F6 for ; Wed, 7 Feb 2018 17:16:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9ED2E73A59 for ; Wed, 7 Feb 2018 17:16:50 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id D818F24907 for ; Wed, 7 Feb 2018 17:16:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w17HGnQH059160 for ; Wed, 7 Feb 2018 17:16:49 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w17HGnBG059159 for freebsd-virtualization@FreeBSD.org; Wed, 7 Feb 2018 17:16:49 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 225579] CPU usage in top command not matching with VMWare Host's esxtop command's vCPU output Date: Wed, 07 Feb 2018 17:16:50 +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-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: rgrimes@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.25 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, 07 Feb 2018 17:16:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225579 Rodney W. Grimes changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rgrimes@FreeBSD.org --- Comment #1 from Rodney W. Grimes --- I can do some investigation here, but using an I/O intensive task and evaluating CPU load is probably not a good choice in benchmarks or testing. Are the FreeBSD guests using UFS, or ZFS or ??? for the file system that the dd operations are going to. Is the backing store in ESXi eager or lazy zero? What file system was used in the ubuntu case? What version of Ununtu? What are the I/O rates during this testing? This really is an I/O benchmark and not a CPU benchmark. Would be interesting to see this running a CPU intensive task. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Wed Feb 7 17:22:29 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2BBFF16AEC for ; Wed, 7 Feb 2018 17:22:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 70A6A73EB0 for ; Wed, 7 Feb 2018 17:22:29 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id A3DC024A5B for ; Wed, 7 Feb 2018 17:22:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w17HMS84079370 for ; Wed, 7 Feb 2018 17:22:28 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w17HMSRp079369 for freebsd-virtualization@FreeBSD.org; Wed, 7 Feb 2018 17:22:28 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 225579] CPU usage in top command not matching with VMWare Host's esxtop command's vCPU output Date: Wed, 07 Feb 2018 17:22:28 +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-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: amvandemore@gmail.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: 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.25 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, 07 Feb 2018 17:22:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225579 amvandemore@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amvandemore@gmail.com --- Comment #2 from amvandemore@gmail.com --- May be related to bug #173541 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Wed Feb 7 23:10:02 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B595EE274E for ; Wed, 7 Feb 2018 23:10:02 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B32F584034 for ; Wed, 7 Feb 2018 23:10:01 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: by mail-qk0-x235.google.com with SMTP id f68so3365083qke.9 for ; Wed, 07 Feb 2018 15:10:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=date:from:to:cc:subject:message-id:in-reply-to:references :organization:mime-version:content-transfer-encoding; bh=cqjPJd8wK2S/3I2j95hRQ15JaagJJfdK4EAjUchAAio=; b=G2WNo8D5fxAD396nQqJGKbU8Ukxp7a1FTrcSNSse2wWSr/pwhsAcJVpx9qQ89uwm32 LVz9mBQM36A6TKjXs/v4OULWF8cKYFmgoj4B0eRnWmAxxZnhqdXQ6Wf0BAUk0PJOFLWU xwqC2lw0KufNPD20/KEl4DbydhPJTbQCyU/f8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:organization:mime-version:content-transfer-encoding; bh=cqjPJd8wK2S/3I2j95hRQ15JaagJJfdK4EAjUchAAio=; b=pE/+MKs/fymn20FkA/np9P1vVdRIOQCigXd4zKMTkqfitrZVbhrMkCMXjTVXGTK0cs Id0TOD5nT/TDwI/zBj+mpmvgNQG/KJI5yAiYo8bwyFcVuVi6aN8uEgJDqPmfqGHF7eEI HBhfPqSAqP+5WUoPN7H46X/ZEvl5EhXl6knAhdcgucXHJsaL0zK4D173BKXJOsZqh2SF R30cFpTKDevP9acLovYmGLi3tWV4KHpNeEZrSvLfTFQYCl0pSTZJcj/YRe4zUlLYAXBS l+6ukOemebJuj8KEYWC8wDN2F0XXtNwFGhtU22gl18zxyRe8UduL3hjDNe8VRBW4Y1Jo S3LA== X-Gm-Message-State: APf1xPAY1bvmQa+qaSJLUAJBcjjujGvXrVzgejr1hQMTMNNERmuTaGOX 57bdLnDbevFVdcT8Mdb/xfoRV2Du X-Google-Smtp-Source: AH8x225M27p8tg8FWmHm1TG016UxDsK3DhcxmsJ9nNnEpRUPRya1y9z56zeZW5UqhXCZuX+0VGIEaQ== X-Received: by 10.55.2.140 with SMTP id v12mr11300750qkg.340.1518045000863; Wed, 07 Feb 2018 15:10:00 -0800 (PST) Received: from Papi.lobos ([177.158.245.220]) by smtp.gmail.com with ESMTPSA id a190sm1219595qkf.20.2018.02.07.15.09.59 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 07 Feb 2018 15:10:00 -0800 (PST) Date: Wed, 7 Feb 2018 20:12:24 -0300 From: Mario Lobo To: freebsd-virtualization@freebsd.org Subject: Re: Bhyve passthrough problems (update) Message-ID: <20180207201224.2c5c4c47@Papi.lobos> In-Reply-To: <20180119175257.3f29d9d6@Papi.lobos> References: <20180117202250.6ef90c6d@Papi.lobos> <20180119175257.3f29d9d6@Papi.lobos> Organization: BSD X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 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, 07 Feb 2018 23:10:02 -0000 On Fri, 19 Jan 2018 17:52:57 -0300 Mario Lobo wrote: > On Thu, 18 Jan 2018 00:58:08 -0800 > Peter Grehan wrote: > > > Hi Mario, > > > > > I'm trying to passthrough a firewire pci card to a windows 7 64 > > > guest. > > > > First, you'll need to verify if that card supports MSI or MSI-x > > since that is required by bhyve for passthru support. This can be > > seen with 'pciconf -lbc' on the FreeBSD host. > > > > > VM exits with: > > > > > > Assertion failed: (mr->name == memp->name), function > > > unregister_mem, file /usr/src/usr.sbin/bhyve/mem.c, line 265. > > > Abort trap > > > > This is bug in bhyve when running Windows with PCI devices that > > have more than 1 memory BAR (e.g. Intel igb ethernet devices), due > > to the order that Windows determines BAR sizes. I've been meaning > > to fix this for a long time so will try and get to it. > > > > later, > > > > Peter. > > Hi there: > > Well, now, even without setting up passthrough, the VM doesn't start > (which it did, before I svned up /usr/src). > > With vnc: > > bhyve -c 4 -s 0,amd_hostbridge > -s 3,ahci-hd,/Vmachines/disk.img,sectorsize=512 > -s 4,ahci-cd,/Extra/Isos/Windows/Windows_7/null_dvd.iso > -s 10,virtio-net,tap0 > -s 11,fbuf,tcp=0.0.0.0:5900,,w=1600,h=900,wait > -s 20,xhci,tablet > -s 31,lpc > -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd > -m 4G -H -w WIN-764 > fbuf frame buffer base: 0x942e00000 [sz 16777216] > > error: > Assertion failed: (error == 0), function modify_bar_registration, > file /usr/src/usr.sbin/bhyve/pci_emul.c, line 491. Abort trap > > > Without vnc: > > bhyve -c 4 -s 0,amd_hostbridge > -s 3,ahci-hd,/Vmachines/disk.img,sectorsize=512 > -s 4,ahci-cd,/Extra/Isos/Windows/Windows_7/null_dvd.iso > -s 10,virtio-net,tap0 > -s 20,xhci,tablet > -s 31,lpc > -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd > -m 4G -H -w WIN-764 > > error: > Assertion failed: (mr->name == memp->name), function unregister_mem, > file /usr/src/usr.sbin/bhyve/mem.c, line 265. Abort trap > > > Revisions (/usr/src 11-STABLE): > > working: 321652 > not working (current): 328163 > > Any updates on this issue? Thanks, -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." From owner-freebsd-virtualization@freebsd.org Wed Feb 7 23:19:25 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0ED0EE326E for ; Wed, 7 Feb 2018 23:19:25 +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 3BC8F845F9 for ; Wed, 7 Feb 2018 23:19:25 +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 7EF8020B1AE8 for ; Thu, 8 Feb 2018 09:19:22 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 7A1972820A7 for ; Thu, 8 Feb 2018 09:19:22 +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 je3SE2ekLBn3 for ; Thu, 8 Feb 2018 09:19:22 +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 AB612280961; Thu, 8 Feb 2018 09:19:20 +1000 (AEST) Subject: Re: Bhyve passthrough problems (update) To: Mario Lobo References: <20180117202250.6ef90c6d@Papi.lobos> <20180119175257.3f29d9d6@Papi.lobos> <20180207201224.2c5c4c47@Papi.lobos> Cc: freebsd-virtualization@freebsd.org From: Peter Grehan Message-ID: Date: Wed, 7 Feb 2018 15:19:18 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180207201224.2c5c4c47@Papi.lobos> 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.3 cv=KPZ08mNo c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=5eVCmCvhg37cu/pjidAGzw==:17 a=IkcTkHD0fZMA:10 a=Op4juWPpsa0A:10 a=PiyLjKvJ7wJXcDsaJesA:9 a=QEXdDO2ut3YA:10 wl=host:3 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 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, 07 Feb 2018 23:19:25 -0000 Hi Mario, >> Well, now, even without setting up passthrough, the VM doesn't start >> (which it did, before I svned up /usr/src). ... >> working: 321652 >> not working (current): 328163 ... > Any updates on this issue? Can you verify if the issue still occurrs if you destroy the guest before re-invoking it ? (i.e. bhyvectl --destroy --vm=WIN-764 ) later, Peter. From owner-freebsd-virtualization@freebsd.org Thu Feb 8 16:22:29 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 675B4F10A41 for ; Thu, 8 Feb 2018 16:22:29 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::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 05ABC6F916 for ; Thu, 8 Feb 2018 16:22:28 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: by mail-yw0-x22c.google.com with SMTP id j128so2992215ywg.7 for ; Thu, 08 Feb 2018 08:22:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DrXifFwcHK3Mr9XCduHPqyHvdI4gJ5p14M5UiYTmFqg=; b=R/t167THCf4NRBN0BPqx0cq0WUyw/x23Rt8BCuJEhqjZ50okK50YzkfHbxNWRrvi8f JQzv1aVrCfKdchQx/RB9WsToi7uDATJJ9S8JSkJlqTxgE/h8YPq0v/KCvjNi6TSXm1Q9 2lT95U248OB96DwE4dug1suqsX7QFXzm1X5V8= 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=DrXifFwcHK3Mr9XCduHPqyHvdI4gJ5p14M5UiYTmFqg=; b=s4byM/qex2yKFvrLbOn0ugYj/vPMGoNiyJSui4IBl4UEYiW7/UDiR+BeavSUr68kMJ 5dgTBIvxOMilgiJCvnV3GjGdl6CqgazRS52qeuN/12lxMqgp2w6b5jHt9f6bgiJfQMYf S8hjKNiDfPNxQ0CBj/CaCkNd40Vw+AJnUiwekcW1Jtpm8VBaIpBJAu2NWEOV/exuuQPw bIo9ecqF4XCfj6BDCCM4hRpdr5f9+azvJbr6t39Bax/NL4RYPwCRS60SQxiqrp9r5CCF O0+j5virJflB+x2M4fZ9AkUUt1eY0QfqD7mlNPIHzV8PUorZWrO2ikUnWUVyKeu69mHB l5Qg== X-Gm-Message-State: APf1xPA8sFkGGgsDy6hQh2XxMz06DIV/n+PSfa6e832KZRlzbdhbAefm ArR7ztj7X2YtOxnDVV4LXhgozqCepO68QeCl9qRElVj1 X-Google-Smtp-Source: AH8x2240lEpt6XLG+vz0+AoylftcdV2ekV6egm2p6Q20+PY0kZ/Ecu8mPsyhM0kWunqKeCWFaJzGvkGesUxoC47yzvs= X-Received: by 10.37.66.215 with SMTP id p206mr916700yba.27.1518106948129; Thu, 08 Feb 2018 08:22:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.139.142 with HTTP; Thu, 8 Feb 2018 08:22:27 -0800 (PST) In-Reply-To: References: <20180117202250.6ef90c6d@Papi.lobos> <20180119175257.3f29d9d6@Papi.lobos> <20180207201224.2c5c4c47@Papi.lobos> From: Mario Lobo Date: Thu, 8 Feb 2018 13:22:27 -0300 Message-ID: Subject: Re: Bhyve passthrough problems (update) To: Peter Grehan Cc: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 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, 08 Feb 2018 16:22:29 -0000 2018-02-07 20:19 GMT-03:00 Peter Grehan : > Hi Mario, > > Well, now, even without setting up passthrough, the VM doesn't start >>> (which it did, before I svned up /usr/src). >>> >> ... > >> working: 321652 >>> not working (current): 328163 >>> >> ... > >> Any updates on this issue? >> > > Can you verify if the issue still occurrs if you destroy the guest before > re-invoking it ? (i.e. bhyvectl --destroy --vm=WIN-764 ) > > later, > > Peter. > Yes, I verified that. It still occurs even after destroying the VM. I also recompiled bhyve from the working (321652) release and the same error messages are still there. I even recreated a new disk.img and followed the same steps that worked before (1 cpu) to reinstall the VM from ISO to no avail. Bhyve doesn't even start any longer and exits with one of the error messages above. What previously worked now doesn't. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!]