[Bug 1389595] [NEW] Error installing nagios3-doc: All `Format' sections are invalid.
Public bug reported: Upon 'apt-get install nagios3-doc' in Ubuntu 14.10, I get this error: Preparing to unpack .../nagios3-doc_3.5.1-1ubuntu2_all.deb ... Unpacking nagios3-doc (3.5.1-1ubuntu2) ... Processing triggers for doc-base (0.10.6) ... Processing 1 added doc-base file... Error in `/usr/share/doc-base/nagios3', line 9: all `Format' sections are invalid. Note: `install-docs --verbose --check file_name' may give more details about the above error. The output of 'install-docs --verbose --check /usr/share/doc-base/nagios3': Warning in `/usr/share/doc-base/nagios3', line 9: file `/usr/share/nagios3/htdocs/docs/index.html' does not exist. Error in `/usr/share/doc-base/nagios3', line 9: all `Format' sections are invalid. /usr/share/doc-base/nagios3: Fatal error found, the file won't be registered. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nagios3-doc 3.5.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 5 12:27:51 2014 Dependencies: InstallationDate: Installed on 2013-09-28 (402 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: nagios3 UpgradeStatus: Upgraded to utopic on 2014-10-30 (5 days ago) ** Affects: nagios3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios3 in Ubuntu. https://bugs.launchpad.net/bugs/1389595 Title: Error installing nagios3-doc: All `Format' sections are invalid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/1389595/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389596] [NEW] upgrade removed ruby
Public bug reported: this morning our machines performed security updates. As a result of this we lost /usr/bin/ruby (it was just non-existant) This seems to be when ruby package is upgraded _before_ libruby1.9.1. Reinstalling the ruby package fixed this. dpkg.log follows (you can see my manual reinstall of ruby at 09:35): 2014-11-05 08:05:30 startup archives unpack 2014-11-05 08:05:31 upgrade libruby1.9.1:amd64 1.9.3.484-2ubuntu1 1.9.3.484-2ubuntu1.1 2014-11-05 08:05:31 status half-configured libruby1.9.1:amd64 1.9.3.484-2ubuntu1 2014-11-05 08:05:31 status unpacked libruby1.9.1:amd64 1.9.3.484-2ubuntu1 2014-11-05 08:05:31 status half-installed libruby1.9.1:amd64 1.9.3.484-2ubuntu1 2014-11-05 08:05:32 status half-installed libruby1.9.1:amd64 1.9.3.484-2ubuntu1 2014-11-05 08:05:32 status unpacked libruby1.9.1:amd64 1.9.3.484-2ubuntu1.1 2014-11-05 08:05:32 status unpacked libruby1.9.1:amd64 1.9.3.484-2ubuntu1.1 2014-11-05 08:05:32 upgrade ruby1.9.1:amd64 1.9.3.484-2ubuntu1 1.9.3.484-2ubuntu1.1 2014-11-05 08:05:32 status half-configured ruby1.9.1:amd64 1.9.3.484-2ubuntu1 2014-11-05 08:05:32 status unpacked ruby1.9.1:amd64 1.9.3.484-2ubuntu1 2014-11-05 08:05:32 status half-installed ruby1.9.1:amd64 1.9.3.484-2ubuntu1 2014-11-05 08:05:32 status triggers-pending man-db:amd64 2.6.7.1-1 2014-11-05 08:05:32 status half-installed ruby1.9.1:amd64 1.9.3.484-2ubuntu1 2014-11-05 08:05:32 status unpacked ruby1.9.1:amd64 1.9.3.484-2ubuntu1.1 2014-11-05 08:05:32 status unpacked ruby1.9.1:amd64 1.9.3.484-2ubuntu1.1 2014-11-05 08:05:32 trigproc man-db:amd64 2.6.7.1-1 2.6.7.1-1 2014-11-05 08:05:32 status half-configured man-db:amd64 2.6.7.1-1 2014-11-05 08:05:33 status installed man-db:amd64 2.6.7.1-1 2014-11-05 08:05:33 startup packages configure 2014-11-05 08:05:33 configure libruby1.9.1:amd64 1.9.3.484-2ubuntu1.1 none 2014-11-05 08:05:33 status unpacked libruby1.9.1:amd64 1.9.3.484-2ubuntu1.1 2014-11-05 08:05:33 status unpacked libruby1.9.1:amd64 1.9.3.484-2ubuntu1.1 2014-11-05 08:05:33 status half-configured libruby1.9.1:amd64 1.9.3.484-2ubuntu1.1 2014-11-05 08:05:34 status installed libruby1.9.1:amd64 1.9.3.484-2ubuntu1.1 2014-11-05 08:05:34 status triggers-pending libc-bin:amd64 2.19-0ubuntu6.3 2014-11-05 08:05:34 configure ruby1.9.1:amd64 1.9.3.484-2ubuntu1.1 none 2014-11-05 08:05:34 status unpacked ruby1.9.1:amd64 1.9.3.484-2ubuntu1.1 2014-11-05 08:05:34 status half-configured ruby1.9.1:amd64 1.9.3.484-2ubuntu1.1 2014-11-05 08:05:34 status installed ruby1.9.1:amd64 1.9.3.484-2ubuntu1.1 2014-11-05 08:05:34 trigproc libc-bin:amd64 2.19-0ubuntu6.3 none 2014-11-05 08:05:34 status half-configured libc-bin:amd64 2.19-0ubuntu6.3 2014-11-05 08:05:34 status installed libc-bin:amd64 2.19-0ubuntu6.3 2014-11-05 09:35:27 startup packages purge 2014-11-05 09:35:27 status installed ruby:all 1:1.9.3.4 2014-11-05 09:35:44 startup archives unpack 2014-11-05 09:35:46 upgrade ruby:all 1:1.9.3.4 1:1.9.3.4 2014-11-05 09:35:46 status half-configured ruby:all 1:1.9.3.4 2014-11-05 09:35:46 status unpacked ruby:all 1:1.9.3.4 2014-11-05 09:35:46 status half-installed ruby:all 1:1.9.3.4 2014-11-05 09:35:46 status triggers-pending man-db:amd64 2.6.7.1-1 2014-11-05 09:35:46 status half-installed ruby:all 1:1.9.3.4 2014-11-05 09:35:46 status unpacked ruby:all 1:1.9.3.4 2014-11-05 09:35:46 status unpacked ruby:all 1:1.9.3.4 2014-11-05 09:35:46 trigproc man-db:amd64 2.6.7.1-1 2.6.7.1-1 2014-11-05 09:35:46 status half-configured man-db:amd64 2.6.7.1-1 2014-11-05 09:35:47 status installed man-db:amd64 2.6.7.1-1 2014-11-05 09:35:47 startup packages configure 2014-11-05 09:35:47 configure ruby:all 1:1.9.3.4 none 2014-11-05 09:35:47 status unpacked ruby:all 1:1.9.3.4 2014-11-05 09:35:47 status half-configured ruby:all 1:1.9.3.4 2014-11-05 09:35:47 status installed ruby:all 1:1.9.3.4 ** Affects: ruby1.9.1 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ruby1.9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1389596 Title: upgrade removed ruby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby1.9.1/+bug/1389596/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389595] Re: Error installing nagios3-doc: All `Format' sections are invalid.
** Description changed: Upon 'apt-get install nagios3-doc' in Ubuntu 14.10, I get this error: Preparing to unpack .../nagios3-doc_3.5.1-1ubuntu2_all.deb ... Unpacking nagios3-doc (3.5.1-1ubuntu2) ... Processing triggers for doc-base (0.10.6) ... Processing 1 added doc-base file... Error in `/usr/share/doc-base/nagios3', line 9: all `Format' sections are invalid. Note: `install-docs --verbose --check file_name' may give more details about the above error. The output of 'install-docs --verbose --check /usr/share/doc-base/nagios3': Warning in `/usr/share/doc-base/nagios3', line 9: file `/usr/share/nagios3/htdocs/docs/index.html' does not exist. Error in `/usr/share/doc-base/nagios3', line 9: all `Format' sections are invalid. /usr/share/doc-base/nagios3: Fatal error found, the file won't be registered. + Looking in /usr/share/doc/nagios3-doc, there is a softlink html pointing to + /usr/share/nagios3/htdocs/docs/. That directory contains only a directory + images, which is empty. + + ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nagios3-doc 3.5.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 5 12:27:51 2014 Dependencies: - + InstallationDate: Installed on 2013-09-28 (402 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: nagios3 UpgradeStatus: Upgraded to utopic on 2014-10-30 (5 days ago) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios3 in Ubuntu. https://bugs.launchpad.net/bugs/1389595 Title: Error installing nagios3-doc: All `Format' sections are invalid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/1389595/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389612] [NEW] cannot install php5-mapscript package, Depends: phpapi-20090626
Public bug reported: Hello, I have problem to install php5-mapscript on my ubuntu 12.04 64bit laptop. my php version is PHP 5.4.34-1+deb.sury.org~precise+1 (cli) (built: Oct 17 2014 15:28:55) . I use ppa:ondrej/php5 Here is the message on the terminal : Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: php5-mapscript : Depends: phpapi-20090626 ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Tags: mapscript php5 ** Description changed: Hello, - I have problem to install php5-package on my ubuntu 12.04 64bit laptop. - my php version is PHP 5.4.34-1+deb.sury.org~precise+1 (cli) (built: Oct - 17 2014 15:28:55) . I use ppa:ondrej/php5 + I have problem to install php5-mapscript on my ubuntu 12.04 64bit + laptop. my php version is PHP 5.4.34-1+deb.sury.org~precise+1 (cli) + (built: Oct 17 2014 15:28:55) . I use ppa:ondrej/php5 Here is the message on the terminal : Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: - php5-mapscript : Depends: phpapi-20090626 + php5-mapscript : Depends: phpapi-20090626 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1389612 Title: cannot install php5-mapscript package, Depends: phpapi-20090626 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1389612/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389614] [NEW] libvirt lts upgrade misses librbd dependency
Public bug reported: Following the automated upgrade path from Precise to Trusty, libvirtd failed to load libvirt_driver_storage.so (and consequently libvirt_driver_qemu.so). In our case, this was fixed by installing librbd-dev (presumably due to librbd1 dependency). Running /etc/init.d/libvirt-bin restart produced the following in libvirtd.log LIBVIRTD.LOG 2014-11-05 09:47:29.359+: 5755: info : libvirt version: 1.2.2 2014-11-05 09:47:29.359+: 5755: error : virDriverLoadModule:79 : failed to load module /usr/lib/libvirt/connection-driver/libvirt_driver_storage.so /usr/lib/libvirt/connection-driver/libvirt_driver_storage.so: undefined symbol: rbd_create3 2014-11-05 09:47:29.365+: 5755: error : virDriverLoadModule:79 : failed to load module /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so: undefined symbol: virStorageFileStat The original version was the server install of Ubuntu 12.04. It has Zentyal installed, which manages most of the server features. The current version as given by lsb_release -rd: OS VERSION: Description:Ubuntu 14.04.1 LTS Release:14.04 LIBVIRT VERSION: libvirt0 : 1.2.2-0ubuntu13.1.6 WHAT YOU EXPECTED TO HAPPEN: a) Running virsh list would show active VMs b) libvirt would load QEMU driver on start-up WHAT HAPPENED INSTEAD: a) Received error error: no connection driver available for qemu:///system b) libvirt loaded without QEMU driver - error only visible in /var/log/libvirtd/libvirtd.log (shown above) ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- 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/1389614 Title: libvirt lts upgrade misses librbd dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1389614/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389612] Re: cannot install php5-mapscript package, Depends: phpapi-20090626
** Tags added: mapscript php5 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1389612 Title: cannot install php5-mapscript package, Depends: phpapi-20090626 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1389612/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389152] Re: please merge libnss-ldap 265-3 (main) from Debian unstable (main)
lp1389152_ubuntu.debdiff is 3.8Mb so it is available on demand if needed ** Patch added: lp1389152_debian.debdiff https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1389152/+attachment/4253629/+files/lp1389152_debian.debdiff ** Changed in: libnss-ldap (Ubuntu) Status: In Progress = Confirmed ** Changed in: libnss-ldap (Ubuntu) Assignee: Louis Bouchard (louis-bouchard) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in Ubuntu. https://bugs.launchpad.net/bugs/1389152 Title: please merge libnss-ldap 265-3 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1389152/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1387594] Re: init: symbol lookup error: /lib/powerpc64le-linux-gnu/libnss_ldap.so.2: undefined symbol: __libc_lock_lock
** Changed in: libnss-ldap (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in Ubuntu. https://bugs.launchpad.net/bugs/1387594 Title: init: symbol lookup error: /lib/powerpc64le-linux- gnu/libnss_ldap.so.2: undefined symbol: __libc_lock_lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1387594/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1373261] Re: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address
The problem is still there. Example: My pserv.yaml contains... generator: http://[fdd1:caf5:2922:8b1f::1]/MAAS/api/1.0/pxeconfig/ Now, realising that this doesn't work, I run ‘dpkg-reconfigure maas- cluster-controller’ and set the MAAS URL to “http://10.9.9.1/MAAS”. The resulting pserv.yaml now contains... generator: http://10.9.9.1:caf5:2922:8b1f::1]/MAAS/api/1.0/pxeconfig/ Note how the first part of the netloc, up to the first colon, is replaced with the new address — but the rest of the netloc is still there. ** Changed in: maas Assignee: Jeroen T. Vermeulen (jtv) = (unassigned) ** Changed in: maas Status: Incomplete = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1373261 Title: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1373261/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1373261] Re: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address
On 5 November 2014 11:23, Jeroen T. Vermeulen 1373...@bugs.launchpad.net wrote: Note how the first part of the netloc, up to the first colon, is replaced with the new address — but the rest of the netloc is still there. Ah, now ISWYM. Sorry, I'd missed that the *existing* MAAS URL in pserv.yaml was an IPv6 address. Thanks for clarification. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1373261 Title: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1373261/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1364442] Re: udaddy is failing to get address handle in Ubuntu 14.10 (Mellanox)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libibverbs (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libibverbs in Ubuntu. https://bugs.launchpad.net/bugs/1364442 Title: udaddy is failing to get address handle in Ubuntu 14.10 (Mellanox) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libibverbs/+bug/1364442/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389647] [NEW] lm-sensors don`t recognize fan in the laptop ASUS M50VN
Public bug reported: lm-sensors don`t recognize fan in the laptop ASUS M50VN ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lm-sensors 1:3.3.4-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 5 19:52:06 2014 InstallationDate: Installed on 2014-11-03 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: lm-sensors UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lm-sensors (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1389647 Title: lm-sensors don`t recognize fan in the laptop ASUS M50VN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1389647/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1388621] Re: Please merge nginx 1.6.2-4 (main) from Debian Unstable (main)
* Provide a new, debian specific, default landing page. Does this need making into an Ubuntu-specific page like in bug 1288690? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1388621 Title: Please merge nginx 1.6.2-4 (main) from Debian Unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1388621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1216817] Re: [SRU] Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors.
Hello, Thomas! I sent work nginx configuration to your e-mail (on ubuntu.com). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1216817 Title: [SRU] Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors. To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1216817/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1374554] Re: ppc64el virsh start fails
Thanks Scott and Breno, I'll push that fix. ** Also affects: libvirt (Ubuntu Vivid) Importance: High Status: Confirmed ** Also affects: libvirt (Ubuntu Utopic) Importance: Undecided Status: New -- 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/1374554 Title: ppc64el virsh start fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1374554/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1388621] Re: Please merge nginx 1.6.2-4 (main) from Debian Unstable (main)
Doh, missed that first time round, that's what I get for working while tired. We should probably change it so it's Ubuntu specific, yes, as we already change the versioning to have Ubuntu branding. I'll redo the debdiffs this afternoon with such a change. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1388621 Title: Please merge nginx 1.6.2-4 (main) from Debian Unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1388621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389647] Re: lm-sensors don`t recognize fan in the laptop ASUS M50VN
That isn't a bug... ** Changed in: lm-sensors (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1389647 Title: lm-sensors don`t recognize fan in the laptop ASUS M50VN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1389647/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1388621] Re: Please merge nginx 1.6.2-4 (main) from Debian Unstable (main)
** Patch added: Merge Debdiff for 1.6.4-4ubuntu1, against Debian Unstable https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1388621/+attachment/4253901/+files/nginx_1.6.2-4_merge_debdiff_against_Debian_Unstable.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1388621 Title: Please merge nginx 1.6.2-4 (main) from Debian Unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1388621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1388621] Re: Please merge nginx 1.6.2-4 (main) from Debian Unstable (main)
** Patch removed: Debdiff for the merge, against Debian 1.6.2-4. https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1388621/+attachment/4251551/+files/nginx-1.6.2-4_merge_compared_to_debian.debdiff ** Patch removed: Debdiff for the merge, against Ubuntu 1.6.2-1ubuntu1.1 https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1388621/+attachment/4251543/+files/nginx-1.6.2-4_merge.debdiff ** Patch added: Merge Debdiff for 1.6.4-4ubuntu1, against Ubuntu Vivid (27MB) https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1388621/+attachment/4253900/+files/nginx_1.6.2-4_merge_debdiff_against_Ubuntu_Vivid.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1388621 Title: Please merge nginx 1.6.2-4 (main) from Debian Unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1388621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1388621] Re: Please merge nginx 1.6.2-4 (main) from Debian Unstable (main)
Debdiffs updated. I also caught a lingering reference to nginx-naxsi in the debian/control file and removed that reference. Apparently it didn't get caught by the merge tool, and I didn't see it first time round. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1388621 Title: Please merge nginx 1.6.2-4 (main) from Debian Unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1388621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1388036] Re: qemu-img segmentation fault when asking for options
Thanks! Brilliant example of how assumptions can interfere with bug reproductions. I had never tried with 'a' not existing. That appears to be the trigger. ** Also affects: qemu-kvm (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: qemu-kvm (Ubuntu) Importance: Undecided = Medium ** Changed in: qemu-kvm (Ubuntu) Status: Incomplete = Fix Released ** Changed in: qemu-kvm (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: qemu-kvm (Ubuntu Precise) Status: New = Triaged -- 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 segmentation fault when asking for options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1388036/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1216817] Re: [SRU] Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors.
Vorobyoff: Thanks for providing the conf, that gives me the basic information I needed to start building a test configuration. To all others: I estimate I'll have a test configuration available by the end of the day, and I will upload the test configuration here accordingly when finished. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1216817 Title: [SRU] Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors. To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1216817/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1387881] Re: qemu fails to recognize full virtualization
I can reproduce this in a VM:
1) boot a clean cloud images (uvt-kvm create lp1387881)
2) apt-get install virtinst
3) sudo virt-install --name juju-bootstrap --ram=2048 --vcpus=1 --hvm
--virt-type=kvm --pxe --boot network,hd --os-variant=ubuntutrusty --graphics
vnc --noautoconsole --os-type=linux --accelerate --nodisks -d
You'll get the following:
$ sudo virt-install --name juju-bootstrap --ram=2048 --vcpus=1 --hvm
--virt-type=kvm --pxe --boot network,hd --os-variant=ubuntutrusty --graphics
vnc --noautoconsole --os-type=linux --accelerate --nodisks -d
[Wed, 05 Nov 2014 16:23:29 virt-install 3297] DEBUG (cli:227) Launched with
command line:
/usr/bin/virt-install --name juju-bootstrap --ram=2048 --vcpus=1 --hvm
--virt-type=kvm --pxe --boot network,hd --os-variant=ubuntutrusty --graphics
vnc --noautoconsole --os-type=linux --accelerate --nodisks -d
[Wed, 05 Nov 2014 16:23:29 virt-install 3297] DEBUG (cli:332) Requesting
libvirt URI default
[Wed, 05 Nov 2014 16:23:29 virt-install 3297] DEBUG (cli:334) Received libvirt
URI qemu:///system
[Wed, 05 Nov 2014 16:23:29 virt-install 3297] DEBUG (virt-install:258)
Requesting virt method 'hvm', hv type 'kvm'.
[Wed, 05 Nov 2014 16:23:29 virt-install 3297] ERROR (cli:445) Host does not
support virtualization type 'hvm'
[Wed, 05 Nov 2014 16:23:29 virt-install 3297] DEBUG (cli:448)
Traceback (most recent call last):
File /usr/bin/virt-install, line 273, in get_virt_type
machine=options.machine)
File /usr/lib/python2.7/dist-packages/virtinst/CapabilitiesParser.py, line
736, in guest_lookup
{'virttype' : osstr, 'arch' : archstr})
ValueError: Host does not support virtualization type 'hvm'
--
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/1387881
Title:
qemu fails to recognize full virtualization
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1387881/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1387881] Re: qemu fails to recognize full virtualization
** Also affects: virtinst (Ubuntu) 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/1387881 Title: qemu fails to recognize full virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1387881/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389820] [NEW] Acer V5-571G: the laptop shuts down, turns off its power LED, and then starts again after a few seconds. It occurs more often when working on battery.
Public bug reported: Acer V5-571G: the laptop shuts down, turns off its power LED, and then starts again after a few seconds. It occurs more often when working on battery. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-40.68-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 5 21:34:12 2014 InstallationDate: Installed on 2014-11-04 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1389820 Title: Acer V5-571G: the laptop shuts down, turns off its power LED, and then starts again after a few seconds. It occurs more often when working on battery. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1389820/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1216817] Re: [SRU] Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors.
Here's a test procedure: (1) Use the attached test configuration file as a base, to test with localhost. (Partly derived from digital ocean's tutorials) (2) Create a PHP file in the specified path. Alternatively, use an alternate root path. (3) `tail -f /var/log/nginx/error.log`. Watch for any error outputs. (4) Load nginx with the config. There should not be any errors triggered similar to above. (5) To further test, load the PHP file you created. It should be rendered correctly and there should not be any errors in the error log similar to those observed with this bug. ** Attachment added: Test configuration for this bug https://bugs.launchpad.net/nginx/+bug/1216817/+attachment/4254042/+files/default-testcase -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1216817 Title: [SRU] Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors. To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1216817/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1216817] Re: [SRU] Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors.
Confirmed that this testcase works. You may use ppa:teward/nginx-sru as a test build if you wish to really test this before it's uploaded to the proposed repositories. I tested this on Trusty, but it should also work for precise. REMEMBER: nginx-extras has the module so this needs to be tested with nginx-extras and not any other package. ** Description changed: [Impact] - * The nginx-http-push module generates errors when using fastcgi_cache + * The nginx-http-push module generates errors when using fastcgi_cache or proxy_cache arguments in the config. - * This adds extra errors to the error logs, and causes problems with + * This adds extra errors to the error logs, and causes problems with the cache manager. - * Caching still works, however, but this causes excessive unnecessary + * Caching still works, however, but this causes excessive unnecessary noise in the error logs and the issue is an incompatibility between the module and the nginx cache manager. [Test Case] - * Use the nginx-extras package, and use any configuration with either - `fastcgi_cache` or `proxy_cache` arguments. (NOTE: I will attempt to - develop a test configuration that you can use to test this) + * Use the nginx-extras package, and use any configuration with either + `fastcgi_cache` or `proxy_cache` arguments. (NOTE: I have provided a + test case below that works with php5-fpm and this. You do not need + php5-fpm for this to work, however it would not hurt to have it + installed at the same time.) [Regression Potential] - * This fix originated upstream, and should not introduce any + * This fix originated upstream, and should not introduce any regressions. [Other Info] - - * The debdiffs here are derived from upstream changes, as detailed at https://github.com/slact/nginx_http_push_module/commit/836e8319c93681386fb00e6bd34d9e37612f3334.diff - * The only changes to this diff were the indentation, to match what was + * The debdiffs here are derived from upstream changes, as detailed at + https://github.com/slact/nginx_http_push_module/commit/836e8319c93681386fb00e6bd34d9e37612f3334.diff + + * The only changes to this diff were the indentation, to match what was in the packages. - [Original Description] system : Ubuntu 12.04 LTS package : nginx-extras 1.4.1-1ppa1~precise Hello, if you try to use proxy_cache or fastcgi_cache you got this error in error.log of nginx : 2013/08/26 00:13:10 [info] 15722#0: Using 32KiB of shared memory for push module in /etc/nginx/nginx.conf:137 2013/08/26 00:13:11 [alert] 15756#0: epoll_ctl(1, 0) failed (1: Operation not permitted) 2013/08/26 00:13:11 [alert] 15756#0: failed to register channel handler while initializing push module worker (1: Operation not permitted) 2013/08/26 00:13:11 [alert] 15757#0: epoll_ctl(1, 0) failed (1: Operation not permitted) 2013/08/26 00:13:11 [alert] 15757#0: failed to register channel handler while initializing push module worker (1: Operation not permitted) 2013/08/26 00:13:11 [alert] 15737#0: cache manager process 15756 exited with fatal code 2 and cannot be respawned You can't disable nginx_push_module, to make nginx cache to work. Everything is fine if you use the daemon off; option. I've seen this issue in many forum/mailing list, i think nginx_push_module shouldn't be in the extras package anymore. system : Ubuntu 12.04 LTS package : nginx-extras 1.4.1-1ppa1~precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1216817 Title: [SRU] Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors. To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1216817/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1216817] Re: [SRU] Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors.
** Attachment added: PRECISE Test configuration for this bug https://bugs.launchpad.net/nginx/+bug/1216817/+attachment/4254048/+files/default-testcase -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1216817 Title: [SRU] Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors. To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1216817/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1216817] Re: [SRU] Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors.
Please use the test configuration for your OS version - the only difference is the fastcgi_pass line because the php5-fpm listener doesn't listen in the same place on Precise as it does in Trusty (and vice versa) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1216817 Title: [SRU] Using `fastcgi_cache` or `proxy_cache` with nginx-extras causes the push module to throw errors. To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1216817/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389839] [NEW] Build with SASL support
Public bug reported: Can libmemcached please be built with SASL support going forward? This is a easy change but very helpful given how prevalent SASL is these days, especially with many of the cloud services that provide memcached requiring SASL for authentication. Ubuntu Version: 14.04 ** Affects: libmemcached (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libmemcached in Ubuntu. https://bugs.launchpad.net/bugs/1389839 Title: Build with SASL support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmemcached/+bug/1389839/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389849] Re: sudo service lxc-net restart does not reload dnsmasq when there is a container running
After consulting with Serge Hallyn, the original author of the upstart
script that governs creation of the lxc-net bridge, I came up with the
following solution:
1. Turn off all lxc containers and the lxc-net (sudo service lxc-net stop)
2. Remove (or move away) the file /etc/init/lxc-net.conf
3. Create the file /etc/init/lxc-net.conf with the following contents:
description lxc network
author Serge Hallyn serge.hal...@canonical.com
start on starting lxc
stop on stopped lxc
env USE_LXC_BRIDGE=true
env LXC_BRIDGE=lxcbr0
env LXC_ADDR=10.0.3.1
env LXC_NETMASK=255.255.255.0
env LXC_NETWORK=10.0.3.0/24
env varrun=/run/lxc
env LXC_DOMAIN=
pre-start script
[ -f /etc/default/lxc ] . /etc/default/lxc
[ x$USE_LXC_BRIDGE = xtrue ] || { stop; exit 0; }
use_iptables_lock=-w
iptables -w -L -n /dev/null 21 || use_iptables_lock=
cleanup() {
# dnsmasq failed to start, clean up the bridge
iptables $use_iptables_lock -D INPUT -i ${LXC_BRIDGE} -p udp --dport 67
-j ACCEPT
iptables $use_iptables_lock -D INPUT -i ${LXC_BRIDGE} -p tcp --dport 67
-j ACCEPT
iptables $use_iptables_lock -D INPUT -i ${LXC_BRIDGE} -p udp --dport 53
-j ACCEPT
iptables $use_iptables_lock -D INPUT -i ${LXC_BRIDGE} -p tcp --dport 53
-j ACCEPT
iptables $use_iptables_lock -D FORWARD -i ${LXC_BRIDGE} -j ACCEPT
iptables $use_iptables_lock -D FORWARD -o ${LXC_BRIDGE} -j ACCEPT
iptables $use_iptables_lock -t nat -D POSTROUTING -s ${LXC_NETWORK} !
-d ${LXC_NETWORK} -j MASQUERADE || true
iptables $use_iptables_lock -t mangle -D POSTROUTING -o ${LXC_BRIDGE}
-p udp -m udp --dport 68 -j CHECKSUM --checksum-fill
ifconfig ${LXC_BRIDGE} down || true
brctl delbr ${LXC_BRIDGE} || true
}
if [ -d /sys/class/net/${LXC_BRIDGE} ]; then
if [ ! -f ${varrun}/network_up ]; then
# bridge exists, but we didn't start it
stop;
fi
exit 0;
fi
# set up the lxc network
brctl addbr ${LXC_BRIDGE} || { echo Missing bridge support in kernel;
stop; exit 0; }
echo 1 /proc/sys/net/ipv4/ip_forward
mkdir -p ${varrun}
ifconfig ${LXC_BRIDGE} ${LXC_ADDR} netmask ${LXC_NETMASK} up
iptables $use_iptables_lock -I INPUT -i ${LXC_BRIDGE} -p udp --dport 67 -j
ACCEPT
iptables $use_iptables_lock -I INPUT -i ${LXC_BRIDGE} -p tcp --dport 67 -j
ACCEPT
iptables $use_iptables_lock -I INPUT -i ${LXC_BRIDGE} -p udp --dport 53 -j
ACCEPT
iptables $use_iptables_lock -I INPUT -i ${LXC_BRIDGE} -p tcp --dport 53 -j
ACCEPT
iptables $use_iptables_lock -I FORWARD -i ${LXC_BRIDGE} -j ACCEPT
iptables $use_iptables_lock -I FORWARD -o ${LXC_BRIDGE} -j ACCEPT
iptables $use_iptables_lock -t nat -A POSTROUTING -s ${LXC_NETWORK} ! -d
${LXC_NETWORK} -j MASQUERADE
iptables $use_iptables_lock -t mangle -A POSTROUTING -o ${LXC_BRIDGE} -p
udp -m udp --dport 68 -j CHECKSUM --checksum-fill
touch ${varrun}/network_up
end script
post-stop script
[ -f /etc/default/lxc ] . /etc/default/lxc
[ -f ${varrun}/network_up ] || exit 0;
# if $LXC_BRIDGE has attached interfaces, don't shut it down
ls /sys/class/net/${LXC_BRIDGE}/brif/* /dev/null 21 exit 0;
if [ -d /sys/class/net/${LXC_BRIDGE} ]; then
use_iptables_lock=-w
iptables -w -L -n /dev/null 21 || use_iptables_lock=
ifconfig ${LXC_BRIDGE} down
iptables $use_iptables_lock -D INPUT -i ${LXC_BRIDGE} -p udp --dport 67
-j ACCEPT
iptables $use_iptables_lock -D INPUT -i ${LXC_BRIDGE} -p tcp --dport 67
-j ACCEPT
iptables $use_iptables_lock -D INPUT -i ${LXC_BRIDGE} -p udp --dport 53
-j ACCEPT
iptables $use_iptables_lock -D INPUT -i ${LXC_BRIDGE} -p tcp --dport 53
-j ACCEPT
iptables $use_iptables_lock -D FORWARD -i ${LXC_BRIDGE} -j ACCEPT
iptables $use_iptables_lock -D FORWARD -o ${LXC_BRIDGE} -j ACCEPT
iptables $use_iptables_lock -t nat -D POSTROUTING -s ${LXC_NETWORK} !
-d ${LXC_NETWORK} -j MASQUERADE || true
iptables $use_iptables_lock -t mangle -D POSTROUTING -o ${LXC_BRIDGE}
-p udp -m udp --dport 68 -j CHECKSUM --checksum-fill
pid=`cat ${varrun}/dnsmasq.pid 2/dev/null` kill -9 $pid || true
rm -f ${varrun}/dnsmasq.pid
brctl delbr ${LXC_BRIDGE}
fi
rm -f ${varrun}/network_up
end script
4. Create the file /etc/init/lxc-dnsmasq.conf with the following
contents:
description lxc dnsmasq service
author Adam Ryczkowski, ispired by Serge Hallyn serge.hal...@canonical.com
expect fork
start on started lxc-net
stop on stopped lxc-net
env USE_LXC_BRIDGE=true
env LXC_BRIDGE=lxcbr0
env LXC_ADDR=10.0.3.1
env LXC_NETMASK=255.255.255.0
env LXC_NETWORK=10.0.3.0/24
env LXC_DHCP_RANGE=10.0.3.2,10.0.3.254
env LXC_DHCP_MAX=253
env LXC_DHCP_CONFILE=
env varrun=/run/lxc-dnsmasq
env LXC_DOMAIN=
pre-start script
[ -f /etc/default/lxc ] . /etc/default/lxc
[ x$USE_LXC_BRIDGE = xtrue ] || { stop; exit 0; }
if [ !
[Bug 1389849] [NEW] sudo service lxc-net restart does not reload dnsmasq when there is a container running
Public bug reported: I know, that I can assign static IP manually, using /etc/network/interfaces. I also know, that I can read the MAC address of the LXC container (e.g. by looking for lxc.network.hwaddr entry in /var/lib/lxc/container- name/config and assign the IP based using entries dhcp-host=mac- addr,10.0.3.3 in /etc/dnsmasq.d/some file. In the file /etc/default/lxc-net I read # Uncomment the next line if you'd like to use a conf-file for the lxcbr0 # dnsmasq. For instance, you can use 'dhcp-host=mail1,10.0.3.100' to have # container 'mail1' always get ip address 10.0.3.100. #LXC_DHCP_CONFILE=/etc/lxc/dnsmasq.conf That would suit my needs; unfortunately doing so has no effect - at least not until the next computer reboot. I would expect that `sudo service lxc-net restart` forces the dnsmasq to reload - unfortunately it never works. To reproduce: On Ubuntu Trusty 14.04 64bit, 1. install package lxc, 2. create a container (e.g. sudo lxc-create -n mycontainer -t ubuntu -- -r trusty) 3. start it (sudo lxc-start -d -n mycontainer) 4. create another container (e.g. sudo lxc-create -n my2ndcontainer -t ubuntu -- -r trusty) 5. edit /etc/default/lxc-net to uncomment the LXC_DHCP_CONFILE 6. edit /etc/lxc/dnsmasq.conf to contain a line like `dhcp-host=my2ndcontainer,10.0.3.142` 7. sudo service lxc-net restart 8. start the 2nd container (sudo lxc-start -d -n my2ndcontainer) The steps 2 and 3 are optional. The 2nd container never gets the ip 10.0.3.142, but it keeps the assigned dynamic IP Walkaround 1: Turn off the computer and test again tomorrow. Walkaround 2 (more serious, but works only if steps 2 and 3 are skipped): name=my2ndcontainer sudo lxc-stop -n $name /dev/null sudo service lxc-net stop /dev/null if [ -d /sys/class/net/$internalif ]; then sudo brctl delbr $internalif /dev/null #Why? See below. fi sudo rm /var/lib/misc/dnsmasq.$internalif.leases sudo service lxc-net start /dev/null sudo lxc-start -d -n $name /dev/null sleep 5 Unfortunately, there is a bug (feature?) in the /etc/init/lxc-net.conf in Ubuntu 14.04 that prevents reloading the dnsmasq unless the bridge device is down for the host. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1389849 Title: sudo service lxc-net restart does not reload dnsmasq when there is a container running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1389849/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
I'm still seeing the problem with new kernels. It breaks my ceph installation badly. [1368555.197934] [ cut here ] [1368555.197945] WARNING: CPU: 3 PID: 4400 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [1368555.197947] name 'fs/nfsfs' [1368555.197949] Modules linked in: gspca_ov534 nls_iso8859_1 usb_storage xt_TCPMSS xt_tcpmss arc4 ppp_mppe ppp_async crc_ccitt vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev xt_multiport pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) xt_conntrack ipt_REJECT veth ip6table_filter ip6_tables ebtable_nat ebtables xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi rfcomm rbd libceph openvswitch gre vxlan ip_tunnel binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt xfs snd_usb_audio snd_usbmidi_lib fglrx(POX) kvm_amd kvm gspca_main videodev wacom serio_raw dm_multipath scsi_dh joydev edac_core edac_mce_amd k10temp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel btusb snd_hda _codec snd_hwdep snd_pcm bluetooth snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore sp5100_tco amd_iommu_v2 i2c_piix4 asus_atk0110 mac_hid parport_pc ppdev lp parport btrfs libcrc32c raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log hid_generic hid_logitech_dj usbhid hid pata_acpi psmouse pata_atiixp ahci e1000e pata_marvell libahci firewire_ohci ptp firewire_core pps_core r8169 crc_itu_t mii floppy wmi [last unloaded: gspca_ov534] [1368555.198044] CPU: 3 PID: 4400 Comm: kworker/u12:1 Tainted: PW OX 3.13.0-37-generic #64-Ubuntu [1368555.198046] Hardware name: System manufacturer System Product Name/M4A79T Deluxe, BIOS 350305/06/2011 [1368555.198051] Workqueue: netns cleanup_net [1368555.198053] 0009 880119017c80 8171ed09 880119017cc8 [1368555.198057] 880119017cb8 8106773d 0005 [1368555.198060] a06e48a8 880323019ab0 0180 880119017d18 [1368555.198063] Call Trace: [1368555.198070] [8171ed09] dump_stack+0x45/0x56 [1368555.198074] [8106773d] warn_slowpath_common+0x7d/0xa0 [1368555.198079] [810677ac] warn_slowpath_fmt+0x4c/0x50 [1368555.198084] [81229839] remove_proc_entry+0x139/0x1b0 [1368555.198103] [a06c44e2] nfs_fs_proc_net_exit+0x62/0x70 [nfs] [1368555.198115] [a06ca5b2] nfs_net_exit+0x12/0x20 [nfs] [1368555.198118] [8161b409] ops_exit_list.isra.1+0x39/0x60 [1368555.198122] [8161bc90] cleanup_net+0x110/0x250 [1368555.198126] [810839c2] process_one_work+0x182/0x450 [1368555.198130] [810847b1] worker_thread+0x121/0x410 [1368555.198133] [81084690] ? rescuer_thread+0x430/0x430 [1368555.198137] [8108b492] kthread+0xd2/0xf0 [1368555.198140] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [1368555.198143] [8172f77c] ret_from_fork+0x7c/0xb0 [1368555.198146] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [1368555.198148] ---[ end trace 007872efa0f6c8f7 ]--- [1372797.021226] libceph: osd0 172.16.0.119:6800 socket closed (con state OPEN) [1373904.941772] libceph: osd2 172.16.0.119:6805 socket closed (con state OPEN) [1374022.647670] [ cut here ] [1374022.647691] WARNING: CPU: 1 PID: 17323 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [1374022.647696] name 'fs/nfsfs' [1374022.647700] Modules linked in: gspca_ov534 nls_iso8859_1 usb_storage xt_TCPMSS xt_tcpmss arc4 ppp_mppe ppp_async crc_ccitt vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev xt_multiport pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) xt_conntrack ipt_REJECT veth ip6table_filter ip6_tables ebtable_nat ebtables xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi rfcomm rbd libceph openvswitch gre vxlan ip_tunnel binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt xfs snd_usb_audio snd_usbmidi_lib fglrx(POX) kvm_amd kvm gspca_main videodev wacom serio_raw dm_multipath scsi_dh joydev edac_core edac_mce_amd k10temp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel btusb snd_hda _codec snd_hwdep snd_pcm bluetooth snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi
[Bug 1389864] [NEW] /etc/dnsmasq.d-available/lxc has no effect on a NetworkManager system
Public bug reported: The lxc package installs dnsmasq configuration as /etc/dnsmasq.d-available/lxc, and a symlink to it is created at /etc/dnsmasq.d/lxc, but neither has any effect on the main dnsmasq instance on systems running NetworkManager, because NetworkManager starts a dnsmasq instance that looks in /etc/NetworkManager/dnsmasq.d instead. This makes directing .lxc domain name lookups to the right place seem to fail, which is how I noticed it. I imagine it also leads to other configurations not working as expected. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Description changed: The lxc package installs dnsmasq configuration as /etc/dnsmasq.d-available/lxc, and a symlink to it is created at - /etc/dnsmasq.d/lxc, but neither has any effect on systems running - NetworkManager, because NetworkManager starts a dnsmasq instance that - looks in /etc/NetworkManager/dnsmasq.d instead. + /etc/dnsmasq.d/lxc, but neither has any effect on the main dnsmasq + instance on systems running NetworkManager, because NetworkManager + starts a dnsmasq instance that looks in /etc/NetworkManager/dnsmasq.d + instead. This makes directing .lxc domain name lookups to the right place seem to - fail, and probably leads to other thinks not seeming to work as - expected. + fail, which is how I noticed it. I imagine it also leads to other + configurations not working as expected. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1389864 Title: /etc/dnsmasq.d-available/lxc has no effect on a NetworkManager system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1389864/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389897] Re: no way to install enough qemu for kvm in a cross platform way
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qemu (Ubuntu) Status: New = Confirmed -- 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/1389897 Title: no way to install enough qemu for kvm in a cross platform way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389897] [NEW] no way to install enough qemu for kvm in a cross platform way
Public bug reported: There is currently no way to install just enough qemu to have kvm work. On x86 you can install qemu-kvm, but even on the other architectures where this is built (e.g. armhf) it depends on qemu-system-x86. Or you can install qemu-system but that installs way more than you need. Quick consensus seemed to be that qemu-kvm should depend on the appropriate qemu-system-$ARCH. ** Affects: qemu (Ubuntu) Importance: Undecided Status: Confirmed -- 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/1389897 Title: no way to install enough qemu for kvm in a cross platform way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1386052] Re: pollen fails to log everytime rsyslog package is upgraded or daemon is bounced
Since the update, it seems that pollen isn't logging anymore: | -rw-r--r-- 1 syslog adm 276100 Nov 4 06:36 pollen.log-20141104.xz | -rw-r--r-- 1 syslog adm 5665237 Nov 5 06:23 pollen.log-20141105 | -rw-r--r-- 1 syslog adm 703 Nov 5 23:23 pollen.log | ubuntu@juju-machine-2-lxc-1:/var/log/pollen$ ps afxu | grep pollen root 393 0.0 0.0 283676 12648 ?Ssl Aug05 33:22 /var/lib/juju/tools/unit-pollen-2/jujud unit --data-dir /var/lib/juju --unit-name pollen/2 --debug | ubuntu 26609 0.0 0.0 8120 936 pts/0S+ 23:25 0:00 \_ grep --color=auto pollen pollen 26584 1.3 0.0 105380 3424 ?Ssl 23:23 0:01 pollen -http-port=80 -https-port=443 -device=/dev/random -bytes=64 -cert=/etc/pollen/cert.pem -key=/etc/pollen/key.pem | ubuntu@juju-machine-2-lxc-1:/var/log/pollen$ tail pollen.log | Nov 5 15:30:40 juju-machine-2-lxc-1 sudo: ubuntu : TTY=pts/0 ; PWD=/var/log/pollen ; USER=root ; COMMAND=/usr/sbin/service pollen restart | Nov 5 15:30:40 juju-machine-2-lxc-1 pollen[17216]: pollen starting at [1415201440626942702] | Nov 5 23:23:05 juju-machine-2-lxc-1 sudo: ubuntu : TTY=pts/0 ; PWD=/var/log/pollen ; USER=root ; COMMAND=/usr/sbin/service pollen restart | Nov 5 23:23:05 juju-machine-2-lxc-1 pollen[26540]: pollen starting at [1415229785441503131] | Nov 5 23:23:40 juju-machine-2-lxc-1 sudo: ubuntu : TTY=pts/0 ; PWD=/var/log/pollen ; USER=root ; COMMAND=/usr/sbin/service rsyslog restart | Nov 5 23:23:40 juju-machine-2-lxc-1 pollen[26584]: pollen starting at [1415229820178875333] -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pollen in Ubuntu. https://bugs.launchpad.net/bugs/1386052 Title: pollen fails to log everytime rsyslog package is upgraded or daemon is bounced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollen/+bug/1386052/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389897] Re: no way to install enough qemu for kvm in a cross platform way
** Patch added: 0001-Increase-sanity-around-qemu-kvm.patch https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+attachment/4254170/+files/0001-Increase-sanity-around-qemu-kvm.patch -- 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/1389897 Title: no way to install enough qemu for kvm in a cross platform way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389897] Re: no way to install enough qemu for kvm in a cross platform way
** Patch added: 0002-Install-usr-bin-kvm-wrapper-for-non-32-bit-power.patch https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+attachment/4254171/+files/0002-Install-usr-bin-kvm-wrapper-for-non-32-bit-power.patch -- 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/1389897 Title: no way to install enough qemu for kvm in a cross platform way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389897] Re: no way to install enough qemu for kvm in a cross platform way
** Patch added: 0003-Handle-32-bit-powerpc.patch https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+attachment/4254172/+files/0003-Handle-32-bit-powerpc.patch -- 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/1389897 Title: no way to install enough qemu for kvm in a cross platform way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389897] Re: no way to install enough qemu for kvm in a cross platform way
Here's a patch that does this, with help from Adam and Ben. You can see a more split out version at https://github.com/mwhudson/qemu/commits /qemu-kvm-arches. ** Patch removed: 0003-Handle-32-bit-powerpc.patch https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+attachment/4254172/+files/0003-Handle-32-bit-powerpc.patch ** Patch removed: 0001-Increase-sanity-around-qemu-kvm.patch https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+attachment/4254170/+files/0001-Increase-sanity-around-qemu-kvm.patch ** Patch removed: 0002-Install-usr-bin-kvm-wrapper-for-non-32-bit-power.patch https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+attachment/4254171/+files/0002-Install-usr-bin-kvm-wrapper-for-non-32-bit-power.patch ** Patch added: qemu-kvm-arches.diff https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+attachment/4254175/+files/qemu-kvm-arches.diff -- 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/1389897 Title: no way to install enough qemu for kvm in a cross platform way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389897] Re: no way to install enough qemu for kvm in a cross platform way
The attachment qemu-kvm-arches.diff seems to be a patch. If it isn't, please remove the patch flag from the attachment, remove the patch tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1389897 Title: no way to install enough qemu for kvm in a cross platform way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389897] Re: no way to install enough qemu for kvm in a cross platform way
+1 (with extreme bias) on this from me. I'll give hallyn some time to review it, but if he doesn't get around to it, I'll just add a debian/changelog entry and sponsor this to vivid. I also feel pretty strongly that we should SRU this back to utopic and trusty. ** Also affects: qemu (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Assignee: (unassigned) = Serge Hallyn (serge-hallyn) -- 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/1389897 Title: no way to install enough qemu for kvm in a cross platform way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389914] [NEW] python-trove uninstallable on trusty w/ juno cloud-archive
Public bug reported: root@controller1:~# apt-get install python-trove Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python-trove : Depends: python-sqlalchemy ( 0.9) but 0.9.7-1~cloud0 is to be installed E: Unable to correct problems, you have held broken packages. root@controller1:~# apt-cache policy python-sqlalchemy python-sqlalchemy: Installed: 0.9.7-1~cloud0 Candidate: 0.9.7-1~cloud0 Version table: *** 0.9.7-1~cloud0 0 100 /var/lib/dpkg/status 0.8.4-1build1 0 500 http://ch.archive.ubuntu.com:80/ubuntu/ trusty/main amd64 Packages root@controller1:~# ** Affects: openstack-trove (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openstack-trove in Ubuntu. https://bugs.launchpad.net/bugs/1389914 Title: python-trove uninstallable on trusty w/ juno cloud-archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openstack-trove/+bug/1389914/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389830] Re: Don't use wlan0 for cluster to region communication [when cluster and region are on same machine]
This is a packaging issue; it detects the IP to configure for DEFAULT_MAAS_URL and then pops up a message about using dpkg-reconfigure if it's wrong. It could do better, is a blanket ignoring of wlan0 appropriate? Or maybe ignore it only if eth* is present. ** Also affects: maas (Ubuntu) Importance: Undecided Status: New ** Changed in: maas Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1389830 Title: Don't use wlan0 for cluster to region communication [when cluster and region are on same machine] To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1389830/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389914] Re: python-trove uninstallable on trusty w/ juno cloud-archive
As a workaround, installing the package from utopic seems to work. root@controller1:~# dpkg -i python-trove_2014.2-0ubuntu1_all.deb Selecting previously unselected package python-trove. (Reading database ... 167716 files and directories currently installed.) Preparing to unpack python-trove_2014.2-0ubuntu1_all.deb ... Unpacking python-trove (2014.2-0ubuntu1) ... dpkg: dependency problems prevent configuration of python-trove: python-trove depends on python-designateclient; however: Package python-designateclient is not installed. dpkg: error processing package python-trove (--install): dependency problems - leaving unconfigured Errors were encountered while processing: python-trove root@controller1:~# apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following extra packages will be installed: python-designateclient The following NEW packages will be installed: python-designateclient 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 13.2 kB of archives. After this operation, 145 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://ch.archive.ubuntu.com:80/ubuntu/ trusty/universe python-designateclient all 1.0.0-0ubuntu1 [13.2 kB] Fetched 13.2 kB in 0s (191 kB/s) Selecting previously unselected package python-designateclient. (Reading database ... 168304 files and directories currently installed.) Preparing to unpack .../python-designateclient_1.0.0-0ubuntu1_all.deb ... Unpacking python-designateclient (1.0.0-0ubuntu1) ... Setting up python-designateclient (1.0.0-0ubuntu1) ... Setting up python-trove (2014.2-0ubuntu1) ... root@controller1:~# ** Tags added: cloud-archive ** Package changed: openstack-trove (Ubuntu) = cloud-archive -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openstack-trove in Ubuntu. https://bugs.launchpad.net/bugs/1389914 Title: python-trove uninstallable on trusty w/ juno cloud-archive To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1389914/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389919] [NEW] Anonymous authentication does not work with mount.cifs
Public bug reported: I have an anonymous-access share on a Windows 2012 server that I'm trying to mount from Ubuntu 14.04. I can access the share via smbclient as expected: $ smbclient -N //foo.example.com/MyShare Anonymous login successful Domain=[LAB9320] OS=[Windows Server 2012 Standard 9200] Server=[Windows Server 2012 Standard 6.2] smb: \ ls . D0 Wed Nov 5 11:46:22 2014 .. D0 Wed Nov 5 11:46:22 2014 testD0 Wed Nov 5 01:58:42 2014 5 blocks of size 4194304. 41916 blocks available However, I can't get the share to mount at all via mount.cifs: $ sudo mount.cifs //foo.example.com/MyShare /mnt/test -o file_mode=0777,dir_mode=0777,uid=500,gid=124,noperm,guest,sec=none mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) For reference, I've modified the following settings in secpol.msc Security Settings Local Policies Security Options on the Windows server to enable anonymous access to the share: 1. Network access: Do not allow anonymous enumeration of SAM accounts and shares: Disabled 2. Network access: Let everyone permissions apply to anonymous users: Enabled 3. Network access: Restrict anonymous access to Named Pipes and shares: Disabled 4. Network access: Shares that can be accessed anonymously: MyShare In addition, I've given the following local SIDs Full Control of the share and the folder itself: Everyone, Guest, and ANONYMOUS LOGON. Please note that the Guest account is NOT enabled on this system, for security purposes (I don't want guest auth, I want anonymous auth). ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1389919 Title: Anonymous authentication does not work with mount.cifs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1389919/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389920] [NEW] The domain option in credentials files isn't working with smbclient
Public bug reported: It seems that smbclient isn't properly parsing domains out of credentials files: $ sudo cat /etc/auto.cifs.mycreds username=myuser password=SuperSecret domain=LAB9320 $ sudo smbclient -A /etc/auto.cifs.mycreds //foo.example.com/MyShare session setup failed: NT_STATUS_LOGON_FAILURE But if I specify the domain (again) via the command line options, it works: $ sudo smbclient -A /etc/auto.cifs.mycreds -W LAB9320 //foo.example.com/MyShare Domain=[LAB9320] OS=[Windows Server 2012 Standard 9200] Server=[Windows Server 2012 Standard 6.2] smb: \ ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1389920 Title: The domain option in credentials files isn't working with smbclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1389920/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389920] Re: The domain option in credentials files isn't working with smbclient
Whoops, forgot to mention: this is on Ubuntu 14.04. $ apt-cache show cifs-utils | grep Version Version: 2:6.0-1ubuntu2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1389920 Title: The domain option in credentials files isn't working with smbclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1389920/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389897] Re: no way to install enough qemu for kvm in a cross platform way
Bah, my patch runs into the dh_install can't rename a file thing. Maybe using dh-exec in a .install file is the answer? I'll try to do that later, but I need to disappear for a few hours first... -- 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/1389897 Title: no way to install enough qemu for kvm in a cross platform way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389930] [NEW] computer hibernates and hibernation can't be turned off
Public bug reported: there is no setting for hibernation (you can enable/disable sleep) supposedly hibernation is disabled by default (/var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla says so too) but still instead of sleeping, computer hibernates. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: pm-utils 1.4.1-15 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Wed Nov 5 19:53:56 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-02 (3 days ago) InstallationMedia: It PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1389930 Title: computer hibernates and hibernation can't be turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1389930/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389938] [NEW] kvm instance can't be launched with '-serial pty'
Public bug reported: 1, version ubuntu@ms01a:~/ming$ uname -a Linux ms01a 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:10:54 UTC 2014 aarch64 aarch64 aarch64 GNU/Linux 2, kvm instance can't be launched, and see below failure log in /var/log/nova/nova-compute.log: 2014-11-05 21:58:58.480 781 INFO nova.compute.manager [-] [instance: 1e3bc825-b44f-47ee-b438-2fc06b133f5d] During sync_power_state the instance has a pending task. Skip. 2014-11-05 21:58:58.697 781 ERROR oslo.messaging.rpc.dispatcher [-] Exception during message handling: internal error: early end of file from monitor: possible problem: qemu-system-aarch64: -serial pty: Failed to create chardev qemu: could not connect serial device to character backend 'pty' 3, once I have done below change, the problem is fixed: nova/virt/libvirt/driver.py: #consolepty = vconfig.LibvirtConfigGuestSerial() #consolepty.type = pty #guest.add_device(consolepty) ** Affects: nova (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1389938 Title: kvm instance can't be launched with '-serial pty' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1389938/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1316579] Re: --upload-tools doesn't work with bootstrap on armhf machine managed by maas
** Changed in: juju-core Status: Triaged = Incomplete ** Changed in: juju-core (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1316579 Title: --upload-tools doesn't work with bootstrap on armhf machine managed by maas To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1316579/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389864] Re: /etc/dnsmasq.d-available/lxc has no effect on a NetworkManager system
** Description changed: The lxc package installs dnsmasq configuration as /etc/dnsmasq.d-available/lxc, and a symlink to it is created at /etc/dnsmasq.d/lxc, but neither has any effect on the main dnsmasq instance on systems running NetworkManager, because NetworkManager starts a dnsmasq instance that looks in /etc/NetworkManager/dnsmasq.d instead. - This makes directing .lxc domain name lookups to the right place seem to - fail, which is how I noticed it. I imagine it also leads to other + This means that when someone adds server=/lxc/10.0.3.1 to lxc's dnsmasq + config file, it doesn't work. I imagine it also leads to other configurations not working as expected. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1389864 Title: /etc/dnsmasq.d-available/lxc has no effect on a NetworkManager system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1389864/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389954] [NEW] Make .lxc domain name resolution easier to discover and enable
Public bug reported: The lxc package on ubuntu does almost nothing to help a user enable DNS resolution for containers via dnsmaq, let alone discover that it is possible. How about enabling it by default? I think all it would take is adding server=/lxc/10.0.3.1 to a file in /etc/NetworkManager/dnsmasq.d/ and uncommenting LXC_DOMAIN=lxc in /etc/default/lxc-net. Even if there's a good reason not to enable this by default, shouldn't it at least be clearly documented someplace obvious instead of buried in a system config file with a misleading comment that mentions the wrong dnsmasq file to edit? (The one currently mentioned by /etc/default/lxc- net does nothing on ubuntu desktop systems, because ubuntu's NetworkManager starts dnsmasq with a special config directory.) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Description changed: The lxc package on ubuntu does almost nothing to help a user enable DNS resolution for containers via dnsmaq, let alone discover that it is possible. How about enabling it by default? I think all it would take is adding server=/lxc/10.0.3.1 to a file in /etc/NetworkManager/dnsmasq.d/ and uncommenting LXC_DOMAIN=lxc in /etc/default/lxc-net. Even if there's a good reason not to enable this by default, shouldn't it at least be clearly documented someplace obvious instead of buried in a system config file with a misleading comment that mentions the wrong - dnsconf file to edit? (The dnsconf file path currently mentioned in + dnsmasq file to edit? (The dnsconf file path currently mentioned in /etc/default/lxc-net does nothing on ubuntu desktop systems, because NetworkManager starts dnsconf with a special config directory.) ** Description changed: The lxc package on ubuntu does almost nothing to help a user enable DNS resolution for containers via dnsmaq, let alone discover that it is possible. How about enabling it by default? I think all it would take is adding server=/lxc/10.0.3.1 to a file in /etc/NetworkManager/dnsmasq.d/ and uncommenting LXC_DOMAIN=lxc in /etc/default/lxc-net. Even if there's a good reason not to enable this by default, shouldn't it at least be clearly documented someplace obvious instead of buried in a system config file with a misleading comment that mentions the wrong - dnsmasq file to edit? (The dnsconf file path currently mentioned in - /etc/default/lxc-net does nothing on ubuntu desktop systems, because - NetworkManager starts dnsconf with a special config directory.) + dnsmasq file to edit? (The one currently mentioned by /etc/default/lxc- + net does nothing on ubuntu desktop systems, because ubuntu's + NetworkManager starts dnsmasq with a special config directory.) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1389954 Title: Make .lxc domain name resolution easier to discover and enable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1389954/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1383704] Re: Can't switch off SSLv3 cipher groups in haproxy
** Changed in: haproxy (Ubuntu) Importance: Undecided = High -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1383704/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389647] Re: lm-sensors don`t recognize fan in the laptop ASUS M50VN
Why not work? Not supported? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1389647 Title: lm-sensors don`t recognize fan in the laptop ASUS M50VN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1389647/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1309439] Re: package samba-libs 2:4.1.6+dfsg-1ubuntu2 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1
** Changed in: samba (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1309439 Title: package samba-libs 2:4.1.6+dfsg-1ubuntu2 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1309439/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1381537] Re: Dovecot version in precise too old to switch off SSLv3 protocol for poodle fix
Dovecot uses Unix password authentication by default. If those passwords leak, they can be used to ssh in and perhaps even for sudo. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1381537 Title: Dovecot version in precise too old to switch off SSLv3 protocol for poodle fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1381537/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1379201] Re: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3: openvswitch kernel module failed to build [error: too many arguments to function ‘ip_select_ident’]
openvswitch (2.0.2-0ubuntu0.14.04.1~cloud1) precise-icehouse; urgency=medium * Backport ip_select_ident signature detection to fix FTBFS of dkms packages due to ABI change in stable kernels (LP: #1379201). ** Changed in: cloud-archive Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1379201 Title: openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3: openvswitch kernel module failed to build [error: too many arguments to function ‘ip_select_ident’] To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1379201/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1387251] Re: apparmor conflict with precise cloud archive
This was fixed under: libvirt (1.2.2-0ubuntu13.1.6~cloud2) precise-icehouse; urgency=medium [ Chuck Short ] * Back out of libvirt apparmor changes which are not compatible with apparmor in Ubuntu 12.04 (LP: #1276719): - d/apparmor/libvirt-qemu - d/apparmor/usr.sbin.libvirtd [ James Page ] * d/control: Drop Conflicts on older apparmor so that installation of libvirt does not force a removal of apparmor. However the changelog had the wrong bug reference. ** Changed in: cloud-archive Status: In Progress = Fix Released -- 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/1387251 Title: apparmor conflict with precise cloud archive To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1387251/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1389897] Re: no way to install enough qemu for kvm in a cross platform way
Here's another attempt. Also not build tested yet. ** Patch added: qemu-kvm-arches-2.diff https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+attachment/4254290/+files/qemu-kvm-arches-2.diff -- 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/1389897 Title: no way to install enough qemu for kvm in a cross platform way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
