From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 8 01:05:05 2015 Return-Path: Delivered-To: virtualization@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6F1118A3 for ; Sun, 8 Feb 2015 01:05:05 +0000 (UTC) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (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 31A4FF54 for ; Sun, 8 Feb 2015 01:05:02 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id EA61016A405 for ; Sun, 8 Feb 2015 02:04:57 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XBSCFrR-yk7A; Sun, 8 Feb 2015 02:04:47 +0100 (CET) Received: from [192.168.10.9] (vaio [192.168.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 093C916A402 for ; Sun, 8 Feb 2015 02:04:47 +0100 (CET) Message-ID: <54D6B62F.5030003@digiware.nl> Date: Sun, 08 Feb 2015 02:04:47 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: virtualization@FreeBSD.org Subject: Running grub-bhyve in the background??? Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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, 08 Feb 2015 01:05:05 -0000 Hi (Peter), I'm trying to run grub-bhyve completely automated but when I run my version of vmrun.sh like ../bin/bhyve-run -f /usr/local/etc/ezbhyve/Ubuntu1204A/rc.conf & Thegrub-bhyve loader waits for me to forground it again, because it wants to write to the output. Probably this is due to the use of curses, which only continues if it is actually connected to the foreground. ==== + /usr/local/sbin/grub-bhyve -e -vvv -r hd0,msdos1 -m ./ubuntu-12.04.map -M 2048M ubuntu-12.04.1 [2] + Suspended (tty output) ../bin/bhyve-run -f /usr/local/etc/ezbhyve/Ubuntu1204A/rc.conf ==== Is it possible on the commandline to get grub-bhyve to continue regardless the backgrounded state? Regards, --Willem Jan From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 8 01:34:39 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2B4B6CD5 for ; Sun, 8 Feb 2015 01:34:39 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 059C8234 for ; Sun, 8 Feb 2015 01:34:38 +0000 (UTC) Received: from [192.168.1.2] (Seawolf.HML3.ScaleEngine.net [209.51.186.28]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 31D4693685 for ; Sun, 8 Feb 2015 01:34:32 +0000 (UTC) Message-ID: <54D6BD46.6000707@freebsd.org> Date: Sat, 07 Feb 2015 20:35:02 -0500 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: Re: Running grub-bhyve in the background??? References: <54D6B62F.5030003@digiware.nl> In-Reply-To: <54D6B62F.5030003@digiware.nl> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="N5pgorReujiSkBuGsafoO9MwkB0caX13v" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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, 08 Feb 2015 01:34:39 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --N5pgorReujiSkBuGsafoO9MwkB0caX13v Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-02-07 20:04, Willem Jan Withagen wrote: > Hi (Peter), >=20 > I'm trying to run grub-bhyve completely automated but when I run my > version of vmrun.sh like > ../bin/bhyve-run -f /usr/local/etc/ezbhyve/Ubuntu1204A/rc.conf & >=20 > Thegrub-bhyve loader waits for me to forground it again, because it > wants to write to the output. Probably this is due to the use of curses= , > which only continues if it is actually connected to the foreground. >=20 > =3D=3D=3D=3D > + /usr/local/sbin/grub-bhyve -e -vvv -r hd0,msdos1 -m ./ubuntu-12.04.ma= p > -M 2048M ubuntu-12.04.1 >=20 > [2] + Suspended (tty output) ../bin/bhyve-run -f > /usr/local/etc/ezbhyve/Ubuntu1204A/rc.conf > =3D=3D=3D=3D >=20 > Is it possible on the commandline to get grub-bhyve to continue > regardless the backgrounded state? >=20 > Regards, > --Willem Jan > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@fr= eebsd.org" >=20 In newer versions of the bhyve loader, you can redirect the output to a nmdm (null modem) device, so it can run unattended --=20 Allan Jude --N5pgorReujiSkBuGsafoO9MwkB0caX13v Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJU1r1JAAoJEJrBFpNRJZKfq2MQAIbW/PFJGDLQn7lI2IjqvcpN F8R+GjLwSMKKDQwg5ehpUtZHQkXqBnI9wkSRXjpmqlmvA31F+nSHv0lgb02VvxW/ 6JSSLskl73gFq27oz0T2sMIMVHh4B+cte3m45IpFuDE4r180rIqstMNaelIpkElS u6jRB2cU/+shjYjDW4u3EfgkO4S79fsHAcJtinA6b4zj9Z4t32eKMbfVVlVqm2eZ 6mKksUXHQmUfD4oHt9/00clqIOZ00yi5s6QtifnbuZxkGd6yi13/rRWa78juliJa HCG+xACmSB/PkC9gbtTpxNnf3k+mvWOFUVQ0HVRd7zQefQGXXrwMV++ydIu8/BmA w7SKVMy424d7ofcCfuh94kmw2jCClaqFeZBLQHsGjaqaW+51owlLvAiC4V0aZEb+ qQKks6wMKcVXqMy0NXu8cPsZ4B2rjBauc9ybjxgSV4pt0jXVZVPin6hkEMLDTCM0 36v9tGOgNEhRQGRh3UhtmjE87spI4cHm3Booka5rfaamWS/7wyd9LWKbV4hhErx9 fg3jiKE2pMIRrg5GMKSatAF0Bc77+udJPM8kH4YEtzLdcvzO8+rLIAHqBYiutWbL ugSycCCHyS+IlC3fc2TqCvzAkJm0DnA/ttlWN9OA5xlnvpaQZXRtlPbiIgihPgAa NVXicSi5qjXAEuPpjXx/ =GTLb -----END PGP SIGNATURE----- --N5pgorReujiSkBuGsafoO9MwkB0caX13v-- From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 8 15:03:13 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7862EACC; Sun, 8 Feb 2015 15:03:13 +0000 (UTC) Received: from smtp.digiware.nl (smtp.digiware.nl [31.223.170.169]) (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 3698A2EE; Sun, 8 Feb 2015 15:03:12 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id C256A16A408; Sun, 8 Feb 2015 16:03:09 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sg4NC9UZIzHc; Sun, 8 Feb 2015 16:02:51 +0100 (CET) Received: from [192.168.10.9] (vaio [192.168.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 9D2A316A402; Sun, 8 Feb 2015 15:53:45 +0100 (CET) Message-ID: <54D77879.2040903@digiware.nl> Date: Sun, 08 Feb 2015 15:53:45 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Allan Jude , freebsd-virtualization@freebsd.org Subject: Re: Running grub-bhyve in the background??? References: <54D6B62F.5030003@digiware.nl> <54D6BD46.6000707@freebsd.org> In-Reply-To: <54D6BD46.6000707@freebsd.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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, 08 Feb 2015 15:03:13 -0000 On 8-2-2015 2:35, Allan Jude wrote: > On 2015-02-07 20:04, Willem Jan Withagen wrote: >> Hi (Peter), >> >> I'm trying to run grub-bhyve completely automated but when I run my >> version of vmrun.sh like >> ../bin/bhyve-run -f /usr/local/etc/ezbhyve/Ubuntu1204A/rc.conf & >> >> Thegrub-bhyve loader waits for me to forground it again, because it >> wants to write to the output. Probably this is due to the use of curses, >> which only continues if it is actually connected to the foreground. >> >> ==== >> + /usr/local/sbin/grub-bhyve -e -vvv -r hd0,msdos1 -m ./ubuntu-12.04.map >> -M 2048M ubuntu-12.04.1 >> >> [2] + Suspended (tty output) ../bin/bhyve-run -f >> /usr/local/etc/ezbhyve/Ubuntu1204A/rc.conf >> ==== >> >> Is it possible on the commandline to get grub-bhyve to continue >> regardless the backgrounded state? > In newer versions of the bhyve loader, you can redirect the output to a > nmdm (null modem) device, so it can run unattended bhyveloader does work like this. And even if there is nobody to listen to the loader, things to continue. It just takes 10 sec. But once in a while I have trouble getting grub-bhyve to act the same. If I connect it to a nmdm-device it just waits for me to connect. And if I do not specify a device, it is nog possible to run it in the background. A inbetween sulution at the moment is to run grub-bhyve -c /dev/null. That continues, dus does not offer the possibility to interfere in the boot process. At least not for my ubuntu-12.04 VMs. So a flag with grub-bhyve to not require a forground process, or even better: ignore flowcontrol on the -c device, would be nice. --WjW From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 8 20:39:55 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 66AFFBA1; Sun, 8 Feb 2015 20:39:55 +0000 (UTC) Received: from mail1.yamagi.org (yugo.yamagi.org [212.48.122.103]) (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 2682C80F; Sun, 8 Feb 2015 20:39:53 +0000 (UTC) Received: from p579a7a27.dip0.t-ipconnect.de ([87.154.122.39] helo=kosei.home.yamagi.org.dhcp.yamagi.org) by mail1.yamagi.org with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.85 (FreeBSD)) (envelope-from ) id 1YKY5h-000PrI-KW; Sun, 08 Feb 2015 21:04:26 +0100 Date: Sun, 8 Feb 2015 21:04:19 +0100 From: Yamagi Burmeister To: wjw@digiware.nl Subject: Re: Running grub-bhyve in the background??? Message-Id: <20150208210419.4c503d676018682f63babcc3@yamagi.org> In-Reply-To: <54D77879.2040903@digiware.nl> References: <54D6B62F.5030003@digiware.nl> <54D6BD46.6000707@freebsd.org> <54D77879.2040903@digiware.nl> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.25; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org, allanjude@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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, 08 Feb 2015 20:39:55 -0000 On Sun, 08 Feb 2015 15:53:45 +0100 Willem Jan Withagen wrote: > A inbetween sulution at the moment is to run grub-bhyve -c /dev/null. > That continues, dus does not offer the possibility to interfere in the > boot process. At least not for my ubuntu-12.04 VMs. I hacked around that problem by writing one bit into the nmdm device. Or to say it in code: true > $NMDMB & sleep 0.5 /usr/local/sbin/grub-bhyve -r $BOOT -m $MAP -M $MEMORY -c $NMDMA $NAME & It's not a nice solution but at least it works reliable. Regards, Yamagi -- Homepage: www.yamagi.org XMPP: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 8 20:49:28 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7AD604D1; Sun, 8 Feb 2015 20:49:28 +0000 (UTC) Received: from smtp.digiware.nl (smtp.digiware.nl [31.223.170.169]) (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 37508908; Sun, 8 Feb 2015 20:49:28 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 2CEF416A403; Sun, 8 Feb 2015 21:49:24 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xclv3Cc_IRRb; Sun, 8 Feb 2015 21:48:57 +0100 (CET) Received: from [192.168.10.9] (vaio [192.168.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id C38F116A401; Sun, 8 Feb 2015 21:48:57 +0100 (CET) Message-ID: <54D7CBB9.3040206@digiware.nl> Date: Sun, 08 Feb 2015 21:48:57 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Yamagi Burmeister Subject: Re: Running grub-bhyve in the background??? References: <54D6B62F.5030003@digiware.nl> <54D6BD46.6000707@freebsd.org> <54D77879.2040903@digiware.nl> <20150208210419.4c503d676018682f63babcc3@yamagi.org> In-Reply-To: <20150208210419.4c503d676018682f63babcc3@yamagi.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org, allanjude@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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, 08 Feb 2015 20:49:28 -0000 On 8-2-2015 21:04, Yamagi Burmeister wrote: > On Sun, 08 Feb 2015 15:53:45 +0100 > Willem Jan Withagen wrote: > >> A inbetween sulution at the moment is to run grub-bhyve -c /dev/null. >> That continues, dus does not offer the possibility to interfere in the >> boot process. At least not for my ubuntu-12.04 VMs. > > I hacked around that problem by writing one bit into the nmdm device. > Or to say it in code: > > true > $NMDMB & > sleep 0.5 > /usr/local/sbin/grub-bhyve -r $BOOT -m $MAP -M $MEMORY -c $NMDMA $NAME & > > It's not a nice solution but at least it works reliable. Hi Yamagi, Nice trick. The advantage is probably that you can use the nmdm device in the grub-session if things do go south? I've starting ripping the guts out of Grub2.... But it really looks like a huge swiss-army knive and has several stacked layers of routines. Even ignoring all languages, modules and odd platforms...... I've got it loading now, but very little output trace. Curses is taking most of it. :( --WjW From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 8 20:53:38 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8089D7D2; Sun, 8 Feb 2015 20:53:38 +0000 (UTC) Received: from mail-yk0-x22e.google.com (mail-yk0-x22e.google.com [IPv6:2607:f8b0:4002:c07::22e]) (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 3C50C9C2; Sun, 8 Feb 2015 20:53:38 +0000 (UTC) Received: by mail-yk0-f174.google.com with SMTP id 9so4498651ykp.5; Sun, 08 Feb 2015 12:53:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=GW0PtphFpnHAvOEYvP5+27FwcyjM6aV0ry3ifDP9icE=; b=aDjz1BDlgFqQ/+Lyyvpj2zoXQ/LGOzfEV0RIBWs6hwyW7h0cQBn+LriD05AlexK/k+ 8l7RhIMBo6QrhIw/vqUXkL7K6jwbfgxMxLo/wEivhXR5VteS0GmaCbpvmfqiUQA0sMFV fNS73MiS+TOr1ITlUcgLYftl0t9XN4F6tAMUjTKF/vcAHbuB7DU+f94OR+km8ntHX3Aa THyFTS4+F19b9a8cA4aJ4pCQ6eqFl99DIaOAf/XAhyTasvMw147tIRg3+BrHqF/WbM38 MrfiIy/e1jK3oj2QQiYjOx5RBtY4Lj66gcujoPjBYeMTz/VT35rmFVQg+auPEXfrnenr hsuw== X-Received: by 10.236.191.230 with SMTP id g66mr4814972yhn.29.1423428817359; Sun, 08 Feb 2015 12:53:37 -0800 (PST) MIME-Version: 1.0 Sender: jtubnor@gmail.com Received: by 10.170.60.148 with HTTP; Sun, 8 Feb 2015 12:53:17 -0800 (PST) In-Reply-To: <54D77879.2040903@digiware.nl> References: <54D6B62F.5030003@digiware.nl> <54D6BD46.6000707@freebsd.org> <54D77879.2040903@digiware.nl> From: Jason Tubnor Date: Mon, 9 Feb 2015 07:53:17 +1100 X-Google-Sender-Auth: FXRVOpGjZXX876aoAZbWDrF0o-4 Message-ID: Subject: Re: Running grub-bhyve in the background??? To: Willem Jan Withagen Content-Type: text/plain; charset=UTF-8 Cc: freebsd-virtualization@freebsd.org, Allan Jude X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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, 08 Feb 2015 20:53:38 -0000 For my OpenBSD guests, I just re-direct the grub-bhyve output to /dev/null while feeding in my step-through configuration for grub-bhyve. If I know how grub-bhyve is going to behave, I don't really need to see what is happening at that level and just hook bhyve to nmdm. On 9 February 2015 at 01:53, Willem Jan Withagen wrote: > On 8-2-2015 2:35, Allan Jude wrote: >> On 2015-02-07 20:04, Willem Jan Withagen wrote: >>> Hi (Peter), >>> >>> I'm trying to run grub-bhyve completely automated but when I run my >>> version of vmrun.sh like >>> ../bin/bhyve-run -f /usr/local/etc/ezbhyve/Ubuntu1204A/rc.conf & >>> >>> Thegrub-bhyve loader waits for me to forground it again, because it >>> wants to write to the output. Probably this is due to the use of curses, >>> which only continues if it is actually connected to the foreground. >>> >>> ==== >>> + /usr/local/sbin/grub-bhyve -e -vvv -r hd0,msdos1 -m ./ubuntu-12.04.map >>> -M 2048M ubuntu-12.04.1 >>> >>> [2] + Suspended (tty output) ../bin/bhyve-run -f >>> /usr/local/etc/ezbhyve/Ubuntu1204A/rc.conf >>> ==== >>> >>> Is it possible on the commandline to get grub-bhyve to continue >>> regardless the backgrounded state? > >> In newer versions of the bhyve loader, you can redirect the output to a >> nmdm (null modem) device, so it can run unattended > > bhyveloader does work like this. And even if there is nobody to listen > to the loader, things to continue. It just takes 10 sec. > > But once in a while I have trouble getting grub-bhyve to act the same. > If I connect it to a nmdm-device it just waits for me to connect. > And if I do not specify a device, it is nog possible to run it in the > background. > > A inbetween sulution at the moment is to run grub-bhyve -c /dev/null. > That continues, dus does not offer the possibility to interfere in the > boot process. At least not for my ubuntu-12.04 VMs. > > So a flag with grub-bhyve to not require a forground process, or even > better: ignore flowcontrol on the -c device, would be nice. > > --WjW > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" -- "Roads? Where we're going, we don't need roads" - Dr. Emmett "Doc" Brown From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 8 21:26:11 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 694965B0; Sun, 8 Feb 2015 21:26:11 +0000 (UTC) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (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 27F70D5C; Sun, 8 Feb 2015 21:26:10 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id BDD7D16A403; Sun, 8 Feb 2015 22:26:07 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fs7BWGwyjcYq; Sun, 8 Feb 2015 22:25:41 +0100 (CET) Received: from [192.168.10.9] (vaio [192.168.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 3935216A401; Sun, 8 Feb 2015 22:25:41 +0100 (CET) Message-ID: <54D7D455.1030508@digiware.nl> Date: Sun, 08 Feb 2015 22:25:41 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Jason Tubnor Subject: Re: Running grub-bhyve in the background??? References: <54D6B62F.5030003@digiware.nl> <54D6BD46.6000707@freebsd.org> <54D77879.2040903@digiware.nl> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org, Allan Jude X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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, 08 Feb 2015 21:26:11 -0000 On 8-2-2015 21:53, Jason Tubnor wrote: > For my OpenBSD guests, I just re-direct the grub-bhyve output to > /dev/null while feeding in my step-through configuration for > grub-bhyve. > > If I know how grub-bhyve is going to behave, I don't really need to > see what is happening at that level and just hook bhyve to nmdm. I agree with the later... And connecting stdout of grub-bhyve to /dev/null would probably work as well.... Will give it a shot. --WjW > On 9 February 2015 at 01:53, Willem Jan Withagen > wrote: >> On 8-2-2015 2:35, Allan Jude wrote: >>> On 2015-02-07 20:04, Willem Jan Withagen wrote: >>>> Hi (Peter), >>>> >>>> I'm trying to run grub-bhyve completely automated but when I >>>> run my version of vmrun.sh like ../bin/bhyve-run -f >>>> /usr/local/etc/ezbhyve/Ubuntu1204A/rc.conf & >>>> >>>> Thegrub-bhyve loader waits for me to forground it again, >>>> because it wants to write to the output. Probably this is due >>>> to the use of curses, which only continues if it is actually >>>> connected to the foreground. >>>> >>>> ==== + /usr/local/sbin/grub-bhyve -e -vvv -r hd0,msdos1 -m >>>> ./ubuntu-12.04.map -M 2048M ubuntu-12.04.1 >>>> >>>> [2] + Suspended (tty output) ../bin/bhyve-run -f >>>> /usr/local/etc/ezbhyve/Ubuntu1204A/rc.conf ==== >>>> >>>> Is it possible on the commandline to get grub-bhyve to >>>> continue regardless the backgrounded state? >> >>> In newer versions of the bhyve loader, you can redirect the >>> output to a nmdm (null modem) device, so it can run unattended >> >> bhyveloader does work like this. And even if there is nobody to >> listen to the loader, things to continue. It just takes 10 sec. >> >> But once in a while I have trouble getting grub-bhyve to act the >> same. If I connect it to a nmdm-device it just waits for me to >> connect. And if I do not specify a device, it is nog possible to >> run it in the background. >> >> A inbetween sulution at the moment is to run grub-bhyve -c >> /dev/null. That continues, dus does not offer the possibility to >> interfere in the boot process. At least not for my ubuntu-12.04 >> VMs. >> >> So a flag with grub-bhyve to not require a forground process, or >> even better: ignore flowcontrol on the -c device, would be nice. >> >> --WjW _______________________________________________ >> freebsd-virtualization@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To >> unsubscribe, send any mail to >> "freebsd-virtualization-unsubscribe@freebsd.org" > > > From owner-freebsd-virtualization@FreeBSD.ORG Mon Feb 9 21:34:35 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CF76773D for ; Mon, 9 Feb 2015 21:34:35 +0000 (UTC) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8C0C924B for ; Mon, 9 Feb 2015 21:34:34 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id ED49528429 for ; Mon, 9 Feb 2015 22:34:30 +0100 (CET) Received: from illbsd.quip.test (ip-89-177-50-74.net.upcbroadband.cz [89.177.50.74]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 2100B28428 for ; Mon, 9 Feb 2015 22:34:30 +0100 (CET) Message-ID: <54D927E5.6050601@quip.cz> Date: Mon, 09 Feb 2015 22:34:29 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:33.0) Gecko/20100101 Firefox/33.0 SeaMonkey/2.30 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: virtualbox-ose-4.3.16 USB passthrough does not work Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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, 09 Feb 2015 21:34:35 -0000 Hi, I have virtualbox-ose-4.3.16 and virtualbox-ose-kmod-4.3.16 installed on my PC-BSD (FreeBSD 10.1-RELEASE-p8 amd64 GENERIC). I tried to connect DJ mixer Rane TTM57SL and pass it's USB device (Serato sound card + special HID) to VBox guest Windows 7 Ultimated 32bit. I correctly set the USB filter, started the VM and then got following error: Failed to attach the USB device Serato TTM57SL to the virtual machine Windows 7 Ultimate 32 bit. Failed to create a proxy device for the USB device. (Error: VERR_READ_ERROR). Result Code: NS_ERROR_FAILURE (0x80004005) Component: Console Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6} VBoxManage lists the device (the last one): # VBoxManage list usbhost Host USB Devices: UUID: dc25c3c2-88b4-422a-a195-c13dfba58a6c VendorId: 0x045e (045E) ProductId: 0x0047 (0047) Revision: 0.0 (0000) Port: 0 USB version/speed: 0/1 Manufacturer: Microsoft Product: Microsoft 5-Button Mouse with IntelliEyeTM Address: /dev/ugen1.3 Current State: Busy UUID: f9613731-eb1c-41a1-a516-86707a4e596a VendorId: 0x067b (067B) ProductId: 0x2305 (2305) Revision: 0.0 (0000) Port: 0 USB version/speed: 0/1 Manufacturer: vendor 0x067b Product: IEEE-1284 Controller Address: /dev/ugen2.3 Current State: Busy UUID: 1c22de78-a318-4830-be8d-f6aecd0f3617 VendorId: 0x13e5 (13E5) ProductId: 0x0003 (0003) Revision: 0.0 (0000) Port: 0 USB version/speed: 0/1 Manufacturer: Serato Product: TTM57SL SerialNumber: TTM.01.00 Address: /dev/ugen1.4 Current State: Held Device permissions are OK: # ls -l /dev/ugen1.4 lrw-rw-rw- 1 root wheel 9 Feb 9 18:33 /dev/ugen1.4 -> usb/1.4.0 VirtualBox is running as root. Is USB passthrough supported on this version of VirtualBox? Should I have some special settings on host to allow this device for VBox guest? Miroslav Lachman From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 10 11:06:34 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CBF26CB0 for ; Tue, 10 Feb 2015 11:06:34 +0000 (UTC) Received: from host202-129-static.10-188-b.business.telecomitalia.it (host202-129-static.10-188-b.business.telecomitalia.it [188.10.129.202]) by mx1.freebsd.org (Postfix) with ESMTP id 48C61B3F for ; Tue, 10 Feb 2015 11:06:33 +0000 (UTC) Received: from [192.168.0.60] (MAURIZIO-PC [192.168.0.60]) by host202-129-static.10-188-b.business.telecomitalia.it (Postfix) with ESMTP id B6F6E16523; Tue, 10 Feb 2015 11:58:29 +0100 (CET) Message-ID: <54D9E455.1080506@cloverinformatica.it> Date: Tue, 10 Feb 2015 11:58:29 +0100 From: Maurizio Vairani User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-virtualization@freebsd.org Subject: Re: virtualbox-ose-4.3.16 USB passthrough does not work References: <54D927E5.6050601@quip.cz> In-Reply-To: <54D927E5.6050601@quip.cz> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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, 10 Feb 2015 11:06:34 -0000 Il 09/02/2015 22:34, Miroslav Lachman ha scritto: > Hi, > I have virtualbox-ose-4.3.16 and virtualbox-ose-kmod-4.3.16 installed > on my PC-BSD (FreeBSD 10.1-RELEASE-p8 amd64 GENERIC). I tried to > connect DJ mixer Rane TTM57SL and pass it's USB device (Serato sound > card + special HID) to VBox guest Windows 7 Ultimated 32bit. > > I correctly set the USB filter, started the VM and then got following > error: > > Failed to attach the USB device Serato TTM57SL to the virtual machine > Windows 7 Ultimate 32 bit. > > Failed to create a proxy device for the USB device. (Error: > VERR_READ_ERROR). > > Result Code: NS_ERROR_FAILURE (0x80004005) > Component: Console > Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6} > > > VBoxManage lists the device (the last one): > > # VBoxManage list usbhost > Host USB Devices: > > UUID: dc25c3c2-88b4-422a-a195-c13dfba58a6c > VendorId: 0x045e (045E) > ProductId: 0x0047 (0047) > Revision: 0.0 (0000) > Port: 0 > USB version/speed: 0/1 > Manufacturer: Microsoft > Product: Microsoft 5-Button Mouse with IntelliEyeTM > Address: /dev/ugen1.3 > Current State: Busy > > UUID: f9613731-eb1c-41a1-a516-86707a4e596a > VendorId: 0x067b (067B) > ProductId: 0x2305 (2305) > Revision: 0.0 (0000) > Port: 0 > USB version/speed: 0/1 > Manufacturer: vendor 0x067b > Product: IEEE-1284 Controller > Address: /dev/ugen2.3 > Current State: Busy > > UUID: 1c22de78-a318-4830-be8d-f6aecd0f3617 > VendorId: 0x13e5 (13E5) > ProductId: 0x0003 (0003) > Revision: 0.0 (0000) > Port: 0 > USB version/speed: 0/1 > Manufacturer: Serato > Product: TTM57SL > SerialNumber: TTM.01.00 > Address: /dev/ugen1.4 > Current State: Held > > > Device permissions are OK: > > # ls -l /dev/ugen1.4 > lrw-rw-rw- 1 root wheel 9 Feb 9 18:33 /dev/ugen1.4 -> usb/1.4.0 > > VirtualBox is running as root. > > Is USB passthrough supported on this version of VirtualBox? > > Should I have some special settings on host to allow this device for > VBox guest? > > Miroslav Lachman > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscribe@freebsd.org" Hi, this bug was solved in version 4.3.20_1. Look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194196 Regards, Maurizio ** From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 11 03:39:17 2015 Return-Path: Delivered-To: virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4671C369 for ; Wed, 11 Feb 2015 03:39:17 +0000 (UTC) Received: from mail-yk0-x22c.google.com (mail-yk0-x22c.google.com [IPv6:2607:f8b0:4002:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0D8EF8DD for ; Wed, 11 Feb 2015 03:39:14 +0000 (UTC) Received: by mail-yk0-f172.google.com with SMTP id 131so452820ykp.3 for ; Tue, 10 Feb 2015 19:39:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:content-type; bh=zoAtDPMADnGunzWL9eAC1rYR7ooB0h8RBTJrthQGFpw=; b=YlQKE1m9v42yk3rA6bmFE3XjzcA7CDWg02PIhrKZ63oh/T6W3Kdq2VZbVuXR0QDOGU g+3uf+YzA6czo2dHKKKc0BY39Xqh/6N5vvOZ9jiuD991FBOatWhRmcKU/jwDhR3L+tVY qYRZES9+n6zY3BEn5vyRscmZUcGV5mUacGJb1AFrMPBX1J8RAfumA8rBbjNwhRF95bkj RRgZiG+BF4KtfheGgpgdBXuo2XO9GhTsxJVRG8bg/7OEiz3xiNSBFdbFjAL4gSUe2z9c vCxz4BpFt29YLmSFr/MvAFQZG+yG00QUzy5TKdaTuVtc1n8HeykiQGd3PlDt9LyKOizG TNmw== X-Received: by 10.236.32.4 with SMTP id n4mr6687605yha.128.1423625952957; Tue, 10 Feb 2015 19:39:12 -0800 (PST) MIME-Version: 1.0 Sender: jtubnor@gmail.com Received: by 10.170.60.148 with HTTP; Tue, 10 Feb 2015 19:38:52 -0800 (PST) From: Jason Tubnor Date: Wed, 11 Feb 2015 14:38:52 +1100 X-Google-Sender-Auth: A_ujWsYrg6jTHKH2RWjzIwU9Y4o Message-ID: Subject: OpenBSD guest in bhyve on AMD CPU To: virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Feb 2015 03:39:17 -0000 Hi, As posted in IRC, I am checking here if anyone has come across this issue. During boot on OpenBSD I get: panic: trap type 4, code=0, pc=ffffffff811b7134 The operating system has halted. Please press any key to reboot. I don't get this with the same ISO on an Intel CPU. Below is the console from the OpenBSD boot, the dmesg from FreeBSD and the bhyve command. Any suggestions or tips greatly appreciated. Thanks, Jason. -------------------------- console Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2015 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.7-beta (RAMDISK_CD) #733: Tue Jan 20 15:39:52 MST 2015 deraadt@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 1056964608 (1008MB) avail mem = 1027194880 (979MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xf101f (9 entries) bios0: vendor BHYVE version "1.00" date 03/14/2014 acpi0 at bios0: rev 2 acpi0: sleep states S5 acpi0: tables DSDT APIC FACP HPET MCFG acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Phenom(tm) II X4 955 Processor, 3214.13 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,CX8,APIC,SEP,PGE,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,POPCNT,HV,NXE,MMXX,FFXSR,PAGE1GB,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,SKINIT,PERF,ITSC cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache, 6MB 64b/line 48-way L3 cache cpu0: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu0: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative fatal protection fault in supervisor mode trap type 4 code 0 rip ffffffff811b7134 cs 8 rflags 10286 cr2 0 cpl e rsp ffffffff818058e0 panic: trap type 4, code=0, pc=ffffffff811b7134 The operating system has halted. Please press any key to reboot. ----- dmesg Copyright (c) 1992-2015 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.1-STABLE #0 r278028: Sun Feb 1 18:05:27 UTC 2015 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 CPU: AMD Phenom(tm) II X4 955 Processor (3214.18-MHz K8-class CPU) Origin="AuthenticAMD" Id=0x100f43 Family=0x10 Model=0x4 Stepping=3 Features=0x178bfbff Features2=0x802009 AMD Features=0xee500800 AMD Features2=0x37ff SVM: NP,NRIP,NAsids=64 TSC: P-state invariant real memory = 17179869184 (16384 MB) avail memory = 16063627264 (15319 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0: Changing APIC ID to 8 ioapic0 irqs 0-23 on motherboard random: initialized kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, cfbf0000 (3) failed cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x73 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xee00-0xeeff mem 0xd0000000-0xdfffffff,0xfdfe0000-0xfdfeffff,0xfde00000-0xfdefffff irq 18 at device 5.0 on pci1 vgapci0: Boot video device hdac0: mem 0xfdffc000-0xfdffffff irq 19 at device 5.1 on pci1 pcib2: irq 18 at device 2.0 on pci0 pci2: on pcib2 em0: port 0xdf00-0xdf1f mem 0xfdde0000-0xfddfffff,0xfddc0000-0xfdddffff irq 18 at device 0.0 on pci2 ----- bhyve command bhyve -AI -H -P -W -s 0:0,amd_hostbridge -s 1:0,lpc -s 2:0,virtio-net,tap20 -s 2:1,virtio-net,tap22 -s 2:2,virtio-net,tap23 -s 3:0,virtio-blk,/bhyve/vm/vmhost/disk/disk01.img -s 4:0,ahci-cd,/iso/OpenBSD-install57beta.iso -l com1,/dev/nmdm1A -c 1 -m 1024M vmhost From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 11 05:40:18 2015 Return-Path: Delivered-To: virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DE4E94A9 for ; Wed, 11 Feb 2015 05:40:17 +0000 (UTC) Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) (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 717855EA for ; Wed, 11 Feb 2015 05:40:17 +0000 (UTC) Received: by mail-wg0-f54.google.com with SMTP id y19so1147007wgg.13 for ; Tue, 10 Feb 2015 21:40:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+d/PT8/PHdDy7i79tivUpcEcSVQCYVs6CT3FZJe5ROA=; b=pIwg77edF6Bg2XOjZ3cPjXxpIMfTekkrCvj74uaI+CniAzWTAtFYVnyD9XVzc6qbZy VwEJAUFTIIj8m9LCFrheYX5NouOcztj+mcEshCHNvv2hfumGq85fHY4QrmdoElmXSIPE B1eM7tz60kdYmPkqzMzKSpJou+800F0sno1i2PLzLrgSLdzPw2UuetnLZvb/ibGE0K1s 6vDVKfpel+763sx5EMu9We9ZMgSuJ9M6ymQY1i64b0yZX+n+OCandsewxFzQMdrKSWmh NIwgq0iN7V2Opv+JaLpFseo6Wk7kIcZxC9I/AeV/w3aTmnWypCLfp0Kv/F3sM42hmzBo /pbA== MIME-Version: 1.0 X-Received: by 10.180.19.7 with SMTP id a7mr51629580wie.62.1423633215991; Tue, 10 Feb 2015 21:40:15 -0800 (PST) Received: by 10.27.91.79 with HTTP; Tue, 10 Feb 2015 21:40:15 -0800 (PST) In-Reply-To: References: Date: Tue, 10 Feb 2015 21:40:15 -0800 Message-ID: Subject: Re: OpenBSD guest in bhyve on AMD CPU From: Neel Natu To: Jason Tubnor Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Feb 2015 05:40:18 -0000 Hi Jason, On Tue, Feb 10, 2015 at 7:38 PM, Jason Tubnor wrote: > Hi, > > As posted in IRC, I am checking here if anyone has come across this > issue. During boot on OpenBSD I get: > > panic: trap type 4, code=0, pc=ffffffff811b7134 > I suspect that the guest is getting a #GP exception when accessing an MSR that is not emulated by bhyve. Can you start the guest with the "-w" option passed to bhyve? best Neel > The operating system has halted. > Please press any key to reboot. > > I don't get this with the same ISO on an Intel CPU. Below is the > console from the OpenBSD boot, the dmesg from FreeBSD and the bhyve > command. Any suggestions or tips greatly appreciated. > > Thanks, > > Jason. > > -------------------------- > console > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > Copyright (c) 1995-2015 OpenBSD. All rights reserved. http://www.OpenBSD.org > > OpenBSD 5.7-beta (RAMDISK_CD) #733: Tue Jan 20 15:39:52 MST 2015 > deraadt@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD > real mem = 1056964608 (1008MB) > avail mem = 1027194880 (979MB) > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xf101f (9 entries) > bios0: vendor BHYVE version "1.00" date 03/14/2014 > acpi0 at bios0: rev 2 > acpi0: sleep states S5 > acpi0: tables DSDT APIC FACP HPET MCFG > acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: AMD Phenom(tm) II X4 955 Processor, 3214.13 MHz > cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,CX8,APIC,SEP,PGE,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,POPCNT,HV,NXE,MMXX,FFXSR,PAGE1GB,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,SKINIT,PERF,ITSC > cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB > 64b/line 16-way L2 cache, 6MB 64b/line 48-way L3 cache > cpu0: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative > cpu0: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative > fatal protection fault in supervisor mode > trap type 4 code 0 rip ffffffff811b7134 cs 8 rflags 10286 cr2 0 cpl e > rsp ffffffff818058e0 > panic: trap type 4, code=0, pc=ffffffff811b7134 > > The operating system has halted. > Please press any key to reboot. > > ----- > dmesg > > Copyright (c) 1992-2015 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 10.1-STABLE #0 r278028: Sun Feb 1 18:05:27 UTC 2015 > root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 > CPU: AMD Phenom(tm) II X4 955 Processor (3214.18-MHz K8-class CPU) > Origin="AuthenticAMD" Id=0x100f43 Family=0x10 Model=0x4 Stepping=3 > Features=0x178bfbff > Features2=0x802009 > AMD Features=0xee500800 > AMD Features2=0x37ff > SVM: NP,NRIP,NAsids=64 > TSC: P-state invariant > real memory = 17179869184 (16384 MB) > avail memory = 16063627264 (15319 MB) > Event timer "LAPIC" quality 400 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > FreeBSD/SMP: 1 package(s) x 4 core(s) > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > ioapic0: Changing APIC ID to 8 > ioapic0 irqs 0-23 on motherboard > random: initialized > kbd1 at kbdmux0 > acpi0: on motherboard > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, cfbf0000 (3) failed > cpu0: on acpi0 > cpu1: on acpi0 > cpu2: on acpi0 > cpu3: on acpi0 > attimer0: port 0x40-0x43 irq 0 on acpi0 > Timecounter "i8254" frequency 1193182 Hz quality 0 > Event timer "i8254" frequency 1193182 Hz quality 100 > atrtc0: port 0x70-0x73 irq 8 on acpi0 > Event timer "RTC" frequency 32768 Hz quality 0 > Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: port 0xee00-0xeeff mem > 0xd0000000-0xdfffffff,0xfdfe0000-0xfdfeffff,0xfde00000-0xfdefffff irq > 18 at device 5.0 on pci1 > vgapci0: Boot video device > hdac0: mem 0xfdffc000-0xfdffffff irq 19 > at device 5.1 on pci1 > pcib2: irq 18 at device 2.0 on pci0 > pci2: on pcib2 > em0: port 0xdf00-0xdf1f > mem 0xfdde0000-0xfddfffff,0xfddc0000-0xfdddffff irq 18 at device 0.0 > on pci2 > > ----- > bhyve command > > bhyve -AI -H -P -W -s 0:0,amd_hostbridge -s 1:0,lpc -s > 2:0,virtio-net,tap20 -s 2:1,virtio-net,tap22 -s 2:2,virtio-net,tap23 > -s 3:0,virtio-blk,/bhyve/vm/vmhost/disk/disk01.img -s > 4:0,ahci-cd,/iso/OpenBSD-install57beta.iso -l com1,/dev/nmdm1A -c 1 -m > 1024M vmhost > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 12 11:23:27 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7741BBF6 for ; Thu, 12 Feb 2015 11:23:27 +0000 (UTC) Received: from mail.h3q.com (mail.h3q.com [213.73.89.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.h3q.com", Issuer "Thawte DV SSL CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 10BB51E6 for ; Thu, 12 Feb 2015 11:23:26 +0000 (UTC) Received: (qmail 16689 invoked from network); 12 Feb 2015 11:16:42 -0000 Received: from mail.h3q.com (HELO mail.h3q.com) (cryx) by mail.h3q.com with ESMTPS (DHE-RSA-CAMELLIA256-SHA encrypted); 12 Feb 2015 11:16:42 -0000 Message-ID: <54DC8B98.4090902@h3q.com> Date: Thu, 12 Feb 2015 12:16:40 +0100 From: Philipp Wuensche User-Agent: Postbox 3.0.11 (Macintosh/20140602) MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: bhyve and PCI Passthrough a USB Controller Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Feb 2015 11:23:27 -0000 Hi, I'm currently trying to passthrough a PCIe USB 3.0 Controller to one of my bhyve VMs. I'm running 10.1-RELEASE and the controller is a Renesas Technology Corp. uPD720202 USB 3.0 Host Controller After disabling the xhci driver in the FreeBSD kernel and putting the correct pci-id into loader.conf the controller is hooked to the vmm module: ppt1@pci0:7:0:0: class=0x0c0330 card=0x00151912 chip=0x00151912 rev=0x02 hdr=0x00 vendor = 'Renesas Technology Corp.' class = serial bus subclass = USB lspic shows me this: # lspci -vxxs 07:00.0 07:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02) (prog-if 30 [XHCI]) Subsystem: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller Flags: bus master, fast devsel, latency 0, IRQ 40 Memory at fbff0000 (64-bit, non-prefetchable) Capabilities: [50] Power Management version 3 Capabilities: [70] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [90] MSI-X: Enable- Count=8 Masked- Capabilities: [a0] Express Endpoint, MSI 00 00: 12 19 15 00 46 00 10 00 02 30 03 0c 10 00 00 00 10: 04 00 ff fb 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 12 19 15 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 28 01 00 00 I then try to bind the controller to the VM using the bhyve command option "-s 7,passthru,7/0/0". The loader starts but then bhyve exits with: "Unsupported MSI-X configuration: 7/0/0" I've had an intel PCIe ethernet card in the very same slot as the USB controller and pci passthrough worked without a problem. I did some research on the matter and I found this post regarding VMware and the very same controller https://communities.vmware.com/message/2203210 There the problem was solved by "deactivating the "Message-Signaled Interrupts" of the "passthroughed" PCI card in the virtual machine, the USB 3.0 controller works now." Is there anything similar with bhyve to get the controller working or should I start hunting for a different controller that might work as on the VMware mailinglist suggested? Any suggestions for known to be working USB Controllers with bhyve and PCI passthrough? Greetings, Philipp From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 12 23:07:16 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7D06B6E5 for ; Thu, 12 Feb 2015 23:07:16 +0000 (UTC) Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au [203.13.68.150]) (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 39A98B13 for ; Thu, 12 Feb 2015 23:07:15 +0000 (UTC) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id DE902281111 for ; Fri, 13 Feb 2015 09:07:12 +1000 (EST) X-Amavis-Modified: Mail body modified (using disclaimer) - iredmail.onthenet.com.au X-Virus-Scanned: amavisd-new at 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 10024) with ESMTP id i7U_YtZkGEmE for ; Fri, 13 Feb 2015 09:07:12 +1000 (EST) Received: from Peters-MacBook-Pro.local (unknown [64.245.0.210]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id 85E5B280F56; Fri, 13 Feb 2015 09:07:09 +1000 (EST) Message-ID: <54DD321C.80808@freebsd.org> Date: Thu, 12 Feb 2015 15:07:08 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Philipp Wuensche Subject: Re: bhyve and PCI Passthrough a USB Controller References: <54DC8B98.4090902@h3q.com> In-Reply-To: <54DC8B98.4090902@h3q.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Feb 2015 23:07:16 -0000 Hi Philipp, > I then try to bind the controller to the VM using the bhyve command > option "-s 7,passthru,7/0/0". The loader starts but then bhyve exits with: > > "Unsupported MSI-X configuration: 7/0/0" This error message is when bhyve sees the MSI-x table and PBA (pending bit-array) regions being in the same physical page. It's perhaps overly cautious since we don't implement the PBA in any case. Would you be willing to try a patch that relaxes that check ? Another option for bhyve is to hide the MSI-x capability from the guest, which should hopefully fall back to using MSI. > Is there anything similar with bhyve to get the controller working or > should I start hunting for a different controller that might work as on > the VMware mailinglist suggested? > > Any suggestions for known to be working USB Controllers with bhyve and > PCI passthrough? I've not tried with any discrete cards, but any XHCI controller that has the table and PBA regions either in separate BARs or not in the same 4K region (recommended behaviour in the PCIe spec) should be fine. later, Peter, From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 12 23:14:01 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B873091B for ; Thu, 12 Feb 2015 23:14:01 +0000 (UTC) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6DC48C2D for ; Thu, 12 Feb 2015 23:14:00 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 0F5E22842C; Fri, 13 Feb 2015 00:13:52 +0100 (CET) Received: from illbsd.quip.test (ip-89-177-50-74.net.upcbroadband.cz [89.177.50.74]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id B767428434; Fri, 13 Feb 2015 00:13:50 +0100 (CET) Message-ID: <54DD33AE.5070100@quip.cz> Date: Fri, 13 Feb 2015 00:13:50 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Maurizio Vairani , freebsd-virtualization@freebsd.org Subject: Re: virtualbox-ose-4.3.16 USB passthrough does not work References: <54D927E5.6050601@quip.cz> <54D9E455.1080506@cloverinformatica.it> In-Reply-To: <54D9E455.1080506@cloverinformatica.it> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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, 12 Feb 2015 23:14:01 -0000 Maurizio Vairani wrote on 02/10/2015 11:58: > Il 09/02/2015 22:34, Miroslav Lachman ha scritto: >> Hi, >> I have virtualbox-ose-4.3.16 and virtualbox-ose-kmod-4.3.16 installed >> on my PC-BSD (FreeBSD 10.1-RELEASE-p8 amd64 GENERIC). I tried to >> connect DJ mixer Rane TTM57SL and pass it's USB device (Serato sound >> card + special HID) to VBox guest Windows 7 Ultimated 32bit. [...] >> VirtualBox is running as root. >> >> Is USB passthrough supported on this version of VirtualBox? >> >> Should I have some special settings on host to allow this device for >> VBox guest? >> >> Miroslav Lachman > Hi, > this bug was solved in version 4.3.20_1. Look at > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194196 Thank you for your reply. I upgraded VirtualBox to version 4.3.20_4 but now I have a different problem. I must modified devd/usb.conf to disable loading of kernel modules snd_uaudio and uhid, I also disabled webcamd because it was launched by USB device connect event. I also tried to stop devd. The problem is, that Windows 7 in VirtualBox does see the Serato USB device as Sound card (listed in Windows Device Manager) # VBoxManage list usbhost UUID: d692318e-eff6-4aeb-8acc-c4a0b8d48dcd VendorId: 0x13e5 (13E5) ProductId: 0x0003 (0003) Revision: 0.0 (0000) Port: 0 USB version/speed: 0/1 Manufacturer: Serato Product: TTM57SL SerialNumber: TTM.01.00 Address: /dev/ugen1.4 Current State: Captured but when I run Serato Scratch Live or drivers install, the device disappeared from the guest. VBoxManage shows it as Busy and with different UUID and different ProductId # VBoxManage list usbhost UUID: 7dff504b-adea-4740-b146-0d2c487dd961 VendorId: 0x13e5 (13E5) ProductId: 0x8003 (8003) Revision: 0.0 (0000) Port: 0 USB version/speed: 0/1 Manufacturer: Serato Product: TTM57SL SerialNumber: TTM.01.00 Address: /dev/ugen1.4 Current State: Busy These two lines are written in to /var/log/messages in the event of the disappearance from guest. Feb 13 00:02:18 xxx kernel: ugen1.4: at usbus1 (disconnected) Feb 13 00:02:19 xxx kernel: ugen1.4: at usbus1 Is there something more I can try to tune up? Miroslav Lachman From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 12 23:54:24 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E18FC290 for ; Thu, 12 Feb 2015 23:54:23 +0000 (UTC) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6FDBEFDA for ; Thu, 12 Feb 2015 23:54:23 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 7F3E928428; Fri, 13 Feb 2015 00:54:21 +0100 (CET) Received: from illbsd.quip.test (ip-89-177-50-74.net.upcbroadband.cz [89.177.50.74]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 2035A28426; Fri, 13 Feb 2015 00:54:20 +0100 (CET) Message-ID: <54DD3D2B.10506@quip.cz> Date: Fri, 13 Feb 2015 00:54:19 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Maurizio Vairani , freebsd-virtualization@freebsd.org Subject: Re: virtualbox-ose-4.3.16 USB passthrough does not work References: <54D927E5.6050601@quip.cz> <54D9E455.1080506@cloverinformatica.it> <54DD33AE.5070100@quip.cz> In-Reply-To: <54DD33AE.5070100@quip.cz> 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.18-1 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, 12 Feb 2015 23:54:24 -0000 Miroslav Lachman wrote on 02/13/2015 00:13: > Maurizio Vairani wrote on 02/10/2015 11:58: >> Il 09/02/2015 22:34, Miroslav Lachman ha scritto: >>> Hi, >>> I have virtualbox-ose-4.3.16 and virtualbox-ose-kmod-4.3.16 installed >>> on my PC-BSD (FreeBSD 10.1-RELEASE-p8 amd64 GENERIC). I tried to >>> connect DJ mixer Rane TTM57SL and pass it's USB device (Serato sound >>> card + special HID) to VBox guest Windows 7 Ultimated 32bit. > > [...] > >>> VirtualBox is running as root. >>> >>> Is USB passthrough supported on this version of VirtualBox? >>> >>> Should I have some special settings on host to allow this device for >>> VBox guest? >>> >>> Miroslav Lachman > > >> Hi, >> this bug was solved in version 4.3.20_1. Look at >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194196 > > Thank you for your reply. I upgraded VirtualBox to version 4.3.20_4 but > now I have a different problem. > > I must modified devd/usb.conf to disable loading of kernel modules > snd_uaudio and uhid, I also disabled webcamd because it was launched by > USB device connect event. I also tried to stop devd. > > The problem is, that Windows 7 in VirtualBox does see the Serato USB > device as Sound card (listed in Windows Device Manager) > > # VBoxManage list usbhost > > UUID: d692318e-eff6-4aeb-8acc-c4a0b8d48dcd > VendorId: 0x13e5 (13E5) > ProductId: 0x0003 (0003) > Revision: 0.0 (0000) > Port: 0 > USB version/speed: 0/1 > Manufacturer: Serato > Product: TTM57SL > SerialNumber: TTM.01.00 > Address: /dev/ugen1.4 > Current State: Captured > > but when I run Serato Scratch Live or drivers install, the device > disappeared from the guest. > > > VBoxManage shows it as Busy and with different UUID and different ProductId > > > # VBoxManage list usbhost > > UUID: 7dff504b-adea-4740-b146-0d2c487dd961 > VendorId: 0x13e5 (13E5) > ProductId: 0x8003 (8003) > Revision: 0.0 (0000) > Port: 0 > USB version/speed: 0/1 > Manufacturer: Serato > Product: TTM57SL > SerialNumber: TTM.01.00 > Address: /dev/ugen1.4 > Current State: Busy > > > These two lines are written in to /var/log/messages in the event of the > disappearance from guest. > > Feb 13 00:02:18 xxx kernel: ugen1.4: at usbus1 (disconnected) > Feb 13 00:02:19 xxx kernel: ugen1.4: at usbus1 > > > Is there something more I can try to tune up? I got it. The Serato device is detected as soundcard by default, but when the manufacturer's software touch it, it is internally switched to some special device, no longer detected as soundcard and this is why it changes it's ProductId. VirtualBox guest must have both type of devices added as USB filter. Miroslav Lachman