On 12/22/2009 01:58 AM, Gleb Natapov wrote:
Your cable TV provider does likely also control what beside the FW (if anything)
runs on your set-top-box. So he can verify the FW upgrade doesn't break anything
in the field. That pre-deployment verification is not possible in non closed
environments.
On 12/21/2009 12:24 PM, Sebastian Herbszt wrote:
As stated before i don't like the idea of automagically upgrading the
firmware
on reset, e.g. after a live migration to a newer qemu version. You
have explained
that qemu-kvm needs this in order to work with live migration and
changed hw
Anthony Liguori wrote:
On 12/21/2009 12:24 PM, Sebastian Herbszt wrote:
As stated before i don't like the idea of automagically upgrading the
firmware
on reset, e.g. after a live migration to a newer qemu version. You
have explained
that qemu-kvm needs this in order to work with live migration
On Mon, Dec 21, 2009 at 01:17:23PM -0600, Anthony Liguori wrote:
Does any OS (Windows?) depend on the tables the bios creates (e.g.
smbios)
for licensing? It would be ugly if Windows wants you to
re-activate after a reboot
following a migration to newer qemu version and therefore possibly
On Mon, Dec 21, 2009 at 08:39:03PM +0100, Sebastian Herbszt wrote:
Anthony Liguori wrote:
On 12/21/2009 12:24 PM, Sebastian Herbszt wrote:
As stated before i don't like the idea of automagically
upgrading the firmware
on reset, e.g. after a live migration to a newer qemu version.
You have
Gleb Natapov wrote:
On Mon, Dec 21, 2009 at 08:39:03PM +0100, Sebastian Herbszt wrote:
Anthony Liguori wrote:
On 12/21/2009 12:24 PM, Sebastian Herbszt wrote:
As stated before i don't like the idea of automagically
upgrading the firmware
on reset, e.g. after a live migration to a newer qemu
On Mon, Dec 21, 2009 at 09:16:17PM +0100, Sebastian Herbszt wrote:
Gleb Natapov wrote:
On Mon, Dec 21, 2009 at 08:39:03PM +0100, Sebastian Herbszt wrote:
Anthony Liguori wrote:
On 12/21/2009 12:24 PM, Sebastian Herbszt wrote:
As stated before i don't like the idea of automagically
upgrading
