It's qcow2 and increasing size is not what the problem is. The problem
is, if the forked image is smaller than the base image. In that case,
qemu-img should not create the image in first place.
--
qemu-img baseimage creation doesn't warn for image being smaller
should really raise a warning if ../base-dont-touch.img is smaller than 10GB
Here you are saying if the forked image is larger than the base image.
If QEmu doesn't handle a differnent size, even a bigger one, I don't see why
qemu-img create -b ... should take a size argument at all.
I just
You're right. the descriptive text is wrong. In fact, I was typing the
bug report up very quickly.
I did not want to change the size of the base image. Basically I just
wanted to checkpoint my machine. So in fact, I couldn't bother less
about the size and I thought qemu-img made me. But now I've
** Changed in: qemu-kvm (Ubuntu)
Status: New = Invalid
--
qemu-img baseimage creation doesn't warn for image being smaller
https://bugs.launchpad.net/bugs/565659
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
It's qcow2 and increasing size is not what the problem is. The problem
is, if the forked image is smaller than the base image. In that case,
qemu-img should not create the image in first place.
--
qemu-img baseimage creation doesn't warn for image being smaller
should really raise a warning if ../base-dont-touch.img is smaller than 10GB
Here you are saying if the forked image is larger than the base image.
If QEmu doesn't handle a differnent size, even a bigger one, I don't see why
qemu-img create -b ... should take a size argument at all.
I just
You're right. the descriptive text is wrong. In fact, I was typing the
bug report up very quickly.
I did not want to change the size of the base image. Basically I just
wanted to checkpoint my machine. So in fact, I couldn't bother less
about the size and I thought qemu-img made me. But now I've
** Changed in: qemu-kvm (Ubuntu)
Status: New = Invalid
--
qemu-img baseimage creation doesn't warn for image being smaller
https://bugs.launchpad.net/bugs/565659
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
What image format is the base image?
I just tested with qcow2 format and increased the size from 6g to 10g just fine
(of course the file system size remained the same)
kvm-img create -b Lucid_64_Base.qcow2 -f qcow2 test_img.qcow2 10G
If you don't specify a format I think raw is used:
kvm-img
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Low
--
qemu-img baseimage creation doesn't warn for image being smaller
https://bugs.launchpad.net/bugs/565659
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Low
--
qemu-img baseimage creation doesn't warn for image being smaller
https://bugs.launchpad.net/bugs/565659
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/44622926/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/44622927/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/44622928/Dependencies.txt
**
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/44622926/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/44622927/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/44622928/Dependencies.txt
**
13 matches
Mail list logo
