Message ID | 20241212134504.1983757-1-vkuznets@redhat.com (mailing list archive) |
---|---|
Headers | show |
Series | vpc: Read images exported from Azure correctly | expand |
Vitaly Kuznetsov <vkuznets@redhat.com> writes: > Changes since v3: > - Split the change into two patches [Philippe Mathieu-Daude]. > > It was found that 'qemu-nbd' is not able to work with some disk images > exported from Azure as it uses a currently unknown 'wa\0\0' 'creator app' > signature. QEMU currently supports two methods for determining the image > size: CHS and 'current_size' and the list of known 'creator app's is used > to decide between the two. Invert the logic in QEMU and make 'current_size' > the default as it seems that VPC and old QEMU are the only two legacy apps > where preferring CHS makes sense. > > Vitaly Kuznetsov (2): > vpc: Split off vpc_ignore_current_size() helper > vpc: Read images exported from Azure correctly Ping?
Am 12.12.2024 um 14:45 hat Vitaly Kuznetsov geschrieben: > Changes since v3: > - Split the change into two patches [Philippe Mathieu-Daude]. > > It was found that 'qemu-nbd' is not able to work with some disk images > exported from Azure as it uses a currently unknown 'wa\0\0' 'creator app' > signature. QEMU currently supports two methods for determining the image > size: CHS and 'current_size' and the list of known 'creator app's is used > to decide between the two. Invert the logic in QEMU and make 'current_size' > the default as it seems that VPC and old QEMU are the only two legacy apps > where preferring CHS makes sense. > > Vitaly Kuznetsov (2): > vpc: Split off vpc_ignore_current_size() helper > vpc: Read images exported from Azure correctly Thanks, applied to the block branch. Kevin