There's no downside for me.
http://www.seabios.org/pipermail/seabios/2015-January/008546.html and
http://www.seabios.org/pipermail/seabios/2015-January/008547.html have a
couple of answers. Basically, CONFIG_VGA_ALLOCATE_EXTRA_STACK improves
things for some old DOS programs. No examples were given.
I see I haven't given a status update here... There were a couple of
patches on the mailing list. One definitely fixes it. The other fixes
it, but possibly (I should retest) breaks video output while booting (on
seabios git, but not 1.7.4).
--
You received this bug notification because you are a
A workaround: chmod +x /etc/etckeeper/commit.d/50vcs-commit
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to etckeeper in Ubuntu.
https://bugs.launchpad.net/bugs/1385885
Title:
etckeeper (with git) fails to commit any data on fresh u
I no longer use KVM. It is unsupported, it seems.
Yours
Federico
On Fri, Jan 16, 2015 at 5:16 PM, Ryan Harper <1318...@bugs.launchpad.net>
wrote:
> Hi,
>
> Are you running ntp in the host or timekeeping in the guest? If so, is
> the guest clock close to what current time should be?
>
> Also, can
This bug was fixed in the package qemu - 1:2.1+dfsg-11ubuntu2
---
qemu (1:2.1+dfsg-11ubuntu2) vivid; urgency=medium
* Cherrypick upstream patch needed to allow ESx hosts to run under
kvm (LP: #1411575)
-- Serge HallynFri, 16 Jan 2015 16:32:48 -0600
** Changed in: qemu (Ubu
I report the same situation as comment 129.
Spark Cluster installed with Ambari 1.7, installed HDP 2.2 running Zookeeper,
Ganglia, HDFS and YARN.
Ubuntu 12.04
uname -r
3.2.0-67-virtual
Instances running fine until the start of a Spark of Hadoop job with YARN. The
Job gets accepted but then 2 s
Public bug reported:
I am unable to recover the desktop for my vmware workstation image
(amd64). I updated from 14.04 to 14.10 and since then has not started.
It shows sa-compile error.
** Affects: spamassassin (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug no
*** This bug is a duplicate of bug 1391322 ***
https://bugs.launchpad.net/bugs/1391322
** This bug has been marked a duplicate of bug 1391322
[ubuntu- 14.10] librtas: fixes for LE support
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscr
** Branch linked: lp:ubuntu/trusty-proposed/libnss-ldap
** Branch linked: lp:~ubuntu-branches/ubuntu/utopic/libnss-ldap/utopic-
proposed
--
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/
Hi,
Are you running ntp in the host or timekeeping in the guest? If so, is
the guest clock close to what current time should be?
Also, can you try adding this option:
-global mc146818rtc.lost_tick_policy=slew
--
You received this bug notification because you are a member of Ubuntu
Server Team
Hello Louis, or anyone else affected,
Accepted libnss-ldap into utopic-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/libnss-
ldap/264-2.2ubuntu4.14.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Louis, or anyone else affected,
Accepted libnss-ldap into trusty-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/libnss-
ldap/264-2.2ubuntu4.14.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** Changed in: qemu (Ubuntu)
Status: Incomplete => 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/1318830
Title:
High CPU usage on windows virtual machine
To manage notific
** Changed in: qemu (Ubuntu)
Importance: Undecided => Low
** Changed in: qemu (Ubuntu)
Status: New => Triaged
--
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/1396497
Title:
'
Thanks - just to be clear, was ther eany downside to setting
CONFIG_VGA_ALLOCATE_EXTRA_STACK=n?
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
** Changed in: qemu (Ubuntu)
Importance: Undecided => Medium
** Changed in: qemu (Ubuntu)
Importance: Medium => High
--
You receive
** Changed in: qemu (Ubuntu)
Status: New => Invalid
** Changed in: qemu
Status: New => Invalid
** Changed in: virtinst (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu
Please reply if you can still reproduce this bug.
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed => Incomplete
--
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/1047040
Titl
This issue should be fixed in the qemu-kvm version included in precise.
** Changed in: qemu-kvm (Ubuntu)
Status: Triaged => Fix Released
--
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.
The file seems to be in qemu-system-common (at least in Ubuntu 14.10).
The next question is how to best help the user to run the right command.
Should it go into the manpage?
** Package changed: qemu-kvm (Ubuntu) => qemu (Ubuntu)
** Changed in: qemu (Ubuntu)
Importance: Undecided => Medium
*
If this is still an issue, please try to reproduce it with the lastest
upstream daily build from https://launchpad.net/~ubuntu-
virt/+archive/ubuntu/virt-daily-upstream
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
** Changed in: qemu-kvm (Ubuntu)
Status: New => Confirmed
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided => Wishlist
--
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/
This sort of result is not unexpected when the guest is under high load,
depending on your setup and whether the nics are emulated.
Can you show your kvm command line?
** Changed in: qemu-kvm (Ubuntu)
Status: New => Incomplete
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided => L
If you are still having an issue, please reply.
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed => Incomplete
--
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/1256866
Title:
Is this still an issue for you?
There were some actual KSM corruption bugs which were somewhat recently
fixed.
KSM in general wil use more CPU in order to reduce memory contention, so
your results are not necessarily unexpected. Aside from turning KSM
off, you can also reduce the KSM frequency.
Not by design, no. Any of that, really, since I wouldn't have known
where to go to make these alterations if I wanted to (well, now that you
pointed that out, I should be able to reverse-engineer it and see if it
at least assigns IP addresses to containers automatically that way).
It's a pretty new
Just to be sure you do also get this error if you just type
/usr/bin/qemu-system-x86_64 -vnc :1
?
--
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/1408692
Title:
libvirt does not start
Could you show the results of:
strings /lib/x86_64-linux-gnu/libusb-1.0.so.0.1.0 | grep libusb_get_p
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https:/
** Package changed: qemu-kvm (Ubuntu) => qemu (Ubuntu)
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
--
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/1408692
Title:
libv
** Summary changed:
- qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)
+ qcow2 image corruption on non-extent filesystems (ext3)
--
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/bu
> Finally, on my host I get:
> root@srv-Ub1404:~# ps -ef | grep dnsmasq
> lxc-dns+ 11309 1 0 Jan15 ?00:00:00 dnsmasq -u lxc-dnsmasq
> --strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --conf-file=
> --listen-address 10.0.3.1 --dhcp-range 10.0.1.2,10.0.1.254
>
** Package changed: php-ps (Ubuntu) => php5 (Ubuntu)
** Also affects: mysql-5.6 (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscri
Thanks for the update. I will mark this 'invalid' meaning "cannot be
reproduced now".
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs
On Fri, Jan 16, 2015 at 18:05:04 -, Ryan Tandy wrote:
> will no longer be used. But switching to nss-pam-ldapd is a good
> recommendation anyway, since the older modules are dead upstream.
(In fact there is discussion underway regarding downgrading libnss-ldap
and libpam-ldap out of main; see
** No longer affects: hundredpapercuts
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libpam-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1410195
Title:
Ctrl+Alt+F7 bypasses the light-locker lock-screen under XFCE
To manage noti
@Stephen,
I think you know why I stated that the ResourceDisk.Format variable is a
remarkable explanation for specific behaviour of waagent.
It must also be clear why I (also) stated that some parts of the waagent
script are rather obsolete or unnecessary.
A huge part of the waagent script can b
That's what I meant, on Ubuntu images the ResourceDisk.Format should be
"n" because cloud-init handles this. We do not want the Linux agent and
cloud-init fighting over formatting or reformatting, and then mounting
the resource disk.
You're right, perhaps these parameters should not exist in the
@Daniel,
I did all the testing before and came to the same result (as you are
probably aware of) BUT with a different CONCLUSION.
I personally concluded that the use of swap partitions, if ever
desirable, is (also) not desirable in the current case AND certainly not
on an ephemeral disk, given th
@Stephen,
The mount location CAN be changed by setting
- ResourceDisk.Format=y (instead of "n") AND
- ResourceDisk.MountPoint=/opt (or any other directory, instead of /mnt)
in waagent.conf.
The change becomes effective after a shutdown and start-up sequence (and
I assume the same applies to a n
This looks like the correct problem statement - the SCSI layer schedules
these tasks and so subtle timings could cause disk names to change.
This is also we recommend UUIDs or labels or similar to be used in
fstab.
The logic for DeviceForIdePort() is based on the fact that our vmbus
driver at leas
Might be related to bug 781737. pam-ldap/nss-ldap dropping privileges
is, AFAIK, caused by libgcrypt (bug 423252). If this is the same bug,
then the pending openldap merge (bug 1395098) will resolve it, as gcrypt
will no longer be used. But switching to nss-pam-ldapd is a good
recommendation anyway
** Changed in: libnss-ldap (Ubuntu)
Importance: Undecided => Critical
** Changed in: libnss-ldap (Ubuntu)
Status: New => Triaged
** Changed in: libpam-ldap (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team
Switching to libpam-ldapd and nslcd have fixed this issue. I've marked
this as an issue against libpam-ldap.
** Changed in: light-locker (Ubuntu)
Status: Confirmed => Invalid
** Changed in: openldap (Ubuntu)
Status: Confirmed => Invalid
** Changed in: policykit-1 (Ubuntu)
S
https://github.com/opscode-cookbooks/openldap/issues/44 <-- this has
been filed, as this is why we ended up with the outdated package
** Also affects: libnss-ldap (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server
This bug was fixed in the package cloud-initramfs-tools - 0.26ubuntu1
---
cloud-initramfs-tools (0.26ubuntu1) vivid; urgency=medium
* cloud-initramfs-dyn-netconf: support BOOTIF= that contains
upper case a-f.
* overlayroot: use required 'workdir' option on overlayfs mount for
OK, so passing a file containing the following as custom-data gives us a
swap partition and a mounted disk at /mnt:
#cloud-config
disk_setup:
ephemeral0:
table_type: mbr
layout: [[66, 82], 33]
overwrite: True
fs_setup:
- device: ephemeral0.1
filesystem: swap
** Branch linked: lp:~ubuntu-branches/ubuntu/vivid/cloud-initramfs-tools
/vivid-proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1411294
Title:
kernel panic dur
fix uploaded.
just for some more information, can fairly easily reproduce this bug using a
cloud image:
img_url="http://cloud-images.ubuntu.com/daily/server/vivid/current/vivid-server-cloudimg-amd64-disk1.img";
img_dl="${img_url##*/}"
Public bug reported:
msgpack-python version 0.4.4 is out on PyPI. Would you mind updating the
Ubuntu packages to 0.4.4?
(It would be great to see a newer version in Precise as well)
** Affects: msgpack-python (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug not
** Branch linked: lp:cloud-initramfs-tools
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1411294
Title:
kernel panic during MAAS fastpath install of Vivid images
To
@Daniel,
I just read your latest (two) posts, I was not able to read them while
commenting, my apologies.
The "makeswap" bug (when using partitions) is very different from the
"swap" bug and the "alias" bug.
In short:
- the "swap" bug can be resolved by sanitizing declarations of form [ swap, x
Daniel,
I was aware of DataSourceAzure.py and cc_mounts.py and the fact that
built-in config for Azure requires declaration of "sdb" (and not
"ephemeral0"). The before mentioned fact is only an inconvenience for
users that would like to declare custom mount points and make the
mistake to use an in
** Changed in: cloud-initramfs-tools (Ubuntu)
Status: Triaged => In Progress
** Changed in: cloud-initramfs-tools (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud
Try replacing pam-ldap/nss-ldap with nslcd and/or nssov and see if the
problem persists. I'd bet it doesn't. See here
https://bugs.launchpad.net/debian/+source/sudo/+bug/423252/comments/84
for reasons why you should have abandoned pam-ldap/nss-ldap years ago.
--
You received this bug notification
Actually, I've realised that I was passing in invalid cloud
configuration data. If I have the following in azure-disk.cfg:
#cloud-config
disk_setup:
ephemeral0:
table_type: mbr
layout: [66, 33]
overwrite: True
fs_setup:
- device: ephemeral0.1
filesystem: ext4
Uploaded to Trusty and Utopic with minor changes as discussed with Louis
on IRC.
Note that I've looked at the patches, but they're too in depth for me to
follow really. Superficially they look fine, and Debian have also
included them so they're in Vivid, and so I think this is sufficient
provided
** Description changed:
[SRU justification]
The version of the library in the archive for Utopic and Trusty has been
built prior to a change in glibc that removes an expected symbol. Rebuild of
the libnss-ldap library with the current source package will render the library
unusable and may
looks like I forgot to attach the trusty debdiff
** Patch added: "lp1387594_glibc_trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1387594/+attachment/4299974/+files/lp1387594_glibc_trusty.debdiff
--
You received this bug notification because you are a member of Ubu
Anything I can do to help this SRU along? This is affecting our Trusty
and Utopic boxes. Right now, I've manually pulled in a Vivid package so
I actually have working systems. It would be nice to get this into the
*-updates repos.
--
You received this bug notification because you are a member
trialotto, I've just been doing some testing, and I've realised my above
answer is incorrect; this is definitely a problem in how cloud-init's
Azure data source works.
I'm looking in to it now.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscri
** Changed in: qemu (Ubuntu)
Importance: Undecided => Medium
** 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/1411575
Title
Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=88492.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
Howard, It's having the usernames come from ldap, rather than the local
system, that causes policykit to have weird stuff happen, that causes
screen locking. It's all interconnected :)
The bug isn't in the parts individually, but in the integration of them
all.
** No longer affects: openldap
--
As I noted in our ITS#8025, this has nothing to do with upstream
OpenLDAP. It may be specific to the particular way you built OpenLDAP in
your distro, or it may be due to pam_ldap itself, but neither of these
are in the purview of the OpenLDAP Project. Certainly there is nothing
in vanilla OpenLDAP
Can;t seem to link the openldap bug, so
http://www.openldap.org/its/index.cgi/Incoming?id=8025
** Also affects: openldap
Importance: Undecided
Status: New
** Changed in: hundredpapercuts
Status: Incomplete => Confirmed
** Changed in: light-locker (Ubuntu)
Status: Incompl
The "T" argument is removed from the getopt argument, but the
corresponding ":" is not removed.
+Index: bsd-mailx-8.1.2-0.2006cvs/main.c
+===
+--- bsd-mailx-8.1.2-0.2006cvs.orig/main.c 2015-01-05 11:39:00.136339604
-0500
+++
** Bug watch added: freedesktop.org Bugzilla #88492
https://bugs.freedesktop.org/show_bug.cgi?id=88492
** Also affects: light-locker via
https://bugs.freedesktop.org/show_bug.cgi?id=88492
Importance: Unknown
Status: Unknown
** Project changed: light-locker => policykit-1
--
You
*** This bug is a duplicate of bug 1261873 ***
https://bugs.launchpad.net/bugs/1261873
Jiri Vanek (bin-0) , thank you!
> Replace the parameter "valid users" for just "users" don't use any
> more valid users on your
> configuration it will either deny access to Samba server or deny access
Public bug reported:
I have a server application that uses the command "mail -N". It has been
working in Ubuntu server for "I do not know how many years". After an
"apt-get dist-upgrade" yesterday this command broke. It now states that
an argument is needed.
$ mail -N
mail: option requires an arg
Hi trialotto,
cloud-init has default settings for Azure instances that ensure that the
first partition of the ephemeral disk is formatted as ext4. It does this
by providing default values for disk_setup and fs_setup; you can see
these at http://bazaar.launchpad.net/~cloud-init-dev/cloud-
init/trun
Steve,
I have just filed https://bugs.launchpad.net/ubuntu/+source/cloud-
init/+bug/1411582 regarding the inconstancy of device naming; could you
confirm that I've captured the issue accurately?
Thanks,
Dan
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
Currently we assume it will be /dev/sdb, but this may change. There is
an example of how to handle this in the Azure Linux agent.
To quote stevez in a comment on bug 1410835:
Device names are not persistent in Linux and could change, so it is not
guaranteed that the ephemera
You can however minimise the downtime:
Currently this happens:
prerm libvirt-bin -> stop libvirt
...
upgrade hundreds of packages
...
postinst libvirt-bin -> start libvirt
However using --restart-after-upgrade option should be feasible:
-R, --restart-after-upgrade
Do not stop t
Public bug reported:
There is a need to spin up an ESx host under KVM. We found that a patch
is needed, and there is a fix upstream. Actually this fix is on 2.2.0
version of qemu, but we need that backported to Trusty.
This link provides more information about it:
https://lists.gnu.org/archive/h
Error:
Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf',
'ip', 'netns', 'exec', 'qrouter-e8521385-ab12-4fbf-9e02-d1c9f43f0686', 'ipsec',
'whack', '--ctlbase',
'/var/lib/neutron/ipsec/e8521385-ab12-4fbf-9e02-d1c9f43f0686/var/run/pluto',
'--status']
Exit code: 1
Stdout
I'm hitting this on mailservers which runs with system wide umask of
007, set in /etc/profile.
After /etc/cron.daily/spamassassin has run, and the first email is
processed, amavis will shut down, since it cant' read
/var/lib/spamassassin/3.004000/updates_spamassassin_org.cf resulting in
an uppile
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: spamassassin (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to spamassassin in Ubuntu.
https://bugs.launchpad.n
76 matches
Mail list logo
