Public bug reported:
If bootstrapping a machine on a trusty cloud image and then directly
installing the gui:
/usr/bin/juju bootstrap /usr/bin/juju deploy juju-gui --to 0
/usr/bin/juju expose juju-gui
The installation of the charm fails after the bootstrap.
Bootstrapping environment manual
Public bug reported:
If I have 'prefer-ipv6' set and bootstrap a manual environment, then
the dns-name and public address entries show the IPv6 address, not the
dns-name for that IPv6 address - even though it is available via a DNS
PTR record.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Public bug reported:
The tools stream for juju doesn't have tools for 'wily' that correspond
with the version of the packages in the main repository.
ubuntu@srv-2f16s:~$ juju --version
1.22.6-wily-amd64
From
https://streams.canonical.com/juju/tools/streams/v1/com.ubuntu.juju:released:tools.json
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1410288
Title:
qemu-img conversion to qcow2 hangs with blank image
Public bug reported:
If you try to convert a blank image to qcow2 that is less than 100kiB in
size then qemu-img hangs trying to seek to the end of the file.
$ truncate --size 102399 /tmp/temp
$ qemu-img convert -p -O qcow2 /tmp/temp /tmp/temp2.qcow2
I'm finding this on all versions of qemu-img
Workaround is to 'fallocate'. Problem seems to be linked to files with
sparse holes in them.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1410288
Title:
qemu-img conversion to qcow2
ubuntu@srv-puxvl:~$ uname -a
Linux srv-puxvl 3.2.0-70-virtual #105-Ubuntu SMP Wed Sep 24 20:06:46 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@srv-puxvl:~$ dpkg -s qemu-utils | grep Version
Version: 1.0+noroms-0ubuntu14.20
ubuntu@srv-puxvl:~$ qemu-img convert -O qcow2 -o ? a b
Supported
ubuntu@srv-3wzed:~$ uname -a
Linux srv-3wzed 3.2.0-69-virtual #103-Ubuntu SMP Tue Sep 2 05:28:41 UTC 2014
i686 i686 i386 GNU/Linux
ubuntu@srv-3wzed:~$ dpkg -s qemu-utils | grep Version
Version: 1.0+noroms-0ubuntu14.20
ubuntu@srv-3wzed:~$ qemu-img convert -O qcow2 -o ? a b
Supported options:
size
this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1388036/+subscriptions
--
Neil Wilson
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1388036
Title:
qemu-img
From RH Bug list:
It appears the cause was identified and fixed in the latest haproxy upstream
release, 1.5.7. From the release announcement on the haproxy mailing list:
- John Leach reported an interesting bug in the way SSL certificates were
loaded : if a certificate with an invalid
Public bug reported:
When you ask for options for a command on the precise version of qemu-
img
qemu-img convert -O qcow2 -o ? a b
The tool seg faults:
Supported options:
size Virtual disk size
backing_file File name of a base image
backing_fmt Image format of the base
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1383704
Title:
Can't switch off SSLv3 cipher groups in haproxy
To manage
The issue seems to be caused by a self-signed cert we're using. A cert
from a CA seems to work as expected.
** Attachment added: ssl_cert.pem.orig.fixed
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1383704/+attachment/4241193/+files/ssl_cert.pem.orig.fixed
--
You received this
/bugs/1068756
Title:
IPv6 Privacy Extensions enabled on Ubuntu Server by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1068756/+subscriptions
--
Neil Wilson
--
You received this bug notification because you are a member
/1068756
Title:
IPv6 Privacy Extensions enabled on Ubuntu Server by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1068756/+subscriptions
--
Neil Wilson
--
You received this bug notification because you are a member of Ubuntu
/1073204/+subscriptions
--
Neil Wilson
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1073204
Title:
ssh-authkey-fingerprints fails on boot
To manage notifications about
This is only really a problem when you use the default wildcard address
for your MTA binds.
And it looks like there already is an option in postfix that allows you
to fix the outbound source address.
smtp_bind_address6
So perhaps its a configuration/documentation issue.
--
You received this
http://www.postfix.org/postconf.5.html#smtp_bind_address6
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1089342
Title:
Postfix uses temporary IPv6 address for outbound connections
Public bug reported:
By default IPv6 privacy extensions is installed on Ubuntu server and
temporary addresses are preferred.
This means that outgoing connections from Postfix will use the temporary
IPv6 addresses, which will likely fail reverse DNS checks and cause mail
to bounce.
Postfix
Public bug reported:
I'm getting a failure in cloud-init on boot
Oct 30 14:34:45 srv-2dg76 [CLOUDINIT] util.py[WARNING]: Running
ssh-authkey-fingerprints (module
'cloudinit.config.cc_ssh_authkey_fingerprints' from
Is the netdev *group* used by Ubuntu server?
The way I've done it myself prior to Quantal is to delegate the problem
to the user-setup package.
add_default_user() {
echo Setting up '${CLOUD_DEFAULT_USERNAME}' default user
debconf-set-selections EOF
user-setup
/ubuntu/+source/cloud-init/+bug/1054035/+subscriptions
--
Neil Wilson
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1054035
Title:
Adding default user fails due to lack
/group layout?
--
Neil Wilson
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1054035
Title:
Adding default user fails due to lack of 'netdev' group
To manage notifications about
Public bug reported:
I've had a look but I can't see any facilities within cloud-init config
system to manipulate the sshd configuration settings.
ISTM that cloud-init should open up sshd to the minimum required by the
users configured by the cloud-init process (or if told to widen it
further).
** Description changed:
I've had a look but I can't see any facilities within cloud-init config
system to manipulate the sshd configuration settings.
ISTM that cloud-init should open up sshd to the minimum required by the
users configured by the cloud-init process (or if told to widen
Public bug reported:
I've created a build using the 'standard' and 'cloud-image' tasks on
Quantal, but without setting a default user.
Cloud-init fails with the following in the log.
2012-09-21 12:47:31,426 - helpers.py[DEBUG]: Running config-users-groups using
lock (FileLock using file
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1054035
Title:
Adding default user fails due to lack of 'netdev' group
To manage notifications about this bug go to:
Public bug reported:
When defining a network with an IPv6 address, libvirt fails to allocate
the address properly and the launch of the supporting dnsmasq processes
fails.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: libvirt-bin 0.9.2-4ubuntu14
ProcVersionSignature: Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/862136
Title:
Can't define network with IPv6 address in libvirt - fails to define
address
To manage notifications about this bug go
Syslog trace with just the IPv4 address:
Sep 29 09:38:13 acer-aspire-5536 kernel: [ 4463.577520] device br02-nic
entered promiscuous mode
Sep 29 09:38:13 acer-aspire-5536 kernel: [ 4463.582585] ADDRCONF(NETDEV_UP):
br02: link is not ready
Sep 29 09:38:13 acer-aspire-5536
Install libvirt-bin and qemu-kvm on standard workstation install.
Remove the default network with 'virsh net-destroy default'
Define the new network with 'virsh net-define fred.xml'
Try to start the network with 'virsh net-start br02'
This results in an error:
error: Failed to start
Syslog trace during 'net-start' while IPv6 entry is in place:
Sep 29 09:36:41 acer-aspire-5536 kernel: [ 4372.079686] device br02-nic
entered promiscuous mode
Sep 29 09:36:41 acer-aspire-5536 NetworkManager[889]: warn
/sys/devices/virtual/net/br02: couldn't determine device driver;
From:
https://bbs.archlinux.org/viewtopic.php?id=123855
In commit 1faa4356a3bd89ea11fb92752d897cff3a20ec0e to the Linux kernel
(which was before 2.6.39 got released so this is the first affected
version) the behavior of bridges was changed so that they set the
carrier state to off if no
The dummy interface on the bridge is marked down in libvirt to prevent
it showing up in the ifconfig listing.
But that now also means it won't activate the bridge interface.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in
Possible patch here:
http://patchwork.ozlabs.org/patch/113174/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/862136
Title:
Can't define network with IPv6 address in libvirt -
You might want to try setting the dummy interface up in libvirt. That
may workaround it for now at the expense of polluting the ifconfig
listings.
** Patch added: Start dummy bridge interface 'up' rather than 'down'
apport information
** Attachment added: AcpiTables.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480664/+files/AcpiTables.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: AplayDevices.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480666/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480665/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: ArecordDevices.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480667/+files/ArecordDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480668/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: Card0.Amixer.values.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480669/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: Card0.Codecs.codec.0.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480670/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: Card0.Codecs.codec.1.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480671/+files/Card0.Codecs.codec.1.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: Card1.Codecs.codec.0.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480672/+files/Card1.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480675/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/862136
apport information
** Attachment added: PciMultimedia.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480676/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480677/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480679/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: PulseSources.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480681/+files/PulseSources.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480684/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480673/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480674/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480678/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480683/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480685/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: RfKill.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480682/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
apport information
** Attachment added: PulseSinks.txt
https://bugs.launchpad.net/bugs/862136/+attachment/2480680/+files/PulseSinks.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
0.9.3 libvirt has native qemu/kvm reboot support baked in now.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/368962
Title:
Can't reboot kvm virtual machines using virsh
To manage
This is just about rebuilding the current Ubuntu package,
Exactly.
Nobody is expecting an auto merge here.
This is the standard distribution package as uploaded automatically to
Bzr being built on that distribution by the Launchpad builder system.
And currently for this package it doesn't
That's hardly user friendly.
Surely if the builder is to be of any use whatsoever it should build the
Ubuntu source branch with a simple command.
Having to manipulate a source package upload to get it to build is
totally counter-intuitive.
--
You received this bug notification because you are
The patch needs to go into Lucid as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/697197
Title:
Empty password allows access to VNC in libvirt
--
Ubuntu-server-bugs
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/697197
Title:
Empty password allows access to VNC in libvirt
--
The solution to this problem is to reverse the commit
52c18be9e99dabe295321153fda7fce9f76647ac in the main Qemu archive.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/697197
Title:
** Patch added: qemu-kvm_0.12.5+noroms-0ubuntu7.2.debdiff
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/697197/+attachment/1812796/+files/qemu-kvm_0.12.5%2Bnoroms-0ubuntu7.2.debdiff
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Installed patched build onto Maverick server. vnc_listen set to 0.0.0.0
in /etc/libvirt/qemu.conf
Set vnc_password=' with vnc_tls=1 in /etc/libvirt/qemu.conf and
confirmed that the lanched server now rejects authentication for any
password, whereas it turned off authentication and encryption
Please sponsor for upload
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/697197
Title:
Empty password allows access to VNC in libvirt
--
Ubuntu-server-bugs mailing list
This fault probably affects all the current versions of qemu-kvm. It's
present in 0.11 and the current qemu master branch.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/697197
This is fixed in natty by the upstart job conversion. (version
1:2.3.14-7ubuntu4)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xinetd in ubuntu.
https://bugs.launchpad.net/bugs/704435
Title:
xinetd init script - reload terminates
Public bug reported:
Binary package hint: xinetd
If you are using the 'redirect' service of xinetd, the redirection forks
a separate copy of xinetd for each service.
e.g
service vnc-redirect
{
type= UNLISTED
socket_type = stream
protocol= tcp
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xinetd in ubuntu.
https://bugs.launchpad.net/bugs/704435
Title:
xinetd init script - reload terminates redirected services
--
Ubuntu-server-bugs mailing list
** Attachment added: Fixed xinetd.init
https://bugs.launchpad.net/ubuntu/+source/xinetd/+bug/704435/+attachment/1798056/+files/xinetd.init
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xinetd in ubuntu.
** Description changed:
Binary package hint: xinetd
If you are using the 'redirect' service of xinetd, the redirection forks
a separate copy of xinetd for each service.
e.g
service vnc-redirect
{
- type= UNLISTED
- socket_type = stream
-
CVE issued putting the onus squarely on qemu's shoulders.
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2011-0011
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Invalid
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
** Bug watch added: Red Hat
Libvirt is in the clear on this one. It is a mild security issue
introduced into QEMU.
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Invalid
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
When I say in the clear, the libvirt guys think they're in the clear.
Checked the qemu source and there is no fix for this problem. Could be a
change of behaviour.
** Changed in: libvirt (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member
(Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a direct subscriber
of the bug.
https://bugs.launchpad.net/bugs/697197
Title:
Empty password allows access to VNC in libvirt
--
Neil Wilson
--
You received this bug
to figure that out so I'll just mention that here to
save someone time.
--
You received this bug notification because you are a direct subscriber
of the bug.
https://bugs.launchpad.net/bugs/368962
Title:
Can't reboot kvm virtual machines using virsh
--
Neil Wilson
--
You received
Public bug reported:
The help in the /etc/libvirt/qemu.conf states
To allow access without passwords, leave this commented out. An empty
string will still enable passwords, but be rejected by QEMU
effectively preventing any use of VNC.
yet setting:
vnc_password=
allows access to the vnc
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/697197
Title:
Empty password allows access to VNC in libvirt
--
Ubuntu-server-bugs mailing list
** Bug watch added: Red Hat Bugzilla #667097
https://bugzilla.redhat.com/show_bug.cgi?id=667097
** Also affects: libvirt via
https://bugzilla.redhat.com/show_bug.cgi?id=667097
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
Note that apparmor will need adjusting to allow qemu to access /etc/sasl
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/546745
Title:
libvirt tries to read /etc/sasl/libvirt.conf
/etc/apparmor.d/abstractions/libvirt-qemu needs
/etc/sasl/qemu.conf r,
adding to it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/546745
Title:
libvirt tries to read
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/546745
Title:
libvirt tries to read /etc/sasl/libvirt.conf not
The cyrus-sasl package in Debian/Ubuntu uses '/etc/sasl' as the standard
directory in which to find the application configurations.
The fault here with the libvirt package is that it is putting the
example sasl configuration in /etc/sasl2 which is wrong for
Debian/Ubuntu.
--
You received this
** Patch added: sasl.patch
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/546745/+attachment/1775464/+files/sasl.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
** Bug watch added: Debian Bug tracker #552180
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552180
** Also affects: libvirt (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552180
Importance: Unknown
Status: Unknown
--
You received this bug notification because
of the bug.
https://bugs.launchpad.net/bugs/685258
Title:
vmbuilder fails to unmount cdrom cleanly
--
Neil Wilson
--
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/685258
Sure. I've attached the build script I use.
** Attachment added: build-template.sh
https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/685258/+attachment/1760517/+files/build-template.sh
** Changed in: vm-builder (Ubuntu)
Status: Incomplete = Confirmed
--
You received this
Public bug reported:
When using a cd image for building machines, vmbuilder always leaves the
loop device setup.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: python-vm-builder 0.12.4-0ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic
--
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/685258
Title:
vmbuilder fails to unmount cdrom cleanly
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Series 12 vmbuilder just doesn't support seem to support ec2 building
yet. If you need that facility then you need to use the 0.11 branch.
I'm sure they are trying to tidy it up as it all seems a bit messy at
the moment. Really it needs refactoring so that the EC2 stuff is a
decorator pattern
Public bug reported:
When a bridge starts up, you generally have to 'kick' the radvd daemon
with a HUP signal to get it to recognise the new interface and start
issuing router advertisements (assuming it is configured in
'ignoreifmissing' mode).
libvirt should check to see if radvd is running
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/49599404/Dependencies.txt
--
no ipv6 router advertisements when bridge starts
https://bugs.launchpad.net/bugs/589090
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
When defining a network in libvirt that does not have a dhcp section,
dnsmasq is still started for the that network. This prevents you from
starting your own version, or binding other software to that interface
that does the same thing.
For example.
network
namenet1/name
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/49007670/Dependencies.txt
--
libvirt launches dnsmasq for non-dhcp networks.
https://bugs.launchpad.net/bugs/584862
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
libvirt networks need to be shutdown and restarted to add ranges and/or
static mappings to the dhcp definition sections. This breaks service for
those VM guests currently running.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: libvirt-bin 0.7.5-5ubuntu27
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/49012026/Dependencies.txt
--
libvirt can't add host definitions to DHCP without network restart
https://bugs.launchpad.net/bugs/584910
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Bug watch added: Red Hat Bugzilla #595323
https://bugzilla.redhat.com/show_bug.cgi?id=595323
** Also affects: libvirt via
https://bugzilla.redhat.com/show_bug.cgi?id=595323
Importance: Unknown
Status: Unknown
--
libvirt can't add host definitions to DHCP without network
Public bug reported:
The options on the vmbuilder manual page are out of date wrt. the actual
application. Needs bringing up to date.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: python-vm-builder 0.12.3-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.33-server 2.6.32.11+drm33.2
Uname:
1 - 100 of 134 matches
Mail list logo
