Looks like Serge's fix has been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=efc8243d00ab4cf4fa05a9b
... so let's close this bug now.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I came here from : http://lists.gnu.org/archive/html/qemu-
devel/2011-07/msg02806.html
Actually, I experience an issue which may be useful to you.
I have a corrupted VHD file (as explained in that thread :
https://forums.virtualbox.org/viewtopic.php?f=7&t=20614 ). I wanted to
follow that procedur
** Branch linked: lp:ubuntu/qemu-kvm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/814222
Title:
kvm cannot use vhd files over 127GB
To manage notifications about this bug go to:
https://bugs.launc
This bug was fixed in the package qemu-kvm - 0.14.1+noroms-0ubuntu5
---
qemu-kvm (0.14.1+noroms-0ubuntu5) oneiric; urgency=low
* debian/patches/vpc.patch: detect vpc files which are too big
(LP: #814222)
-- Serge HallynMon, 12 Sep 2011 11:28:36 -0500
** Changed in: qemu-kv
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/814222
Title:
kvm cannot use vhd files over 127GB
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+b
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/814222
Title:
kvm cannot use vhd files over 127GB
To manage notifications about th
** Patch added: "proposed fix for upstream qemu"
https://bugs.launchpad.net/qemu/+bug/814222/+attachment/2231766/+files/0001-block-vpc.c-Detect-too-large-vpc-file.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
@Matthew
thanks for the attachments.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/814222
Title:
kvm cannot use vhd files over 127GB
To manage notifications about this bug go to:
https://bugs.laun
** Also affects: qemu
Importance: Undecided
Status: New
** Changed in: qemu-kvm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/814222
Title:
kvm ca
Also looking at your notes it looks like that previous patch which was
committed only affected the creation. So perhaps the same sort of check
can be incorporated into the conversion process as well, so that you
don't have the silent error.
--
You received this bug notification because you are a
I have attached a couple of VHDs that I created with Windows 7. These
should be helpful in your reproduction.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/814222
Title:
kvm cannot use vhd files ov
This is a dynamically expanding VHD file created using the reproduction
steps above on Windows 7. This one is 140GB and silently errors on
conversion.
This has not been formatted or even initialized.
"kvm-img info 140g-dynamic.vhd" does not show the proper geometry.
** Attachment added: "140g-d
This is a dynamically expanding VHD file created using the reproduction
steps above on Windows 7. This one is 120GB and converts correctly.
This has not been formatted or even initialized.
"kvm-img info 120g-dynamic.vhd" shows the proper geometry.
** Attachment added: "120g-dynamic.vhd"
ht
This could be tough to reproduce, as I don't seem to have a way to
create a vpc image > 127G in the first place:
root@ip-10-36-186-165:/mnt# qemu-img create -f vpc vpc2.img 130G
Formatting 'vpc2.img', fmt=vpc size=139586437120
qemu-img: The image size is too large for file format 'vpc'
root@ip-1
@Matthew,
yes, the definitions are at https://wiki.ubuntu.com/Bugs/Importance.
Your reasoning makes sense. I'll bump it back up, thanks.
** Changed in: qemu-kvm (Ubuntu)
Importance: Low => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Are the priority definitions documented somewhere?
I personally think you were right on when you had the priority at
medium.
Primarily because of the fact that no error is generated. It can't just
silently fail. If it generated an error (so that people knew they
needed to look for a work around
I'm afraid I'll need time to find a place where I can reproduce this.
As converting to fixed is listed as a workaround, I'm changing the
priority to low per priority definitions.
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed => New
** Changed in: qemu-kvm (Ubuntu)
Importance: Medi
Hm, no - that patch is already in natty and oneiric's qemu-kvm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/814222
Title:
kvm cannot use vhd files over 127GB
To manage notifications about this bu
Thanks for taking the time to submit this bug.
It looks like the 127G limit is known. A recent patch went in to help
with the symptom you are seeing, but unfortunately it only makes the
failure detectable :) It's a start at least.
The following commit should be pulled in:
commit 6e9ea0c0629fe
19 matches
Mail list logo
