I'm using this version on xenial,
andy@bastion:~/temp$ qemu-img -h
qemu-img version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.31), Copyright (c)
2004-2008 Fabrice Bellard
qemu-img convert -f raw -O vpc -o subformat=fixed,force_size
/tmp/azure_config_disk_image20180901-22672-16zxelu papapa2.vhd
unfortun
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a reg
** Changed in: qemu (Ubuntu Xenial)
Importance: Medium => Wishlist
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to convert raw->VHD (fixed) adds extra padding
This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.10
---
qemu (1:2.5+dfsg-5ubuntu10.10) xenial; urgency=medium
[Nishanth Aravamudan]
* debian/patches/ubuntu/add_force_size_option.patch:
block/vpc: fix VHD size calculation. (LP: #1490611)
-- Christian Ehrhardt M
Verified Proposed:
dd if=/dev/zero of=source-disk.img bs=1M count=4096
qemu-img convert -f raw -o subformat=fixed -O vpc source-disk.img
dest-disk-old.vhd
#upgrade
$qemu-img convert -f raw -o subformat=fixed -O vpc source-disk.img
dest-disk-new.vhd
$qemu-img convert -f raw -o subformat=fixed,for
Hello Stephen, or anyone else affected,
Accepted qemu into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.5+dfsg-
5ubuntu10.10 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
The other fixes I wanted to bundle turned out to have a too low rate of
response and some show issues on testing. To not postpone this fix any
longer (which it already had it share of) I un-bundled this fix and
moved it into xenial-proposed now.
It is now in the SRU review queue and given that th
Simplified steps to reproduce (without Azure cli / credentials)
1. Start as in the SRU Template:
2. qemu-img convert -f raw -o subformat=fixed,force_size -O vpc source-disk.img
dest-disk-old.vhd
3. upgrade
4. qemu-img convert -f raw -o subformat=fixed,force_size -O vpc source-disk.img
dest-disk-
I could confirm the fix on its raw alignment:
Image with 4G
Pre Fix (4295467520-512)/1024/1024 = 4096,4765625
With Fix (4295467520-512)/1024/1024 = 4096,4765625
With Fix + force_size set: (4294967808-512)/1024/1024 = 4096
That means
1. no change without opt in
2. the desired effect when option is
Tests for any regressions on the ppa look good so far, going to try to
test the fixed case explicitly.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to convert raw
Preliminary builds as preparation for an SRU currently building at
Xenial https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2502
My testing will start on those, but if you can please give it as much
testing as you can as well.
--
You received this bug notification because you are a me
On Fri, Feb 17, 2017 at 11:29 PM, Nish Aravamudan <
nish.aravamu...@canonical.com> wrote:
> I believe Christian has it on his todo for the next SRU, though;
> Christian, could you confirm?
>
Yes, that is correct.
Sorry for the inconvenient delay due to the chain SRUs.
But at least the bigger ones
Hello Alexandre,
Yes, sorry, there have been several qemu SRUs pending and this one kept
getting pushed back. Note that as far as end-users are concerned wrt.
qemu, 16.04.2 is not really a relevant milestone. You'd still need to
`apt update; apt upgrade` to get the latest from the repositories --
Is it correct to assume that current 16.04.2 Xenial with the 2.5 QEMU
package, doesn't have this patch and can't generate MiB aligned Azure
images with qemu-img (no force_size support) ?
Any recommended PPA backport of QEMU from 16.10 (2.6+) ?
cheers.
--
You received this bug notification becau
On 17.08.2016 [10:20:26 -0700], Nish Aravamudan wrote:
> On 17.08.2016 [13:12:19 -], Chris J Arges wrote:
> > Can you rebase your fix on 1:2.5+dfsg-5ubuntu10.4 (due to the
> > regression fix mentioned in #25)?
>
> Will do!
Done.
> > Another thing about your backport is that it dropped the qe
** Attachment added: "attachment"
https://bugs.launchpad.net/bugs/1490611/+attachment/4724312/+files/attachment
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to
On 17.08.2016 [13:12:19 -], Chris J Arges wrote:
> Can you rebase your fix on 1:2.5+dfsg-5ubuntu10.4 (due to the
> regression fix mentioned in #25)?
Will do!
> Another thing about your backport is that it dropped the qem2 bits
> from the patch. Is there a reason for this? If so please mention
Can you rebase your fix on 1:2.5+dfsg-5ubuntu10.4 (due to the regression fix
mentioned in #25)?
Another thing about your backport is that it dropped the qem2 bits from the
patch. Is there a reason for this? If so please mention it in the debian/patch
file.
--
You received this bug notification
It looks like there was a regression caused by that security update see
bug 1612089. It might be best to coordinate with the security team, if
they are doing a regular SRU, regarding the the fix for this bug.
--
You received this bug notification because you are a member of qemu-
devel-ml, which
Uploaded.
** Changed in: qemu (Ubuntu Xenial)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to convert raw->VHD (fixed) adds
** Attachment added: "attachment"
https://bugs.launchpad.net/bugs/1490611/+attachment/4714298/+files/attachment
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to
Rejected:
Rejected by Brian Murray: There was a security update to qemu today, so
the SRU will need to be redone on top of that.
** Changed in: qemu (Ubuntu Xenial)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of qemu-
devel-ml, which is s
On 04.08.2016 [10:49:47 -], Robie Basak wrote:
> Uploaded to Xenial, thanks. Am I right in thinking that the new option
> force_size is required to be used with the patch to fix the problem?
> It's probably worth mentioning this in the Test Case in the bug
> description; otherwise it will appea
Uploaded to Xenial, thanks. Am I right in thinking that the new option
force_size is required to be used with the patch to fix the problem?
It's probably worth mentioning this in the Test Case in the bug
description; otherwise it will appear to testers that the fix doesn't
work.
--
You received t
** Changed in: qemu (Ubuntu)
Importance: Undecided => Medium
** Changed in: qemu (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
** Description changed:
- Starting with a raw disk image, using "qemu-img convert" to convert from
- raw to VHD results in the output VHD file's virtual size being aligned
- to the nearest 516096 bytes (16 heads x 63 sectors per head x 512 bytes
- per sector), instead of preserving the input file'
** Changed in: qemu (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to convert raw->VHD (fixed) adds extra padding
I have submitted a test build of 2.5+dfsg-5ubuntu10.1~ppa1 to
https://launchpad.net/~nacc/+archive/ubuntu/lp1490611. Please test that
version on 16.04.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/14
Just did a source check of 1:2.6+dfsg-3ubuntu1 in yakkety and the
upstream fix is already present (as it is 2.6 based). Working on the
backport now to 16.04.
** Changed in: qemu (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: qemu (Ubuntu Xenial)
Assignee: (unassigned) => Ni
Apologies, I uploaded an incorrect version to the PPA, please test 2.5
+dfsg-5ubuntu10.3~ppa1.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to convert raw->VHD (f
** Attachment added: "attachment"
https://bugs.launchpad.net/bugs/1490611/+attachment/4700967/+files/attachment
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to convert raw->VHD (fixed) adds extra pad
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to convert raw->VHD (fixed) adds ex
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Usin
Fix is available with QEMU 2.6:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=fb9245c2610932d33ce14
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to convert raw->
For the status change, I am really sorry.
I think at that time, I just want to check the status/history of this bug, but
I maybe click certain button by mistake.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad
Sounds good. I don't plan to retest unless you'd like me to; that change
shouldn't affect me.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to convert raw->VHD (fi
Thanks for testing! It is worth noting there is a v2 on the list now,
that changes the creator app string to "qem2" from "qemu" when using the
force_size option. That should only matter if you try to use your
converted images on QEMU (so QEMU will know on that image to rely by
default on the curr
It looks like the option is "force_size" rather than "force-size".
It also seems to be having the intended effect. I regenerate my nixos
iso with various configurations:
qemu-master + jeffcody patches + force_size = 2147484160
qemu-master + jeffcody patches (no force_size) = 2147992064
qemu-stabl
I've posted a series to qemu-devel to hopefully address this issue.
Cole, or anyone else that wants to test it out:
http://lists.nongnu.org/archive/html/qemu-devel/2016-02/msg05511.html
For the specific qemu-img convert case mentioned in this bug report, I
believe using the new "force-size" option
Unfortunately, VHDX is not supported in Azure.
I would be happy to help test out any patches.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to convert raw->VHD (f
First, I'd say that if you are converting an image over to use on
Hyper-V, you would probably be better served using the VHDX format
(completely different from VHD) - it is the newer format (and completely
different from VHD), and is supported by QEMU as well. It is better
defined and more consist
If you create a subformat option I would humbly recommend focusing on
Hyper-V and Azure compat, and then create an option that enforces the
legacy behavior with your patch. This is essentially what some Linux
distros have started to do.
--
You received this bug notification because you are a mem
In short: VHD is a mess and Microsoft isn't compatible with itself.
That's the root cause of all the trouble we have with it.
When the qemu VHD driver was written, it was designed to be compatible
with Virtual PC, which used the disk geometry as the definite source for
the image size. In order to
I bisected to this commit:
c70221df1f89953e85a3f1f96ceefbd6888bb55f
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to convert raw->VHD (fixed) adds extra padding to
Kevin Wolf, I added you since you were the author of the commit that I
bisected this bug to. Can you advise at all on this bug? Thank you.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Judging by their comments on bug 1399191, jan-wang1989 doesn't appear to
be a QEMU developer.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to convert raw->VHD (fi
Which release contains this fix?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to convert raw->VHD (fixed) adds extra padding to
the result file, which Microsoft
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to convert raw->VHD (fixed) adds extra padding to
the result
Public bug reported:
Starting with a raw disk image, using "qemu-img convert" to convert from
raw to VHD results in the output VHD file's virtual size being aligned
to the nearest 516096 bytes (16 heads x 63 sectors per head x 512 bytes
per sector), instead of preserving the input file's size as t
50 matches
Mail list logo
