I'm seeing this in Vivid -> Wily too, but in a Xen VM, not an LXC
container. None of the above suggestions worked, it logs the same errors
as Serge.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
OK, I have feedback from my ISP. Their kernel does not include dmi, on
the basis that it's been deprecated since 2005!
They've worked around this problem by installing the natty libvirt
package which does not suffer this problem.
I guess a backport request would be appropriate.
Sorry to trouble
Apport says this:
Package libvirt not installed and no hook available, ignoring
*** Updating problem report
No additional information collected.
Press any key to continue...
No pending crash reports. Try --help for more information.
What it's saying is technically correct because there is no
That search finds nothing.
The kernel is supplied and configured by my ISP - the stock kernel is
not stable - I've asked them to contribute to this report.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
Public bug reported:
I'm attempting to install kvm-qemu with libvirt on Ubuntu Lucid amd64 on
a quad-core i7. It's a brand-new clean install, fully updated and
rebooted. I've been following the Ubuntu KVM docs (from
https://help.ubuntu.com/community/KVM/Installation), but I'm getting
this
That doesn't really work since it collects info only on libvert itself,
which is a virtual package and returns nothing. I don't know quite which
bit of libvert this should be attached to - maybe libvert-bin?
--
You received this bug notification because you are a member of Ubuntu
Server Team,
This still happens on Lucid, but there's a less complicated fix for
this. The status moule is normally enabled with `a2enmod status`. All
that seems to be required to fix munin after that is to add
'ExtendedStatus On' to /etc/apache2/mods-enabled/status.conf so it looks
like this:
IfModule
FYI, I supplied a VM I built to Soren off-site. He found it ran OK. I
asked for a VM built using the same config on a known-good server that I
could try. So far the story is:
VMs I build won't run poperly on this server
VMs built elsewhere (using different config) do run on this server
VMs I
Here's the debug log. I see a lot of debug-level notices about missing
methods, but it doesn't seem to be leading to any actual errors, like
this:
2010-05-06 01:03:47,288 DEBUG : Calling install_bootloader method in
VMBuilder.plugins.libvirt plugin.
2010-05-06 01:03:47,289 DEBUG : No such
** Attachment added: Screen shot 2010-05-05 at 16.38.55.png
http://launchpadlibrarian.net/47877692/Screen%20shot%202010-05-05%20at%2016.38.55.png
--
VMs built with vm-builder won't run
https://bugs.launchpad.net/bugs/575839
You received this bug notification because you are a member of
Public bug reported:
I'm running vmbuilder 0.12.3-0ubuntu1 on Lucid server. vmbuilder
apparently runs and assembles a machine image without error, but the
resulting VM just doesn't run properly, going extremely slowly (about 50
mins to reach a login prompt, though login isn't possible as it
** Attachment added: Screen shot 2010-05-05 at 16.36.51.png
http://launchpadlibrarian.net/47877680/Screen%20shot%202010-05-05%20at%2016.36.51.png
--
VMs built with vm-builder won't run
https://bugs.launchpad.net/bugs/575839
You received this bug notification because you are a member of
I'd guess so since kvm insists on running as root! I've had the same problem
with the vm folder and image owned by me and root, so I guess it's not that.
Do you have a known-good config I can use to generate a VM image to test with,
possibly compare it with the image created on a machine that
If I run run.sh without sudo it says this:
open /dev/kvm: Permission denied
Could not initialize KVM, will disable KVM support
That said, it does open a qemu window, but it shows the same errors as
previously reported.
Re ownership, I've tried running with the folder owned by me, and
changed it
I'd hope not, since it more or less renders Lucid's entire headline
cloud offering useless...
--
--firstboot option broken in 0.12.2-0ubuntu3
https://bugs.launchpad.net/bugs/536942
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
There are two files in there. One called ubuntu.xml that refers to an image
file created in a folder called ubuntu-kvm (i.e. a default, as you suspected),
the other called vm1.xml, which is what I specified as my hostname.
I'm also curious that that file is in the libvirt folder instead of
I've now tried this without the -o option (having spotted the
self.vm.overwrite is the root of the problem), but that didn't make any
difference. Any chance of getting some attention to this as it's a
complete showstopper for me. It means my entire UEC / JeOS
virtualization plans are on hold.
Yay! That did it! I added a --hostname and it just worked, so thanks very much.
I don't think it's to do with whether a VM already exists as I have none in my
folder and have been wiping /tmp files between each build (because it doesn't
clean up after dying). In my case it should have nothing to
Public bug reported:
This is just a small feature request. While vmbuilder is running, it
constructs the new VM in /tmp under a randomly generated folder name
like 'tmpkJv90L'. When it's finished, it moves the completed image file
to the location given by the --dest option, however, it retains
I'm wary of making changes there as that page is for the older shell
script version of vmbuilder and I don't know if the same things apply -
I don't want to break things for Intrepid users just because Lucid is
different.
I also noticed that hostname is missing from the man page too.
I'm also
Indeed - this went away when I removed the proxy option, thanks for the
pointer. The proxy log shows timeouts from the repo.
Now I'm stuck with bug 562189 again.
--
vm-builder fails to resolve package dependency in vanilla system
https://bugs.launchpad.net/bugs/562575
You received this bug
Still there with libvirt 0.7.5-5ubuntu25
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in ubuntu.
--
Ubuntu-server-bugs
ok, after a full-upgrade and a reboot before building a vm, I'm still
getting similar errors, however, it seems to be intermittent - I did one
build that was chock-full of dependency failures (in debootstrap.log),
then did another one which didn't but had other problems, though missing
packages
Unfortunately it was just hiding, and it's back again with libvirt
0.7.5-5ubuntu23. Same config, same error.
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Server Team, which
Still there with libvirt 0.7.5-5ubuntu24.
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in ubuntu.
--
Ubuntu-server-bugs
Public bug reported:
Running vmbuilder with this command:
vmbuilder kvm ubuntu \
--suite lucid \
--flavour virtual \
--arch amd64 \
-o \
--libvirt qemu:///system \
--part vmbuilder.partition \
--user user \
--name user \
--pass default \
--ip 192.168.176.100 \
--mirror
I noticed that libvirt got updated to 0.7.5-5ubuntu22 today, and it's
possible that this bug has been fixed by it, however, I'm not sure as
I've got another bug instead that may just be obscuring it...
--
AttributeError: 'Libvirt' object has no attribute 'vm'
Public bug reported:
Using this vmbuilder command (note no additional packages requested,
just creating a completely vanilla system):
vmbuilder kvm ubuntu \
--suite lucid \
--flavour virtual \
--arch amd64 \
-o \
--libvirt qemu:///system \
--part vmbuilder.partition \
--user user \
--name user \
*** This bug is a duplicate of bug 536942 ***
https://bugs.launchpad.net/bugs/536942
** This bug has been marked a duplicate of bug 536942
--firstboot option broken in 0.12.2-0ubuntu3
--
vmbuilder: error: no such option: --firstboot
https://bugs.launchpad.net/bugs/550687
You received
29 matches
Mail list logo
