[Bug 1053893] [NEW] cloud-init should be able to switch off password auth in sshd

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).

[Bug 1053893] Re: cloud-init should be able to switch off password auth in sshd

** 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 i

[Bug 1054035] [NEW] Adding default user fails due to lack of 'netdev' group

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 () 2012-09-21 12:47:31,427

[Bug 1054035] Re: Adding default user fails due to lack of 'netdev' group

-- 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: https://bugs.l

[Bug 1054035] Re: Adding default user fails due to lack of 'netdev' group

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

Re: [Bug 1054035] Re: Adding default user fails due to lack of 'netdev' group

5 > > Title: > Adding default user fails due to lack of 'netdev' group > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1054035/+subscriptions -- Neil Wilson -- You received this bug notification because you ar

Re: [Bug 1054035] Re: Adding default user fails due to lack of 'netdev' group

allation packages so that a debootstrapped Ubuntu system has the expected /etc/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

[Bug 1073204] [NEW] ssh-authkey-fingerprints fails on boot

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 () failed Oct 30 14:34:45 srv-2dg76 [CLOUDINIT] util.py[DEBUG]: Running ssh-authkey-fingerprints () failed#012Traceback (most recent call

[Bug 1089342] [NEW] 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 should

[Bug 1089342] Re: Postfix uses temporary IPv6 address for outbound connections

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 bu

[Bug 1089342] Re: Postfix uses temporary IPv6 address for outbound connections

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

Re: [Bug 368962] Re: Can't reboot kvm virtual machines using virsh

kvm to be able to do. > > [1]: https://wiki.ubuntu.com/Bugs/Importance > > -- > Can't reboot kvm virtual machines using virsh > https://bugs.launchpad.net/bugs/368962 > You received this bug notification because you are a direct subscriber > of the bug. > -- Nei

Re: [Bug 368962] Re: Can't reboot kvm virtual machines using virsh

about bugs. At the moment *everybody* has to implement 'shutdown, poll for a bit, startup' (or would do if the acpi scripts worked). I've just written another one this week, whereas a default one that hung around for a bit and worked with a standard Ubuntu server would have been plenty

[Bug 580454] [NEW] qemu-ifup script stops libvirt 'ethernet' interface machines from starting.

Public bug reported: Binary package hint: qemu-kvm qemu-kvm assumes that a bridge exists (/etc/qemu-ifup doesn't check if the bridge exists before adding an interface to it.) and that the user will always want the interface added to it. This is not necessarily the case and causes properly define

[Bug 580454] Re: qemu-ifup script stops libvirt 'ethernet' interface machines from starting.

** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/48438401/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/48438404/CurrentDmesg.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/48438405/Lspci.txt ** Attachment adde

[Bug 580454] Re: libvirt 'ethernet' interface machines won't start.

/etc/qemu-ifup and /etc/qemu-ifdown don't check if the bridge exists before trying to add devices. Initially it looked like this may be the cause, but fixing them doesn't help. ** Summary changed: - qemu-ifup script stops libvirt 'ethernet' interface machines from starting. + libvirt 'ethernet' i

[Bug 580454] Re: libvirt 'ethernet' interface machines won't start.

Further analysis of this shows that the 'kvm' process executes and then dies. The 'qemu-ifup' script is not executed so the kvm process must die before then. Running the domain by hand (the output of 'virsh domxml-to-native qemu- argv ubuntu.xml') as root works as expected. (Once you've connected

[Bug 580454] Re: libvirt 'ethernet' interface machines won't start.

Checking the log file shows different output if the command is executed via libvirt. LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 256 -smp 1 -name ubuntu -uuid 48c31f45-33a6-1575-c677-55df6a349c01 -charde

[Bug 584862] [NEW] libvirt launches dnsmasq for non-dhcp networks.

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. net1 Whe

[Bug 584862] Re: libvirt launches dnsmasq for non-dhcp networks.

** 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 l

[Bug 584910] [NEW] libvirt can't add host definitions to DHCP without network restart

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 ProcVersionSig

[Bug 584910] Re: libvirt can't add host definitions to DHCP without network restart

** 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 584910] Re: libvirt can't add host definitions to DHCP without network restart

** 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 restar

[Bug 584945] [NEW] python-vm-builder man page out of date

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: L

[Bug 584945] Re: python-vm-builder man page out of date

** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/49019147/Dependencies.txt ** Attachment added: "RelatedPackageVersions.txt" http://launchpadlibrarian.net/49019148/RelatedPackageVersions.txt -- python-vm-builder man page out of date https://bugs.launchpad.net/bugs/584

[Bug 580454] Re: libvirt 'ethernet' or 'bridge' interface machines won't start.

There is the same problem with 'bridge' interfaces. >From a VM generated with 'vmbuilder' sudo vmbuilder kvm ubuntu -v -m 256 --swapsize 256 --domain vm.brightbox.net --addpkg=openssh-server --hostname=test1 --mac=02:24:19:01:00:01 --libvirt=qemu:///system --bridge=virbr0 and an internal bridge

Re: [Bug 584945] Re: python-vm-builder man page out of date

https://bugs.launchpad.net/bugs/584945 > You received this bug notification because you are a direct subscriber > of the bug. > -- Neil Wilson -- python-vm-builder man page out of date https://bugs.launchpad.net/bugs/584945 You received this bug notification because you are a m

[Bug 589090] [NEW] no ipv6 router advertisements when bridge starts

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 and

[Bug 589090] Re: no ipv6 router advertisements when bridge starts

** 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

[Bug 580454] Re: libvirt 'ethernet' or 'bridge' interface machines won't start.

Ok. The bridge stuff is working, but 'raw ethernet' isn't. Run: sudo vmbuilder kvm ubuntu -v -m 256 --swapsize 256 --domain vm.brightbox.net --addpkg=openssh-server --hostname=test1 --mac=02:24:19:01:00:01 --libvirt=qemu:///system --bridge=virbr1 virsh edit test1 and alter the interface specific

[Bug 576501] Re: vmbuilder doesn't recognize --ec2 flag

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 arou

[Bug 766242] Re: lp:ubuntu/cloud-init is not buildable by bzr-builder

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 a

[Bug 766242] Re: lp:ubuntu/cloud-init is not buildable by bzr-builder

"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 wor

[Bug 1481683] [NEW] juju-core version out of sync with tools stream - bootstrap fails

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

[Bug 1482226] [NEW] juju status with 'prefer-ipv6' shows address, not DNS name.

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 Package

[Bug 1482644] [NEW] Can't deploy charm directly after bootstrap

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 "manu

[Bug 1410288] [NEW] qemu-img conversion to qcow2 hangs with blank image less than 100kiB

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

[Bug 1410288] Re: qemu-img conversion to qcow2 hangs with blank image less than 100kiB

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

[Bug 1410288] Re: qemu-img conversion to qcow2 hangs with blank image less than 100kiB

** 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 less

Re: [Bug 1073204] Re: ssh-authkey-fingerprints fails on boot

gs.launchpad.net/ubuntu/+source/cloud-init/+bug/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

Re: [Bug 1068756] Re: IPv6 Privacy Extensions enabled on Ubuntu Server by default

- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/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/+

Re: [Bug 1068756] Re: IPv6 Privacy Extensions enabled on Ubuntu Server by default

gs.launchpad.net/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

[Bug 685258] [NEW] vmbuilder fails to unmount cdrom cleanly

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 x86_

[Bug 685258] Re: vmbuilder fails to unmount cdrom cleanly

-- 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 Mo

[Bug 685258] Re: vmbuilder fails to unmount cdrom cleanly

The cleanup on exception was commented out. If there isn't a reason for that then the attached patch runs cleanup on BaseException (to catch interrupts) and after post_install, which removes the iso mount. ** Patch added: "Cleanup after interrupt, exception and at end." https://bugs.launchpad

[Bug 685258] Re: vmbuilder fails to unmount cdrom cleanly

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

Re: [Bug 685258] Re: vmbuilder fails to unmount cdrom cleanly

on because you are a direct subscriber > 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-

[Bug 546745] Re: libvirt tries to read /etc/sasl/libvirt.conf not /etc/sasl2/libvirt.conf despite docs

** 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

[Bug 546745] Re: libvirt tries to read /etc/sasl/libvirt.conf not /etc/sasl2/libvirt.conf despite docs

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 bu

[Bug 546745] Re: libvirt tries to read /etc/sasl/libvirt.conf not /etc/sasl2/libvirt.conf despite docs

** 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. https://bugs.launchpad.net/bugs/546

[Bug 546745] Re: libvirt tries to read /etc/sasl/libvirt.conf not /etc/sasl2/libvirt.conf despite docs

** 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 y

[Bug 546745] Re: libvirt tries to read /etc/sasl/libvirt.conf not /etc/sasl2/libvirt.conf despite docs

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 no

[Bug 546745] Re: libvirt tries to read /etc/sasl/libvirt.conf not /etc/sasl2/libvirt.conf despite docs

/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 /etc/sasl/l

[Bug 697197] [NEW] Empty password allows access to VNC in libvirt

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 co

[Bug 697197] Re: Empty password allows access to VNC in libvirt

-- 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 Ubuntu-server-bugs@lists.ubuntu.com

[Bug 697197] Re: Empty password allows access to VNC in libvirt

** 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 Ub

Re: [Bug 368962] Re: Can't reboot kvm virtual machines using virsh

e awhile 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 mac

Re: [Bug 697197] Re: Empty password allows access to VNC in libvirt

ad.net> wrote: > ** Changed in: libvirt (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 pas

[Bug 697197] Re: Empty password allows access to VNC in libvirt

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 membe

[Bug 697197] Re: Empty password allows access to VNC in libvirt

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

[Bug 697197] Re: Empty password allows access to VNC in libvirt

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 B

[Bug 704435] [NEW] xinetd init script - reload terminates redirected services

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

[Bug 704435] Re: xinetd init script - reload terminates redirected services

-- 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 Ubuntu-server-bugs@lists

[Bug 704435] Re: xinetd init script - reload terminates redirected services

** 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. https://bugs.launchpad.n

[Bug 704435] Re: xinetd init script - reload terminates redirected services

** 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 - proto

[Bug 704435] Re: xinetd init script - reload terminates redirected services

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

[Bug 697197] Re: Empty password allows access to VNC in libvirt

** 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 -- U

[Bug 697197] Re: 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:

[Bug 697197] Re: Empty password allows access to VNC in libvirt

** 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 Serv

[Bug 697197] Re: Empty password allows access to VNC in libvirt

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 com

[Bug 697197] Re: Empty password allows access to VNC in libvirt

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 Ubuntu-se

[Bug 697197] Re: Empty password allows access to VNC in libvirt

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 Title

[Bug 697197] Re: Empty password allows access to VNC in libvirt

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 mailing

[Bug 368962] Re: Can't reboot kvm virtual machines using virsh

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

[Bug 862136] [NEW] Can't define network with IPv6 address in libvirt - fails to define address

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 3.0.0-12.19-ge

[Bug 862136] Re: Can't define network with IPv6 address in libvirt - fails to define address

-- 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

[Bug 862136] Re: Can't define network with IPv6 address in libvirt - fails to define address

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 NetworkManager[

[Bug 862136] Re: Can't define network with IPv6 address in libvirt - fails to define address

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 netwo

[Bug 862136] Re: Can't define network with IPv6 address in libvirt - fails to define address

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]: /sys/devices/virtual/net/br02: couldn't determine device driver; ignoring

[Bug 862136] Re: Can't define network with IPv6 address in libvirt - fails to define address

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 interfac

[Bug 862136] Re: Can't define network with IPv6 address in libvirt - fails to define address

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 Ub

[Bug 862136] Re: Can't define network with IPv6 address in libvirt - fails to define address

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 - fail

[Bug 862136] Re: Can't define network with IPv6 address in libvirt - fails to define address

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'" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/862136/+attachment/2

[Bug 862136] AcpiTables.txt

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. https://bugs.launchpad.net

[Bug 862136] AplayDevices.txt

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. https://bugs.launchpad

[Bug 862136] AlsaDevices.txt

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. https://bugs.launchpad.n

[Bug 862136] ArecordDevices.txt

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. https://bugs.launc

[Bug 862136] BootDmesg.txt

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. https://bugs.launchpad.net/b

[Bug 862136] Card0.Amixer.values.txt

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. https://

[Bug 862136] Card0.Codecs.codec.0.txt

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. https:

[Bug 862136] Card0.Codecs.codec.1.txt

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. https:

[Bug 862136] Card1.Codecs.codec.0.txt

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. https:

[Bug 862136] Lspci.txt

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/86213

[Bug 862136] PciMultimedia.txt

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. https://bugs.launchp

[Bug 862136] ProcCpuinfo.txt

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. https://bugs.launchpad.n

[Bug 862136] ProcModules.txt

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. https://bugs.launchpad.n

[Bug 862136] PulseSources.txt

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. https://bugs.launchpad

[Bug 862136] UdevLog.txt

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. https://bugs.launchpad.net/bugs/8

[Bug 862136] CurrentDmesg.txt

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. https://bugs.launchpad

[Bug 862136] IwConfig.txt

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. https://bugs.launchpad.net/bug

  1   2   >