Public bug reported:
Machines built with vmbuilder appear not to boot when started with
# virsh start VMName
at least, virt-viewer does not see them.
A sample command line is here:
sudo vmbuilder kvm ubuntu --suite lucid --flavour virtual --arch amd64
--libvirt qemu:///system --user matt --pass xxxx --components
main,universe,restricted,multiverse --addpkg wordpress --addpkg emacs-snapshot
--addpkg openssh-server --domain suntour --dest suntour --name="Matt Price"
--hostname suntour -o
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: python-vm-builder 0.12.4-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.28-server 2.6.35.3
Uname: Linux 2.6.35-19-server x86_64
Architecture: amd64
Date: Thu Sep 9 17:06:00 2010
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64
(20100816.2)
PackageArchitecture: all
ProcEnviron:
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: vm-builder
** Affects: vm-builder (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug maverick
--
new virtual machines do not boot
https://bugs.launchpad.net/bugs/634488
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
