<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 03/19/2018 08:02 PM, <a class="moz-txt-link-abbreviated"
href="mailto:mad.scientist.at.large@tutanota.com">mad.scientist.at.large@tutanota.com</a>
wrote:
<blockquote type="cite" cite="mid:L8-gtOe--3-0@tutanota.com">
<pre wrap="">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).</pre>
</blockquote>
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)<br>
<br>
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.<br>
<br>
I don't have any UEFI machines as I hate UEFI (all my machines run
coreboot with the grub payload)<br>
<blockquote type="cite" cite="mid:L8-gtOe--3-0@tutanota.com">
<pre wrap="">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.</pre>
</blockquote>
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.<br>
</body>
</html>