From owner-freebsd-virtualization@FreeBSD.ORG Fri Dec 12 02:15:21 2014 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 BF19021A for ; Fri, 12 Dec 2014 02:15:21 +0000 (UTC) Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F2DE9B5 for ; Fri, 12 Dec 2014 02:15:21 +0000 (UTC) Received: by mail-wi0-f178.google.com with SMTP id em10so1165438wid.5 for ; Thu, 11 Dec 2014 18:15:19 -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=sqznUVeT9C11f2MTSZnnecGaZwHNhB3WdcmhX+AkrGc=; b=IWlutGSzPzGajF9Y9/3+bweeO2SrOuwWUdxZDibzVaCNsHyqY5c87jcqlK2E6ElFtJ o4hVDko8FrpoUe6dRT4+jcF5y1MicJvzlFRzJR08wnE6Qu/m27LiAFfxLX+YzH870viu l2/EtmZxCcPBLsdIEfPdYLUPaWrL/axdt7vAcalPGHZXF5bo14ZzBPMKD6pySGsfxbx4 JmM3GAsZeG40/SKNA6csP6SW12Ye0pQfJ1mFOTJ8C8VqJSS+hqvkjL4CmRTgc3p2iMlO Xil65hLDvJimMhbWZ8HlCLzRHlvyDdQv95POxlXd7NEp0wtqZpMV42IOASBU8vD3haAb OsHw== MIME-Version: 1.0 X-Received: by 10.180.211.201 with SMTP id ne9mr3246658wic.30.1418350519787; Thu, 11 Dec 2014 18:15:19 -0800 (PST) Received: by 10.27.82.21 with HTTP; Thu, 11 Dec 2014 18:15:19 -0800 (PST) In-Reply-To: <207531434.2147650.1418173543122.JavaMail.zimbra@xinuos.com> References: <2021452008.2147540.1418173300017.JavaMail.zimbra@xinuos.com> <207531434.2147650.1418173543122.JavaMail.zimbra@xinuos.com> Date: Thu, 11 Dec 2014 18:15:19 -0800 Message-ID: Subject: Re: vmrun.sh error From: Neel Natu To: Susan Stanziano 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: Fri, 12 Dec 2014 02:15:21 -0000 Hi Susan, On Tue, Dec 9, 2014 at 5:05 PM, Susan Stanziano wrote: > > Hello, > > Craig suggested that I send this question to this mail alias: > > A couple of comments after creating VM's and using the vmrun.sh in /usr/share/examples/bhyve/vmrun.sh: > > 1) I know you can't run two VM's at the same time with the same vmname, but the error message from bhyveload is not informative to a new user: > > bhyveload: could not open "vmname" > > 2) The solution with the multiple use of a vmname seems to be that after vmrun.sh issues the bhyvectl --destroy command, if there was a "sleep 1" added, giving time for the destroy, the error message from bhyveload wouldn't have to happen. > > What do you think? > I think the issue you are hinting at is that if /dev/vmm/testvm exists there isn't a reliable way to know whether or not 'testvm' is actually "running". There is no good way to fix this until we get to a single process model. However, you know for sure that if '/dev/vmm/testvm' does not exist then it is also not running. So, perhaps the following patch fixes your problem: https://people.freebsd.org/~neel/patches/vmrun_destroy.patch best Neel > Thanks, > > Susan Stanziano > > > _______________________________________________ > 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"