Date: Fri, 27 May 2016 10:13:30 -0700 From: Peter Grehan <grehan@freebsd.org> To: Roman Bogorodskiy <novel@FreeBSD.org> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: bhyve graphics support Message-ID: <e69b25be-9527-e9e1-9112-127b5115cbc8@freebsd.org> In-Reply-To: <20160527170347.GA25472@kloomba> References: <442c6d8f-2b64-c88b-382a-cf73eb6f7404@freebsd.org> <20160527170347.GA25472@kloomba>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Roman, > I've just tried to do a Fedora installation and it worked like a charm. > > A couple of questions: > > * There was a limitation that AHCI devices must use slots 3-6. [1] > Is it still there? If yes, any plans to get rid of it? It's not a limitation for guests that can use MSI for AHCI. Older versions of Windows use legacy interrupts, but I noticed that 2k16 (and maybe recent builds of 10) are using now using MSI. The real fix is to have more flexible ACPI DSDT generation from inside of UEFI, but that's a non-trivial project. > * It *seems* that now it's OK to cycle a VM this way: > > host# bhyve ... > guest# reboot # guest goes away > host# bhyve ... # run it again > > Previously (with bhyveload) it didn't work (for me at least) without > doing "bhyvectl --destroy". Is it safe now not to call "bhyvectl > --destroy" before the second run now? Yes, except for the case when you modify the amount of memory given to the guest - then you will need to delete prior to the run with the new config. later, Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e69b25be-9527-e9e1-9112-127b5115cbc8>