On 03/20/2018 02:02 PM, taii...@gmx.com wrote: > On 03/19/2018 08:02 PM, mad.scientist.at.la...@tutanota.com wrote: >> A virtual machine is useful largely because it isolates the VM from the real >> hardware, therefore it's not likely you can update firmware from a VM (you >> really shouldn't be able to). > Actually you can update firmware from a VM, I have done it many times > on many different PCI-e cards and I already updated the IR mode > firmware to the latest version in a linux VM (but you need DOS to go > IR>IT) > > It is part of the reason as to why SR-IOV was created besides the > performance benefits you also get security benefits with restricted > registers and the inability to flash a malicious firmware from a guest > if you attach a VF to the VM instead of the PF. > > I don't have any UEFI machines as I hate UEFI (all my machines run > coreboot with the grub payload) >> The reason they still want us to upgrade with dos is it's a lowest common >> denominator, i.e. every one has it or can get it (freedos). it also helps >> that it's a minimal enviroment. >> >> In any case, I suggest you run a REAL freedos on a Real machine, so that you >> can update real not virtual firmware. i.e. no Virtual Machine. > The issue is not being able to use linux as well and having a bare > metal freedos won't help my disk driver issue there still won't be a > way to load the files. . Curious ... you cannot use 'FreeDOS' even as a bootable cdrom? Its very easy to open the image, tuck in two files and one new directory, then close and burn the image.
FreeDOS comes with a 'generic' PATA / SATA driver for cdrom drives. Correction : (but you need DOS to go IR>IT) ---> the EFI Shell also can do it. Corbin
