Date: Thu, 8 Feb 2018 13:22:27 -0300 From: Mario Lobo <lobo@bsd.com.br> To: Peter Grehan <grehan@freebsd.org> Cc: freebsd-virtualization@freebsd.org Subject: Re: Bhyve passthrough problems (update) Message-ID: <CA%2ByoEx9-Xit-6VJ=0a-Na4GV%2BuLGhvr%2BqA%2BezTY052MpOCa5eA@mail.gmail.com> In-Reply-To: <bdef6d20-2dc7-8e91-7436-52a4c13be272@freebsd.org> References: <20180117202250.6ef90c6d@Papi.lobos> <b85ae2a8-1656-9dcb-a117-564deeb66214@freebsd.org> <20180119175257.3f29d9d6@Papi.lobos> <20180207201224.2c5c4c47@Papi.lobos> <bdef6d20-2dc7-8e91-7436-52a4c13be272@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2018-02-07 20:19 GMT-03:00 Peter Grehan <grehan@freebsd.org>: > Hi Mario, > > Well, now, even without setting up passthrough, the VM doesn't start >>> (which it did, before I svned up /usr/src). >>> >> ... > >> working: 321652 >>> not working (current): 328163 >>> >> ... > >> Any updates on this issue? >> > > Can you verify if the issue still occurrs if you destroy the guest before > re-invoking it ? (i.e. bhyvectl --destroy --vm=WIN-764 ) > > later, > > Peter. > Yes, I verified that. It still occurs even after destroying the VM. I also recompiled bhyve from the working (321652) release and the same error messages are still there. I even recreated a new disk.img and followed the same steps that worked before (1 cpu) to reinstall the VM from ISO to no avail. Bhyve doesn't even start any longer and exits with one of the error messages above. What previously worked now doesn't. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2ByoEx9-Xit-6VJ=0a-Na4GV%2BuLGhvr%2BqA%2BezTY052MpOCa5eA>