Date: Mon, 11 Nov 2013 22:13:13 -0800 From: Michael Dexter <editor@callfortesting.org> To: "Abhishek Gupta (LIS)" <abgupta@microsoft.com>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: Use of Floppy Drive with FreeBSD Virtual Machines Message-ID: <5281C6F9.8040109@callfortesting.org> In-Reply-To: <8c6f3f012fc94908bf6a40cdd0d235d7@BL2PR03MB210.namprd03.prod.outlook.com> References: <bbe6d48d21024e199eebb47601a8f0f7@BL2PR03MB210.namprd03.prod.outlook.com> <528128E2.6000006@callfortesting.org> <8c6f3f012fc94908bf6a40cdd0d235d7@BL2PR03MB210.namprd03.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Abhishek, On 11/11/13 11:37 AM, Abhishek Gupta (LIS) wrote: > Thanks so much for replying. Some follow up questions: > > a) Is it not possible to use an ISO file to do the BIOS updates? I have not. > b) I did not quite understand your second comment on why PCI pass > through may promote floppy disk use. Please could you elaborate a bit > more? The scenario I see the most is a virtualized (HyperV, VMware etc.) FreeNAS guest to which you pass a PCIe storage controller card to so that ZFS is given "bare metal" access to hardware disks yet has the benefit of the fast internal backplane if you will for networking, rather than going over copper or optical network interfaces. Because the FreeNAS guest may be one among many, it would not be desirable to reboot the whole system and boot to a floppy to apply a BIOS update to a PCIe controller card. Again, I have not tried anything like this but it is a possible use case of what you describe. Also mind you I never want to see another floppy-based BIOS again but they are still out there. Michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5281C6F9.8040109>