Date: Mon, 15 Dec 2014 16:13:05 -0500 (EST) From: Susan Stanziano <susan.stanziano@xinuos.com> To: Neel Natu <neelnatu@gmail.com> Cc: freebsd-virtualization@freebsd.org Subject: Re: vmrun.sh error Message-ID: <703912028.2258586.1418677985251.JavaMail.zimbra@xinuos.com> In-Reply-To: <CAFgRE9EVTOsL6osv_E5cQK45hYh_58_-mvc8DUjNNy1ufg2fSg@mail.gmail.com> References: <2021452008.2147540.1418173300017.JavaMail.zimbra@xinuos.com> <207531434.2147650.1418173543122.JavaMail.zimbra@xinuos.com> <CAFgRE9EVTOsL6osv_E5cQK45hYh_58_-mvc8DUjNNy1ufg2fSg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks, Neel, Thats a simple solution - I'll try it out. Are these patch fixes advertised in some way to the freebsd world? just want to know if there's a place to check before reporting a problem. ----- Original Message ----- From: "Neel Natu" <neelnatu@gmail.com> To: "Susan Stanziano" <susan.stanziano@xinuos.com> Cc: freebsd-virtualization@freebsd.org Sent: Thursday, December 11, 2014 9:15:19 PM Subject: Re: vmrun.sh error Hi Susan, On Tue, Dec 9, 2014 at 5:05 PM, Susan Stanziano <susan.stanziano@xinuos.com> 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?703912028.2258586.1418677985251.JavaMail.zimbra>