Public bug reported:
I have a thinkpad t440s. When running the 4.4 kernel, all is fine.
Under the 4.8 hwe kernel, every few minutes the screen will flicker
once. It's quite unsettling. I see nothing relevant in syslog.
** Affects: linux-meta-hwe (Ubuntu)
Importance: Undecided
@mattofak - thanks for filing the bug. I've linked it to the manpage
project. It'll get fixed.
** Also affects: ubuntu-manpage-repository
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Note, the actual manpage makes no mention of the package. Which is
how it should be, as the manpage comes from upstream and not from
Ubuntu.
So if this is a bug, it is a bug against manpages.ubuntu.com.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1696989 ***
https://bugs.launchpad.net/bugs/1696989
Thanks for reporting this bug. This appears to be a duplicate of
1696989, which I'd say also confirms it.
Could you show the result of
cat /etc/*-release
?
** This bug has been marked a duplicate of bug
Hi,
thanks for taking the time to report this bug.
This actually appears to be a problem not in libpam-cgfs itself:
Setting up libpam-cgfs (2.0.7-0ubuntu1~17.04.1) ...
Use of uninitialized value $reply in scalar chomp at
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.
I'm going to
Note, I'm happy to update a fix for this for a (and a -proposed one
for xenial).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1695808
Title:
tasks killed for nop (-1)
To manage notifications
Public bug reported:
As the seccomp manpage points out, after seeing a SECCOMP_RET_TRACE, a
tracer can set nr to -1 to skip the syscall. Similarly, one task could
be debugging another seccomp'd task, simply doing PTRACE_SYSCALL without
using SECCOMP_PTRACE, and want to make the tracee skip a
Thanks for filing, Radu.
The commit which fixed it is in this PR:
https://github.com/shadow-maint/shadow/pull/72
(wget https://github.com/shadow-maint/shadow/pull/72.patch)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@bryanquigley - no. i had opened one for networkmanager (or planned on
it, don't remember how far i got), but in the end to provide meaningful
details i'd have to *run* it. Stop trying to get me to run it. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@bryanquigley that's an odd non-sequitur. I'm avoiding switching to
systemd (in part for power usage), and cgroupfs-mount is not the thing
being removed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I don't expect upstart to be supported, but it would be nice to keep it
in universe.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649310
Title:
RM Upstart, obsolete, superseded by systemd
To
Serge Hallyn
DL 20794613
512-534-8891
I'd like to schedule a drivers test for non-CDL class B license if
possible during the afternoon on Friday, May 5.
sincerely,
Serge Hallyn
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
I'm concerned about upstart in particular. Indeed cgmanager is
unsupported. I'm using upstart with cgroupfs-mount.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649310
Title:
RM Upstart,
(and with that, i'll be needing a new distro :( )
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649310
Title:
RM Upstart, obsolete, superseeded by systemd
To manage notifications about this bug
Note, the last I heard it was not deprecated by *upstream*, but by
redhat.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680997
Title:
Container file system corruption on libvirtd restart
To
Hi,
this would be deemed a high priority bug for upstream libvirt, but
Ubuntu has always, back to 2010, supported lxc, then lxd, instead of
libvirt-lxc. (So it's not that libvirt-lxc is deprecated, rather it was
never supported in Ubuntu)
Which version of Ubuntu are you using?
Can you reliably
*** This bug is a duplicate of bug 1667113 ***
https://bugs.launchpad.net/bugs/1667113
** This bug has been marked a duplicate of bug 1667113
System users appears in Ligthdm and user switcher (Accountsservice has no
filter for shell types)
--
You received this bug notification because
Thanks, Nish. My thoughts:
1.a sounds good
1.b i'd like another way to do that, but not sure what a better way would
be.
1.c does lvm also fail in privileged containers? I can see no use to
running it (for now) in an unprivileged container, so the same solution
as 1.a seems reasonable.
1.d
Sorry, this got lost in my inbox. I used dput. I seemed to recall that
in some recent cycle the it became either ok or preferred to use
$release-updates instead of $release-proposed in SRUs. I can trivially
change it ack to yakkety-proposed if preferred.
For Trusty, I just noticed that the
Ye,s we should SRU to that, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1534090
Title:
'call to get_tasks_recursive failed' errors from su
To manage notifications about this bug go to:
Thanks for looking. I'll push that tonight.
Original Message
From: Cam Cope
Sent: Monday, March 6, 2017 3:50 PM
To: serge.hal...@gmail.com
Reply To: Bug 1668724
Subject: [Bug 1668724] Re: fails to mount cgroupfs inside containers running on
16.04
LGTM
--
You received this bug
(s@/tmp/2@/proc/cgroups@ of course)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668724
Title:
fails to mount cgroupfs inside containers running on 16.04
To manage notifications about this bug
FWIW something like:
for d in `tail -n +2 /tmp/2 | awk '{
if ($2 == 0)
print $1
else if (a[$2])
a[$2] = a[$2]","$1
else
a[$2]=$1
};END{
for(i in a) {
print a[i]
}
}'`; do
mkdir -p
There is a bug (which is fixed in newer versions) in lxc in that it does
not ignore cgroups which are not used by the container. So in your
particular case, if you're not using the co-mounted controllers, then
indeed fixing the lxc bug should work for you as well.
Nevertheless some people will
This bug incidentally also affects the cgroupfs-mount package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668724
Title:
fails to mount cgroupfs inside containers running on 16.04
To manage
(Note - this means the patch I just pushed to zesty is in fact wrong.
Since zesty requires systemd this doesn't really matter, but we must get
a working patch before pushing SRU patches)
@ccope, please let me know if you care to write an update patch.
--
You received this bug notification
Hm, yes i see (hierarchy 0). I do worry that means that systems with
the unified hierarchy will be still more of a problem, since it is
mounted as hierarchy 0. But then it's probably fine to just say that
cgroup-lite doesn't support unified hierarchy.
--
You received this bug notification
** Also affects: cgroup-lite (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: cgroup-lite (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: cgroup-lite (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects:
I assume /sys/fs/cgroup/systemd was used because that's where systemd
expected to see it. I can't find any version which mounts it at
/sys/fs/cgroup/name=systemd - do you have a version that does that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for the patches. Note that you've changed the loop variable from
d to c, but the loop is still using d, so nothing gets mounted with that
patch verbatim. Switching the variable back to d fixes the issue for
me.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: cgroup-lite (Ubuntu)
Importance: Undecided => High
** Changed in: cgroup-lite (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668724
Title:
Note vmbuilder is set to be forked soon so it may have a future after
all
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1260062
Title:
Please remove vmbuilder from the archive in 14.04
To manage
Seems like just adding
ConditionVirtualization=!container
to debian//open-iscsi.service should fix it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576341
Title:
fails in lxd container
To
Thanks I've created https://github.com/lxc/lxcfs/issues/164 to track
this.
** Bug watch added: LXCFS bug tracker #164
https://github.com/lxc/lxcfs/issues/164
** Changed in: lxcfs (Ubuntu)
Importance: Undecided => Medium
** Changed in: lxcfs (Ubuntu)
Status: New => Triaged
--
You
Just re-tested. The z kernel builds fine. the yakkety-proposed kernel
still fails to build:
cc1: fatal error:
/home/ubuntu/linux-4.8.0/ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h:
No such file or directory
compilation terminated.
--
You received this bug notification because you
Hi,
we try to keep spice in sync with Debian. Can you open a debian
bug requesting a newer version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645838
Title:
spice is not built for arm64
To
Quoting Robie Basak (1641...@bugs.launchpad.net):
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
>
> It looks like libvirtd was not running at the time of an upgrade, and
> this caused uvtool-libvirt's postinst to fail. So this is a libvirt bug,
> not a
** Tags added: bot-stop-nagging
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641168
Title:
packaging error in yakkety kernel
Public bug reported:
When I try to build the kernel source from yakkety-updates locally, I
get failure like:
cc1: fatal error:
/home/ubuntu/linux-4.8.0/ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h:
No such file or directory
** Affects: linux (Ubuntu)
Importance: Undecided
This is related to the other open bugs caused by systemd starting to
mount the unified hierarchy. There had been a branch of cgmanager able
to handle unified, around June 2015, but it was only experimental.
Does unity still require cgmanager? Note that cgmanager's deprecation
Hi Christian,
just for future references, it's of course ideal if we can verify that
the reported bug is fixed, but after 14-21 days it becomes ok to
simply run the qa-regression-tests and verify that there are no new
failures. Whether or not to drop the set if we can't verify the
original bug
Verified, thanks.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631996
Title:
syntax error: EEXISTS should be EEXIST
To
** Description changed:
https://github.com/ansible/ansible-modules-core/issues/2585
This is fixed in yakkety but broken in xenial. The single-line fix
should be SRU'd.
+
+ Impact: when the file module fails, ansible fails trying to report the erorr
message.
+ Test case:
+ ansible
Public bug reported:
https://github.com/ansible/ansible-modules-core/issues/2585
This is fixed in yakkety but broken in xenial. The single-line fix
should be SRU'd.
** Affects: ansible (Ubuntu)
Importance: High
Status: Fix Released
** Affects: ansible (Ubuntu Xenial)
Ubuntu follows Debian as much as possible, and Debian does not yet have a
2.7 package. We'll merge it as soon as it does. We can merge upstream
directly if urgent, but that ends up complicating future merges.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi,
how can we reproduce this? Can you give a precise set of steps to
download/build an image and run qemu with it?
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Could you build qemu from upstream git and run that under gdb to
reproduce and get a full stack trace?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630226
Title:
segfault in qemu-system-x86_64
There appears to be a init configuration error:
insserv: warning: script 'K07smfpd' missing LSB tags and overrides
insserv: warning: script 'smfpd' missing LSB tags and overrides
insserv: warning: script 'ccpd' missing LSB tags and overrides
insserv: There is a loop between service smfpd and
You might ask on #virt for the opinion there, but I don't believe
migrating backward is supported in any case. t->x->t doesn't change
the fact that there is x->t.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Migrating a VM from xenial -> trusty (or anything moving backward) is
not supported.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536487
Title:
Unable to migrate pc-i440fx-2.4 KVM guest from QEMU
virt-install is one alternative. Using cloud images with cloud-init is
another.
Note that if there is interest by community members in maintaining
vmbuilder, that would be very welcome.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Awesome - thanks Christian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621042
Title:
qemu machine types broken in wily and missed to be updated in xenial
and yakkety
To manage notifications
To $(clarify or argue :),
A xenial machine type should indeed be defined based on the newest
mt available in xenial, and SRU'd to xenial. A yakkety type should
probably be defined at the end of the y cycle, and obviously not
SRUd.
Thanks.
--
You received this bug notification because you are
The intent is to update qemu as soon as it hits debian.
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
** Changed in: qemu (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please open a new bug - thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448269
Title:
qemu guest hangs on nested kvm startup with host kernel oops
To manage notifications about this bug go
Please give the output of:
which qemu
dpkg -l | egrep -e "(qemu|kvm)"
cat /etc/*-release
** Changed in: qemu-kvm (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On precise, use the qemu-kvm-spice package.
** Changed in: qemu-kvm (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/939437
Title:
spice is not supported by
You do not show a 'lxc-start' command. You do need to manually start
the container before you can attach to it.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Seems safe to assume this must be fixed by now, please ping if it is
still happening.
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looking at the contents of those files, I think giving libvirt vms read
access by default to all of them should be safe.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1610368
Title:
2016-08-01 11:20:22,446 DEBUG failed to SystemUnLock() (E:ロックされていません)
2016-08-01 11:44:18,624 ERROR got an error from dpkg for pkg: 'initscripts':
'conffile プロンプトでの標準入力にファイル終端があります'
2016-08-01 11:44:18,625 DEBUG running apport_pkgfailure() initscripts: conffile
プロンプトでの標準入力にファイル終端があります
2016-08-01
Thanks for reporting this bug. The error log doesn't really make sense
to me:
libpolkit-backend-1-0:amd64 (0.105-14.1) を設定しています ...
cgmanager (0.39-2ubuntu5) を設定しています ...
insserv: Service mountkernfs has to be enabled to start service cgmanager
insserv: exiting now!
update-rc.d: error: insserv
Can you please show by hand the results of
uname -a
cat /etc/*-release
dpkg -l | grep qemu
sudo apt install qemu-user-static
and attach the contents of /var/log/apt/term.log ?
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
I don't use unity - is this now the default?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/684431
Title:
hard to get to terminal menubar when not full-screened
To manage notifications about this
Indeed, that (-d) is a difference in how the upstart and systemctl
jobs expect to function. The upstart job was 'expect daemon' and
specifies -d in the upstart job itself (not in
/etc/default/libvirt-bin)
Assuming Ubuntu doesn't drop the upstart job altogether (which would
be a problem for me)
Here's where I'm happy to be using a custom /etc/acpi based lock trigger
(using slock).
I'd have to agree with Phil, this bug seems worse. Having to manually
lock my screen and verify that it worked before suspending every time
would be unacceptable to me.
--
You received this bug notification
** Changed in: libvirt (Ubuntu)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565424
Title:
libvirtd crashed with SIGSEGV in _int_malloc()
To manage
Thanks for the information. In the past, we've provided upgrade scripts
when problems developed with older machine types, but 0.11 is old enough
that it probably isn't worth it.
** Changed in: qemu-kvm (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you
Gotcha, thanks. (I'm not using unity so haven't seen this re-appear.
Though I also don't recall it ever having been fixed)
\o
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734908
Title:
Unity is
Interesting wording, "you need to" - does that mean this bug should be
marked wontfix or opinion?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734908
Title:
Unity is visible on top of fullscreen
Thanks for the info.
If updating kernels fixes it, then it's possible, but unlikely, that it
can be fixed in userspace. Marking this as affecting the kernel.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
I'm sorry, I'm as context-swapped as you are... can you remind me why
it is needed, versus simply having libpam-cgfs setup to give you cgroups
upon login?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Quoting David Planella (david.plane...@ubuntu.com):
> In my case it's disabled, but even after enabling it manually, I'm
> getting the same errors that I had a few months back:
>
> "cgmanager:do_create_main: pid 2118 (uid 1000 gid 1000) may not create
> under /run/cgmanager/fs/freezer"
This
Why is it being *dis*abled? it's not needed, but it's also not in the
way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535058
Title:
applications close instantly when launched from the launcher
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602443
Title:
Bad page state in qemu-system-x86 process
To manage
Awesome- thanks for verifying
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297218
Title:
guest hangs after live migration due to tsc jump
To manage
We will follow when debian gets 2.7. Note that 2.7 does not currently
exist.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1599607
Title:
[Feature] UbuntuKVM: Update QEMU to version to 2.7
To
No, I'm afraid not. But if you can test when this package is accepted
into trusty-proposed that'll be great.
** Description changed:
+ =
+ SRU Justification:
+ 1. Impact: guests hang after live migration with 100% cpu
+ 2. Upstream fix: a set of four patches
Conflicting experimental packages in that ppa, trying ubuntu-virt/ppa
instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297218
Title:
guest hangs after live migration due to tsc jump
To
Thank you. I'm doing a test build in ppa:serge-hallyn/virt, and will
run a full regression test from there. I'll push for SRU if that
passes.
Would you mind putting in the bug Description (at top) a concise summary
of the test case, for the SRU process?
--
You received this bug notification
I'm confused as to why you reported this bug against lxc in ubuntu.
Were you running vagrant+virtualbox inside an ubuntu lxc container?
** Package changed: lxc (Ubuntu) => cloud-images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Package changed: libvirt (Ubuntu) => virtinst (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597610
Title:
virt-install default to virtio type - disk and network
To manage
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to convert raw->VHD (fixed) adds
*** This bug is a duplicate of bug 1490611 ***
https://bugs.launchpad.net/bugs/1490611
WOuld be nice to have, however vpc.c seems to have changed quite a bit
already and the patch does not apply cleanly. If someone can backport
the patch I will put it up for sru testing.
I'm going to mark
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to convert raw->VHD (fixed) adds extra
How do you figure verification needed? See comment #3.
** Tags removed: verification-needed-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584163
Title:
cgroup namespace update
To manage
See
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1297218/+attachment/4301780/+files/backport.patch
referenced in comment #29
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297218
Title:
@Steve,
it seems to me those are the same as the 'backport.patch' from an
earlier comment?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297218
Title:
guest hangs after live migration due to tsc
Hi,
Looking at the dpkg terminal log, this does not appear to be a qemu
issue:
Setting up qemu-block-extra:amd64 (1:2.5+dfsg-5ubuntu10.2) ...
Setting up qemu-system-common (1:2.5+dfsg-5ubuntu10.2) ...
insserv: warning: script 'K01smfpd' missing LSB tags and overrides
insserv: warning: script
*** This bug is a duplicate of bug 1591724 ***
https://bugs.launchpad.net/bugs/1591724
Thanks - so it's fixed upstream and in ubuntu yakkety. I'll mark it as
a dup of bug 1591724.
** Changed in: qemu (Ubuntu)
Status: Confirmed => Fix Released
** This bug has been marked a duplicate
Thanks.
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585008
Title:
Windows 7 guests hang on bootup when qxl video is used
To
@Anthony - are you saying this affects you under Arch? (If so I'll mark
it as affecting upstream qemu project)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585008
Title:
Windows 7 guests hang on
I recommend opening new bugs against libvirt and docker. Libvirt moves
VMS into a cpuset by default. I assume docker does the same. (My
xenial laptop runs upstart, so this is not systemd's doing)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi,
no, thanks, actually since this fix patches virt-aa-helper itself, just
creating a new vm after the upgrade should have sufficed. No reboot
should have been needed. However trying to start a pre-existing vm that
previously failed would not work, as the policy needs to be re-
generated.
Did you reboot the system after the upgrade?
(restarting apparmor should suffice, but since this package fixed it for
me I'd like to make sure about whether the core fix failed for you, or
just the upgrade experience)
--
You received this bug notification because you are a member of Ubuntu
"LXC cases, like docker and KVM" - did you mean non-lxc cases?
xenial by default should now be using libpam-cgfs, should not be using
cgmanager, and should not be creating cpusets.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With xenial kernel:
132 125 0:57 /lxc/x1 /sys/fs/cgroup/blkio
rw,nosuid,nodev,noexec,relatime - cgroup cgroup rw,blkio,nsroot=/lxc/x1
with xenial-proposed kernel:
134 125 0:59 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime -
cgroup cgroup rw,blkio
** Tags removed:
Thanks - confirmed the packages are identical except for changelog,
ubuntu-maintainers, and diff context dates.
** Changed in: spice (Ubuntu)
Status: New => Triaged
** Changed in: spice (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are
I've enabled ppc64le builds for that ppa. Hopefully it proceeds to
automatically build the packages now, though I suspect the pkgs will
need to be re-pushed.
On Fri, Jun 10, 2016 at 5:14 PM, Breno Leitão
<1541...@bugs.launchpad.net> wrote:
> Hi Jon, Serge,
>
> I think the PPA is somehow
Public bug reported:
I'm dropping unity/gnome stuff from my desktop, but as I was trying
sudo apt purge yelp
it wanted to delete pasaffe. Please make that not a hard depends :)
Thanks!
** Affects: pasaffe (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
101 - 200 of 15549 matches
Mail list logo
