This bug was fixed in the package vm-builder - 0.12.4-0ubuntu0.3
---
vm-builder (0.12.4-0ubuntu0.3) lucid-proposed; urgency=low
* debian/patches/0001-lp531599.patch: Backport fix for
LP: #531599 which removes dev maps created by parted.
-- Louis Bouchard
Changed tag to verification-done. tested in a Lucid environment with
initial reproducer and it no longer leaves a lingering dm map. Behavior
is as expected.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of
Hello Simon, or anyone else affected,
Accepted vm-builder into lucid-proposed. The package will build now and
be available at http://launchpad.net/ubuntu/+source/vm-
builder/0.12.4-0ubuntu0.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/lucid-proposed/vm-builder
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/531599
Title:
device mappings for partitions not removed after build using
Corrected the bug number in the changelog entry, retarrgeted the upload
at lucid-proposed, and uploaded.
It's now waiting for SRU team review.
** Changed in: vm-builder (Ubuntu Lucid)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Unsubscribing sponsors as I don't see a patch for lucid, please
resubscribe when a patch or merge proposal is ready
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/531599
Title:
@micah
I'm sorry, I thought I had done so. Here is the debdiff against the
ubuntu version. Let me know if this is sufficient.
** Patch added: vm-builder_0.12.4-0ubuntu0.3.debdiff
** Also affects: vm-builder (Ubuntu Lucid)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/531599
Title:
device mappings for
** Description changed:
+ SRU Request for Lucid
+
+ [Impact] This bug occurs systematically when the --raw option is used to
+ create a VM. This results in file system data corruption messages in the
+ VM created.
+
+ [Development/Stable Fix] Fixed in 0.12.4+bzr475-0ubuntu1 for precise as
** Also affects: vmbuilder
Importance: Undecided
Status: New
** No longer affects: vmbuilder
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/531599
Title:
device
@Simon
Could you please provide an example of the vmbuilder command that you
used to generate the problem, so I can test with it ?
Kind regards
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
@Simon
Nevermind the previous request, I was able to reproduce the bug myself.
As the issue fixed by this patch only happens when --raw is used, the
modification is not restrictive enough and try to remove nonexistent
maps. I'll work on refining the patch.
--
You received this bug notification
The new fix 0.12.4+bzr475-0ubuntu1 seems to have created another bug:
Repoduce the Bug : Use vmbuilder to create VM, execution would terminate right
at Unmounting target filesystem.
An error occurs when the system tries to unmount /dev/mapper/loop0pp1
It seems to be a typo, it should be
** Branch linked: lp:~vmbuilder-dev/vmbuilder/packaging
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/531599
Title:
device mappings for partitions not removed after build using
This bug was fixed in the package vm-builder - 0.12.4+bzr475-0ubuntu1
---
vm-builder (0.12.4+bzr475-0ubuntu1) precise; urgency=low
[ Louis Bouchard ]
* Remove dev maps created by parted. (LP: #531599)
[ Serge Hallyn ]
* pre-hook to create vcsversion.py is failing, work
I have been able to test a potential fix for this problem. The unmap()
function is responsible for tearing apart the device maps created by the
kpartx commands. Those are created by the map_partitions() function.
While tearing down the device maps created by the parted command, which
is invoked
** Branch linked: lp:~louis-bouchard/ubuntu/precise/vm-builder/lp531599
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/531599
Title:
device mappings for partitions not removed
After doing some test to identify what is creating this duplicate set of
dm maps, it seems to be the following 'parted mkpart' commands that
triggers the udev rule :
From /usr/share/pyshared/VMBuilder/disk.py :
def create(self, disk):
Adds partition to the disk image (does
I can confirm this bug too, using vmbuilder 0.12.4 on an up to date lucid.
Vmbuilder complete guest creation without an error. But launching the guest
with the mapping cause immediate fs corruption.
This has nothing to do with the lv size.
Simon have done all the investigation correctly but I
After some investigation it looks like vmbuilder is nicely registering a
callback hook to unmap the devices it sets up using kpartx. The problem
is udev rules adding device mappings using kpartx as soon as the raw
device gets partitioned.
AFAIK the relevant udev rule is
20 matches
Mail list logo
