From owner-freebsd-virtualization@freebsd.org Sun Oct 30 19:51:16 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B094EC27750 for ; Sun, 30 Oct 2016 19:51:16 +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 96E0218A6 for ; Sun, 30 Oct 2016 19:51:16 +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 u9UJpFcB088289 for ; Sun, 30 Oct 2016 19:51:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 213333] FreeBSD 11-RELEASE fails to boot under KVM/Qemu Date: Sun, 30 Oct 2016 19:51:16 +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 Only Me X-Bugzilla-Who: akelling@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.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, 30 Oct 2016 19:51:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213333 Andrew Keling changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |akelling@gmail.com --- Comment #1 from Andrew Keling --- I am also seeing this issue with KVM on OpenSUSE 42.1. I have also tried the same troubleshooting steps.=20 My system information. Repository: openSUSE-Leap-42.1-Update Name: qemu-kvm Version: 2.3.1-19.3 Arch: x86_64 Vendor: openSUSE sharp@TwoRivers:~> uname -a Linux TwoRivers 4.1.34-33-default #1 SMP PREEMPT Thu Oct 20 08:03:29 UTC 20= 16 (fe18aba) x86_64 x86_64 x86_64 GNU/Linux sharp@TwoRivers:~> cat /proc/cpuinfo=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20 =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20 [192/948] processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 1 model name : AMD FX(tm)-8120 Eight-Core Processor stepping : 2 microcode : 0x6000629 cpu MHz : 1400.000 cache size : 2048 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca = cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 cx16 sse4_1 sse4_2 popcnt aes xsave avx lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw = ibs xop skinit wdt lwp fma4 nodeid_msr topoext perfctr_core perfctr_nb ar at cpb hw_pstate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyas= id decodeassists pausefilter pfthreshold vmmcall bugs : fxsave_leak sysret_ss_attrs bogomips : 6241.87 TLB size : 1536 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm 100mhzsteps hwpstate cpb --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Sun Oct 30 20:01:16 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1E8B4C27901 for ; Sun, 30 Oct 2016 20:01:16 +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 0D1701CE4 for ; Sun, 30 Oct 2016 20:01:16 +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 u9UK1FVH030414 for ; Sun, 30 Oct 2016 20:01:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 213333] FreeBSD 11-RELEASE fails to boot under KVM/Qemu Date: Sun, 30 Oct 2016 20:01:16 +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 Only Me X-Bugzilla-Who: akelling@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: 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, 30 Oct 2016 20:01:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213333 --- Comment #2 from Andrew Keling --- Found a work around. Seems to be an issue with copying the the host CPU topology and with the Opteron_G4 CPU arch too. Switching to Opteron_G3 or selecting Hypervisor_Default seems to mitigate t= his issue. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Sun Oct 30 20:04:55 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B1B92C27AB8 for ; Sun, 30 Oct 2016 20:04:55 +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 A108A1046 for ; Sun, 30 Oct 2016 20:04:55 +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 u9UK4t40058462 for ; Sun, 30 Oct 2016 20:04:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 213333] FreeBSD 11-RELEASE fails to boot under KVM/Qemu Date: Sun, 30 Oct 2016 20:04:55 +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 Only Me X-Bugzilla-Who: akelling@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: 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, 30 Oct 2016 20:04:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213333 --- Comment #3 from Andrew Keling --- Should note that this corrected my issue upgrading my servers from 10.3 to = 11. I was also seeing issue with the install cd locking up too. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Sun Oct 30 21:01:03 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3294DC2737A for ; Sun, 30 Oct 2016 21:01:03 +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 0E4C91871 for ; Sun, 30 Oct 2016 21:01:03 +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 u9UL01th070189 for ; Sun, 30 Oct 2016 21:01:02 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201610302101.u9UL01th070189@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, 30 Oct 2016 21:01:02 +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, 30 Oct 2016 21:01:03 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 212711 | [typo] bhyve: virtio-rnd PCI ID doesn't match vio New | 212820 | FreeBSD 10-STABLE from latest HEAD and 11-RELEASE Open | 212721 | FreeBSD 11.0-RC2/RC3/RELEASE fails on Hyper-V 201 3 problems total for which you should take action. From owner-freebsd-virtualization@freebsd.org Tue Nov 1 04:45:10 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DDF06C29B3B for ; Tue, 1 Nov 2016 04:45:10 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C998314AD for ; Tue, 1 Nov 2016 04:45:10 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1c1QwZ-000FNV-Qr for freebsd-virtualization@freebsd.org; Mon, 31 Oct 2016 22:45:03 -0600 Date: Mon, 31 Oct 2016 22:45:03 -0600 From: The Doctor To: freebsd-virtualization@freebsd.org Subject: Windows 2016 Message-ID: <20161101044503.GA58756@doctor.nl2k.ab.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.7.1 (2016-10-04) 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, 01 Nov 2016 04:45:11 -0000 I was able to install the Windows 2016 using the GUI method. One proble. It is assigned an IP but the netmask and the default route is not showing up. Also The virtual Windows 2016 box does not see a network interface. What must I do to convince this box that is it on a switch 192.168.0.60 Thar is handling the default routing to the interent. For argument sake , the Windows server is IP as 192.168.0.68 I have an ubuntu up at 192.168.0.57 a Centos at 192.168.0.54 and Fedora at 192.168.0.53 all running successfully. -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!! From owner-freebsd-virtualization@freebsd.org Tue Nov 1 08:14:52 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28D62C2989B for ; Tue, 1 Nov 2016 08:14:52 +0000 (UTC) (envelope-from daniel.tihanyi@tetragir.com) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 001AD164F for ; Tue, 1 Nov 2016 08:14:51 +0000 (UTC) (envelope-from daniel.tihanyi@tetragir.com) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 119CC20A28 for ; Tue, 1 Nov 2016 04:14:50 -0400 (EDT) Received: from web2 ([10.202.2.212]) by compute1.internal (MEProxy); Tue, 01 Nov 2016 04:14:50 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=tetragir.com; h= x-me-sender:message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:date:subject :references; s=mesmtp; bh=zYfYC6sg5VIfYTP1cO4+aztnhTo=; b=hY72vs uuQNta3n076NGX0DNQ+mo6j9Rus2F1PSWo8h0JoVzJA1ySz6or9Z3IAVPgHBDPL5 1Itu6BcrBadeZGykjbAsxEa2fRGHr8snFhShiChijb5Ja94XciLxlRdFRedeta9a xY5/nCxJEkPYJhLUUUuqilSHe10RuV4fpHtVg= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-me-sender:message-id:from:to :mime-version:content-transfer-encoding:content-type:in-reply-to :date:subject:references; s=smtpout; bh=zYfYC6sg5VIfYTP1cO4+aztn hTo=; b=cWYfjNXrkB/lkVvLSvG/L8w4/ZnArltdUwjvJ38Dx42IS76/xBF9C0YY W9mR2oahNz2aTuk7vZcp3atKADQLnR/kK1OEKqEpdaW6E0wo1mwsQkMehHrHxwai KojjvjEf1/4YbW5MBGOB3MU4tJrliPQD2saStB7gMjvLSuqKdKg= X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id DAE6C626B2; Tue, 1 Nov 2016 04:14:49 -0400 (EDT) Message-Id: <1477988089.1453927.773507953.4D0BFD5C@webmail.messagingengine.com> From: Daniel Tihanyi To: freebsd-virtualization@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-996895c6 In-Reply-To: <20161101044503.GA58756@doctor.nl2k.ab.ca> Date: Tue, 01 Nov 2016 08:14:49 +0000 Subject: Re: Windows 2016 References: <20161101044503.GA58756@doctor.nl2k.ab.ca> 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, 01 Nov 2016 08:14:52 -0000 Hi, first of all, could you please clarify if you use VirtualBox, bhyve or any other virtualization platform? Additionally, could you please share, how did you configured your network for the VMs? What do you use for DHCP Server? Is it configured properly? Thank you very much! -- Daniel Tihanyi On Tue, Nov 1, 2016, at 04:45, The Doctor wrote: > I was able to install the Windows 2016 using the GUI method. > > One proble. > > It is assigned an IP but > > the netmask and the default route is not showing up. > > Also The virtual Windows 2016 box does not see a network interface. > > What must I do to convince this box that is it on a switch > > 192.168.0.60 > > Thar is handling the default routing to the interent. > > For argument sake , > > the Windows server is IP as 192.168.0.68 > > > I have an ubuntu up at 192.168.0.57 > a Centos at 192.168.0.54 > and > Fedora at 192.168.0.53 > > all running successfully. > > -- > Member - Liberal International This is doctor@@nl2k.ab.ca Ici > doctor@@nl2k.ab.ca > God,Queen and country!Never Satan President Republic!Beware AntiChrist > rising! > http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism > Time for the USA to hold a referendum on its republic and vote to > dissolve!! > _______________________________________________ > 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 Tue Nov 1 09:03:34 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D3B61C299C8 for ; Tue, 1 Nov 2016 09:03:34 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-outbound.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.userve.net", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 59AAD11ED for ; Tue, 1 Nov 2016 09:03:34 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) by smtp-outbound.userve.net (8.15.1/8.15.1) with ESMTPS id uA1933Gv081144 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 1 Nov 2016 09:03:04 GMT (envelope-from matt.churchyard@userve.net) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=201508; t=1477990984; bh=FN4l4AyLvZ51f+7UsDHorTi2KaiAVTlO7EsLRWtYWTY=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=gIT5RRXtbVG+XthGOALaFqPnoO/nka0gc0487cU3/8juN9rl4eBiGNEYO1rvwO9WW 3gakV9xSa2zhIpi6cKnoQ+Scn/Lis7zmAgWFK2cqKdnHJ885Ao2CE3gJ4XbkTsqA4a bs/4VXWNJkZEKVMOq8NAaTvxyFbGJcuu+yJDrrxo= Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Tue, 1 Nov 2016 09:02:57 +0000 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Tue, 1 Nov 2016 09:02:57 +0000 From: Matt Churchyard To: The Doctor CC: "freebsd-virtualization@freebsd.org" Subject: RE: Windows 2016 Thread-Topic: Windows 2016 Thread-Index: AQHSM/rIdWE82Qm9HE2AlMaCqt5JpKDD05aw Date: Tue, 1 Nov 2016 09:02:57 +0000 Message-ID: References: <20161101044503.GA58756@doctor.nl2k.ab.ca> In-Reply-To: <20161101044503.GA58756@doctor.nl2k.ab.ca> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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: Tue, 01 Nov 2016 09:03:34 -0000 >I was able to install the Windows 2016 using the GUI method. >One proble. >It is assigned an IP but >the netmask and the default route is not showing up. >Also The virtual Windows 2016 box does not see a network interface. This makes very little sense. You usually specify the netmask and default r= oute when you assign Windows an IP address. And how have you assigned the guest an IP address if it has no network inte= rface? >What must I do to convince this box that is it on a switch On the bhyve host it should be configured just like any other bhyve virtual= machine. The guest should have a virtio-net device, which is linked to a t= ap interface on the host. That tap interface should be bridged with whichev= er physical network adapter you want the guest connected to. However, I think I mentioned in a previous message that Windows does not ha= ve the virtio-net drivers by default. You need to boot the guest with the v= irtio-net driver ISO attached and install the driver. You should see the in= terface in Device Manager flagged as not installed/working. Matt >192.168.0.60 >Thar is handling the default routing to the interent. >For argument sake , >the Windows server is IP as 192.168.0.68 >I have an ubuntu up at 192.168.0.57 >a Centos at 192.168.0.54 >and >Fedora at 192.168.0.53 >all running successfully. From owner-freebsd-virtualization@freebsd.org Tue Nov 1 09:21:28 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8DA15C281D0 for ; Tue, 1 Nov 2016 09:21:28 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-outbound.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.userve.net", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2916914A8 for ; Tue, 1 Nov 2016 09:21:27 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) by smtp-outbound.userve.net (8.15.1/8.15.1) with ESMTPS id uA19L9aP057405 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 1 Nov 2016 09:21:13 GMT (envelope-from matt.churchyard@userve.net) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=201508; t=1477992073; bh=dVB2bkB0ebHMqyAVNBpAHaNb7bSL/vtbitT1VIEgFwc=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=HdBhkuMJgm6U0JPFB0/MGa1HRQ7ypPcNUaXBmxsXkpqWNmbuoVFjDyYOz1UBd9PzQ UyGq1zFRWosr4sQ6KU+5aRtmzAtDQKy9HHILvVl+52ZKHaLNs3ukj2VJ3squHlKdxT WrF1PYFkAz8/EOzDA1qt2R/M7/T3QZy81VXWZr9A= Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Tue, 1 Nov 2016 09:21:03 +0000 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Tue, 1 Nov 2016 09:21:03 +0000 From: Matt Churchyard To: "freebsd-virtualization@freebsd.org" Subject: RE: Windows 2016 Thread-Topic: Windows 2016 Thread-Index: AQHSM/rIdWE82Qm9HE2AlMaCqt5JpKDD05awgAAFgeA= Date: Tue, 1 Nov 2016 09:21:02 +0000 Message-ID: <51a088cbe3964542aec18bf6f1f2c4af@SERVER.ad.usd-group.com> References: <20161101044503.GA58756@doctor.nl2k.ab.ca> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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: Tue, 01 Nov 2016 09:21:28 -0000 >I was able to install the Windows 2016 using the GUI method. >One proble. >It is assigned an IP but >the netmask and the default route is not showing up. >Also The virtual Windows 2016 box does not see a network interface. This makes very little sense. You usually specify the netmask and default r= oute when you assign Windows an IP address. And how have you assigned the guest an IP address if it has no network inte= rface? >What must I do to convince this box that is it on a switch On the bhyve host it should be configured just like any other bhyve virtual= machine. The guest should have a virtio-net device, which is linked to a t= ap interface on the host. That tap interface should be bridged with whichev= er physical network adapter you want the guest connected to. However, I think I mentioned in a previous message that Windows does not ha= ve the virtio-net drivers by default. You need to boot the guest with the v= irtio-net driver ISO attached and install the driver. You should see the in= terface in Device Manager flagged as not installed/working. -------------------------------------------- Just one other thing to add to this. I'm not sure if this is the case here,= but it's something I've seen a few times now. When configuring IP addresses, etc for a guest, this should be done -inside= - the guest. Do not assign a guest's IP address to the host, or to the tap interface. Bhyve works just like any other hypervisor. IP settings are done in the gue= st as if it was a real machine, the host just acts like a switch. -------------------------------------------- Matt >192.168.0.60 >Thar is handling the default routing to the interent. >For argument sake , >the Windows server is IP as 192.168.0.68 >I have an ubuntu up at 192.168.0.57 >a Centos at 192.168.0.54 >and >Fedora at 192.168.0.53 >all running successfully. From owner-freebsd-virtualization@freebsd.org Tue Nov 1 13:48:31 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A45AC27DD2 for ; Tue, 1 Nov 2016 13:48:31 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1430C1163 for ; Tue, 1 Nov 2016 13:48:30 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1c1ZQT-0007FP-LV; Tue, 01 Nov 2016 07:48:29 -0600 Date: Tue, 1 Nov 2016 07:48:29 -0600 From: The Doctor To: Daniel Tihanyi Cc: freebsd-virtualization@freebsd.org Subject: Re: Windows 2016 Message-ID: <20161101134829.GA27402@doctor.nl2k.ab.ca> References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <1477988089.1453927.773507953.4D0BFD5C@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1477988089.1453927.773507953.4D0BFD5C@webmail.messagingengine.com> User-Agent: Mutt/1.7.1 (2016-10-04) 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, 01 Nov 2016 13:48:31 -0000 On Tue, Nov 01, 2016 at 08:14:49AM +0000, Daniel Tihanyi wrote: > Hi, > > first of all, could you please clarify if you use VirtualBox, bhyve or > any other virtualization platform? > Additionally, could you please share, how did you configured your > network for the VMs? > What do you use for DHCP Server? Is it configured properly? > Thank you very much! > It is bhyve and I do not use DHCP. Please NEVER top post! > -- > Daniel Tihanyi > > On Tue, Nov 1, 2016, at 04:45, The Doctor wrote: > > I was able to install the Windows 2016 using the GUI method. > > > > One proble. > > > > It is assigned an IP but > > > > the netmask and the default route is not showing up. > > > > Also The virtual Windows 2016 box does not see a network interface. > > > > What must I do to convince this box that is it on a switch > > > > 192.168.0.60 > > > > Thar is handling the default routing to the interent. > > > > For argument sake , > > > > the Windows server is IP as 192.168.0.68 > > > > > > I have an ubuntu up at 192.168.0.57 > > a Centos at 192.168.0.54 > > and > > Fedora at 192.168.0.53 > > > > all running successfully. > > > > -- > > Member - Liberal International This is doctor@@nl2k.ab.ca Ici > > doctor@@nl2k.ab.ca > > God,Queen and country!Never Satan President Republic!Beware AntiChrist > > rising! > > http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism > > Time for the USA to hold a referendum on its republic and vote to > > dissolve!! > > _______________________________________________ > > 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-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!! From owner-freebsd-virtualization@freebsd.org Tue Nov 1 14:02:51 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 613D5C2828B for ; Tue, 1 Nov 2016 14:02:51 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4AE501115 for ; Tue, 1 Nov 2016 14:02:51 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1c1ZeL-0007Zs-T6; Tue, 01 Nov 2016 08:02:49 -0600 Date: Tue, 1 Nov 2016 08:02:49 -0600 From: The Doctor To: Matt Churchyard Cc: "freebsd-virtualization@freebsd.org" Subject: Re: Windows 2016 Message-ID: <20161101140249.GB27402@doctor.nl2k.ab.ca> References: <20161101044503.GA58756@doctor.nl2k.ab.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) 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, 01 Nov 2016 14:02:51 -0000 On Tue, Nov 01, 2016 at 09:02:57AM +0000, Matt Churchyard wrote: > >I was able to install the Windows 2016 using the GUI method. > > >One problem. > > >It is assigned an IP but > > >the netmask and the default route is not showing up. > > >Also The virtual Windows 2016 box does not see a network interface. > > This makes very little sense. You usually specify the netmask and default route when you assign Windows an IP address. > And how have you assigned the guest an IP address if it has no network interface? > The taps are allocated an IP address. I fully concur. In the install at one point, I declare that the IP address, netmask and gateway are 'declared' at the 'MB ' BIOS interface. > >What must I do to convince this box that is it on a switch > > On the bhyve host it should be configured just like any other bhyve virtual machine. The guest should have a virtio-net device, which is linked to a tap interface on the host. That tap interface should be bridged with whichever physical network adapter you want the guest connected to. > > However, I think I mentioned in a previous message that Windows does not have the virtio-net drivers by default. You need to boot the guest with the virtio-net driver ISO attached and install the driver. You should see the interface in Device Manager flagged as not installed/working. > That is correct . I do have an iso of the MB drivers, namely a Supermicro X10DRW-i MB and from Intel I did obtain the .exe file for the i350GbE drivers. I script a 2 phase installation as follows: 1) /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/14393.0.160715-1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO -s 4,ahci-hd,windows2016.img -s 5,virtio-net,tap15 -s 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -s 30,xhci,tablet -s 31,lpc -l com1,stdio -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd windows2016guest 2) /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/null-install.iso -s 4,ahci-hd,windows2016.img -s 5,virtio-net,tap15 -s 29,fbuf,tcp=0.0.0.0:5900,w=1024,h=768,wait -s 30,xhci,tablet -s 31,lpc -l com1,/dev/nmdm15A -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd windows2016guest & As I said, I have picked up an ISO from the MB manufacturer let's call it manufacturer.iso . Where do I place said iso in the 'phase' of things? > Matt > > >192.168.0.60 > > >Thar is handling the default routing to the interent. > > >For argument sake , > > >the Windows server is IP as 192.168.0.68 > > > >I have an ubuntu up at 192.168.0.57 > >a Centos at 192.168.0.54 > >and > >Fedora at 192.168.0.53 > > >all running successfully. -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!! From owner-freebsd-virtualization@freebsd.org Tue Nov 1 14:09:07 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52259C283B1 for ; Tue, 1 Nov 2016 14:09:07 +0000 (UTC) (envelope-from randy@terbush.org) 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 10DEF1C71 for ; Tue, 1 Nov 2016 14:09:07 +0000 (UTC) (envelope-from randy@terbush.org) Received: by mail-qk0-x235.google.com with SMTP id q130so80104714qke.1 for ; Tue, 01 Nov 2016 07:09:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=terbush.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=xFtYiidELYD85gfW9hv+M3aXF8YETD8DEOxufHeSuB8=; b=kJr3SV7OdI2MEISJa8OjwDlhdfatvHyPYAMI/aU5UAvDDdpyzS4QLkebRUGEg3rArZ RMSdBBlgNVwsVchz4VNkcqISK+ovydh/FKUZmptgfsWwOrBSbT4LOq+SxIwsRV/ypnq9 KzfO/jwsfEa1i2i0cprLKjw9RICqXg3+AmNto= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=xFtYiidELYD85gfW9hv+M3aXF8YETD8DEOxufHeSuB8=; b=g55KK8e40TWIAhchUoO77L8/Qdvx+lSeza8s+0wO1JKfYxdIsWUV1LSyO7Kdrb0y/r xsP4JZnHohF+xDQrLpwY5qlskhS49U9d1aFmBQwPbL/W45WXT2EGAr7QSkm/uh19CVPG bUlEhMhh3+ph8D+hH4A8Xz94+YGPribt4Q7/FeTHwR2QgtHcan3qc0okd5DBIbjb0G4p E3taeq8YFQl7lyae9nXeiRHHsvLvUx7X/TruiDxF9VTkZ4zEzjPHBxdU07eGbWTvyuWO Pu0UiILqRRokz2OGyRrDOF0OVVquESYod0Zyz/DQhAQmY573CzDxGYGJT2HKj7GCtanz jL/Q== X-Gm-Message-State: ABUngvetn+m52mJZwQwhqodWGzWrygk7KpIAQYHoazzN9bN+4V+bDqR2gP6fppxYYfud6uHTzcXlRF41GpQrTg== X-Received: by 10.55.12.10 with SMTP id 10mr28883862qkm.49.1478009346048; Tue, 01 Nov 2016 07:09:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.51.82 with HTTP; Tue, 1 Nov 2016 07:08:35 -0700 (PDT) In-Reply-To: <51a088cbe3964542aec18bf6f1f2c4af@SERVER.ad.usd-group.com> References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <51a088cbe3964542aec18bf6f1f2c4af@SERVER.ad.usd-group.com> From: Randy Terbush Date: Tue, 1 Nov 2016 08:08:35 -0600 Message-ID: Subject: Re: Windows 2016 To: "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, 01 Nov 2016 14:09:07 -0000 On Tue, Nov 1, 2016 at 3:21 AM, Matt Churchyard via freebsd-virtualization = < freebsd-virtualization@freebsd.org> wrote: > >I was able to install the Windows 2016 using the GUI method. > > >One proble. > > >It is assigned an IP but > > >the netmask and the default route is not showing up. > > >Also The virtual Windows 2016 box does not see a network interface. > > This makes very little sense. You usually specify the netmask and default > route when you assign Windows an IP address. > And how have you assigned the guest an IP address if it has no network > interface? > > >What must I do to convince this box that is it on a switch > > On the bhyve host it should be configured just like any other bhyve > virtual machine. The guest should have a virtio-net device, which is link= ed > to a tap interface on the host. That tap interface should be bridged with > whichever physical network adapter you want the guest connected to. > > However, I think I mentioned in a previous message that Windows does not > have the virtio-net drivers by default. You need to boot the guest with t= he > virtio-net driver ISO attached and install the driver. You should see the > interface in Device Manager flagged as not installed/working. > > -------------------------------------------- > Just one other thing to add to this. I'm not sure if this is the case > here, but it's something I've seen a few times now. > When configuring IP addresses, etc for a guest, this should be done > -inside- the guest. > Do not assign a guest's IP address to the host, or to the tap interface. > Bhyve works just like any other hypervisor. IP settings are done in the > guest as if it was a real machine, the host just acts like a switch. > -------------------------------------------- > > =E2=80=8B > This issue may be unique to Windows 2016. =E2=80=8BI've had success installing most Windows releases with exception o= f Windows 2016. Windows 10 Enterprise and others ultimately work after attaching the virtio ISO and installing the drivers by hand, however, note of caution that the 126 release of virtio drivers did not work for me. Version 102 does. This is still work in progress from my perspective.=E2=80=8B From owner-freebsd-virtualization@freebsd.org Tue Nov 1 14:16:16 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54CF7C285BC for ; Tue, 1 Nov 2016 14:16:16 +0000 (UTC) (envelope-from daniel.tihanyi@tetragir.com) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 140DA1D08 for ; Tue, 1 Nov 2016 14:16:15 +0000 (UTC) (envelope-from daniel.tihanyi@tetragir.com) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 97032206DA for ; Tue, 1 Nov 2016 10:16:14 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Tue, 01 Nov 2016 10:16:14 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=tetragir.com; h= 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=mesmtp; bh=ipJmIl+4HGwvTae pfsYvWVrOIpE=; b=PtEuz49gecKxzDcuV3xviixR6vzc7sa3TRWvxlj5v853zGY QMWVpWQAqbiTkkx26BwhIObfwKIMvR4v4etHBnE1BShO6qHL5gBjrn4uF2c7qk+L d+oh5N2ZAR8kGqz4Z3QH/R8WB0d/cbD4uFnUYGshieBeVMf13XiUwy0YBEf4= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=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= smtpout; bh=ipJmIl+4HGwvTaepfsYvWVrOIpE=; b=mJ6GM8ct1gP5+ARN6YwL Ejt7I/U7SAYyvO6YZFZNkacicjcoDUSFjvmas94OFVw1sRvkWXpX/fpXZT88nYNc ZVft0FG3ZTjzBLRKRpimh2VLwlWsSHeEzQcstMSXzsmYDqASFaaWtA0uXZMypLT7 Z/PBnhHuPGTXpMTM2HhpWaw= X-ME-Sender: X-Sasl-enc: Q+5pm/n9MjynY1FNtElqASiKaIxlDWRGrdRFJX12UZNX 1478009774 Received: from [10.25.249.127] (pd95c0bdc.dip0.t-ipconnect.de [217.92.11.220]) by mail.messagingengine.com (Postfix) with ESMTPA id F00A5F29C9 for ; Tue, 1 Nov 2016 10:16:13 -0400 (EDT) Message-ID: <1478009772.19546.74.camel@fastmail.fm> Subject: Re: Windows 2016 From: Daniel Tihanyi To: freebsd-virtualization@freebsd.org Date: Tue, 01 Nov 2016 15:16:12 +0100 In-Reply-To: <20161101140249.GB27402@doctor.nl2k.ab.ca> References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <20161101140249.GB27402@doctor.nl2k.ab.ca> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit 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, 01 Nov 2016 14:16:16 -0000 On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote: > On Tue, Nov 01, 2016 at 09:02:57AM +0000, Matt Churchyard wrote: > > > > > > > > I was able to install the Windows 2016 using the GUI method. > > > > > > One problem. > > > > > > It is assigned an IP but > > > > > > the netmask and the default route is not showing up. > > > > > > Also  The virtual Windows 2016 box does not see a network > > > interface. > > This makes very little sense. You usually specify the netmask and > > default route when you assign Windows an IP address. > > And how have you assigned the guest an IP address if it has no > > network interface? > > > The taps are allocated an IP address. > > I fully concur. > > In the install at one point, I declare that the IP address, netmask > and gateway > are 'declared' at the 'MB ' BIOS interface. > > > > > > > > > > What must I do to convince this box that is it on a switch > > On the bhyve host it should be configured just like any other bhyve > > virtual machine. The guest should have a virtio-net device, which > > is linked to a tap interface on the host. That tap interface should > > be bridged with whichever physical network adapter you want the > > guest connected to. > > > > However, I think I mentioned in a previous message that Windows > > does not have the virtio-net drivers by default. You need to boot > > the guest with the virtio-net driver ISO attached and install the > > driver. You should see the interface in Device Manager flagged as > > not installed/working. > > > > That is correct . > > I do have an iso of the MB drivers, > > namely a Supermicro  X10DRW-i MB  > > and  > > from Intel I did obtain the .exe file for the i350GbE drivers. > I script a 2 phase installation as follows: > > 1) > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/14393.0.160715- > 1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO -s 4,ahci- > hd,windows2016.img -s 5,virtio-net,tap15 -s > 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -s 30,xhci,tablet -s 31,lpc > -l com1,stdio -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd > windows2016guest > > 2) > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/null-install.iso > -s 4,ahci-hd,windows2016.img -s 5,virtio-net,tap15 -s > 29,fbuf,tcp=0.0.0.0:5900,w=1024,h=768,wait -s 30,xhci,tablet -s > 31,lpc -l com1,/dev/nmdm15A -l bootrom,/usr/local/share/uefi- > firmware/BHYVE_UEFI.fd windows2016guest & > > As I said, I have picked up an ISO from the MB manufacturer > > let's call it manufacturer.iso . > > Where do I place said iso in the 'phase' of things? You use virtio network adapters, you have to install the virtio drivers and NOT the drivers for the physical interface. Then configure the IP Address, gateway, etc. in Windows. From owner-freebsd-virtualization@freebsd.org Tue Nov 1 14:18:43 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC44EC28622 for ; Tue, 1 Nov 2016 14:18:43 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D419D11AA for ; Tue, 1 Nov 2016 14:18:43 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1c1Zti-00081j-L4; Tue, 01 Nov 2016 08:18:42 -0600 Date: Tue, 1 Nov 2016 08:18:42 -0600 From: The Doctor To: Randy Terbush Cc: "freebsd-virtualization@freebsd.org" Subject: Re: Windows 2016 Message-ID: <20161101141842.GE27402@doctor.nl2k.ab.ca> References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <51a088cbe3964542aec18bf6f1f2c4af@SERVER.ad.usd-group.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) 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, 01 Nov 2016 14:18:44 -0000 On Tue, Nov 01, 2016 at 08:08:35AM -0600, Randy Terbush wrote: > On Tue, Nov 1, 2016 at 3:21 AM, Matt Churchyard via freebsd-virtualization < > freebsd-virtualization@freebsd.org> wrote: > > > >I was able to install the Windows 2016 using the GUI method. > > > > >One proble. > > > > >It is assigned an IP but > > > > >the netmask and the default route is not showing up. > > > > >Also The virtual Windows 2016 box does not see a network interface. > > > > This makes very little sense. You usually specify the netmask and default > > route when you assign Windows an IP address. > > And how have you assigned the guest an IP address if it has no network > > interface? > > > > >What must I do to convince this box that is it on a switch > > > > On the bhyve host it should be configured just like any other bhyve > > virtual machine. The guest should have a virtio-net device, which is linked > > to a tap interface on the host. That tap interface should be bridged with > > whichever physical network adapter you want the guest connected to. > > > > However, I think I mentioned in a previous message that Windows does not > > have the virtio-net drivers by default. You need to boot the guest with the > > virtio-net driver ISO attached and install the driver. You should see the > > interface in Device Manager flagged as not installed/working. > > > > -------------------------------------------- > > Just one other thing to add to this. I'm not sure if this is the case > > here, but it's something I've seen a few times now. > > When configuring IP addresses, etc for a guest, this should be done > > -inside- the guest. > > Do not assign a guest's IP address to the host, or to the tap interface. > > Bhyve works just like any other hypervisor. IP settings are done in the > > guest as if it was a real machine, the host just acts like a switch. > > -------------------------------------------- As I said I have install recent versions of Fedora Centos and Ubuntu similarly. > > > > ??? > > > > This issue may be unique to Windows 2016. > > ???I've had success installing most Windows releases with exception of > Windows 2016. > > Windows 10 Enterprise and others ultimately work after attaching the virtio > ISO and installing the drivers by hand, however, note of caution that the > 126 release of virtio drivers did not work for me. Version 102 does. > > This is still work in progress from my perspective.??? You might be correct. iThe Win2016 Vm Does recognise the 2 IP localhost and its assigned IP but netmask and gateway are having issues. I notice a yellow triangle by the Ethernet card in Device manager. All right, is there a way inside the win2016 VM to creeate an external link to the virtual switch. > _______________________________________________ > 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" -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!! From owner-freebsd-virtualization@freebsd.org Tue Nov 1 14:22:58 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D5930C287BD for ; Tue, 1 Nov 2016 14:22:58 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BE0BF1CEF for ; Tue, 1 Nov 2016 14:22:58 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1c1Zxq-0008Ay-0v; Tue, 01 Nov 2016 08:22:58 -0600 Date: Tue, 1 Nov 2016 08:22:58 -0600 From: The Doctor To: Daniel Tihanyi Cc: freebsd-virtualization@freebsd.org Subject: Re: Windows 2016 Message-ID: <20161101142257.GF27402@doctor.nl2k.ab.ca> References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <20161101140249.GB27402@doctor.nl2k.ab.ca> <1478009772.19546.74.camel@fastmail.fm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1478009772.19546.74.camel@fastmail.fm> User-Agent: Mutt/1.7.1 (2016-10-04) 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, 01 Nov 2016 14:22:59 -0000 On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote: > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote: > > On Tue, Nov 01, 2016 at 09:02:57AM +0000, Matt Churchyard wrote: > > > > > > > > > > > I was able to install the Windows 2016 using the GUI method. > > > > > > > > One problem. > > > > > > > > It is assigned an IP but > > > > > > > > the netmask and the default route is not showing up. > > > > > > > > Also??The virtual Windows 2016 box does not see a network > > > > interface. > > > This makes very little sense. You usually specify the netmask and > > > default route when you assign Windows an IP address. > > > And how have you assigned the guest an IP address if it has no > > > network interface? > > > > > The taps are allocated an IP address. > > > > I fully concur. > > > > In the install at one point, I declare that the IP address, netmask > > and gateway > > are 'declared' at the 'MB ' BIOS interface. > > > > > > > > > > > > > > > What must I do to convince this box that is it on a switch > > > On the bhyve host it should be configured just like any other bhyve > > > virtual machine. The guest should have a virtio-net device, which > > > is linked to a tap interface on the host. That tap interface should > > > be bridged with whichever physical network adapter you want the > > > guest connected to. > > > > > > However, I think I mentioned in a previous message that Windows > > > does not have the virtio-net drivers by default. You need to boot > > > the guest with the virtio-net driver ISO attached and install the > > > driver. You should see the interface in Device Manager flagged as > > > not installed/working. > > > > > > > That is correct . > > > > I do have an iso of the MB drivers, > > > > namely a Supermicro??X10DRW-i MB? > > > > and? > > > > from Intel I did obtain the .exe file for the i350GbE drivers. > > I script a 2 phase installation as follows: > > > > 1) > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/14393.0.160715- > > 1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO -s 4,ahci- > > hd,windows2016.img -s 5,virtio-net,tap15 -s > > 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -s 30,xhci,tablet -s 31,lpc > > -l com1,stdio -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd > > windows2016guest > > > > 2) > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/null-install.iso > > -s 4,ahci-hd,windows2016.img -s 5,virtio-net,tap15 -s > > 29,fbuf,tcp=0.0.0.0:5900,w=1024,h=768,wait -s 30,xhci,tablet -s > > 31,lpc -l com1,/dev/nmdm15A -l bootrom,/usr/local/share/uefi- > > firmware/BHYVE_UEFI.fd windows2016guest & > > > > As I said, I have picked up an ISO from the MB manufacturer > > > > let's call it manufacturer.iso . > > > > Where do I place said iso in the 'phase' of things? > > You use virtio network adapters, you have to install the virtio drivers > and NOT the drivers for the physical interface. Then configure the IP > Address, gateway, etc. in Windows. All right, let me repeat what I am up aginst. I do set the IP configuration in the virtual BIOS. However when the Win2016 VM boots it sees 1) the localhost 2) its assigned IP address 3) A yellow triangle where the ethernet adaptor is. > _______________________________________________ > 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" -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!! From owner-freebsd-virtualization@freebsd.org Tue Nov 1 14:35:40 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A0B1BC28C26 for ; Tue, 1 Nov 2016 14:35:40 +0000 (UTC) (envelope-from daniel.tihanyi@tetragir.com) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 73C211AB7 for ; Tue, 1 Nov 2016 14:35:40 +0000 (UTC) (envelope-from daniel.tihanyi@tetragir.com) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 19EDE20856 for ; Tue, 1 Nov 2016 10:35:39 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Tue, 01 Nov 2016 10:35:39 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=tetragir.com; h= 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=mesmtp; bh=W5lYgzALYHnwztM 98NiA5vH5sTA=; b=Q4hJPRN9T83cPEMm5Cc0X3XsyUqsufpwg9ddV9Cp2bGydwl zYxDahzbUsK04R3n8KfXUcxpN2hVuinM2qmfpJ/0Mf3N3xh4NWe39Ha0AHm7TblV 98RGsZNOv6Q7pVIP6RShiWf2yIVeFGBgVNR4vUcxcGEb068/ICJlDrNeO1Hk= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=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= smtpout; bh=W5lYgzALYHnwztM98NiA5vH5sTA=; b=D6aMiAjH/+2tKq5bNLQU Xxsj8xF4mOL+rjxpFSyaBfA/0ykNE77DOO2NFbancMH/XOa8MnFjW38BMvlMmnNM qQ1ED27kAhRz7EIMsiH7x2qWJ7/xdk8UEa1qw8tfG5Ldwlc12mMD97XyW9sw2LDt Fuz5LHf4zulSnnzuM8fC8iI= X-ME-Sender: X-Sasl-enc: nxD8xa5VrvY88KE1kykU+n0AW3TfsB8axsLneY/Tyhfq 1478010938 Received: from [10.25.249.127] (pd95c0bdc.dip0.t-ipconnect.de [217.92.11.220]) by mail.messagingengine.com (Postfix) with ESMTPA id 74052F29CB for ; Tue, 1 Nov 2016 10:35:38 -0400 (EDT) Message-ID: <1478010937.19546.83.camel@fastmail.fm> Subject: Re: Windows 2016 From: Daniel Tihanyi To: freebsd-virtualization@freebsd.org Date: Tue, 01 Nov 2016 15:35:37 +0100 In-Reply-To: <20161101142257.GF27402@doctor.nl2k.ab.ca> References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <20161101140249.GB27402@doctor.nl2k.ab.ca> <1478009772.19546.74.camel@fastmail.fm> <20161101142257.GF27402@doctor.nl2k.ab.ca> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit 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, 01 Nov 2016 14:35:40 -0000 On Tue, 2016-11-01 at 08:22 -0600, The Doctor wrote: > On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote: > > > > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote: > > > > > > On Tue, Nov 01, 2016 at 09:02:57AM +0000, Matt Churchyard wrote: > > > > > > > > > > > > > > > > > > > > > > > I was able to install the Windows 2016 using the GUI method. > > > > > > > > > > One problem. > > > > > > > > > > It is assigned an IP but > > > > > > > > > > the netmask and the default route is not showing up. > > > > > > > > > > Also??The virtual Windows 2016 box does not see a network > > > > > interface. > > > > This makes very little sense. You usually specify the netmask > > > > and > > > > default route when you assign Windows an IP address. > > > > And how have you assigned the guest an IP address if it has no > > > > network interface? > > > > > > > The taps are allocated an IP address. > > > > > > I fully concur. > > > > > > In the install at one point, I declare that the IP address, > > > netmask > > > and gateway > > > are 'declared' at the 'MB ' BIOS interface. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > What must I do to convince this box that is it on a switch > > > > On the bhyve host it should be configured just like any other > > > > bhyve > > > > virtual machine. The guest should have a virtio-net device, > > > > which > > > > is linked to a tap interface on the host. That tap interface > > > > should > > > > be bridged with whichever physical network adapter you want the > > > > guest connected to. > > > > > > > > However, I think I mentioned in a previous message that Windows > > > > does not have the virtio-net drivers by default. You need to > > > > boot > > > > the guest with the virtio-net driver ISO attached and install > > > > the > > > > driver. You should see the interface in Device Manager flagged > > > > as > > > > not installed/working. > > > > > > > That is correct . > > > > > > I do have an iso of the MB drivers, > > > > > > namely a Supermicro??X10DRW-i MB? > > > > > > and? > > > > > > from Intel I did obtain the .exe file for the i350GbE drivers. > > > I script a 2 phase installation as follows: > > > > > > 1) > > > > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci- > > > cd,./.iso/14393.0.160715- > > > 1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO -s 4,ahci- > > > hd,windows2016.img -s 5,virtio-net,tap15 -s > > > 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -s 30,xhci,tablet -s > > > 31,lpc > > > -l com1,stdio -l bootrom,/usr/local/share/uefi- > > > firmware/BHYVE_UEFI.fd  > > > windows2016guest > > > > > > 2) > > > > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/null- > > > install.iso  > > > -s 4,ahci-hd,windows2016.img -s 5,virtio-net,tap15 -s > > > 29,fbuf,tcp=0.0.0.0:5900,w=1024,h=768,wait -s 30,xhci,tablet -s > > > 31,lpc -l com1,/dev/nmdm15A -l bootrom,/usr/local/share/uefi- > > > firmware/BHYVE_UEFI.fd windows2016guest & > > > > > > As I said, I have picked up an ISO from the MB manufacturer > > > > > > let's call it manufacturer.iso . > > > > > > Where do I place said iso in the 'phase' of things? > > You use virtio network adapters, you have to install the virtio > > drivers > > and NOT the drivers for the physical interface. Then configure the > > IP > > Address, gateway, etc. in Windows. > All right, let me repeat what I am up aginst. > > I do set the IP configuration in the virtual BIOS. > > However when the Win2016 VM boots it sees > > 1) the localhost > > 2) its assigned IP address > > 3) A yellow triangle where the ethernet adaptor is. > > I don't really understand, what do you mean by virtual BIOS. If you boot up Windows, configure the IP Address, etc from there. Follow this guide to do so: https://ittutorials.net/microsoft/windows-server-2016/s et-windows-server-2016-with-a-static-ip-address/ From owner-freebsd-virtualization@freebsd.org Tue Nov 1 14:59:30 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8105FC285AD for ; Tue, 1 Nov 2016 14:59:30 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-outbound.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.userve.net", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 356CA12A3 for ; Tue, 1 Nov 2016 14:59:29 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) by smtp-outbound.userve.net (8.15.1/8.15.1) with ESMTPS id uA1Ex2MG071909 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 1 Nov 2016 14:59:03 GMT (envelope-from matt.churchyard@userve.net) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=201508; t=1478012347; bh=YLqUnvzrb92mbq3tb24rctNMgO4r4g06akTxcvt2ZdI=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=Y/hDyXkYgT1+kAwJQ26Faj3s2szYjT6ooiNMiukods5wDutImXzpEKRgxCA3ttmDQ qZ46YBEaidCKMlz20a5AkZ8QbSRMF5bR+JHsDcIy6Hh+KxIwXNzyxKhqqnsgUbzAlE fFf0mlokmW/wNfCagBEcpnOGNrDKhCFq/Gjjx2xA= Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Tue, 1 Nov 2016 14:58:57 +0000 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Tue, 1 Nov 2016 14:58:57 +0000 From: Matt Churchyard To: The Doctor , Daniel Tihanyi CC: "freebsd-virtualization@freebsd.org" Subject: RE: Windows 2016 Thread-Topic: Windows 2016 Thread-Index: AQHSNEil+zRmbvXF3EKEgyLLpp/j2qDELG0AgAAB5ACAAAZGAA== Date: Tue, 1 Nov 2016 14:58:56 +0000 Message-ID: References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <20161101140249.GB27402@doctor.nl2k.ab.ca> <1478009772.19546.74.camel@fastmail.fm> <20161101142257.GF27402@doctor.nl2k.ab.ca> In-Reply-To: <20161101142257.GF27402@doctor.nl2k.ab.ca> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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: Tue, 01 Nov 2016 14:59:30 -0000 On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote: > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote: > > On Tue, Nov 01, 2016 at 09:02:57AM +0000, Matt Churchyard wrote: > > >=20 > > > >=20 > > > > I was able to install the Windows 2016 using the GUI method. > > > >=20 > > > > One problem. > > > >=20 > > > > It is assigned an IP but > > > >=20 > > > > the netmask and the default route is not showing up. > > > >=20 > > > > Also??The virtual Windows 2016 box does not see a network=20 > > > > interface. > > > This makes very little sense. You usually specify the netmask and=20 > > > default route when you assign Windows an IP address. > > > And how have you assigned the guest an IP address if it has no=20 > > > network interface? > > >=20 > > The taps are allocated an IP address. > >=20 > > I fully concur. > >=20 > > In the install at one point, I declare that the IP address, netmask=20 > > and gateway are 'declared' at the 'MB ' BIOS interface. > >=20 > >=20 > > >=20 > > > >=20 > > > > What must I do to convince this box that is it on a switch > > > On the bhyve host it should be configured just like any other=20 > > > bhyve virtual machine. The guest should have a virtio-net device,=20 > > > which is linked to a tap interface on the host. That tap interface=20 > > > should be bridged with whichever physical network adapter you want=20 > > > the guest connected to. > > >=20 > > > However, I think I mentioned in a previous message that Windows=20 > > > does not have the virtio-net drivers by default. You need to boot=20 > > > the guest with the virtio-net driver ISO attached and install the=20 > > > driver. You should see the interface in Device Manager flagged as=20 > > > not installed/working. > > >=20 > >=20 > > That is correct . > >=20 > > I do have an iso of the MB drivers, > >=20 > > namely a Supermicro??X10DRW-i MB? > >=20 > > and? > >=20 > > from Intel I did obtain the .exe file for the i350GbE drivers. > > I script a 2 phase installation as follows: > >=20 > > 1) > >=20 > >=20 > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/14393.0.160715-=20 > > 1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO -s 4,ahci-=20 > > hd,windows2016.img -s 5,virtio-net,tap15 -s=20 > > 29,fbuf,tcp=3D0.0.0.0:5900,w=3D800,h=3D600,wait -s 30,xhci,tablet -s=20 > > 31,lpc -l com1,stdio -l=20 > > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd > > windows2016guest > >=20 > > 2) > >=20 > >=20 > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s=20 > > 3,ahci-cd,./.iso/null-install.iso -s 4,ahci-hd,windows2016.img -s=20 > > 5,virtio-net,tap15 -s 29,fbuf,tcp=3D0.0.0.0:5900,w=3D1024,h=3D768,wait = -s=20 > > 30,xhci,tablet -s 31,lpc -l com1,/dev/nmdm15A -l=20 > > bootrom,/usr/local/share/uefi- firmware/BHYVE_UEFI.fd=20 > > windows2016guest & > >=20 > > As I said, I have picked up an ISO from the MB manufacturer > >=20 > > let's call it manufacturer.iso . > >=20 > > Where do I place said iso in the 'phase' of things? >=20 > You use virtio network adapters, you have to install the virtio=20 > drivers and NOT the drivers for the physical interface. Then configure=20 > the IP Address, gateway, etc. in Windows. >All right, let me repeat what I am up aginst. >I do set the IP configuration in the virtual BIOS. >However when the Win2016 VM boots it sees >1) the localhost >2) its assigned IP address >3) A yellow triangle where the ethernet adaptor is. I'm not sure what people find so difficult about this - Just treat it like = it was a real Windows machine 1) Do not assign the guest's IP address on the host 2) Do not set the IP in the guest BIOS (I'm not even sure what you mean by = this) As you have found, the virtio-net network adapter has a yellow triangle in = Windows, because it is not installed. You need to run bhyve but replace the= Windows ISO with the virtio-net driver ISO, which you can download off the= Internet; Then install the network driver through VNC. The guest has a "vi= rtio-net" interface which is created by bhyve - This has nothing to do with= your motherboard and you do not need to install any of the motherboard or = physical interface drivers in the guest. Once you have the virtio driver installed, you will have a "Redhat VirtIO" = network adapter in Windows, and you can assign an IP/Netmask/Gateway to thi= s just as you normally would in Windows. Forget about the Linux machines. They have the virtio-net driver built in, = so you can just configure eth0 out-of-the-box like normal. If you've config= ured their IP addresses on the bhyve host then that's not really the correc= t way to configure things, even if it doesn't actually break anything; The = IP address should be configured inside the guest OS. Matt From owner-freebsd-virtualization@freebsd.org Tue Nov 1 15:13:16 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3814BC28C33 for ; Tue, 1 Nov 2016 15:13:16 +0000 (UTC) (envelope-from randy@terbush.org) Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (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 021431A48 for ; Tue, 1 Nov 2016 15:13:15 +0000 (UTC) (envelope-from randy@terbush.org) Received: by mail-qk0-x231.google.com with SMTP id o68so202944174qkf.3 for ; Tue, 01 Nov 2016 08:13:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=terbush.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xvLMK2spjUpmGK4v3P7aDGMFfpX6S57hbfjwQRMn3LI=; b=inWx/SgVHRK65/9hBz+Yrki0mFWgk5UmoEtrhUn88VSHbtmOQzXrUcTnNxPAL5ftLr 5B3aLhErZXoUPXqBH77StNLhWEm4Vp9X7bZHueRrxG7gCr7a4Bc4QknzM8GyW4ifB2Jo bzoZaIdpxw+E4w4f7VAj+cl7ZOpJ2AWXJJSC4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xvLMK2spjUpmGK4v3P7aDGMFfpX6S57hbfjwQRMn3LI=; b=IuvUipwEfbVFn20P8U0VWKPgvqeYnd0I6oU4jxGBtKlX9ysyY28K8t8mvWXFbKcgwu KeCESrz2LIF9A3CaPNWRWmb6WnRj/6W/gkWNEQ46xmjZxphPBTzgvMXzaRbLVH9bzd1O bOflkLz9KdvmKSaGh0I3kxxEVOLF5CgWhXOfryhxXESNas9bQXPwIAznE95A17FcSm6k yBvmN3bJoBpZpd35G7I87ISu1gmmd8oz8FmK1E9VeaFmjjkFXieLgMtS8Na01Wajo/8O A+BeRKB3ExayIUa2oJKXYTMhc1CRLROYd19degmpIFAO+AXYcfNN3epTJ8azXJJRym0v XZ/w== X-Gm-Message-State: ABUngveKC2nxaPKjdEEmJYX37+2mbq2+5S53UjgwJ0fsTEI2yyGC0sU64PoRWNnEJOOVNKWdlnDt919ueOy3Fw== X-Received: by 10.55.103.133 with SMTP id b127mr15663352qkc.16.1478013195103; Tue, 01 Nov 2016 08:13:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.51.82 with HTTP; Tue, 1 Nov 2016 08:12:44 -0700 (PDT) In-Reply-To: References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <20161101140249.GB27402@doctor.nl2k.ab.ca> <1478009772.19546.74.camel@fastmail.fm> <20161101142257.GF27402@doctor.nl2k.ab.ca> From: Randy Terbush Date: Tue, 1 Nov 2016 09:12:44 -0600 Message-ID: Subject: Re: Windows 2016 To: Matt Churchyard Cc: The Doctor , Daniel Tihanyi , "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, 01 Nov 2016 15:13:16 -0000 On Tue, Nov 1, 2016 at 8:58 AM, Matt Churchyard via freebsd-virtualization = < freebsd-virtualization@freebsd.org> wrote: > On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote: > > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote: > > > On Tue, Nov 01, 2016 at 09:02:57AM +0000, Matt Churchyard wrote: > > > > > > > > > > > > > > I was able to install the Windows 2016 using the GUI method. > > > > > > > > > > One problem. > > > > > > > > > > It is assigned an IP but > > > > > > > > > > the netmask and the default route is not showing up. > > > > > > > > > > Also??The virtual Windows 2016 box does not see a network > > > > > interface. > > > > This makes very little sense. You usually specify the netmask and > > > > default route when you assign Windows an IP address. > > > > And how have you assigned the guest an IP address if it has no > > > > network interface? > > > > > > > The taps are allocated an IP address. > > > > > > I fully concur. > > > > > > In the install at one point, I declare that the IP address, netmask > > > and gateway are 'declared' at the 'MB ' BIOS interface. > > > > > > > > > > > > > > > > > > > > What must I do to convince this box that is it on a switch > > > > On the bhyve host it should be configured just like any other > > > > bhyve virtual machine. The guest should have a virtio-net device, > > > > which is linked to a tap interface on the host. That tap interface > > > > should be bridged with whichever physical network adapter you want > > > > the guest connected to. > > > > > > > > However, I think I mentioned in a previous message that Windows > > > > does not have the virtio-net drivers by default. You need to boot > > > > the guest with the virtio-net driver ISO attached and install the > > > > driver. You should see the interface in Device Manager flagged as > > > > not installed/working. > > > > > > > > > > That is correct . > > > > > > I do have an iso of the MB drivers, > > > > > > namely a Supermicro??X10DRW-i MB? > > > > > > and? > > > > > > from Intel I did obtain the .exe file for the i350GbE drivers. > > > I script a 2 phase installation as follows: > > > > > > 1) > > > > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/14393.0.160715- > > > 1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO -s 4,ahci- > > > hd,windows2016.img -s 5,virtio-net,tap15 -s > > > 29,fbuf,tcp=3D0.0.0.0:5900,w=3D800,h=3D600,wait -s 30,xhci,tablet -s > > > 31,lpc -l com1,stdio -l > > > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd > > > windows2016guest > > > > > > 2) > > > > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s > > > 3,ahci-cd,./.iso/null-install.iso -s 4,ahci-hd,windows2016.img -s > > > 5,virtio-net,tap15 -s 29,fbuf,tcp=3D0.0.0.0:5900,w=3D1024,h=3D768,wai= t -s > > > 30,xhci,tablet -s 31,lpc -l com1,/dev/nmdm15A -l > > > bootrom,/usr/local/share/uefi- firmware/BHYVE_UEFI.fd > > > windows2016guest & > > > > > > As I said, I have picked up an ISO from the MB manufacturer > > > > > > let's call it manufacturer.iso . > > > > > > Where do I place said iso in the 'phase' of things? > > > > You use virtio network adapters, you have to install the virtio > > drivers and NOT the drivers for the physical interface. Then configure > > the IP Address, gateway, etc. in Windows. > > >All right, let me repeat what I am up aginst. > > >I do set the IP configuration in the virtual BIOS. > > >However when the Win2016 VM boots it sees > > >1) the localhost > > >2) its assigned IP address > > >3) A yellow triangle where the ethernet adaptor is. > > I'm not sure what people find so difficult about this - Just treat it lik= e > it was a real Windows machine > > 1) Do not assign the guest's IP address on the host > 2) Do not set the IP in the guest BIOS (I'm not even sure what you mean b= y > this) > > As you have found, the virtio-net network adapter has a yellow triangle i= n > Windows, because it is not installed. You need to run bhyve but replace t= he > Windows ISO with the virtio-net driver ISO, which you can download off th= e > Internet; Then install the network driver through VNC. The guest has a > "virtio-net" interface which is created by bhyve - This has nothing to do > with your motherboard and you do not need to install any of the motherboa= rd > or physical interface drivers in the guest. > > Once you have the virtio driver installed, you will have a "Redhat VirtIO= " > network adapter in Windows, and you can assign an IP/Netmask/Gateway to > this just as you normally would in Windows. > > Forget about the Linux machines. They have the virtio-net driver built in= , > so you can just configure eth0 out-of-the-box like normal. If you've > configured their IP addresses on the bhyve host then that's not really th= e > correct way to configure things, even if it doesn't actually break > anything; The IP address should be configured inside the guest OS. > > Matt > > =E2=80=8BCan you guys confirm that you actually have a Windows 2016 vm runn= ing? As I have said, I have installed nearly every version of Windows OS vms with Bhyve (vm-bhyve) successfully with the exception of Windows 2016. DHCP does not work. Assigning an address by hand does not work. Any attempt to configure the IP on the network device or even uninstall it just results in long delays and spinning cursors. If you've got this working, I would love to see a vm-bhyve template and to know what virtio driver package version you are using. =E2=80=8B From owner-freebsd-virtualization@freebsd.org Tue Nov 1 15:22:18 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9916C290C4 for ; Tue, 1 Nov 2016 15:22:18 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-outbound.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.userve.net", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48680144B for ; Tue, 1 Nov 2016 15:22:17 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) by smtp-outbound.userve.net (8.15.1/8.15.1) with ESMTPS id uA1FLp3f097383 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 1 Nov 2016 15:21:51 GMT (envelope-from matt.churchyard@userve.net) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=201508; t=1478013713; bh=nFl6HBfd1ElCNh0T6TURO/u7K+wpRR0XU0o67uydZyk=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=Ci6Eup64RKWZlz5tjLkTAg1/Kr4wkKvHmB5zIF5zMgbiCyvVjRUMli0szgpq51ZiV xbaFgShgwA09VprtY5Bg2Okmp7/VzXtKbT7H8IxO3gQxzNbfNSVY6Yc4a3VGy3PmyV 0PXrnPVim/LfXY1lNggiO85b5BTPBPoSjVmOZI3Q= Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Tue, 1 Nov 2016 15:21:46 +0000 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Tue, 1 Nov 2016 15:21:45 +0000 From: Matt Churchyard To: Randy Terbush CC: The Doctor , Daniel Tihanyi , "freebsd-virtualization@freebsd.org" Subject: RE: Windows 2016 Thread-Topic: Windows 2016 Thread-Index: AQHSNEil+zRmbvXF3EKEgyLLpp/j2qDELG0AgAAB5ACAAAZGAIAAB6IAgAABGGA= Date: Tue, 1 Nov 2016 15:21:45 +0000 Message-ID: References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <20161101140249.GB27402@doctor.nl2k.ab.ca> <1478009772.19546.74.camel@fastmail.fm> <20161101142257.GF27402@doctor.nl2k.ab.ca> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2016 15:22:18 -0000 T24gVHVlLCBOb3YgMSwgMjAxNiBhdCA4OjU4IEFNLCBNYXR0IENodXJjaHlhcmQgdmlhIGZyZWVi c2QtdmlydHVhbGl6YXRpb24gPGZyZWVic2QtdmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc8bWFp bHRvOmZyZWVic2QtdmlydHVhbGl6YXRpb25AZnJlZWJzZC5vcmc+PiB3cm90ZToNCk9uIFR1ZSwg Tm92IDAxLCAyMDE2IGF0IDAzOjE2OjEyUE0gKzAxMDAsIERhbmllbCBUaWhhbnlpIHdyb3RlOg0K PiBPbiBUdWUsIDIwMTYtMTEtMDEgYXQgMDg6MDIgLTA2MDAsIFRoZSBEb2N0b3Igd3JvdGU6DQo+ ID4gT24gVHVlLCBOb3YgMDEsIDIwMTYgYXQgMDk6MDI6NTdBTSArMDAwMCwgTWF0dCBDaHVyY2h5 YXJkIHdyb3RlOg0KPiA+ID4NCj4gPiA+ID4NCj4gPiA+ID4gSSB3YXMgYWJsZSB0byBpbnN0YWxs IHRoZSBXaW5kb3dzIDIwMTYgdXNpbmcgdGhlIEdVSSBtZXRob2QuDQo+ID4gPiA+DQo+ID4gPiA+ IE9uZSBwcm9ibGVtLg0KPiA+ID4gPg0KPiA+ID4gPiBJdCBpcyBhc3NpZ25lZCBhbiBJUCBidXQN Cj4gPiA+ID4NCj4gPiA+ID4gdGhlIG5ldG1hc2sgYW5kIHRoZSBkZWZhdWx0IHJvdXRlIGlzIG5v dCBzaG93aW5nIHVwLg0KPiA+ID4gPg0KPiA+ID4gPiBBbHNvPz9UaGUgdmlydHVhbCBXaW5kb3dz IDIwMTYgYm94IGRvZXMgbm90IHNlZSBhIG5ldHdvcmsNCj4gPiA+ID4gaW50ZXJmYWNlLg0KPiA+ ID4gVGhpcyBtYWtlcyB2ZXJ5IGxpdHRsZSBzZW5zZS4gWW91IHVzdWFsbHkgc3BlY2lmeSB0aGUg bmV0bWFzayBhbmQNCj4gPiA+IGRlZmF1bHQgcm91dGUgd2hlbiB5b3UgYXNzaWduIFdpbmRvd3Mg YW4gSVAgYWRkcmVzcy4NCj4gPiA+IEFuZCBob3cgaGF2ZSB5b3UgYXNzaWduZWQgdGhlIGd1ZXN0 IGFuIElQIGFkZHJlc3MgaWYgaXQgaGFzIG5vDQo+ID4gPiBuZXR3b3JrIGludGVyZmFjZT8NCj4g PiA+DQo+ID4gVGhlIHRhcHMgYXJlIGFsbG9jYXRlZCBhbiBJUCBhZGRyZXNzLg0KPiA+DQo+ID4g SSBmdWxseSBjb25jdXIuDQo+ID4NCj4gPiBJbiB0aGUgaW5zdGFsbCBhdCBvbmUgcG9pbnQsIEkg ZGVjbGFyZSB0aGF0IHRoZSBJUCBhZGRyZXNzLCBuZXRtYXNrDQo+ID4gYW5kIGdhdGV3YXkgYXJl ICdkZWNsYXJlZCcgYXQgdGhlICdNQiAnIEJJT1MgaW50ZXJmYWNlLg0KPiA+DQo+ID4NCj4gPiA+ DQo+ID4gPiA+DQo+ID4gPiA+IFdoYXQgbXVzdCBJIGRvIHRvIGNvbnZpbmNlIHRoaXMgYm94IHRo YXQgaXMgaXQgb24gYSBzd2l0Y2gNCj4gPiA+IE9uIHRoZSBiaHl2ZSBob3N0IGl0IHNob3VsZCBi ZSBjb25maWd1cmVkIGp1c3QgbGlrZSBhbnkgb3RoZXINCj4gPiA+IGJoeXZlIHZpcnR1YWwgbWFj aGluZS4gVGhlIGd1ZXN0IHNob3VsZCBoYXZlIGEgdmlydGlvLW5ldCBkZXZpY2UsDQo+ID4gPiB3 aGljaCBpcyBsaW5rZWQgdG8gYSB0YXAgaW50ZXJmYWNlIG9uIHRoZSBob3N0LiBUaGF0IHRhcCBp bnRlcmZhY2UNCj4gPiA+IHNob3VsZCBiZSBicmlkZ2VkIHdpdGggd2hpY2hldmVyIHBoeXNpY2Fs IG5ldHdvcmsgYWRhcHRlciB5b3Ugd2FudA0KPiA+ID4gdGhlIGd1ZXN0IGNvbm5lY3RlZCB0by4N Cj4gPiA+DQo+ID4gPiBIb3dldmVyLCBJIHRoaW5rIEkgbWVudGlvbmVkIGluIGEgcHJldmlvdXMg bWVzc2FnZSB0aGF0IFdpbmRvd3MNCj4gPiA+IGRvZXMgbm90IGhhdmUgdGhlIHZpcnRpby1uZXQg ZHJpdmVycyBieSBkZWZhdWx0LiBZb3UgbmVlZCB0byBib290DQo+ID4gPiB0aGUgZ3Vlc3Qgd2l0 aCB0aGUgdmlydGlvLW5ldCBkcml2ZXIgSVNPIGF0dGFjaGVkIGFuZCBpbnN0YWxsIHRoZQ0KPiA+ ID4gZHJpdmVyLiBZb3Ugc2hvdWxkIHNlZSB0aGUgaW50ZXJmYWNlIGluIERldmljZSBNYW5hZ2Vy IGZsYWdnZWQgYXMNCj4gPiA+IG5vdCBpbnN0YWxsZWQvd29ya2luZy4NCj4gPiA+DQo+ID4NCj4g PiBUaGF0IGlzIGNvcnJlY3QgLg0KPiA+DQo+ID4gSSBkbyBoYXZlIGFuIGlzbyBvZiB0aGUgTUIg ZHJpdmVycywNCj4gPg0KPiA+IG5hbWVseSBhIFN1cGVybWljcm8/P1gxMERSVy1pIE1CPw0KPiA+ DQo+ID4gYW5kPw0KPiA+DQo+ID4gZnJvbSBJbnRlbCBJIGRpZCBvYnRhaW4gdGhlIC5leGUgZmls ZSBmb3IgdGhlIGkzNTBHYkUgZHJpdmVycy4NCj4gPiBJIHNjcmlwdCBhIDIgcGhhc2UgaW5zdGFs bGF0aW9uIGFzIGZvbGxvd3M6DQo+ID4NCj4gPiAxKQ0KPiA+DQo+ID4NCj4gPiAvdXNyL3NiaW4v Ymh5dmUgLWMgMiAtbSA0RyAtdyAtSCAtcyAzLGFoY2ktY2QsLi8uaXNvLzE0MzkzLjAuMTYwNzE1 LQ0KPiA+IDE2MTYuUlMxX1JFTEVBU0VfU0VSVkVSX0VWQUxfWDY0RlJFX0VOLVVTLklTTyAtcyA0 LGFoY2ktDQo+ID4gaGQsd2luZG93czIwMTYuaW1nIC1zIDUsdmlydGlvLW5ldCx0YXAxNSAtcw0K PiA+IDI5LGZidWYsdGNwPTAuMC4wLjA6NTkwMDxodHRwOi8vMC4wLjAuMDo1OTAwPix3PTgwMCxo PTYwMCx3YWl0IC1zIDMwLHhoY2ksdGFibGV0IC1zDQo+ID4gMzEsbHBjIC1sIGNvbTEsc3RkaW8g LWwNCj4gPiBib290cm9tLC91c3IvbG9jYWwvc2hhcmUvdWVmaS1maXJtd2FyZS9CSFlWRV9VRUZJ LmZkDQo+ID4gd2luZG93czIwMTZndWVzdA0KPiA+DQo+ID4gMikNCj4gPg0KPiA+DQo+ID4gL3Vz ci9zYmluL2JoeXZlIC1jIDIgLW0gNEcgLXcgLUggLXMNCj4gPiAzLGFoY2ktY2QsLi8uaXNvL251 bGwtaW5zdGFsbC5pc28gLXMgNCxhaGNpLWhkLHdpbmRvd3MyMDE2LmltZyAtcw0KPiA+IDUsdmly dGlvLW5ldCx0YXAxNSAtcyAyOSxmYnVmLHRjcD0wLjAuMC4wOjU5MDA8aHR0cDovLzAuMC4wLjA6 NTkwMD4sdz0xMDI0LGg9NzY4LHdhaXQgLXMNCj4gPiAzMCx4aGNpLHRhYmxldCAtcyAzMSxscGMg LWwgY29tMSwvZGV2L25tZG0xNUEgLWwNCj4gPiBib290cm9tLC91c3IvbG9jYWwvc2hhcmUvdWVm aS0gZmlybXdhcmUvQkhZVkVfVUVGSS5mZA0KPiA+IHdpbmRvd3MyMDE2Z3Vlc3QgJg0KPiA+DQo+ ID4gQXMgSSBzYWlkLCBJIGhhdmUgcGlja2VkIHVwIGFuIElTTyBmcm9tIHRoZSBNQiBtYW51ZmFj dHVyZXINCj4gPg0KPiA+IGxldCdzIGNhbGwgaXQgbWFudWZhY3R1cmVyLmlzbyAuDQo+ID4NCj4g PiBXaGVyZSBkbyBJIHBsYWNlIHNhaWQgaXNvIGluIHRoZSAncGhhc2UnIG9mIHRoaW5ncz8NCj4N Cj4gWW91IHVzZSB2aXJ0aW8gbmV0d29yayBhZGFwdGVycywgeW91IGhhdmUgdG8gaW5zdGFsbCB0 aGUgdmlydGlvDQo+IGRyaXZlcnMgYW5kIE5PVCB0aGUgZHJpdmVycyBmb3IgdGhlIHBoeXNpY2Fs IGludGVyZmFjZS4gVGhlbiBjb25maWd1cmUNCj4gdGhlIElQIEFkZHJlc3MsIGdhdGV3YXksIGV0 Yy4gaW4gV2luZG93cy4NCg0KPkFsbCByaWdodCwgbGV0IG1lIHJlcGVhdCB3aGF0IEkgYW0gdXAg YWdpbnN0Lg0KDQo+SSBkbyBzZXQgdGhlIElQIGNvbmZpZ3VyYXRpb24gaW4gdGhlIHZpcnR1YWwg QklPUy4NCg0KPkhvd2V2ZXIgd2hlbiB0aGUgV2luMjAxNiBWTSBib290cyBpdCBzZWVzDQoNCj4x KSB0aGUgbG9jYWxob3N0DQoNCj4yKSBpdHMgYXNzaWduZWQgSVAgYWRkcmVzcw0KDQo+MykgQSB5 ZWxsb3cgdHJpYW5nbGUgd2hlcmUgdGhlIGV0aGVybmV0IGFkYXB0b3IgaXMuDQpJJ20gbm90IHN1 cmUgd2hhdCBwZW9wbGUgZmluZCBzbyBkaWZmaWN1bHQgYWJvdXQgdGhpcyAtIEp1c3QgdHJlYXQg aXQgbGlrZSBpdCB3YXMgYSByZWFsIFdpbmRvd3MgbWFjaGluZQ0KDQoxKSBEbyBub3QgYXNzaWdu IHRoZSBndWVzdCdzIElQIGFkZHJlc3Mgb24gdGhlIGhvc3QNCjIpIERvIG5vdCBzZXQgdGhlIElQ IGluIHRoZSBndWVzdCBCSU9TIChJJ20gbm90IGV2ZW4gc3VyZSB3aGF0IHlvdSBtZWFuIGJ5IHRo aXMpDQoNCkFzIHlvdSBoYXZlIGZvdW5kLCB0aGUgdmlydGlvLW5ldCBuZXR3b3JrIGFkYXB0ZXIg aGFzIGEgeWVsbG93IHRyaWFuZ2xlIGluIFdpbmRvd3MsIGJlY2F1c2UgaXQgaXMgbm90IGluc3Rh bGxlZC4gWW91IG5lZWQgdG8gcnVuIGJoeXZlIGJ1dCByZXBsYWNlIHRoZSBXaW5kb3dzIElTTyB3 aXRoIHRoZSB2aXJ0aW8tbmV0IGRyaXZlciBJU08sIHdoaWNoIHlvdSBjYW4gZG93bmxvYWQgb2Zm IHRoZSBJbnRlcm5ldDsgVGhlbiBpbnN0YWxsIHRoZSBuZXR3b3JrIGRyaXZlciB0aHJvdWdoIFZO Qy4gVGhlIGd1ZXN0IGhhcyBhICJ2aXJ0aW8tbmV0IiBpbnRlcmZhY2Ugd2hpY2ggaXMgY3JlYXRl ZCBieSBiaHl2ZSAtIFRoaXMgaGFzIG5vdGhpbmcgdG8gZG8gd2l0aCB5b3VyIG1vdGhlcmJvYXJk IGFuZCB5b3UgZG8gbm90IG5lZWQgdG8gaW5zdGFsbCBhbnkgb2YgdGhlIG1vdGhlcmJvYXJkIG9y IHBoeXNpY2FsIGludGVyZmFjZSBkcml2ZXJzIGluIHRoZSBndWVzdC4NCg0KT25jZSB5b3UgaGF2 ZSB0aGUgdmlydGlvIGRyaXZlciBpbnN0YWxsZWQsIHlvdSB3aWxsIGhhdmUgYSAiUmVkaGF0IFZp cnRJTyIgbmV0d29yayBhZGFwdGVyIGluIFdpbmRvd3MsIGFuZCB5b3UgY2FuIGFzc2lnbiBhbiBJ UC9OZXRtYXNrL0dhdGV3YXkgdG8gdGhpcyBqdXN0IGFzIHlvdSBub3JtYWxseSB3b3VsZCBpbiBX aW5kb3dzLg0KDQpGb3JnZXQgYWJvdXQgdGhlIExpbnV4IG1hY2hpbmVzLiBUaGV5IGhhdmUgdGhl IHZpcnRpby1uZXQgZHJpdmVyIGJ1aWx0IGluLCBzbyB5b3UgY2FuIGp1c3QgY29uZmlndXJlIGV0 aDAgb3V0LW9mLXRoZS1ib3ggbGlrZSBub3JtYWwuIElmIHlvdSd2ZSBjb25maWd1cmVkIHRoZWly IElQIGFkZHJlc3NlcyBvbiB0aGUgYmh5dmUgaG9zdCB0aGVuIHRoYXQncyBub3QgcmVhbGx5IHRo ZSBjb3JyZWN0IHdheSB0byBjb25maWd1cmUgdGhpbmdzLCBldmVuIGlmIGl0IGRvZXNuJ3QgYWN0 dWFsbHkgYnJlYWsgYW55dGhpbmc7IFRoZSBJUCBhZGRyZXNzIHNob3VsZCBiZSBjb25maWd1cmVk IGluc2lkZSB0aGUgZ3Vlc3QgT1MuDQoNCk1hdHQNCg0KDQrigIs+Q2FuIHlvdSBndXlzIGNvbmZp cm0gdGhhdCB5b3UgYWN0dWFsbHkgaGF2ZSBhIFdpbmRvd3MgMjAxNiB2bSBydW5uaW5nPw0KDQo+ QXMgSSBoYXZlIHNhaWQsIEkgaGF2ZSBpbnN0YWxsZWQgbmVhcmx5IGV2ZXJ5IHZlcnNpb24gb2Yg V2luZG93cyBPUyB2bXMgd2l0aCBCaHl2ZSAodm0tYmh5dmUpIHN1Y2Nlc3NmdWxseSB3aXRoIHRo ZSA+ZXhjZXB0aW9uIG9mIFdpbmRvd3MgMjAxNi4NCg0KPkRIQ1AgZG9lcyBub3Qgd29yay4gQXNz aWduaW5nIGFuIGFkZHJlc3MgYnkgaGFuZCBkb2VzIG5vdCB3b3JrLiBBbnkgYXR0ZW1wdCB0byBj b25maWd1cmUgdGhlIElQIG9uIHRoZSBuZXR3b3JrIGRldmljZSBvciA+ZXZlbiB1bmluc3RhbGwg aXQganVzdCByZXN1bHRzIGluIGxvbmcgZGVsYXlzIGFuZCBzcGlubmluZyBjdXJzb3JzLg0KDQo+ SWYgeW91J3ZlIGdvdCB0aGlzIHdvcmtpbmcsIEkgd291bGQgbG92ZSB0byBzZWUgYSB2bS1iaHl2 ZSB0ZW1wbGF0ZSBhbmQgdG8ga25vdyB3aGF0IHZpcnRpbyBkcml2ZXIgcGFja2FnZSB2ZXJzaW9u IHlvdSBhcmUgPnVzaW5nLg0K4oCLDQpJIGhhdmUgV2luZG93cyAyMDE2IEV2YWx1YXRpb24gcnVu bmluZyB3aXRob3V0IGFueSBwcm9ibGVtcy4gLSBodHRwOi8vaW1ndXIuY29tL2EvYjlkd3MNCg0K VGhlIGNvbmZpZ3VyYXRpb24gZm9yIHZtLWJoeXZlIEnigJltIHVzaW5nIGlzIGJlbG93IChJIGFj dHVhbGx5IHdyb3RlIHZtLWJoeXZlKS4NCkkgdXNlZCB2aXJ0aW8td2luLTAuMS4xMTguaXNvIGFz IHRoYXQgaGFwcGVucyB0byBiZSB3aGF0IEkgaGFkIGx5aW5nIGFyb3VuZCBhdCB0aGUgdGltZS4g SeKAmXZlIG5vIGlkZWEgd2hhdCBvdGhlciB2aXJ0aW8gZHJpdmVyIHZlcnNpb25zIGFyZSBsaWtl Lg0KVGhlIGd1ZXN0IGlzIGN1cnJlbnRseSB1c2luZyBESENQIGFsdGhvdWdoIEkgaGF2ZSBubyBy ZWFzb24gdG8gc3VzcGVjdCB0aGVyZeKAmWQgYmUgYSBwcm9ibGVtIGFzc2lnbmluZyBhIHN0YXRp Yy4NCg0KdWVmaT0ieWVzIg0KZ3JhcGhpY3M9InllcyINCmdyYXBoaWNzX3Jlcz0iMTI4MHg3MjAi DQp4aGNpX21vdXNlPSJ5ZXMiDQpjcHU9Mg0KbWVtb3J5PTJHDQphaGNpX2RldmljZV9saW1pdD0i NCINCm5ldHdvcmswX3R5cGU9InZpcnRpby1uZXQiDQpuZXR3b3JrMF9zd2l0Y2g9InB1YmxpYyIN CmRpc2swX3R5cGU9ImFoY2ktaGQiDQpkaXNrMF9uYW1lPSJkaXNrMC5pbWciDQp1dWlkPSIyMzgx ZDdmZS04Yzk5LTExZTYtYWE0NC01MGU1NDkzNjliYzYiDQpuZXR3b3JrMF9tYWM9IjU4OjljOmZj OjA0OjhhOmEwIg0KDQpNYXR0DQoNCg== From owner-freebsd-virtualization@freebsd.org Tue Nov 1 17:24:33 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4532EC29541 for ; Tue, 1 Nov 2016 17:24:33 +0000 (UTC) (envelope-from randy@terbush.org) Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::22a]) (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 F1FC518E8 for ; Tue, 1 Nov 2016 17:24:32 +0000 (UTC) (envelope-from randy@terbush.org) Received: by mail-qt0-x22a.google.com with SMTP id p16so98129700qta.0 for ; Tue, 01 Nov 2016 10:24:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=terbush.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=CnWW1G8N3YpE+M3l5LOIUA8zJdiI87b9hxACe0Hbbq4=; b=BC2DVdC0NjppQM/6uQKjE3XsUKJ3uH0RUdgHMYYAAeF37zRP2yV3y5Ha2FHT0jn1b/ 8bvyi0kgP0yRLSSyQcWM9cCpFjSvjE6SCaHDce9vst6KcQFgTw8kmRbpth3CFP0oPcqi SBz+qqL8bAmj2/j+yWdiKTUkbOBbbENel7C6E= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=CnWW1G8N3YpE+M3l5LOIUA8zJdiI87b9hxACe0Hbbq4=; b=IBeqhw4aGnUy/VIN31+UYpDhN/LcttCY2Q9fVzBMuEKsAD1ypH8cbz9SSo6sPqNPRk YAd/gn4V0bRf8qEn/R+XnlQ6hmzzLFo96RtRABFrwyAE2VzLqI7Mbqi85T0jVD1k7CfN QwatLziG4tz1FulmglwdPNh6HHb5jC25Fu+usA/kavUtMyB4X2iHhK9x8oixgg2IVgCi gFgnV+RqV7b0VxtvOKdVw6UavScpT+f2uTZ7t0ZxQm5DtW10aUVkVY5f72RkhHwfr2AO w4HkU91W9zkJ6o+tYv1zMgrOcjaUOEFjCiR1cihJGx2B1xEhicfKrwwMKmM+2oT7g062 nG/w== X-Gm-Message-State: ABUngvcJQx5c0z0aV/D3oR+xa3RKG6YNDUY9RQSZIveK/obiahgMcTPniOm6TLnAtIhpEIXFDL49GrSwewlgKw== X-Received: by 10.237.47.4 with SMTP id l4mr25410776qtd.129.1478021071552; Tue, 01 Nov 2016 10:24:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.51.82 with HTTP; Tue, 1 Nov 2016 10:24:01 -0700 (PDT) In-Reply-To: References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <20161101140249.GB27402@doctor.nl2k.ab.ca> <1478009772.19546.74.camel@fastmail.fm> <20161101142257.GF27402@doctor.nl2k.ab.ca> From: Randy Terbush Date: Tue, 1 Nov 2016 11:24:01 -0600 Message-ID: Subject: Re: Windows 2016 To: "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, 01 Nov 2016 17:24:33 -0000 On Tue, Nov 1, 2016 at 9:21 AM, Matt Churchyard wrote: > On Tue, Nov 1, 2016 at 8:58 AM, Matt Churchyard via freebsd-virtualizatio= n > wrote: > > On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote: > > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote: > > > On Tue, Nov 01, 2016 at 09:02:57AM +0000, Matt Churchyard wrote: > > > > > > > > > > > > > > I was able to install the Windows 2016 using the GUI method. > > > > > > > > > > One problem. > > > > > > > > > > It is assigned an IP but > > > > > > > > > > the netmask and the default route is not showing up. > > > > > > > > > > Also??The virtual Windows 2016 box does not see a network > > > > > interface. > > > > This makes very little sense. You usually specify the netmask and > > > > default route when you assign Windows an IP address. > > > > And how have you assigned the guest an IP address if it has no > > > > network interface? > > > > > > > The taps are allocated an IP address. > > > > > > I fully concur. > > > > > > In the install at one point, I declare that the IP address, netmask > > > and gateway are 'declared' at the 'MB ' BIOS interface. > > > > > > > > > > > > > > > > > > > > What must I do to convince this box that is it on a switch > > > > On the bhyve host it should be configured just like any other > > > > bhyve virtual machine. The guest should have a virtio-net device, > > > > which is linked to a tap interface on the host. That tap interface > > > > should be bridged with whichever physical network adapter you want > > > > the guest connected to. > > > > > > > > However, I think I mentioned in a previous message that Windows > > > > does not have the virtio-net drivers by default. You need to boot > > > > the guest with the virtio-net driver ISO attached and install the > > > > driver. You should see the interface in Device Manager flagged as > > > > not installed/working. > > > > > > > > > > That is correct . > > > > > > I do have an iso of the MB drivers, > > > > > > namely a Supermicro??X10DRW-i MB? > > > > > > and? > > > > > > from Intel I did obtain the .exe file for the i350GbE drivers. > > > I script a 2 phase installation as follows: > > > > > > 1) > > > > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/14393.0.160715- > > > 1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO -s 4,ahci- > > > hd,windows2016.img -s 5,virtio-net,tap15 -s > > > 29,fbuf,tcp=3D0.0.0.0:5900,w=3D800,h=3D600,wait -s 30,xhci,tablet -s > > > 31,lpc -l com1,stdio -l > > > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd > > > windows2016guest > > > > > > 2) > > > > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s > > > 3,ahci-cd,./.iso/null-install.iso -s 4,ahci-hd,windows2016.img -s > > > 5,virtio-net,tap15 -s 29,fbuf,tcp=3D0.0.0.0:5900,w=3D1024,h=3D768,wai= t -s > > > 30,xhci,tablet -s 31,lpc -l com1,/dev/nmdm15A -l > > > bootrom,/usr/local/share/uefi- firmware/BHYVE_UEFI.fd > > > windows2016guest & > > > > > > As I said, I have picked up an ISO from the MB manufacturer > > > > > > let's call it manufacturer.iso . > > > > > > Where do I place said iso in the 'phase' of things? > > > > You use virtio network adapters, you have to install the virtio > > drivers and NOT the drivers for the physical interface. Then configure > > the IP Address, gateway, etc. in Windows. > > >All right, let me repeat what I am up aginst. > > >I do set the IP configuration in the virtual BIOS. > > >However when the Win2016 VM boots it sees > > >1) the localhost > > >2) its assigned IP address > > >3) A yellow triangle where the ethernet adaptor is. > > I'm not sure what people find so difficult about this - Just treat it lik= e > it was a real Windows machine > > 1) Do not assign the guest's IP address on the host > 2) Do not set the IP in the guest BIOS (I'm not even sure what you mean b= y > this) > > As you have found, the virtio-net network adapter has a yellow triangle i= n > Windows, because it is not installed. You need to run bhyve but replace t= he > Windows ISO with the virtio-net driver ISO, which you can download off th= e > Internet; Then install the network driver through VNC. The guest has a > "virtio-net" interface which is created by bhyve - This has nothing to do > with your motherboard and you do not need to install any of the motherboa= rd > or physical interface drivers in the guest. > > Once you have the virtio driver installed, you will have a "Redhat VirtIO= " > network adapter in Windows, and you can assign an IP/Netmask/Gateway to > this just as you normally would in Windows. > > Forget about the Linux machines. They have the virtio-net driver built in= , > so you can just configure eth0 out-of-the-box like normal. If you've > configured their IP addresses on the bhyve host then that's not really th= e > correct way to configure things, even if it doesn't actually break > anything; The IP address should be configured inside the guest OS. > > Matt > > > > > > =E2=80=8B>Can you guys confirm that you actually have a Windows 2016 vm r= unning? > > > > >As I have said, I have installed nearly every version of Windows OS vms > with Bhyve (vm-bhyve) successfully with the >exception of Windows 2016. > > > > >DHCP does not work. Assigning an address by hand does not work. Any > attempt to configure the IP on the network device or >even uninstall it > just results in long delays and spinning cursors. > > > > >If you've got this working, I would love to see a vm-bhyve template and > to know what virtio driver package version you are >using. > > =E2=80=8B > > I have Windows 2016 Evaluation running without any problems. - > http://imgur.com/a/b9dws > > > > The configuration for vm-bhyve I=E2=80=99m using is below (I actually wro= te > vm-bhyve). > > I used virtio-win-0.1.118.iso as that happens to be what I had lying > around at the time. I=E2=80=99ve no idea what other virtio driver version= s are like. > > The guest is currently using DHCP although I have no reason to suspect > there=E2=80=99d be a problem assigning a static. > > > > uefi=3D"yes" > > graphics=3D"yes" > > graphics_res=3D"1280x720" > > xhci_mouse=3D"yes" > > cpu=3D2 > > memory=3D2G > > ahci_device_limit=3D"4" > > network0_type=3D"virtio-net" > > network0_switch=3D"public" > > disk0_type=3D"ahci-hd" > > disk0_name=3D"disk0.img" > > uuid=3D"2381d7fe-8c99-11e6-aa44-50e549369bc6" > > network0_mac=3D"58:9c:fc:04:8a:a0" > > > > Matt > > > =E2=80=8BMy setup is not much different with exception that I am attempting= to install Windows Server 2016 Essentials, release version, and I have added both guest=3D"windows" and have set disk0_opts=3D"sectorsize=3D512" based o= n some previous help you gave me regarding failed SQL server installs. I tried booting the existing image I was working on and switched from the 102 release of the virtio drivers to the 118 version to see if that made any difference. It did not. Overall, my install has taken FOREVER, to do anything and often simple operations like deleting drivers hangs. Not sure if this is because of lack of network or also suspicious of the 512 block size. I threw in the towel on the old image and have tried a clean install this time. I attempted a sectorsize=3D4096, but the end result is an image that won't boot and just provides a EFI bios message of failed boot.. Creating an image with sectorsize=3D512 works and is bootable. Install runs normally. There is a VERY long period of "setting up computer" in this process which runs for nearly 30 minutes. But at the end of it all, I am unable to install a working ethernet device. I can assign an address and that device address is pingable, but I cannot ping the router on the network. Attempts to work with this driver to uninstall, reinstall either take a very long time, or hang completely. This is working with virtio bundle 118. From owner-freebsd-virtualization@freebsd.org Tue Nov 1 17:46:27 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5D1F5C29B82 for ; Tue, 1 Nov 2016 17:46:27 +0000 (UTC) (envelope-from randy@terbush.org) Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 0623018D6 for ; Tue, 1 Nov 2016 17:46:27 +0000 (UTC) (envelope-from randy@terbush.org) Received: by mail-qk0-x233.google.com with SMTP id q130so88384528qke.1 for ; Tue, 01 Nov 2016 10:46:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=terbush.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=qrUB18gSBfgTNUODvNUNv2YVUWHHZs1zyKJkhmuLJ5g=; b=I+eV5ezMEbu370XRbxHgSu1mXNSfeTkamqjGC6WiuFax+da0p9Xh/7N7xcBMoE6j6+ UNTmCVLtqFyPiYazdWgu6bHQD0KAfZi5PUXMfh6NrA/P1JMCdOJycLVY3CMbwciOn86X 5RA2lW6x06I4RG1CvletDNWGu0KLt9Iyxrs6I= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=qrUB18gSBfgTNUODvNUNv2YVUWHHZs1zyKJkhmuLJ5g=; b=WTZpBlLlXtxpXy1j9KcswQW/B3b2cXNv8Qscue249QMafDkiT+4lehDvkw+ulLXDUR NoDz5QiiSyn4Wd4rslgs/j1OLsNxlsxF8NAgxic9GqN2ELRzOBSBs734c1pqDrXTIwIa DEbzlHcIkghXpUzJVbOZbH0i/KY9tGxLCOGosm1A1iPdEOmJ4rXP7hghDZr2hvQmCt/H nLl3Aun3/lysYgIE7fMslQnhCqpPfmQwmVXXw5yLSJHvzsq+YjXAGt7Ai/u7djzSNyAx aOjqySYS3ilfLUZU9vnbZtlnmCukP+oPViVl5IzEpH8zD1Ig/FyXtmxVPccN5329HQxq 3ypA== X-Gm-Message-State: ABUngvdDuEmw/OvlzYjLKuZSXklKu0kh8bUOjiOTbg9QpnAkE++0oGdDTf9KLfYBBEhw8m1LntD9ap5+K+h+3Q== X-Received: by 10.55.75.17 with SMTP id y17mr12469458qka.26.1478022386008; Tue, 01 Nov 2016 10:46:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.51.82 with HTTP; Tue, 1 Nov 2016 10:45:55 -0700 (PDT) In-Reply-To: References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <20161101140249.GB27402@doctor.nl2k.ab.ca> <1478009772.19546.74.camel@fastmail.fm> <20161101142257.GF27402@doctor.nl2k.ab.ca> From: Randy Terbush Date: Tue, 1 Nov 2016 11:45:55 -0600 Message-ID: Subject: Re: Windows 2016 To: "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, 01 Nov 2016 17:46:27 -0000 On Tue, Nov 1, 2016 at 11:24 AM, Randy Terbush wrote: > On Tue, Nov 1, 2016 at 9:21 AM, Matt Churchyard < > matt.churchyard@userve.net> wrote: > >> On Tue, Nov 1, 2016 at 8:58 AM, Matt Churchyard via >> freebsd-virtualization wrote: >> >> On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote: >> > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote: >> > > On Tue, Nov 01, 2016 at 09:02:57AM +0000, Matt Churchyard wrote: >> > > > >> > > > > >> > > > > I was able to install the Windows 2016 using the GUI method. >> > > > > >> > > > > One problem. >> > > > > >> > > > > It is assigned an IP but >> > > > > >> > > > > the netmask and the default route is not showing up. >> > > > > >> > > > > Also??The virtual Windows 2016 box does not see a network >> > > > > interface. >> > > > This makes very little sense. You usually specify the netmask and >> > > > default route when you assign Windows an IP address. >> > > > And how have you assigned the guest an IP address if it has no >> > > > network interface? >> > > > >> > > The taps are allocated an IP address. >> > > >> > > I fully concur. >> > > >> > > In the install at one point, I declare that the IP address, netmask >> > > and gateway are 'declared' at the 'MB ' BIOS interface. >> > > >> > > >> > > > >> > > > > >> > > > > What must I do to convince this box that is it on a switch >> > > > On the bhyve host it should be configured just like any other >> > > > bhyve virtual machine. The guest should have a virtio-net device, >> > > > which is linked to a tap interface on the host. That tap interface >> > > > should be bridged with whichever physical network adapter you want >> > > > the guest connected to. >> > > > >> > > > However, I think I mentioned in a previous message that Windows >> > > > does not have the virtio-net drivers by default. You need to boot >> > > > the guest with the virtio-net driver ISO attached and install the >> > > > driver. You should see the interface in Device Manager flagged as >> > > > not installed/working. >> > > > >> > > >> > > That is correct . >> > > >> > > I do have an iso of the MB drivers, >> > > >> > > namely a Supermicro??X10DRW-i MB? >> > > >> > > and? >> > > >> > > from Intel I did obtain the .exe file for the i350GbE drivers. >> > > I script a 2 phase installation as follows: >> > > >> > > 1) >> > > >> > > >> > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/14393.0.160715- >> > > 1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO -s 4,ahci- >> > > hd,windows2016.img -s 5,virtio-net,tap15 -s >> > > 29,fbuf,tcp=3D0.0.0.0:5900,w=3D800,h=3D600,wait -s 30,xhci,tablet -s >> > > 31,lpc -l com1,stdio -l >> > > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd >> > > windows2016guest >> > > >> > > 2) >> > > >> > > >> > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s >> > > 3,ahci-cd,./.iso/null-install.iso -s 4,ahci-hd,windows2016.img -s >> > > 5,virtio-net,tap15 -s 29,fbuf,tcp=3D0.0.0.0:5900,w=3D1024,h=3D768,wa= it -s >> > > 30,xhci,tablet -s 31,lpc -l com1,/dev/nmdm15A -l >> > > bootrom,/usr/local/share/uefi- firmware/BHYVE_UEFI.fd >> > > windows2016guest & >> > > >> > > As I said, I have picked up an ISO from the MB manufacturer >> > > >> > > let's call it manufacturer.iso . >> > > >> > > Where do I place said iso in the 'phase' of things? >> > >> > You use virtio network adapters, you have to install the virtio >> > drivers and NOT the drivers for the physical interface. Then configure >> > the IP Address, gateway, etc. in Windows. >> >> >All right, let me repeat what I am up aginst. >> >> >I do set the IP configuration in the virtual BIOS. >> >> >However when the Win2016 VM boots it sees >> >> >1) the localhost >> >> >2) its assigned IP address >> >> >3) A yellow triangle where the ethernet adaptor is. >> >> I'm not sure what people find so difficult about this - Just treat it >> like it was a real Windows machine >> >> 1) Do not assign the guest's IP address on the host >> 2) Do not set the IP in the guest BIOS (I'm not even sure what you mean >> by this) >> >> As you have found, the virtio-net network adapter has a yellow triangle >> in Windows, because it is not installed. You need to run bhyve but repla= ce >> the Windows ISO with the virtio-net driver ISO, which you can download o= ff >> the Internet; Then install the network driver through VNC. The guest has= a >> "virtio-net" interface which is created by bhyve - This has nothing to d= o >> with your motherboard and you do not need to install any of the motherbo= ard >> or physical interface drivers in the guest. >> >> Once you have the virtio driver installed, you will have a "Redhat >> VirtIO" network adapter in Windows, and you can assign an >> IP/Netmask/Gateway to this just as you normally would in Windows. >> >> Forget about the Linux machines. They have the virtio-net driver built >> in, so you can just configure eth0 out-of-the-box like normal. If you've >> configured their IP addresses on the bhyve host then that's not really t= he >> correct way to configure things, even if it doesn't actually break >> anything; The IP address should be configured inside the guest OS. >> >> Matt >> >> >> >> >> >> =E2=80=8B>Can you guys confirm that you actually have a Windows 2016 vm = running? >> >> >> >> >As I have said, I have installed nearly every version of Windows OS vms >> with Bhyve (vm-bhyve) successfully with the >exception of Windows 2016. >> >> >> >> >DHCP does not work. Assigning an address by hand does not work. Any >> attempt to configure the IP on the network device or >even uninstall it >> just results in long delays and spinning cursors. >> >> >> >> >If you've got this working, I would love to see a vm-bhyve template and >> to know what virtio driver package version you are >using. >> >> =E2=80=8B >> >> I have Windows 2016 Evaluation running without any problems. - >> http://imgur.com/a/b9dws >> >> >> >> The configuration for vm-bhyve I=E2=80=99m using is below (I actually wr= ote >> vm-bhyve). >> >> I used virtio-win-0.1.118.iso as that happens to be what I had lying >> around at the time. I=E2=80=99ve no idea what other virtio driver versio= ns are like. >> >> The guest is currently using DHCP although I have no reason to suspect >> there=E2=80=99d be a problem assigning a static. >> >> >> >> uefi=3D"yes" >> >> graphics=3D"yes" >> >> graphics_res=3D"1280x720" >> >> xhci_mouse=3D"yes" >> >> cpu=3D2 >> >> memory=3D2G >> >> ahci_device_limit=3D"4" >> >> network0_type=3D"virtio-net" >> >> network0_switch=3D"public" >> >> disk0_type=3D"ahci-hd" >> >> disk0_name=3D"disk0.img" >> >> uuid=3D"2381d7fe-8c99-11e6-aa44-50e549369bc6" >> >> network0_mac=3D"58:9c:fc:04:8a:a0" >> >> >> >> Matt >> >> >> > > =E2=80=8BMy setup is not much different with exception that I am attempti= ng to > install Windows Server 2016 Essentials, release version, and I have added > both guest=3D"windows" and have set disk0_opts=3D"sectorsize=3D512" based= on some > previous help you gave me regarding failed SQL server installs. > > I tried booting the existing image I was working on and switched from the > 102 release of the virtio drivers to the 118 version to see if that made > any difference. It did not. Overall, my install has taken FOREVER, to do > anything and often simple operations like deleting drivers hangs. Not sur= e > if this is because of lack of network or also suspicious of the 512 block > size. > > I threw in the towel on the old image and have tried a clean install this > time. I attempted a sectorsize=3D4096, but the end result is an image tha= t > won't boot and just provides a EFI bios message of failed boot.. > Creating an image with sectorsize=3D512 works and is bootable. Install ru= ns > normally. There is a VERY long period of "setting up computer" in this > process which runs for nearly 30 minutes. But at the end of it all, I am > unable to install a working ethernet device. I can assign an address and > that device address is pingable, but I cannot ping the router on the > network. Attempts to work with this driver to uninstall, reinstall either > take a very long time, or hang completely. > > This is working with virtio bundle 118. > > > =E2=80=8BActually... after attempting to uninstall driver and software thro= ugh Device Manager and giving up after a long hang. After the reboot... 1. I went back to Device Manager to find the device disabled.=E2=80=8B =E2=80=8B2. Successfully deleted and removed driver software for the networ= k device. 3. Went back to ISO #118 image for virtio and installed the w10 amd64 driver and the network interface immediately came up. Success. So here is my working config: Windows 2016 Essentials release vm-bhyve template as follows: guest=3D"windows" uefi=3D"yes" cpu=3D2 memory=3D4G network0_type=3D"virtio-net" network0_switch=3D"public" graphics=3D"yes" graphics_res=3D"1600x900" graphics_wait=3D"yes" graphics_port=3D"5900" xhci_mouse=3D"yes" disk0_type=3D"ahci-hd" disk0_name=3D"disk0.img" disk0_opts=3D"sectorsize=3D512" disk1_type=3D"ahci-cd" disk1_name=3D"virtio-win-0.1.118.iso" And plenty of stubborness.... =E2=80=8B From owner-freebsd-virtualization@freebsd.org Tue Nov 1 18:30:47 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F427C25B33 for ; Tue, 1 Nov 2016 18:30:47 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1597E1CD4 for ; Tue, 1 Nov 2016 18:30:46 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1c1dpb-0009yo-FD; Tue, 01 Nov 2016 12:30:43 -0600 Date: Tue, 1 Nov 2016 12:30:43 -0600 From: The Doctor To: Daniel Tihanyi Cc: freebsd-virtualization@freebsd.org Subject: Re: Windows 2016 Message-ID: <20161101183043.GA38200@doctor.nl2k.ab.ca> References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <20161101140249.GB27402@doctor.nl2k.ab.ca> <1478009772.19546.74.camel@fastmail.fm> <20161101142257.GF27402@doctor.nl2k.ab.ca> <1478010937.19546.83.camel@fastmail.fm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1478010937.19546.83.camel@fastmail.fm> User-Agent: Mutt/1.7.1 (2016-10-04) 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, 01 Nov 2016 18:30:47 -0000 On Tue, Nov 01, 2016 at 03:35:37PM +0100, Daniel Tihanyi wrote: > On Tue, 2016-11-01 at 08:22 -0600, The Doctor wrote: > > On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote: > > > > > > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote: > > > > > > > > On Tue, Nov 01, 2016 at 09:02:57AM +0000, Matt Churchyard wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > I was able to install the Windows 2016 using the GUI method. > > > > > > > > > > > > One problem. > > > > > > > > > > > > It is assigned an IP but > > > > > > > > > > > > the netmask and the default route is not showing up. > > > > > > > > > > > > Also??The virtual Windows 2016 box does not see a network > > > > > > interface. > > > > > This makes very little sense. You usually specify the netmask > > > > > and > > > > > default route when you assign Windows an IP address. > > > > > And how have you assigned the guest an IP address if it has no > > > > > network interface? > > > > > > > > > The taps are allocated an IP address. > > > > > > > > I fully concur. > > > > > > > > In the install at one point, I declare that the IP address, > > > > netmask > > > > and gateway > > > > are 'declared' at the 'MB ' BIOS interface. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > What must I do to convince this box that is it on a switch > > > > > On the bhyve host it should be configured just like any other > > > > > bhyve > > > > > virtual machine. The guest should have a virtio-net device, > > > > > which > > > > > is linked to a tap interface on the host. That tap interface > > > > > should > > > > > be bridged with whichever physical network adapter you want the > > > > > guest connected to. > > > > > > > > > > However, I think I mentioned in a previous message that Windows > > > > > does not have the virtio-net drivers by default. You need to > > > > > boot > > > > > the guest with the virtio-net driver ISO attached and install > > > > > the > > > > > driver. You should see the interface in Device Manager flagged > > > > > as > > > > > not installed/working. > > > > > > > > > That is correct . > > > > > > > > I do have an iso of the MB drivers, > > > > > > > > namely a Supermicro??X10DRW-i MB? > > > > > > > > and? > > > > > > > > from Intel I did obtain the .exe file for the i350GbE drivers. > > > > I script a 2 phase installation as follows: > > > > > > > > 1) > > > > > > > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci- > > > > cd,./.iso/14393.0.160715- > > > > 1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO -s 4,ahci- > > > > hd,windows2016.img -s 5,virtio-net,tap15 -s > > > > 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -s 30,xhci,tablet -s > > > > 31,lpc > > > > -l com1,stdio -l bootrom,/usr/local/share/uefi- > > > > firmware/BHYVE_UEFI.fd? > > > > windows2016guest > > > > > > > > 2) > > > > > > > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/null- > > > > install.iso? > > > > -s 4,ahci-hd,windows2016.img -s 5,virtio-net,tap15 -s > > > > 29,fbuf,tcp=0.0.0.0:5900,w=1024,h=768,wait -s 30,xhci,tablet -s > > > > 31,lpc -l com1,/dev/nmdm15A -l bootrom,/usr/local/share/uefi- > > > > firmware/BHYVE_UEFI.fd windows2016guest & > > > > > > > > As I said, I have picked up an ISO from the MB manufacturer > > > > > > > > let's call it manufacturer.iso . > > > > > > > > Where do I place said iso in the 'phase' of things? > > > You use virtio network adapters, you have to install the virtio > > > drivers > > > and NOT the drivers for the physical interface. Then configure the > > > IP > > > Address, gateway, etc. in Windows. > > All right, let me repeat what I am up aginst. > > > > I do set the IP configuration in the virtual BIOS. > > > > However when the Win2016 VM boots it sees > > > > 1) the localhost > > > > 2) its assigned IP address > > > > 3) A yellow triangle where the ethernet adaptor is. > > > > > I don't really understand, what do you mean by virtual BIOS. If you > boot up Windows, configure the IP Address, etc from there. Follow this > guide to do so:?https://ittutorials.net/microsoft/windows-server-2016/s > et-windows-server-2016-with-a-static-ip-address/ I guess you missed point 3), there is a yellow triangle where the ethernet adapter is. Hence that I T Tutorial will not work. I need to find a mtheod to get the Ethernet connection to work properly. > _______________________________________________ > 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" -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!! From owner-freebsd-virtualization@freebsd.org Tue Nov 1 18:34:24 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AD74FC25CCF for ; Tue, 1 Nov 2016 18:34:24 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5BACA1D82 for ; Tue, 1 Nov 2016 18:34:24 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1c1dt6-000A4s-Jr; Tue, 01 Nov 2016 12:34:20 -0600 Date: Tue, 1 Nov 2016 12:34:20 -0600 From: The Doctor To: Matt Churchyard Cc: Randy Terbush , Daniel Tihanyi , "freebsd-virtualization@freebsd.org" Subject: Re: Windows 2016 Message-ID: <20161101183420.GA38570@doctor.nl2k.ab.ca> References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <20161101140249.GB27402@doctor.nl2k.ab.ca> <1478009772.19546.74.camel@fastmail.fm> <20161101142257.GF27402@doctor.nl2k.ab.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) 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, 01 Nov 2016 18:34:24 -0000 On Tue, Nov 01, 2016 at 03:21:45PM +0000, Matt Churchyard wrote: > On Tue, Nov 1, 2016 at 8:58 AM, Matt Churchyard via freebsd-virtualization > wrote: > On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote: > > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote: > > > On Tue, Nov 01, 2016 at 09:02:57AM +0000, Matt Churchyard wrote: > > > > > > > > > > > > > > I was able to install the Windows 2016 using the GUI method. > > > > > > > > > > One problem. > > > > > > > > > > It is assigned an IP but > > > > > > > > > > the netmask and the default route is not showing up. > > > > > > > > > > Also??The virtual Windows 2016 box does not see a network > > > > > interface. > > > > This makes very little sense. You usually specify the netmask and > > > > default route when you assign Windows an IP address. > > > > And how have you assigned the guest an IP address if it has no > > > > network interface? > > > > > > > The taps are allocated an IP address. > > > > > > I fully concur. > > > > > > In the install at one point, I declare that the IP address, netmask > > > and gateway are 'declared' at the 'MB ' BIOS interface. > > > > > > > > > > > > > > > > > > > > What must I do to convince this box that is it on a switch > > > > On the bhyve host it should be configured just like any other > > > > bhyve virtual machine. The guest should have a virtio-net device, > > > > which is linked to a tap interface on the host. That tap interface > > > > should be bridged with whichever physical network adapter you want > > > > the guest connected to. > > > > > > > > However, I think I mentioned in a previous message that Windows > > > > does not have the virtio-net drivers by default. You need to boot > > > > the guest with the virtio-net driver ISO attached and install the > > > > driver. You should see the interface in Device Manager flagged as > > > > not installed/working. > > > > > > > > > > That is correct . > > > > > > I do have an iso of the MB drivers, > > > > > > namely a Supermicro??X10DRW-i MB? > > > > > > and? > > > > > > from Intel I did obtain the .exe file for the i350GbE drivers. > > > I script a 2 phase installation as follows: > > > > > > 1) > > > > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/14393.0.160715- > > > 1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO -s 4,ahci- > > > hd,windows2016.img -s 5,virtio-net,tap15 -s > > > 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -s 30,xhci,tablet -s > > > 31,lpc -l com1,stdio -l > > > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd > > > windows2016guest > > > > > > 2) > > > > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s > > > 3,ahci-cd,./.iso/null-install.iso -s 4,ahci-hd,windows2016.img -s > > > 5,virtio-net,tap15 -s 29,fbuf,tcp=0.0.0.0:5900,w=1024,h=768,wait -s > > > 30,xhci,tablet -s 31,lpc -l com1,/dev/nmdm15A -l > > > bootrom,/usr/local/share/uefi- firmware/BHYVE_UEFI.fd > > > windows2016guest & > > > > > > As I said, I have picked up an ISO from the MB manufacturer > > > > > > let's call it manufacturer.iso . > > > > > > Where do I place said iso in the 'phase' of things? > > > > You use virtio network adapters, you have to install the virtio > > drivers and NOT the drivers for the physical interface. Then configure > > the IP Address, gateway, etc. in Windows. > > >All right, let me repeat what I am up aginst. > > >I do set the IP configuration in the virtual BIOS. > > >However when the Win2016 VM boots it sees > > >1) the localhost > > >2) its assigned IP address > > >3) A yellow triangle where the ethernet adaptor is. > I'm not sure what people find so difficult about this - Just treat it like it was a real Windows machine > > 1) Do not assign the guest's IP address on the host > 2) Do not set the IP in the guest BIOS (I'm not even sure what you mean by this) > > As you have found, the virtio-net network adapter has a yellow triangle in Windows, because it is not installed. You need to run bhyve but replace the Windows ISO with the virtio-net driver ISO, which you can download off the Internet; Then install the network driver through VNC. The guest has a "virtio-net" interface which is created by bhyve - This has nothing to do with your motherboard and you do not need to install any of the motherboard or physical interface drivers in the guest. I have virtio-win-0.1.96.iso in the .iso section. Use that instead of the null-install.iso ?? > > Once you have the virtio driver installed, you will have a "Redhat VirtIO" network adapter in Windows, and you can assign an IP/Netmask/Gateway to this just as you normally would in Windows. > > Forget about the Linux machines. They have the virtio-net driver built in, so you can just configure eth0 out-of-the-box like normal. If you've configured their IP addresses on the bhyve host then that's not really the correct way to configure things, even if it doesn't actually break anything; The IP address should be configured inside the guest OS. > > Matt > > > ???>Can you guys confirm that you actually have a Windows 2016 vm running? > > >As I have said, I have installed nearly every version of Windows OS vms with Bhyve (vm-bhyve) successfully with the >exception of Windows 2016. > > >DHCP does not work. Assigning an address by hand does not work. Any attempt to configure the IP on the network device or >even uninstall it just results in long delays and spinning cursors. > > >If you've got this working, I would love to see a vm-bhyve template and to know what virtio driver package version you are >using. > ??? > I have Windows 2016 Evaluation running without any problems. - http://imgur.com/a/b9dws > > The configuration for vm-bhyve I???m using is below (I actually wrote vm-bhyve). > I used virtio-win-0.1.118.iso as that happens to be what I had lying around at the time. I???ve no idea what other virtio driver versions are like. > The guest is currently using DHCP although I have no reason to suspect there???d be a problem assigning a static. > > uefi="yes" > graphics="yes" > graphics_res="1280x720" > xhci_mouse="yes" > cpu=2 > memory=2G > ahci_device_limit="4" > network0_type="virtio-net" > network0_switch="public" > disk0_type="ahci-hd" > disk0_name="disk0.img" > uuid="2381d7fe-8c99-11e6-aa44-50e549369bc6" > network0_mac="58:9c:fc:04:8a:a0" > > Matt > -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!! From owner-freebsd-virtualization@freebsd.org Tue Nov 1 18:49:37 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 713FFC28212 for ; Tue, 1 Nov 2016 18:49:37 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 3CAD41F7D for ; Tue, 1 Nov 2016 18:49:36 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id A57BD20777 for ; Tue, 1 Nov 2016 14:49:35 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Tue, 01 Nov 2016 14:49:35 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=zvKZA0VcjClbVf69OYgN9E5wCPU=; b=Z+ldCX ZMa9InkUWA+jlSCvmTBWVrc1LkogjyBYCJGGFJacrHJf6NJ72W+2/6//oB1TvO1i JeL6zuPWo3YiR0jNQEyKReRnW8LWilx/3ML/sxL4TUTgCO5+HUFXTEXgzy6Ov3ZR D3lsNNJVKcxKrQudFeKM1KlgMzWs0fWRaRYWU= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=smtpout; bh=zvKZA0VcjClbVf 69OYgN9E5wCPU=; b=RiPppJokMOfMZNlFkFXhzPq83F+0ZEwb4ppzPxomPn336g q4ptZZkYKF0LWl95K998YraaA8zLt41yfEAjrcPG78NS/+uUePAdBYvlZ4a5Znc2 2xSwFs0ZulNDj4BZ8ULBHnMo9ZQmxPSUHMSg2YXRLUpOYbAFrcPdq0B4k89GU= X-ME-Sender: X-Sasl-enc: uWjI6FLLSL248K09UXnkj/zFOSnOPm91fwKNqwLjkYlr 1478026175 Received: from pumpkin.growveg.org (pumpkin.growveg.org [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id 49D81F29CC for ; Tue, 1 Nov 2016 14:49:35 -0400 (EDT) To: freebsd-virtualization@freebsd.org From: tech-lists Subject: ubuntu 14.04 guest problem on freebsd 10 host Message-ID: Date: Tue, 1 Nov 2016 18:49:33 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2016 18:49:37 -0000 Hello list, I have a number of ubuntu guests on this freebsd host, and I start them more or less the same way, but with one of them, the login prompt never arrives. To restart, I do this: 1. (each of them runs in screen, so I resume the screen, and from elsewhere, I log in via ssh and run shutdown -r now as root. So in the screen now, the vm has exited and I'm now at the freebsd server prompt.) 2. bhyvectl --destroy --vm=ubuntu0 3. grub-bhyve -m device.map -r hd0,msdos1 -M 4096M ubuntu0 4. bhyve -AI -H -P -s 0:0,hostbridge -s 1:0,lpc -s 2:0,virtio-net,tap3 -s 3:0,virtio-blk,./ubuntu0.img -l com1,stdio -c 2 -m 4096M ubuntu0 The VM gets as far as this: * Starting web server apache2 [OK] * Starting authentication failure monitor fail2ban [ OK ] ...and nothing else. web everything in the vm is working. I'm just not getting the login prompt. How can I fix this? Also is there a way of taking the VM image, mounting it on some mountpoint on the freebsd host and directly editing the files within it? Alternatively, is there a way of making grub boot the image into single-user-mode like one can with freebsd? Many thanks, -- J. From owner-freebsd-virtualization@freebsd.org Tue Nov 1 21:04:24 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8615CC2A1D6 for ; Tue, 1 Nov 2016 21:04:24 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 581E41D31 for ; Tue, 1 Nov 2016 21:04:24 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1c1gEG-000ET3-0G; Tue, 01 Nov 2016 15:04:20 -0600 Date: Tue, 1 Nov 2016 15:04:19 -0600 From: The Doctor To: Matt Churchyard Cc: Daniel Tihanyi , "freebsd-virtualization@freebsd.org" Subject: Re: Windows 2016 Message-ID: <20161101210419.GA55104@doctor.nl2k.ab.ca> References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <20161101140249.GB27402@doctor.nl2k.ab.ca> <1478009772.19546.74.camel@fastmail.fm> <20161101142257.GF27402@doctor.nl2k.ab.ca> <20161101183420.GA38570@doctor.nl2k.ab.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161101183420.GA38570@doctor.nl2k.ab.ca> User-Agent: Mutt/1.7.1 (2016-10-04) 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, 01 Nov 2016 21:04:24 -0000 On Tue, Nov 01, 2016 at 12:34:20PM -0600, The Doctor wrote: > On Tue, Nov 01, 2016 at 03:21:45PM +0000, Matt Churchyard wrote: > > On Tue, Nov 1, 2016 at 8:58 AM, Matt Churchyard via freebsd-virtualization > wrote: > > On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote: > > > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote: > > > > On Tue, Nov 01, 2016 at 09:02:57AM +0000, Matt Churchyard wrote: > > > > > > > > > > > > > > > > > I was able to install the Windows 2016 using the GUI method. > > > > > > > > > > > > One problem. > > > > > > > > > > > > It is assigned an IP but > > > > > > > > > > > > the netmask and the default route is not showing up. > > > > > > > > > > > > Also??The virtual Windows 2016 box does not see a network > > > > > > interface. > > > > > This makes very little sense. You usually specify the netmask and > > > > > default route when you assign Windows an IP address. > > > > > And how have you assigned the guest an IP address if it has no > > > > > network interface? > > > > > > > > > The taps are allocated an IP address. > > > > > > > > I fully concur. > > > > > > > > In the install at one point, I declare that the IP address, netmask > > > > and gateway are 'declared' at the 'MB ' BIOS interface. > > > > > > > > > > > > > > > > > > > > > > > > > What must I do to convince this box that is it on a switch > > > > > On the bhyve host it should be configured just like any other > > > > > bhyve virtual machine. The guest should have a virtio-net device, > > > > > which is linked to a tap interface on the host. That tap interface > > > > > should be bridged with whichever physical network adapter you want > > > > > the guest connected to. > > > > > > > > > > However, I think I mentioned in a previous message that Windows > > > > > does not have the virtio-net drivers by default. You need to boot > > > > > the guest with the virtio-net driver ISO attached and install the > > > > > driver. You should see the interface in Device Manager flagged as > > > > > not installed/working. > > > > > > > > > > > > > That is correct . > > > > > > > > I do have an iso of the MB drivers, > > > > > > > > namely a Supermicro??X10DRW-i MB? > > > > > > > > and? > > > > > > > > from Intel I did obtain the .exe file for the i350GbE drivers. > > > > I script a 2 phase installation as follows: > > > > > > > > 1) > > > > > > > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/14393.0.160715- > > > > 1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO -s 4,ahci- > > > > hd,windows2016.img -s 5,virtio-net,tap15 -s > > > > 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -s 30,xhci,tablet -s > > > > 31,lpc -l com1,stdio -l > > > > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd > > > > windows2016guest > > > > > > > > 2) > > > > > > > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s > > > > 3,ahci-cd,./.iso/null-install.iso -s 4,ahci-hd,windows2016.img -s > > > > 5,virtio-net,tap15 -s 29,fbuf,tcp=0.0.0.0:5900,w=1024,h=768,wait -s > > > > 30,xhci,tablet -s 31,lpc -l com1,/dev/nmdm15A -l > > > > bootrom,/usr/local/share/uefi- firmware/BHYVE_UEFI.fd > > > > windows2016guest & > > > > > > > > As I said, I have picked up an ISO from the MB manufacturer > > > > > > > > let's call it manufacturer.iso . > > > > > > > > Where do I place said iso in the 'phase' of things? > > > > > > You use virtio network adapters, you have to install the virtio > > > drivers and NOT the drivers for the physical interface. Then configure > > > the IP Address, gateway, etc. in Windows. > > > > >All right, let me repeat what I am up aginst. > > > > >I do set the IP configuration in the virtual BIOS. > > > > >However when the Win2016 VM boots it sees > > > > >1) the localhost > > > > >2) its assigned IP address > > > > >3) A yellow triangle where the ethernet adaptor is. > > I'm not sure what people find so difficult about this - Just treat it like it was a real Windows machine > > > > 1) Do not assign the guest's IP address on the host > > 2) Do not set the IP in the guest BIOS (I'm not even sure what you mean by this) > > > > As you have found, the virtio-net network adapter has a yellow triangle in Windows, because it is not installed. You need to run bhyve but replace the Windows ISO with the virtio-net driver ISO, which you can download off the Internet; Then install the network driver through VNC. The guest has a "virtio-net" interface which is created by bhyve - This has nothing to do with your motherboard and you do not need to install any of the motherboard or physical interface drivers in the guest. > > I have virtio-win-0.1.96.iso in the .iso section. > > Use that instead of the null-install.iso > ?? That did it!! Couple of issues. RDP the rules might have changed, have to check. Hyper-V will not install. What gives? > > > > > Once you have the virtio driver installed, you will have a "Redhat VirtIO" network adapter in Windows, and you can assign an IP/Netmask/Gateway to this just as you normally would in Windows. > > > > Forget about the Linux machines. They have the virtio-net driver built in, so you can just configure eth0 out-of-the-box like normal. If you've configured their IP addresses on the bhyve host then that's not really the correct way to configure things, even if it doesn't actually break anything; The IP address should be configured inside the guest OS. > > > > Matt > > > > > > ???>Can you guys confirm that you actually have a Windows 2016 vm running? > > > > >As I have said, I have installed nearly every version of Windows OS vms with Bhyve (vm-bhyve) successfully with the >exception of Windows 2016. > > > > >DHCP does not work. Assigning an address by hand does not work. Any attempt to configure the IP on the network device or >even uninstall it just results in long delays and spinning cursors. > > > > >If you've got this working, I would love to see a vm-bhyve template and to know what virtio driver package version you are >using. > > ??? > > I have Windows 2016 Evaluation running without any problems. - http://imgur.com/a/b9dws > > > > The configuration for vm-bhyve I???m using is below (I actually wrote vm-bhyve). > > I used virtio-win-0.1.118.iso as that happens to be what I had lying around at the time. I???ve no idea what other virtio driver versions are like. > > The guest is currently using DHCP although I have no reason to suspect there???d be a problem assigning a static. > > > > uefi="yes" > > graphics="yes" > > graphics_res="1280x720" > > xhci_mouse="yes" > > cpu=2 > > memory=2G > > ahci_device_limit="4" > > network0_type="virtio-net" > > network0_switch="public" > > disk0_type="ahci-hd" > > disk0_name="disk0.img" > > uuid="2381d7fe-8c99-11e6-aa44-50e549369bc6" > > network0_mac="58:9c:fc:04:8a:a0" > > > > Matt > > > > -- > Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca > God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! > http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism > Time for the USA to hold a referendum on its republic and vote to dissolve!! > _______________________________________________ > 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" -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!! From owner-freebsd-virtualization@freebsd.org Thu Nov 3 01:47:57 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2C89C29476 for ; Thu, 3 Nov 2016 01:47:57 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4D6802D7C for ; Thu, 3 Nov 2016 01:47:56 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1c278C-000GS6-7Y; Wed, 02 Nov 2016 19:47:52 -0600 Date: Wed, 2 Nov 2016 19:47:52 -0600 From: The Doctor To: Matt Churchyard Cc: Daniel Tihanyi , "freebsd-virtualization@freebsd.org" Subject: Re: Windows 2016 Message-ID: <20161103014752.GA54371@doctor.nl2k.ab.ca> References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <20161101140249.GB27402@doctor.nl2k.ab.ca> <1478009772.19546.74.camel@fastmail.fm> <20161101142257.GF27402@doctor.nl2k.ab.ca> <20161101183420.GA38570@doctor.nl2k.ab.ca> <20161101210419.GA55104@doctor.nl2k.ab.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161101210419.GA55104@doctor.nl2k.ab.ca> User-Agent: Mutt/1.7.1 (2016-10-04) 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, 03 Nov 2016 01:47:57 -0000 Yes you can get Windows 2016 to work on a FreeBSD VM Summary below with edits. On Tue, Nov 01, 2016 at 03:04:19PM -0600, The Doctor wrote: > On Tue, Nov 01, 2016 at 12:34:20PM -0600, The Doctor wrote: > > On Tue, Nov 01, 2016 at 03:21:45PM +0000, Matt Churchyard wrote: > > > On Tue, Nov 1, 2016 at 8:58 AM, Matt Churchyard via freebsd-virtualization > wrote: > > > On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote: > > > > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote: > > > > > On Tue, Nov 01, 2016 at 09:02:57AM +0000, Matt Churchyard wrote: > > > > > > > > > > > > > > > > > > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/14393.0.160715- > > > > > 1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO -s 4,ahci- > > > > > hd,windows2016.img -s 5,virtio-net,tap15 -s > > > > > 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -s 30,xhci,tablet -s > > > > > 31,lpc -l com1,stdio -l > > > > > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd > > > > > windows2016guest > > > > > > > > > > 2) > > > > > > > > > > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s > > > > > 3,ahci-cd,./.iso/virtio-win-0.1.96.iso -s 4,ahci-hd,windows2016.img -s > > > > > 5,virtio-net,tap15 -s 29,fbuf,tcp=0.0.0.0:5900,w=1024,h=768,wait -s > > > > > 30,xhci,tablet -s 31,lpc -l com1,/dev/nmdm15A -l > > > > > bootrom,/usr/local/share/uefi- firmware/BHYVE_UEFI.fd > > > > > windows2016guest & Please note I am running the from a /path/to/vm as root of all VMs. > > That did it!! > > Couple of issues. > > RDP the rules might have changed, have to check. Looking at this. > > Hyper-V will not install. > > What gives? > So the question is how do I pass to Windows 2016 that the CPU it is using is a CPU capable of Hyper-V ? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!! From owner-freebsd-virtualization@freebsd.org Thu Nov 3 02:09:26 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 233CCC2986D for ; Thu, 3 Nov 2016 02:09:26 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 9B5BF18D5 for ; Thu, 3 Nov 2016 02:09: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 334D2206BDED for ; Thu, 3 Nov 2016 12:00:11 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 29D7A280AB0 for ; Thu, 3 Nov 2016 12:00:11 +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 ugt_UYjrHjrq for ; Thu, 3 Nov 2016 12:00:11 +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 4DB6D280A3D; Thu, 3 Nov 2016 11:59:56 +1000 (AEST) Subject: Re: Windows 2016 To: The Doctor , Matt Churchyard References: <20161101044503.GA58756@doctor.nl2k.ab.ca> <20161101140249.GB27402@doctor.nl2k.ab.ca> <1478009772.19546.74.camel@fastmail.fm> <20161101142257.GF27402@doctor.nl2k.ab.ca> <20161101183420.GA38570@doctor.nl2k.ab.ca> <20161101210419.GA55104@doctor.nl2k.ab.ca> <20161103014752.GA54371@doctor.nl2k.ab.ca> Cc: Daniel Tihanyi , "freebsd-virtualization@freebsd.org" From: Peter Grehan Message-ID: <3c34674a-4af1-fe4e-6a49-81e583ba12ab@freebsd.org> Date: Wed, 2 Nov 2016 19:00:08 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161103014752.GA54371@doctor.nl2k.ab.ca> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=DZ1nkrlW c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=mwgbnDbW7alINpy3vhoKyg==:17 a=N659UExz7-8A:10 a=L24OOQBejmoA:10 a=TJvHFPfG3C60fYLqKmoA:9 a=pILNOxqGKmIA:10 a=fd4BVhNsD9oA: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: Thu, 03 Nov 2016 02:09:26 -0000 Hi, > So the question is how do I pass to Windows 2016 that the CPU it is using > is a CPU capable of Hyper-V ? That requires nested hypervisor support, which isn't yet in bhyve. later, Peter. From owner-freebsd-virtualization@freebsd.org Thu Nov 3 03:29:01 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6EDCFC2C39D for ; Thu, 3 Nov 2016 03:29:01 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 077781C28; Thu, 3 Nov 2016 03:29:00 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1c28i3-000Jaa-4x; Wed, 02 Nov 2016 21:28:59 -0600 Date: Wed, 2 Nov 2016 21:28:59 -0600 From: The Doctor To: Peter Grehan Cc: "freebsd-virtualization@freebsd.org" Subject: Re: Windows 2016 Message-ID: <20161103032859.GA71900@doctor.nl2k.ab.ca> References: <20161101140249.GB27402@doctor.nl2k.ab.ca> <1478009772.19546.74.camel@fastmail.fm> <20161101142257.GF27402@doctor.nl2k.ab.ca> <20161101183420.GA38570@doctor.nl2k.ab.ca> <20161101210419.GA55104@doctor.nl2k.ab.ca> <20161103014752.GA54371@doctor.nl2k.ab.ca> <3c34674a-4af1-fe4e-6a49-81e583ba12ab@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3c34674a-4af1-fe4e-6a49-81e583ba12ab@freebsd.org> User-Agent: Mutt/1.7.1 (2016-10-04) 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, 03 Nov 2016 03:29:01 -0000 On Wed, Nov 02, 2016 at 07:00:08PM -0700, Peter Grehan wrote: > Hi, > > > So the question is how do I pass to Windows 2016 that the CPU it is using > > is a CPU capable of Hyper-V ? > > That requires nested hypervisor support, which isn't yet in bhyve. > So what would it take for bhyve to programme in nested hypervisor support? > later, > > Peter. > -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!! From owner-freebsd-virtualization@freebsd.org Thu Nov 3 16:48:27 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4FB1CC2DA83 for ; Thu, 3 Nov 2016 16:48:27 +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 056D51320 for ; Thu, 3 Nov 2016 16:48:27 +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 uA3GmQRE057680 for ; Thu, 3 Nov 2016 16:48:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 214107] [bhyve] Error during installation Remote Desktop Services in Windows 2012R2 and 2016 Date: Thu, 03 Nov 2016 16:48:27 +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: 10.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some 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 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, 03 Nov 2016 16:48:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214107 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-virtualization@Free | |BSD.org CC|freebsd-amd64@FreeBSD.org | --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Thu Nov 3 16:50:14 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0250BC2DC48 for ; Thu, 3 Nov 2016 16:50:14 +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 A60F91B21 for ; Thu, 3 Nov 2016 16:50:13 +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 uA3GoBpC059878 for ; Thu, 3 Nov 2016 16:50:13 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 214004] Hyper-V no buffer space are available Date: Thu, 03 Nov 2016 16:50:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE 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: cc assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2016 16:50:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214004 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- CC|freebsd-amd64@FreeBSD.org | Assignee|freebsd-bugs@FreeBSD.org |freebsd-virtualization@Free | |BSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Thu Nov 3 18:09:36 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8B56C2DA5D for ; Thu, 3 Nov 2016 18:09:36 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AF2171B2A; Thu, 3 Nov 2016 18:09:36 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1c2MSA-0001h6-EZ; Thu, 03 Nov 2016 12:09:30 -0600 Date: Thu, 3 Nov 2016 12:09:30 -0600 From: The Doctor To: Peter Grehan Cc: "freebsd-virtualization@freebsd.org" Subject: Re: Windows 2016 Message-ID: <20161103180930.GA3702@doctor.nl2k.ab.ca> References: <1478009772.19546.74.camel@fastmail.fm> <20161101142257.GF27402@doctor.nl2k.ab.ca> <20161101183420.GA38570@doctor.nl2k.ab.ca> <20161101210419.GA55104@doctor.nl2k.ab.ca> <20161103014752.GA54371@doctor.nl2k.ab.ca> <3c34674a-4af1-fe4e-6a49-81e583ba12ab@freebsd.org> <20161103032859.GA71900@doctor.nl2k.ab.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161103032859.GA71900@doctor.nl2k.ab.ca> User-Agent: Mutt/1.7.1 (2016-10-04) 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, 03 Nov 2016 18:09:36 -0000 On Wed, Nov 02, 2016 at 09:28:59PM -0600, The Doctor wrote: > On Wed, Nov 02, 2016 at 07:00:08PM -0700, Peter Grehan wrote: > > Hi, > > > > > So the question is how do I pass to Windows 2016 that the CPU it is using > > > is a CPU capable of Hyper-V ? > > > > That requires nested hypervisor support, which isn't yet in bhyve. > > > > So what would it take for bhyve to programme in nested hypervisor support? I just noted that my CPUs are Intel Xeon 2603v4 . Is it possible to do a passthru instead of programming bhyve to do a nested hypervisor? > > > later, > > > > Peter. > > > > -- > Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca > God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! > http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism > Time for the USA to hold a referendum on its republic and vote to dissolve!! > _______________________________________________ > 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" -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!! From owner-freebsd-virtualization@freebsd.org Fri Nov 4 01:40:06 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10F4CC2EE2C for ; Fri, 4 Nov 2016 01:40:06 +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 00620123E for ; Fri, 4 Nov 2016 01:40:06 +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 uA41e5Gd021195 for ; Fri, 4 Nov 2016 01:40:05 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 214004] Hyper-V no buffer space are available Date: Fri, 04 Nov 2016 01:40:06 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: sepherosa@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.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, 04 Nov 2016 01:40:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214004 Sepherosa Ziehau changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sepherosa@gmail.com --- Comment #1 from Sepherosa Ziehau --- The network driver for Hyper-V before 10.3 is buggy, and becomes unstable e= ven under slight load. Please update to 10.3 or 11.0 if you only want to stick= to releases. Current, 11-stable, and 10-stable are also in good shape for Hyp= er-V support. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Sat Nov 5 19:24:33 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C48B7AF7540 for ; Sat, 5 Nov 2016 19:24:33 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 96162C44 for ; Sat, 5 Nov 2016 19:24:33 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: by mail-pf0-x232.google.com with SMTP id 189so69991191pfz.3 for ; Sat, 05 Nov 2016 12:24:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=bPKUGjn8k1h4IFtfd0lqn6v4sBnz3qoeylXdOz53r0g=; b=Yqphbr9RB89LHzWXQTMBzhyB+3dDXB9v1PQgKJtY/8YQ/8KiYRnXJ2TH4FFPZYjldJ 8FnMCFUtN7PSwxdHZDblv7sjkCTWMrwVwToM9aVI5JLNNpDod/MBV2YOhR5AZWqz+9PF 2H4Kd8cug54nm7u6yjBfuBVg/UDP0Agmh91yjX+hROu6TtkubyRFEHDaoEpcHsJpjW24 nLGQXtUbbZnj/79OQZlmF60T7UBpn2LPoIP8yO/ujitrwE8hML2XAN31VrFJAPQWkU20 4K/4o18j5dqbOVvAHFx3+yqZjHnHu4mlxqdc6raTAU+5Bxez87VRPJahero5j0vUSVZk tZRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=bPKUGjn8k1h4IFtfd0lqn6v4sBnz3qoeylXdOz53r0g=; b=i1ZPzKTK3rlb9tf3Ya4Dy7bkeowHunuBO4UVk8rAacgUwj64K0x0yWvg5qDGlpm3Lo 1cNp9PrMDSXgzXicBekoLEbIZk5Hf8nTAnQg1QSWnXzyDZ4KpdNP2bBhFcgj6F4lKPfk hyZqRFyF4z4Sa8O06//r6tWqIlMmxZzJ5c4EezZ9fOOU9ZnfJFCV1xSL3kkSIp3PXs7A 5NYONnnlfvAAJDgZjTsKhbTNH5Ch1z+K9KH7ZCFKKj5HeTXHYJa1IlF7WdIbTY4qUAR3 +GZ8mQSuCKQNG/P+y72kO9GTH9e1FwELxAXRMNV9EaCZo8leMl57JJe503B8QMWpxkM0 4oqA== X-Gm-Message-State: ABUngvdU0WJyQMCUelBetZNmUI3B7Pv6Rec4PnjKKC06vq9sH/n6gZ8YwBVojRZ10bM8fg== X-Received: by 10.98.35.140 with SMTP id q12mr38106021pfj.180.1478373873095; Sat, 05 Nov 2016 12:24:33 -0700 (PDT) Received: from ?IPv6:2601:2c2:200:12c7:202:c9ff:fe4e:1dc0? ([2601:2c2:200:12c7:202:c9ff:fe4e:1dc0]) by smtp.gmail.com with ESMTPSA id r10sm29396173paw.2.2016.11.05.12.24.31 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 05 Nov 2016 12:24:32 -0700 (PDT) To: freebsd-virtualization@FreeBSD.org From: Rajil Saraswat Subject: Bhyve and Poor network speed with Intel X540-AT2 Message-ID: <9fe097c5-c2ef-fda6-8b99-b4e4d7afff05@gmail.com> Date: Sat, 5 Nov 2016 14:24:29 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2016 19:24:33 -0000 Hello, I am running debian8 in a bhyve instance. The host has a 10g network and uses Intel X540-AT2 NIC. The guest has a poor network speed in the order of 2-3 kBps. However, if i disable the hardware offload features of the NIC it brings the host speed from 10g to 1g, and bhyve shows 1g speed as well. I use the following in rc.conf ifconfig_ix0="-rxcsum -txcsum -vlanmtu -vlanhwtso -tso4 -tso6 -vlanhwtso -vlanhwcsum up" Is there anyway around to get 10g speed on host and better speed in the vm simultaneously? Thanks Rajil