I am attaching a build script that uses a partitions file to demonstrate
the issue. When you run this script, the traceback that I listed doesn't
occur (not sure why). However, the built machine does still complain
about /dev/sda2, and you can verify that it does not have swap.
** Attachment
I moved the ticket status back to New. I've actually been wondering,
is it appropriate for me to alter the ticket state back to new after I
provide the requested information, or would it have been better if I
left it at Incomplete?
--
You received this bug notification because you are a member
This is the partitions file that I used.
** Attachment added: partitions
https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/726790/+attachment/1879354/+files/partitions
** Changed in: vm-builder (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because
Public bug reported:
I am using version 0.12.4+bzr462-0ubuntu1 in Ubuntu Natty. I've noticed
that when I build a lucid virtual machine, it complains during boot.
During build, I see this in the build log:
2011-02-28 15:36:01,700 INFO: Adding type 3 partition to disk image:
/tmp/tmpnFjJJ2
Public bug reported:
Binary package hint: qemu-kvm
If I try to attach a disk image using qemu-kvm to a network block
device, it will not work if I use the --nocache flag. Here is an
example:
$ qemu-nbd -c /dev/nbd7 --nocache whowho.qcow2
$ ls /dev/nbd7*
/dev/nbd7
If you look in dmesg, there
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/47586691/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/47586692/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/47586693/Dependencies.txt
**
I am also seeing the same connection refused error as skogs. Should we
open a separate ticket about it?
--
[Lucid] Error starting domain: could not remove profile
https://bugs.launchpad.net/bugs/517714
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
Binary package hint: qemu-kvm
I am unable to use qemu-nbd as an nbd-server in Lucid. In Karmic, the
following command works, but not in Lucid:
$ qemu-nbd -n -b localhost -p 2000 -P 1 base.qcow2
qemu-nbd: error while reading
Where base.qcow2 is just a regular qcow image.
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/41964977/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/41964978/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41964979/Dependencies.txt
**
It does seem to work without the -P 1 option. Unfortunately, the rest of
the system I've built around this doesn't work if I start the server
that way, but perhaps I can work around. So perhaps the partition option
is what is broken for Lucid?
--
qemu-kvm-0.12.3+noroms-0ubuntu2: qemu-nbd: error
*** This bug is a duplicate of bug 536940 ***
https://bugs.launchpad.net/bugs/536940
If I may, I'd like to contend that this is not a duplicate of bug
#536940. That ticket is about having a --tmpfs flag that will allow us
to indicate that we wish the VM to be built in a tmpfs. That ticket is
Hey Soren, thanks for your consideration!
--
-t option isn't available in python-vm-builder 0.12.2-0ubuntu3
https://bugs.launchpad.net/bugs/539231
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in ubuntu.
--
Also, I just spoke with the powers that pay my salary, and I have
received a green light to write a patch for this ticket. I'm gonna get
started on that now. I've never contributed to Ubuntu before, but I
assume that the standard procedure it to attach a patch to this ticket?
--
-t option isn't
** Branch linked: lp:~vmbuilder/+junk/bug539231
--
-t option isn't available in python-vm-builder 0.12.2-0ubuntu3
https://bugs.launchpad.net/bugs/539231
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in ubuntu.
--
Public bug reported:
If you interrupt the operation of python-vm-builder with the
KeyboardInterrupt, it won't clean up after itself. The version of
vmbuilder that comes with Karmic I believe might do this (haven't
checked, but it does seem to go through a cleanup step). This would be
friendly
I made a commit to the branch for this ticket. I've definitely gotten it
to use the -t flag in some places, but there are still files being
created in /tmp. I haven't yet identified the code that is placing files
in there, but for now I can't spend any more time on this. Hopefully my
work is a
Public bug reported:
The VM will build correctly, but once I start using my new VM (built for
Karmic by Lucid) I get a lot of warnings about locale not being set:
$ svn stat
svn: warning: cannot set LC_CTYPE locale
svn: warning: environment variable LANG is en_US.utf8
svn: warning: please check
Is this something that is likely to be fixed before Lucid goes stable? I
ask mostly because if not, I'd like to change the way a series of my
scripts work, and it'd be nice to know that ahead of time. Thanks!
--
--firstboot option broken in 0.12.2-0ubuntu3
https://bugs.launchpad.net/bugs/536942
Public bug reported:
The version of python-vm-builder that came with Karmic had a -t flag
that you could use to specify where the VM should be built. This was
handy, as it allowed me to build the VM on a tmpfs that I mounted
manually (since the --tmpfs flag didn't work). This flag isn't accepted
Hey John! I haven't made any workaround yet, but I was considering
something that sounds more complicated than I like. You could make an
init script that does the first boot work, removes itself from the
default run level, and then removes itself. There isn't a builtin first
boot functionality to
Public bug reported:
I've been using vm-builder for a while. It's super cool, but it looks to
me like the --tmpfs option doesn't actually do anything. When I grep for
tmpfs in /usr/lib/python2.6/dist-packages/VMBuilder, I only see one
file, and all it is doing is adding the --tmpfs option. I
21 matches
Mail list logo
