[pve-devel] disable-efi-enable-pxe-roms.patch break livemigration from old qemu guest without pxe
Alexandre DERUMIER
aderumier at odiso.com
Fri Oct 23 08:28:26 CEST 2015
>>my $cmd = { execute => 'qom-get', arguments => { path => 'net0', property =>
>>'romfile'} };
>>my $res = PVE::QemuServer::vm_qmp_command($vmid, $cmd);
>>print Dumper($res);
>>$VAR1 = 'efi-virtio.rom';
Seem good. (I'm not sure how to pass arguments to target vm).
If we make a patch, it could be great to backport it to proxmox 3.4, to allow migration between proxmox 3 & 4.
>>Not sure how that helps, so I will revert my changes until we
>>have a better solution for the problem.
I'll try to work on it next week.
----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "aderumier" <aderumier at odiso.com>, "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Vendredi 23 Octobre 2015 08:24:55
Objet: Re: [pve-devel] disable-efi-enable-pxe-roms.patch break livemigration from old qemu guest without pxe
> Another way could be to use add romfile option to netX in vmid.conf,
> and update it at vm_start if a new rom version is available (use glob on rom
> directory, take rom with biggest number suffix)
I don't really like above approach.
> It's possible also to use qmp "info qtree", to retrieve current rom filenames,
>
> on source vm.
> (we could keep roms with version suffix for examples)
my $cmd = { execute => 'qom-get', arguments => { path => 'net0', property =>
'romfile'} };
my $res = PVE::QemuServer::vm_qmp_command($vmid, $cmd);
print Dumper($res);
$VAR1 = 'efi-virtio.rom';
So we could query what files are used currently.
Not sure how that helps, so I will revert my changes until we
have a better solution for the problem.
More information about the pve-devel
mailing list