public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Mira Limbeck <m.limbeck@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH v2 qemu-server 2/2] fix clone_disk failing for nonexistent cloudinit disk
Date: Tue, 6 Oct 2020 13:10:32 +0200	[thread overview]
Message-ID: <1443552e-8e26-ae63-9b09-d9a68d54177b@proxmox.com> (raw)
In-Reply-To: <4eedd179-1ac9-3150-8f35-9c18fd7ef656@proxmox.com>

On 10/6/20 10:56 AM, Mira Limbeck wrote:
>
> On 10/5/20 5:35 PM, Thomas Lamprecht wrote:
>> On 28.09.20 10:36, Mira Limbeck wrote:
>>> After migration or a rollback the cloudinit disk might not be 
>>> allocated, so
>>> volume_size_info() fails. As we override the value anyway for cloudinit
>>> and efi disks simply move the volume_size_info() call into the 'else'
>>> branch.
>>>
>>> Signed-off-by: Mira Limbeck <m.limbeck@proxmox.com>
>>> ---
>>> v2: changed subject
>>>
>>>   PVE/QemuServer.pm | 4 +++-
>>>   1 file changed, 3 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
>>> index 2747c66..49765b7 100644
>>> --- a/PVE/QemuServer.pm
>>> +++ b/PVE/QemuServer.pm
>>> @@ -6895,10 +6895,10 @@ sub clone_disk {
>>>       $storeid = $storage if $storage;
>>>         my $dst_format = resolve_dst_disk_format($storecfg, 
>>> $storeid, $volname, $format);
>>> -    my ($size) = PVE::Storage::volume_size_info($storecfg, 
>>> $drive->{file}, 3);
>>>         print "create full clone of drive $drivename 
>>> ($drive->{file})\n";
>>>       my $name = undef;
>>> +    my $size = undef;
>>>       if (drive_is_cloudinit($drive)) {
>>>           $name = "vm-$newvmid-cloudinit";
>>>           $name .= ".$dst_format" if $dst_format ne 'raw';
>>> @@ -6906,6 +6906,8 @@ sub clone_disk {
>>>           $size = PVE::QemuServer::Cloudinit::CLOUDINIT_DISK_SIZE;
>>>       } elsif ($drivename eq 'efidisk0') {
>>>           $size = get_efivars_size($conf);
>>> +    } else {
>>> +        ($size) = PVE::Storage::volume_size_info($storecfg, 
>>> $drive->{file}, 3);
>>>       }
>>>       $size /= 1024;
>> doesn't this logs a "use of undefined value in division" or something 
>> like that
>> somewhere in the non-else case?
> No, in the cloudinit case we set it to a constant. In the efidisk case 
> we call get_efivars_size() which dies if efivars is not a file, 
> otherwise we get a size (-s). And in the else case we also die if we 
> can't get the size. So size is set in every case before the first use.
To clarify, the returned size in volume_size_info can be undefined, but 
not the other 2 cases. Would a die be a good idea in case the 
volume_size_info call returns 'undef'?
>>
>>>       $newvolid = PVE::Storage::vdisk_alloc($storecfg, $storeid, 
>>> $newvmid, $dst_format, $name, $size);
>>>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>




  reply	other threads:[~2020-10-06 11:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28  8:36 [pve-devel] [PATCH v2 qemu-server 1/2] fix VM clone from snapshot with " Mira Limbeck
2020-09-28  8:36 ` [pve-devel] [PATCH v2 qemu-server 2/2] fix clone_disk failing for nonexistent " Mira Limbeck
2020-10-05 15:35   ` Thomas Lamprecht
2020-10-06  8:56     ` Mira Limbeck
2020-10-06 11:10       ` Mira Limbeck [this message]
2020-10-16 13:45         ` Thomas Lamprecht
2020-10-16 13:40   ` [pve-devel] applied: " Thomas Lamprecht
2020-10-16 13:40 ` [pve-devel] applied: [PATCH v2 qemu-server 1/2] fix VM clone from snapshot with " Thomas Lamprecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1443552e-8e26-ae63-9b09-d9a68d54177b@proxmox.com \
    --to=m.limbeck@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal