From owner-freebsd-virtualization@FreeBSD.ORG Mon May 6 11:06:55 2013 Return-Path: Delivered-To: freebsd-virtualization@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 50FF9A26 for ; Mon, 6 May 2013 11:06:55 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 419E4A1B for ; Mon, 6 May 2013 11:06:55 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r46B6ti5023984 for ; Mon, 6 May 2013 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r46B6sUo023982 for freebsd-virtualization@FreeBSD.org; Mon, 6 May 2013 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 6 May 2013 11:06:54 GMT Message-Id: <201305061106.r46B6sUo023982@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-virtualization@FreeBSD.org Subject: Current problem reports assigned to freebsd-virtualization@FreeBSD.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 May 2013 11:06:55 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/170096 virtualization[vimage] Dynamically-attached network interface will c o kern/169991 virtualization[run] [vimage] panic after device plugged in o kern/165252 virtualization[vimage] [pf] [panic] kernel panics with VIMAGE and PF o kern/161094 virtualization[vimage] [pf] [panic] kernel panic with pf + VIMAGE wh o kern/160541 virtualization[vimage][pf][patch] panic: userret: Returning on td 0x o kern/160496 virtualization[vimage] [pf] [patch] kernel panic with pf + VIMAGE o kern/148155 virtualization[vimage] [pf] Kernel panic with PF + VIMAGE kernel opt a kern/147950 virtualization[vimage] [carp] VIMAGE + CARP = kernel crash s kern/143808 virtualization[pf] pf does not work inside jail a kern/141696 virtualization[rum] [vimage] [panic] rum(4)+ vimage = kernel panic 10 problems total. From owner-freebsd-virtualization@FreeBSD.ORG Mon May 6 19:12:47 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2D41EA7A; Mon, 6 May 2013 19:12:47 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.208.146]) by mx1.freebsd.org (Postfix) with ESMTP id EE690CE6; Mon, 6 May 2013 19:12:46 +0000 (UTC) Received: from maia.hub.org (unknown [200.46.151.188]) by hub.org (Postfix) with ESMTP id 46CE817331BF; Mon, 6 May 2013 16:12:39 -0300 (ADT) Received: from hub.org ([200.46.208.146]) by maia.hub.org (mx1.hub.org [200.46.151.188]) (amavisd-maia, port 10024) with ESMTP id 06289-07; Mon, 6 May 2013 19:12:39 +0000 (UTC) Received: from [10.5.250.150] (remote.ilcs.sd63.bc.ca [142.31.148.2]) by hub.org (Postfix) with ESMTPA id 8840A17331BE; Mon, 6 May 2013 16:12:37 -0300 (ADT) From: "Marc G. Fournier" Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: VirtualBox + FreeBSD 9-STABLE == Frozen Ethernet Date: Mon, 6 May 2013 12:12:35 -0700 Message-Id: <1601E2D3-DF60-4CCB-9F92-9AD05BCBCB10@hub.org> To: "freebsd-net@freebsd.org" Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) X-Mailer: Apple Mail (2.1503) Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 May 2013 19:12:47 -0000 I'm having an odd issue with FreeBSD that I'm not sure how to trace / = where to look =85=20 I have 6 servers, all identical RAM / CPU / Ethernet / etc =85 4 of them = are running VirtualBox, 2 are running Jails =85 one of the 4 I just = switched from Jail -> Virtualbox =85 When running jail(s), the servers are rock solid =85 as soon as I switch = to VirtualBox (the one I just switched is running one Vbox with a = FreeBSD Guest) =85 nothing else is running on the server =85 but I will = get sporadic freezes of the Ethernet. One ran 46 days before it froze, = then after a reboot, it happened a few hours later, now its been running = several hours again without any issues =85 The machine itself is not frozen =85 I can connect via remote console, = login, do ps, etc =85 so its as if the Ethernet (bce device) just went = offline. I was pointed to a wiki about VirtualBox, and my current loader.conf = looks like: =3D=3D=3D aio_load=3D"YES" kern.ipc.shm_use_phys=3D1 accf_http_load=3D"YES" if_bridge_load=3D"YES" if_tap_load=3D"YES" hw.pci.enable_msix=3D0 vboxdrv_load=3D"YES" net.graph.maxdata=3D65536 =3D=3D=3D I'm running the latest version of 9-STABLE as well as the latest version = of vBox available in ports =85 the bce device is an older version of = Broadcom, so not dealing a new one with new features: bce0: And as I say, these work great with jail'd environments ALIASed onto = them =85 The vBox environments are all configured for network using: --nic1 bridged --bridgeadapter1 bce1 Maybe I'm setting up the network wrong? But, it does work for awhile =85=20= I'm not seeing any errors on the console when the ethernet stops working = =85 nothing to indicate an buffer overflowing or something like that =85 = but, again, I can login and run commands, so if there is something I can = run to get more useful details =85 ? From owner-freebsd-virtualization@FreeBSD.ORG Mon May 6 19:43:25 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 886FEFF9; Mon, 6 May 2013 19:43:25 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-vc0-f176.google.com (mail-vc0-f176.google.com [209.85.220.176]) by mx1.freebsd.org (Postfix) with ESMTP id 38C2FE71; Mon, 6 May 2013 19:43:24 +0000 (UTC) Received: by mail-vc0-f176.google.com with SMTP id ib11so3352224vcb.7 for ; Mon, 06 May 2013 12:43:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=EOJogWYIPrRE7sHRMVwSMMVCY3SatMP3Bw+tr5iW11k=; b=diN6sNg70W0a7iGzMN8WaV1MdT/1hnVhuph7wNElSDl/gJgSn5u2ElC9DiVkfiMhQ6 OsclxZ45G+fZMOlBUHSTQifa/9kkqDg9/JN0Vz6BL/Q/nz2N9c9AjOOL0sXGqEnBbN5E O8JW5dUOQfPG73bPsPP7mYO3B8bpYqT9+d420IvIBVPusQXCA4XMFAyrFlp8KsBWIj4f 9MZ60AsTVK8rIasky/wOZ7iX0Z3OyHG7KNAKngS7tKuaVGk1BtRwud9bff1jNtXCZ1nI KhRA/5U5SU3UXDH+4iZeGSbruQOJJ3jFvyzSQU4zN7SANK5hSBTPtlp+B2Ns8zNrimL2 uWnA== MIME-Version: 1.0 X-Received: by 10.220.176.71 with SMTP id bd7mr7174570vcb.12.1367869404398; Mon, 06 May 2013 12:43:24 -0700 (PDT) Received: by 10.220.33.135 with HTTP; Mon, 6 May 2013 12:43:24 -0700 (PDT) In-Reply-To: <1601E2D3-DF60-4CCB-9F92-9AD05BCBCB10@hub.org> References: <1601E2D3-DF60-4CCB-9F92-9AD05BCBCB10@hub.org> Date: Mon, 6 May 2013 15:43:24 -0400 Message-ID: Subject: Re: VirtualBox + FreeBSD 9-STABLE == Frozen Ethernet From: Zaphod Beeblebrox To: "Marc G. Fournier" Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-net@freebsd.org" , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 May 2013 19:43:25 -0000 Heh. VirtualBox has (in my experience) been buggy as heck. Beyond buggy as heck. I have 3 virtualization platforms at my disposal (and the host here is win 7). VirtualBox, VMWare and Windows Virtual PC. I can report that under VirtualBox, every major type of guest caused stability problems with the host (Windows 7, Windows XP, FreeBSD, Linux). Stability problems would include crashing of the guest, crashing of the host, network bogons (from interfaces resetting to interfaces hanging --- like yours). I switched various guests to VMWare (the free "player" version) and everything was smooth. Really smooth. No problems running guests for _days_. No problems running multiple guests. I don't use virtual PC much --- it runs XP mode ... just because that's included with Windows 7... but it never causes problems either FWIW. It seemed to me that every update after Sun passed to Oracle brought more bugs. My advice: run away from VirtualBox. On Mon, May 6, 2013 at 3:12 PM, Marc G. Fournier wrote: > > I'm having an odd issue with FreeBSD that I'm not sure how to trace / > where to look =85 > > I have 6 servers, all identical RAM / CPU / Ethernet / etc =85 4 of them = are > running VirtualBox, 2 are running Jails =85 one of the 4 I just switched = from > Jail -> Virtualbox =85 > > When running jail(s), the servers are rock solid =85 as soon as I switch = to > VirtualBox (the one I just switched is running one Vbox with a FreeBSD > Guest) =85 nothing else is running on the server =85 but I will get spora= dic > freezes of the Ethernet. One ran 46 days before it froze, then after a > reboot, it happened a few hours later, now its been running several hours > again without any issues =85 > > The machine itself is not frozen =85 I can connect via remote console, > login, do ps, etc =85 so its as if the Ethernet (bce device) just went > offline. > > I was pointed to a wiki about VirtualBox, and my current loader.conf look= s > like: > > =3D=3D=3D > aio_load=3D"YES" > kern.ipc.shm_use_phys=3D1 > accf_http_load=3D"YES" > if_bridge_load=3D"YES" > if_tap_load=3D"YES" > hw.pci.enable_msix=3D0 > vboxdrv_load=3D"YES" > net.graph.maxdata=3D65536 > =3D=3D=3D > > I'm running the latest version of 9-STABLE as well as the latest version > of vBox available in ports =85 the bce device is an older version of > Broadcom, so not dealing a new one with new features: > > bce0: > > And as I say, these work great with jail'd environments ALIASed onto them= =85 > > The vBox environments are all configured for network using: > > --nic1 bridged --bridgeadapter1 bce1 > > Maybe I'm setting up the network wrong? But, it does work for awhile =85 > > I'm not seeing any errors on the console when the ethernet stops working = =85 > nothing to indicate an buffer overflowing or something like that =85 but, > again, I can login and run commands, so if there is something I can run t= o > get more useful details =85 ? > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-virtualization@FreeBSD.ORG Mon May 6 21:49:32 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5DBCDDDD for ; Mon, 6 May 2013 21:49:32 +0000 (UTC) (envelope-from nb@informatik.uni-bremen.de) Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by mx1.freebsd.org (Postfix) with ESMTP id E0CF4978 for ; Mon, 6 May 2013 21:49:31 +0000 (UTC) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r46LnSlY029707 for ; Mon, 6 May 2013 23:49:28 +0200 (CEST) Received: from [192.168.0.101] (77-23-66-20-dynip.superkabel.de [77.23.66.20]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id C9DED3B05 for ; Mon, 6 May 2013 23:49:28 +0200 (CEST) Message-ID: <51882568.4080402@informatik.uni-bremen.de> Date: Mon, 06 May 2013 23:49:28 +0200 From: Norbert Beckmann User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: Re: VirtualBox + FreeBSD 9-STABLE == Frozen Ethernet References: <1601E2D3-DF60-4CCB-9F92-9AD05BCBCB10@hub.org> In-Reply-To: <1601E2D3-DF60-4CCB-9F92-9AD05BCBCB10@hub.org> Content-Type: multipart/mixed; boundary="------------090304020008090607020503" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 May 2013 21:49:32 -0000 This is a multi-part message in MIME format. --------------090304020008090607020503 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit To Marc G. Fournier I do not think it's an issue with VirtualBox. I am running VirtualBox under Solaris. And I never had problems with it. Guests: ubuntu, Windows 7, Linux Mint, FreeBSD, Chrome OS. But the people of VirtualBox themselves state that Windows is somewhat delicate (don't remember whether they meant as guest or as host, I think both). Which would be comprehensible, because Windows has never become a real multi user / multi process system as Unix was by birth (nearly). I can neither help concerning the freezing Ethernet nor did I encounter similar things (as far as I remember). But i avail myself of the opportunity of re-posting an issue with just FreeBSD and VirtualBox. Sorry! I'm running FreeBSD 9.1 in VirtualBox. All is fine, but I cannot run the Gnome Desktop, because the mouse in inoperable. I already posted this problem on 03/03/13 and 03/04/13, but never got an answer. Here is a summary of my original posts again: Environment: (Host OS: Solaris 11.1) VirtualBox 4.6.2 (r82870) [4.6.12 now] Guest: FreeBSD 9.1-RELEASE (#0 r243825) Gnome 2.32 I did a fresh install of FreeBSD 9.1 in VirtualBox. After capturing the mouse pointer on black screen, copy/paste works too. Then I installed Gnome 2.32, following all the instructions at http://www.freebsd.org/gnome/docs/faq2.html#full-gnome. (I compiled.) Then I installed the guest additions, following all the instructions at https://wiki.freebsd.org/VirtualBox, chapter "Installing Guest Additions for FreeBSD guests". After the make, I called X -configure and moved a modified copy to /etc/X11/xorg.conf as proposed, and performed all the other things mentioned at that page. Problem: Mouse is not operational in FreeBSD: Gnome disabled and calling X, I get a black screen, the mouse pointer disappears, and I also cannot capture it manually. Gnome enabled, I get a proper gnome login screen after boot, the mouse pointer is there, but does not affect something. The movement and the position of the mouse pointer is even recognized by the login screen and thus Gnome. This is obvious because these small pop-ups like "Log in as .." appear when the mouse pointer moves over them. Hence, the sole functionality missing is the communication between Gnome and the mouse buttons. Extra attempts (no success / no harm): in /etc/rc.conf: enabling hald, dbus, mouse. in /usr/local/etc/hal/fdi/policy/ in addition to 90-vboxguest.fdi, adding 10-mouse-sysmouse.fdi from /usr/local/share/hal/fdi/policy/10osvendor. Attachment: /etc/X11/xorg.conf followed by /etc/rc.conf (both seemingly completely ok). Any ideas? Sorry for posting a question on a question, but after more than a month of silence I'm daring it. Norbert --------------090304020008090607020503 Content-Type: text/plain; charset=us-ascii; name="FreeBSDconfig" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="FreeBSDconfig" $ cat /etc/X11/xorg.conf Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" ModulePath "/usr/local/lib/xorg/modules" FontPath "/usr/local/lib/X11/fonts/misc/" FontPath "/usr/local/lib/X11/fonts/TTF/" FontPath "/usr/local/lib/X11/fonts/OTF" FontPath "/usr/local/lib/X11/fonts/Type1/" FontPath "/usr/local/lib/X11/fonts/100dpi/" FontPath "/usr/local/lib/X11/fonts/75dpi/" EndSection Section "Module" Load "extmod" Load "record" Load "dbe" Load "dri" Load "dri2" Load "glx" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "vboxmouse" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor Model" EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz" ### [arg]: arg optional Identifier "Card0" Driver "vboxvideo" VendorName "InnoTek Systemberatung GmbH" BoardName "VirtualBox Graphics Adapter" BusID "PCI:0:2:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" SubSection "Display" Viewport 0 0 Depth 1 EndSubSection SubSection "Display" Viewport 0 0 Depth 4 EndSubSection SubSection "Display" Viewport 0 0 Depth 8 EndSubSection SubSection "Display" Viewport 0 0 Depth 15 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection $ $ cat /etc/rc.conf hostname="" ifconfig_em0="DHCP" sshd_enable="YES" moused_enable="YES" ntpd_enable="YES" # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable dumpdev="AUTO" ##### Changes after installation vboxguest_enable="YES" vboxservice_enable="YES" # vbox's timesync: default: enabled, conflicts with ntpd (see above) vboxservice_flags="--disable-timesync" # begin extra --- hald_enable="YES" dbus_enable="YES" mouse_enable="YES" # end extra ----- #gnome_enable="YES" $ --------------090304020008090607020503-- From owner-freebsd-virtualization@FreeBSD.ORG Tue May 7 07:40:49 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CD0EE2AD for ; Tue, 7 May 2013 07:40:49 +0000 (UTC) (envelope-from vvm@tut.by) Received: from mail-bk0-x234.google.com (mail-bk0-x234.google.com [IPv6:2a00:1450:4008:c01::234]) by mx1.freebsd.org (Postfix) with ESMTP id 5B12C62B for ; Tue, 7 May 2013 07:40:48 +0000 (UTC) Received: by mail-bk0-f52.google.com with SMTP id q16so108578bkw.25 for ; Tue, 07 May 2013 00:40:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tut.by; s=google; h=x-received:message-id:from:to:cc:subject:date:mime-version :content-type:content-transfer-encoding:x-priority:x-msmail-priority :x-mailer:x-mimeole; bh=bzMOqOSBNNqH4RW4TmpxVvvzSzLGdC+w44T/X8p6pFM=; b=gU55G27vq0IRnHiYqZJZvJ6VA5jA5jQUNxO2lADRlQ5MOyDtCey7pTBC6vqXo505FQ LKoB1q18ChbL0+vc5N0+Mi7u2tOFBgbkp7+1YTNZKrx3xZsfJd6wsXzrUSSzuNbK52wl 3tQ6f0WvIzl+6pZjUDD79MruoKkMGAYUB3TIk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:from:to:cc:subject:date:mime-version :content-type:content-transfer-encoding:x-priority:x-msmail-priority :x-mailer:x-mimeole:x-gm-message-state; bh=bzMOqOSBNNqH4RW4TmpxVvvzSzLGdC+w44T/X8p6pFM=; b=icbf+i3gvUpWJm9xObRUF8qyVPae5YFkyZox4RHglRyQfl14BZsRT+LzRqhegTGByz 76IrbZ3F5/khjbOBHW4MNu388t3h1yyVKHOrhxAy2sfbxTHx+vt2yZeGhrVRUE2oWfbH A57Nf4DsfzLbyyGQjrsFqoDMtQRiHmeDOHRSONlcqPqCObRN5azuTZBUOO1jyHbjQ6N0 5ry1Hz9Bj72gWO1uJTreED9ap5l7nnaOVhC9n3e2/9wfe81hqo135uI/xb3mk1vyn3N5 HjgTj5QUx1QMWfPleTzlv+iV/5wRSFRjn6ZdhjVLfJgGNiEsGG/7DdbuhSTqKe0C2q4Y pncw== X-Received: by 10.205.23.207 with SMTP id rb15mr214022bkb.94.1367912447282; Tue, 07 May 2013 00:40:47 -0700 (PDT) Received: from TSVVM2 (ns1.st.by. [217.23.123.90]) by mx.google.com with ESMTPSA id cn9sm4860362bkb.6.2013.05.07.00.40.45 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 07 May 2013 00:40:46 -0700 (PDT) Message-ID: From: "Victor Miasnikov" To: , "Alexander Motin" Subject: ATA controller and Hyper-V "synthetic storage driver" handle the IDE disks devices ( but not for the CD-ROM) Re: Hyper-V on FreeBSD Date: Tue, 7 May 2013 10:40:41 +0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.3790.4548 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4913 X-Gm-Message-State: ALoCoQn+7m1H2fL9lVTJb9ZrgK3dcxYUGqIgf8UFrcYvrqnXsH3s2slv2Q33U5odNpknLG2wbM/T Cc: larry.melia@ieee.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 07 May 2013 07:40:49 -0000 Hi! > prevent default OS driver from attaching to emulated ATA controller when Hyper-V Disable both primary and secondary ATA controller prevent use CD-ROM device in VM ( guest) Because "synthetic storage driver" not handle CD-ROM devices ( IMHO, even more: Hyper-V host work with CD-ROM only as "PCI bus" device) Best regards, Victor Miasnikov Blog: http://vvm.blog.tut.by/ P.S. http://lists.freebsd.org/pipermail/freebsd-virtualization/2013-April/001180.html == . . . On 23.04.2013 17:07, Larry Melia wrote: . . . > Removing our ATA patches, on the other hand, results in a huge > performance loss. This is because the root file system is managed by the > ATA driver, which is emulated under Hyper-V. == Place on IDE disk only "\boot" ( and bootloader), other on SCSI . P.P.S. Larry, I'm found Youre 3 e-mail accounts, You use all 3 ? From owner-freebsd-virtualization@FreeBSD.ORG Tue May 7 08:07:53 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 16072C56 for ; Tue, 7 May 2013 08:07:53 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-ea0-x22e.google.com (mail-ea0-x22e.google.com [IPv6:2a00:1450:4013:c01::22e]) by mx1.freebsd.org (Postfix) with ESMTP id A1040765 for ; Tue, 7 May 2013 08:07:52 +0000 (UTC) Received: by mail-ea0-f174.google.com with SMTP id f15so132968eak.19 for ; Tue, 07 May 2013 01:07:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=9BuTjySuvJxxfXKFCDPDwBmypLToL/pZy1FEO3Zs0rU=; b=K9lqPY3Yd+tEwECrye+At2txkxPebQt/2L5UouqNAzmswRd0CfzDc1XE/zQJScBuuI D/yhV9DzCfi2cPfdAk3eFZV9g8op4C7GzVke+30+f5Vwupm6inqE0hGpLGVm6y4XaJ1Z 65UHRTC4dG3N/yYmGzrmybCftrcR3pYYUecBdtJkwx7dCL5+/kqTMpwFYwN8PKmLd2kl A1acg6JnNnXNDH1ZBFHXZY9RacBFSw1Z0Ded1o8qUs7Nnec/6m0y+w7wAsGXEEnj2xb6 kDq1Blnuk/ten+jkc9dxCps+Pn7Izjx5qsxEB/QDtly6j+pjjRT3aolVHKgHC+kw/3G9 Hh3g== X-Received: by 10.15.32.71 with SMTP id z47mr2960140eeu.3.1367914071818; Tue, 07 May 2013 01:07:51 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (mavhome.mavhome.dp.ua. [213.227.240.37]) by mx.google.com with ESMTPSA id x41sm28886436eey.17.2013.05.07.01.07.49 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 May 2013 01:07:50 -0700 (PDT) Sender: Alexander Motin Message-ID: <5188B653.5020207@FreeBSD.org> Date: Tue, 07 May 2013 11:07:47 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130413 Thunderbird/17.0.5 MIME-Version: 1.0 To: Victor Miasnikov Subject: Re: ATA controller and Hyper-V "synthetic storage driver" handle the IDE disks devices ( but not for the CD-ROM) Re: Hyper-V on FreeBSD References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: larry.melia@ieee.org, freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 07 May 2013 08:07:53 -0000 On 07.05.2013 10:40, Victor Miasnikov wrote: >> prevent default OS driver from attaching to emulated ATA controller >> when Hyper-V > > Disable both primary and secondary ATA controller prevent use CD-ROM > device in VM ( guest) > > Because "synthetic storage driver" not handle CD-ROM devices > ( IMHO, even more: Hyper-V host work with CD-ROM only as "PCI bus" device) Then may be possibility of blocking/hiding specific ATA channels or devices could be investigated. > http://lists.freebsd.org/pipermail/freebsd-virtualization/2013-April/001180.html > > == > . . . > On 23.04.2013 17:07, Larry Melia wrote: > . . . >> Removing our ATA patches, on the other hand, results in a huge >> performance loss. This is because the root file system is managed by the >> ATA driver, which is emulated under Hyper-V. > == > > Place on IDE disk only "\boot" ( and bootloader), other on SCSI . May be instead of splitting filesystem it could be better to boot from "SCSI" completely and forget about "ATA"? Or there is no option ROM for SCSI boot in Hyper-V? -- Alexander Motin From owner-freebsd-virtualization@FreeBSD.ORG Tue May 7 09:01:04 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 439D92EE for ; Tue, 7 May 2013 09:01:04 +0000 (UTC) (envelope-from vvm@tut.by) Received: from mail-bk0-x233.google.com (mail-bk0-x233.google.com [IPv6:2a00:1450:4008:c01::233]) by mx1.freebsd.org (Postfix) with ESMTP id C4107A13 for ; Tue, 7 May 2013 09:01:03 +0000 (UTC) Received: by mail-bk0-f51.google.com with SMTP id ji2so152282bkc.10 for ; Tue, 07 May 2013 02:01:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tut.by; s=google; h=x-received:message-id:from:to:cc:references:subject:date :mime-version:content-type:content-transfer-encoding:x-priority :x-msmail-priority:x-mailer:x-mimeole; bh=FP5jgfUcKsI6LCQPb3qyN/US/hoED2N717qswzUnxNw=; b=KsqTGgfsjui9U9g7sqORyTtas+NguWqSKoQEHHJBpWEu4hTC2A5k1yczQedxoiy5zZ tdYAHwCuW6naNk3ab/YnJV2gL2NBaVlH8eFVTYGIsk0uTF3jpcI5pgxQHmVpnK5CIoGY zqnA2PG/rMm1YdE5QUC85Cpd6xtW21shuscE4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:from:to:cc:references:subject:date :mime-version:content-type:content-transfer-encoding:x-priority :x-msmail-priority:x-mailer:x-mimeole:x-gm-message-state; bh=FP5jgfUcKsI6LCQPb3qyN/US/hoED2N717qswzUnxNw=; b=MW+ArpFs/wk3lp67v76ZHnmWcPR87PZAQAq9+a9+HzrMWpZCcyGWM3ueFdNDBsEVA5 wwV/vEXqRr+qt+YR22L5knh6TJSujn4zt12YMoiSdObsBrfurHpCPWFOcD4vOm/jPPFN BQ/YTgfP9FqtzI+OWusSyNSD2EKZEAYz6bgJtRKjP+xRXy7jwpW3uB+fkjDWmFAOHblf HjFmSVzC2BArwgTH0o7zsLi3zf6UiboxUpjb1GWlASjrFEcktHZ2LN0tQ01az6/6gJuL eXhqelK8heEYhP5cfeD9DfZoWQRLs2bRns1egtaQg6Dsm56WugZ5QxQq/uTkiUjUcjkL XWmw== X-Received: by 10.204.169.137 with SMTP id z9mr305040bky.33.1367917262317; Tue, 07 May 2013 02:01:02 -0700 (PDT) Received: from TSVVM2 (ns1.st.by. [217.23.123.90]) by mx.google.com with ESMTPSA id tl1sm6312238bkb.7.2013.05.07.02.00.58 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 07 May 2013 02:01:01 -0700 (PDT) Message-ID: <528D3052346640EBAD35D64A806F22BE@local.st.by> From: "Victor Miasnikov" To: "Alexander Motin" References: <5188B653.5020207@FreeBSD.org> Subject: Re: ATA controller and Hyper-V "synthetic storage driver" handle the IDE disks devices ( but not for the CD-ROM) Re: Hyper-V on FreeBSD Date: Tue, 7 May 2013 12:00:56 +0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.3790.4548 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4913 X-Gm-Message-State: ALoCoQnG9SN7hRwufahfGzyVtLQFeHNzykGRgtwIBn8vw7rtMMOlwwvJddZMGl/blH8rivR2fO5l Cc: larry.melia@ieee.org, freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 07 May 2013 09:01:04 -0000 Hi! > On 07.05.2013 10:40, Victor Miasnikov wrote: >>> prevent default OS driver from attaching to emulated ATA controller >>> when Hyper-V >> >> Disable both primary and secondary ATA controller prevent use CD-ROM >> device in VM ( guest) >> >> Because "synthetic storage driver" not handle CD-ROM devices >> ( IMHO, even more: Hyper-V host work with CD-ROM only as "PCI bus" device) > A.M.> Then may be possibility of blocking/hiding specific ATA channels or A.M.> devices could be investigated. IMHO, this ( or some like this) must be investigated In any case, need carefully testing work CD-ROM ( primary for LiveCD and (or) .ISO for setup FreeBSD) in Hyper-V enviroment >> http://lists.freebsd.org/pipermail/freebsd-virtualization/2013-April/001180.html >> >> == >> . . . >> On 23.04.2013 17:07, Larry Melia wrote: >> . . . L.M.>>> Removing our ATA patches, on the other hand, results in a huge L.M.>>> performance loss. This is because the root file system is managed by the L.M.>>> ATA driver, which is emulated under Hyper-V. >> == VVM>> VVM>> Place on IDE disk only "\boot" ( and bootloader), other on SCSI . VVM>> A.M.> A.M.> May be instead of splitting filesystem it could be better to boot from A.M.> "SCSI" completely and forget about "ATA"? A.M.> Or there is no option ROM for SCSI boot in Hyper-V? A.M.> Yes, boot from SCSI disk in Hyper-V VM ( "guest") is impossible Best regards, Victor Miasnikov Blog: http://vvm.blog.tut.by/ From owner-freebsd-virtualization@FreeBSD.ORG Wed May 8 02:49:59 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F2555658; Wed, 8 May 2013 02:49:58 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.208.146]) by mx1.freebsd.org (Postfix) with ESMTP id BF949ED9; Wed, 8 May 2013 02:49:58 +0000 (UTC) Received: from maia.hub.org (unknown [200.46.151.188]) by hub.org (Postfix) with ESMTP id 4F6411E56DB9; Tue, 7 May 2013 23:49:51 -0300 (ADT) Received: from hub.org ([200.46.208.146]) by maia.hub.org (mx1.hub.org [200.46.151.188]) (amavisd-maia, port 10024) with ESMTP id 21571-07; Wed, 8 May 2013 02:49:51 +0000 (UTC) Received: from Marc-Fourniers-Mac-mini.local (S01067cb21b2ff4ca.gv.shawcable.net [24.108.26.71]) by hub.org (Postfix) with ESMTPA id A0E861E56DB8; Tue, 7 May 2013 23:49:50 -0300 (ADT) Message-ID: <5189BD4D.70400@hub.org> Date: Tue, 07 May 2013 19:49:49 -0700 From: "Marc G. Fournier" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org, freebsd-net@freebsd.org Subject: Re: VirtualBox + FreeBSD 9-STABLE == Frozen Ethernet References: <1601E2D3-DF60-4CCB-9F92-9AD05BCBCB10@hub.org> <51882568.4080402@informatik.uni-bremen.de> In-Reply-To: <51882568.4080402@informatik.uni-bremen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 May 2013 02:49:59 -0000 On 2013-05-06 2:49 PM, Norbert Beckmann wrote: > To Marc G. Fournier > > I do not think it's an issue with VirtualBox. I am running VirtualBox > under Solaris. And I never had problems with it. > Guests: ubuntu, Windows 7, Linux Mint, FreeBSD, Chrome OS. > But the people of VirtualBox themselves state that Windows is somewhat > delicate (don't remember whether they meant as guest or as host, I > think both). > Which would be comprehensible, because Windows has never become a real > multi user / multi process system as Unix was by birth (nearly). > I can neither help concerning the freezing Ethernet nor did I encounter > similar things (as far as I remember). My first thought is that its something in the vboxnet kernel module when using a bridge ... I think the problem has been getting progressively worse, with each upgrade, but since I upgrade both vBox and the kernel in tandem, I'm currently working on going 'back in time' with the code, see if I can find some 'stable point' ... If anyone with more knowledge can suggest any commands I can run to provide debug info, or such ... ? I don't mind debugging, just dont' know what to provide that is useful ... From owner-freebsd-virtualization@FreeBSD.ORG Wed May 8 10:16:04 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C66FEF0F for ; Wed, 8 May 2013 10:16:04 +0000 (UTC) (envelope-from nbari@inbox.im) Received: from ca2.route.mx (ca2.route.mx [72.55.175.69]) by mx1.freebsd.org (Postfix) with ESMTP id 7D0A932A for ; Wed, 8 May 2013 10:16:04 +0000 (UTC) Received: (route-mx 8260 invoked from network); 8 May 2013 10:09:21 -0000 Received: from unknown (HELO nbari-z200.diz.la) (nbari@inbox.im@route.mx) (envelope-sender ) by ca2.route.mx (route-mx) with CAMELLIA256-SHA encrypted SMTP for ; 8 May 2013 10:09:21 -0000 Message-ID: <518A244C.3010601@inbox.im> Date: Wed, 08 May 2013 11:09:16 +0100 From: Nicolas de Bari Embriz Garcia Rojas User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130405 Thunderbird/17.0.5 MIME-Version: 1.0 To: "Marc G. Fournier" Subject: Re: VirtualBox + FreeBSD 9-STABLE == Frozen Ethernet References: <1601E2D3-DF60-4CCB-9F92-9AD05BCBCB10@hub.org> <51882568.4080402@informatik.uni-bremen.de> <5189BD4D.70400@hub.org> In-Reply-To: <5189BD4D.70400@hub.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 May 2013 10:16:04 -0000 When using bridge mode, use tap interfaces otherwise you will get problems when using more than one VM. regards On 05/08/2013 03:49, Marc G. Fournier wrote: > On 2013-05-06 2:49 PM, Norbert Beckmann wrote: >> To Marc G. Fournier >> >> I do not think it's an issue with VirtualBox. I am running VirtualBox >> under Solaris. And I never had problems with it. >> Guests: ubuntu, Windows 7, Linux Mint, FreeBSD, Chrome OS. >> But the people of VirtualBox themselves state that Windows is somewhat >> delicate (don't remember whether they meant as guest or as host, I >> think both). >> Which would be comprehensible, because Windows has never become a real >> multi user / multi process system as Unix was by birth (nearly). >> I can neither help concerning the freezing Ethernet nor did I encounter >> similar things (as far as I remember). > My first thought is that its something in the vboxnet kernel module > when using a bridge ... I think the problem has been getting > progressively worse, with each upgrade, but since I upgrade both vBox > and the kernel in tandem, I'm currently working on going 'back in > time' with the code, see if I can find some 'stable point' ... > > If anyone with more knowledge can suggest any commands I can run to > provide debug info, or such ... ? I don't mind debugging, just dont' > know what to provide that is useful ... > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-virtualization@FreeBSD.ORG Wed May 8 16:32:20 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 53B3126F; Wed, 8 May 2013 16:32:20 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.208.146]) by mx1.freebsd.org (Postfix) with ESMTP id 20E5FE06; Wed, 8 May 2013 16:32:20 +0000 (UTC) Received: from maia.hub.org (unknown [200.46.151.189]) by hub.org (Postfix) with ESMTP id 6929F4FFC2B; Wed, 8 May 2013 13:32:18 -0300 (ADT) Received: from hub.org ([200.46.208.146]) by maia.hub.org (mx1.hub.org [200.46.151.189]) (amavisd-maia, port 10024) with ESMTP id 86850-04; Wed, 8 May 2013 16:32:18 +0000 (UTC) Received: from [10.5.250.150] (remote.ilcs.sd63.bc.ca [142.31.148.2]) by hub.org (Postfix) with ESMTPA id C78F84FFC2A; Wed, 8 May 2013 13:32:16 -0300 (ADT) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: VirtualBox + FreeBSD 9-STABLE == Frozen Ethernet From: "Marc G. Fournier" In-Reply-To: <518A244C.3010601@inbox.im> Date: Wed, 8 May 2013 09:32:14 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <1601E2D3-DF60-4CCB-9F92-9AD05BCBCB10@hub.org> <51882568.4080402@informatik.uni-bremen.de> <5189BD4D.70400@hub.org> <518A244C.3010601@inbox.im> To: Nicolas de Bari Embriz Garcia Rojas X-Mailer: Apple Mail (2.1503) Cc: freebsd-net@freebsd.org, freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 May 2013 16:32:20 -0000 Do you happen to know of a HowTO for doing this? =20 figure there are a few extra steps then simply: ifconfig tapX plumb --bridgeadapter tapX Thx .. On 2013-05-08, at 03:09 , Nicolas de Bari Embriz Garcia Rojas = wrote: > When using bridge mode, use tap interfaces otherwise you will get > problems when using more than one VM. >=20 > regards >=20 > On 05/08/2013 03:49, Marc G. Fournier wrote: >> On 2013-05-06 2:49 PM, Norbert Beckmann wrote: >>> To Marc G. Fournier >>>=20 >>> I do not think it's an issue with VirtualBox. I am running = VirtualBox >>> under Solaris. And I never had problems with it. >>> Guests: ubuntu, Windows 7, Linux Mint, FreeBSD, Chrome OS. >>> But the people of VirtualBox themselves state that Windows is = somewhat >>> delicate (don't remember whether they meant as guest or as host, I >>> think both). >>> Which would be comprehensible, because Windows has never become a = real >>> multi user / multi process system as Unix was by birth (nearly). >>> I can neither help concerning the freezing Ethernet nor did I = encounter >>> similar things (as far as I remember). >> My first thought is that its something in the vboxnet kernel module >> when using a bridge ... I think the problem has been getting >> progressively worse, with each upgrade, but since I upgrade both vBox >> and the kernel in tandem, I'm currently working on going 'back in >> time' with the code, see if I can find some 'stable point' ... >>=20 >> If anyone with more knowledge can suggest any commands I can run to >> provide debug info, or such ... ? I don't mind debugging, just dont' >> know what to provide that is useful ... >>=20 >>=20 >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to = "freebsd-net-unsubscribe@freebsd.org" >=20 From owner-freebsd-virtualization@FreeBSD.ORG Sat May 11 10:00:07 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1DFBB6A6 for ; Sat, 11 May 2013 10:00:07 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id EBAFD129 for ; Sat, 11 May 2013 10:00:06 +0000 (UTC) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.14.5/8.14.5) with ESMTP id r4B9xoGM073820 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 11 May 2013 02:59:54 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <518E1691.6080206@freebsd.org> Date: Sat, 11 May 2013 02:59:45 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: FreeBSD virtualization mailing list , Testing@lists.pcbsd.org Subject: virtualbox, PCBSD and NAT mode Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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, 11 May 2013 10:00:07 -0000 I have been unable to get NAT mode to work for me. (bridging seems to work fine) is it known to be broken or otherwise fussy in freebsd 9.1? I have it under PCBSD 9.1 and installed the PBI.. other than the problem with NAT mode it seems to be working fine. but that is a deal breaker for when I'm running from a remote site through a vpn as I just get one VPN address.. I did set net.inet.ip-forwarding=1 but that didn't seem to help. The packets get out but the replies never get passed back through the NAT. They do make it back as far as the PC-BSD machine I do run it that way under OS-X so I know htat is the mode I need.