Hi,
I suspect this points to a problem in the packaging - the lxc1 package
should probably have a >= versioned dependency on lxc-templates. That
way, apt install -t backports lxc1 would have automatically upgraded
lxc-templates for you.
So I do think this is a real bug in trusty-backports.
The version you have of the other lxc templates is from backports, so
perhaps you need to manually request that?
apt install -t trusty-backports lxc-templates
or something. I never use backports, stgraber can probably help you, if
the above does not work.
--
You received this bug notification
Can you show the output of
dpkg -l | grep lxc
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590547
Title:
LXC package for trusty no longer has configuration files
To manage notifications
Reminder - see comment #40 for the proposed fix.
The pertinent question is, given that that is upstream, why is this
apparently not a problem for other systemd-based distros? How does it
work in Fedora?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: qemu (Ubuntu)
Status: New => Triaged
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589923
Title:
https
fwiw until this is fixed upstream, the workaround is 'find /
someregexp 2>/dev/null'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587688
Title:
cannot cd into /var/lib/lxcfs
To manage
The wily SRU has been waiting for validation for quite some time. I'm
wondering whether that is because noone is using wily, or because it's
not high priority?
The patch does not apply cleanly to trusty. In particular, the chunk in
./hw/net/vhost_net.c.rej is quite obsolete in the trusty
Thanks for reporting this bug. Unfortunately the failure message in the
dpkg terminal log is less than informative. Could you please try
sudo systemctl stop libvirt-bin
sudo systemctl start libvirt-bin
and show the results here?
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
Works for me, thanks. Marked as verified.
** 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/1579925
Title:
Sync irssi-plugin-xmpp
Thanks for reporting this bug. Could you please show the result of:
cat /etc/*-release
dpkg -l | egrep -e "(qemu|kvm)"
and show precisely how you tried to start up the failing vms?
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
Yes, I suppose xenial we could do right now, but I'm waiting on
another package to clear trusty-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571209
Title:
Sockfile check retries too
Hi,
IUC this is not a bug in libvirt or virt-manager or qemu. The problem
is that windows 7 does not ship with the needed qxl drivers. You need
to download those and install them in the windows 7 guest.
http://www.spice-space.org/download.html
--
You received this bug notification because
** 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/1393842
Title:
libvirt does not grant qemu-guest-agent channel perms
To manage notifications about this bug go
Wily is going to be EOL in less than two months. Could we please have a
minimal xml for reproduction, or even better verification of the package
in wily-proposed? I would simply recommend closing this bug unsolved,
except the fix is wrapped up with several others which were already verified.
--
With current trusty package I got the error popup as predicted.
After upgrading to -proposed and rebooting, it succeeded.
tag verification-done
untag verification-needed
done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, working on it for yakkety now.
** Changed in: libvirt (Ubuntu)
Assignee: Edward Hope-Morley (hopem) => Serge Hallyn (serge-hallyn)
** Changed in: libvirt (Ubuntu)
Status: Confirmed => In Progress
** Changed in: libvirt (Ubuntu Precise)
Importance: Undecided =
Public bug reported:
upgrading from trusty to xenial
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: uvtool-libvirt 0~bzr99-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-36.42~14.04.1-generic 4.2.8-ckt8
Uname: Linux 4.2.0-36-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture:
Excellent :)
** 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.
https://bugs.launchpad.net/bugs/1584157
Title:
Feature Request: setting a custom root directory
To manage
If you look at lxc.system.conf(5), there is 'lxc.lxc_path' which
equates to the -P lxcpath command line option.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584157
Title:
Feature Request: setting
Public bug reported:
During xenial cycle we applied a patch (and a followon fix for criu)
to fix a usability problem with cgroup namespaces and /proc/self/mountinfo.
Since then, the approach to fix it upstream has changed. Please revert
the two nsroot patches currently in xenial and yakkety,
The cloud archive is the generally recommended way to get newer
releases of libvirt (and other cloud software) in older supported
releases.
@jamespage may be able to tell you when a cloud archive for yakkety
will be set up for 16.04.
Note, there *is* a process for keeping software in sync across
You can use -P to set the container prefix path. Does that do what you
need?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584157
Title:
Feature Request: setting a custom root directory
To
1.3.4 is in yakkety. To get 1.3.3 into 16.04 would be a rather large
change to do in an SRU. I'm inclined to say 'no', but will leave this
open for others to consider.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Pushed a package to ppa:ubuntu-virt/ppa with the patchset.
** Summary changed:
- [FFE] Enable DDW on qemu aiming GPU passthrough performance on Ubuntu KVM
+ Enable DDW on qemu aiming GPU passthrough performance on Ubuntu KVM
--
You received this bug notification because you are a member of
Looks like you need fuse mounts in unprivileged containers - this is
what @sforshee is working on pushing upstream right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583765
Title:
Mounting
Hi,
I cannot reproduce this on xenial with
ii libvirt-bin 1.3.1-1ubuntu10amd64
programs for the libvirt library
Could you show the result of 'journalctl -u libvirt-bin' ?
On Thu, May 19, 2016 at 4:26 PM, David Shaughnessy
I can reproduce it with the package excerpts at
https://code.launchpad.net/~serge-hallyn/+git/pkg1
and
https://code.launchpad.net/~serge-hallyn/+git/pkg2
First
dpkg -i pkg1_1-1_amd64.deb
then
dpkg -i pkg1_1-2_amd64.deb pkg2_1-2_amd64.deb
On yakkety, this gives me:
(Reading
Could you please show the contents of your
/etc/libvirt/qemu/networks/default.xml
file?
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
could you please show your
/etc/libvirt/qemu/networks.default.xml
contents?
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libvirt (Ubuntu)
Status: New => Triaged
** Changed in: libvirt (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582992
Title:
broken
Please do let us know whether the recommendation in comment #2 solved
the problem for you.
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
procps has a patch to sysctl.c to ignore EACCESS. I guess systemd's
systemd-sysctl needs the same kind of patch.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxd (Ubuntu)
Status: Confirmed => Invalid
** Changed in: systemd (Ubuntu)
Ah, I'm sorry, I'd misread your info.
Your container is being started just fine, and has its own devices
cgroup.
What's actually happening is that the container is not allowed to
*reset* its devices cgroup. That is because lxc has set some device
cgroup limits, and the kernel is rightly
I'm going to mark this invalid as I believe it's a non-issue. We may
want lxc and systemd to cooperate more to maximize the protection of
containerized services, though.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
On plain xenial, containers which I start as root get:
sudo lxc-info -H -p -n u1
18144
ubuntu@privlxc:~$ cat /proc/18144/cgroup
11:perf_event:/lxc/u1
10:devices:/lxc/u1/init.scope
9:hugetlb:/lxc/u1
8:memory:/lxc/u1
7:blkio:/lxc/u1
6:net_cls,net_prio:/lxc/u1
5:freezer:/lxc/u1
4:cpu,cpuacct:/lxc/u1
Thanks for reporting this bug.
Could you please show the precise Ubuntu release and lxc version?
cat /etc/*-release
dpkg -l | grep lxc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582364
Title:
Did you do
sudo modprobe nbd
first?
** Changed in: qemu (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1542509
Title:
Could you show the .xml for the two vms you are trying to start? One
thing I'm wondering is whether this has to do with the mac entries in
your network default.xml. Do the two vms by chance list the same
macaddr?
Please show 'journalctl -u libvirt-bin' output, and append the
Please show the output of the two commands shown in the log message.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528136
Title:
[1.2.16] Failed to initialize KVM & other internal errors
To
No, now I have reproduced it:
Adding user `libvirt-qemu' to group `libvirt-qemu' ...
Adding user libvirt-qemu to group libvirt-qemu
Done.
Failed to execute operation: No such file or directory
/usr/bin/deb-systemd-helper: error: systemctl preset failed on
libvirtd.service: No such file or
No that seems to be the entirely wrong patchset.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1541902
Title:
[FFE] Enable DDW on qemu aiming GPU passthrough performance on Ubuntu
KVM
To manage
Happy to. I'll take the patchset from May 11,
Subject: [Qemu-devel] [for-2.7 PATCH v3 00/15] Core based CPU hotplug
for PowerPC sPAPR
Please shout if that is not the best one to use.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks, Ryan. We'll hold off until the next round.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1541902
Title:
[FFE] Enable DDW on qemu aiming GPU passthrough performance on Ubuntu
KVM
To
This is also showing up in other places, including a java app called
Maven
https://github.com/lxc/lxc/issues/1023
** Changed in: apparmor (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Seems like the upstream discussion is still unresolved in some areas
(and no patches are upstream in the git tree) and I don't understand
why.
I'm happy to pull these patches in now. Just as a sanity check,
@rharper - any definite badness that you see?
--
You received this bug notification
(Make that @raharper ^ )
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1541902
Title:
[FFE] Enable DDW on qemu aiming GPU passthrough performance on Ubuntu
KVM
To manage notifications about this
(so this probably should be marked invalid as cannot-be-reproduced, but
i'll leave it to a maintainer to do that in case this bug points to
something which still ought to be fixed)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hm, at this point this doesn't seem to be reproducing any more. Without
any changes to either init-system-helpers or libvirt. Only upgraded
packages are:
libpython3.5-minimal/yakkety 3.5.1-12 amd64 [upgradable from: 3.5.1-11]
libpython3.5-stdlib/yakkety 3.5.1-12 amd64 [upgradable from:
That (effective_cpus) *should* be fixed in the daily ppa by a patch on
Apr 26: "cpuset: fall back to cpuset.cpus on older kernels"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579786
Title:
Public bug reported:
This is a bit of a special case and may be being done wrong by the
package... libvirt is moving the libvirt-bin.service from libvirt-bin
package to libvirtd.service in libvirt-daemon-system package. The
packaging source can be seen at https://git.launchpad.net/~libvirt-
Hi,
does 'sudo lsof' show any results for those files?
If not, I guess try simply moving them:
sudo mv /etc/group+ /etc/group+.bak
sudo mv /etc/group- /etc/group-.bak
sudo mv /etc/gshadow- /etc/gshadow-.bak
--
You received this bug notification because you are a member
So this seems like a dup of bug 1240757. As noted there the correct answer
appears to be to implement .d directory support in bind9.
Should we mark this a dup of that and mark it as affecting lxd?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for that info. The group file looks fine. Could you please
check whether either
/etc/group.lock
or
/etc/gshadow.lock
exists? If so, please remove them and re-try. If not, please let us
know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Completed by doko.
** Changed in: libvirt (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508614
Title:
Build with multiarch support
To manage
Thanks for taking the time to reproduce this bug. I unfortunately have
not been able to reproduce it.
Could you please show the contents of /etc/apt/sources.list and any
files under /etc/apt/sources.list.d/ ?
It seems 'groupadd' actually failed, so please show the contents of the
file
> My advice would be to leave the cgmanager portion as Incomplete until
> someone can come up with repo steps, but unfortunately I don't have
> those. Just some ideas.
Yup let's do that - thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thanks - this is fixed upstream, probably by
commit fb5ab35bfae46f75e988df28da1edce8cbb5f27c
Author: Christian Brauner
Date: Mon Apr 11 17:13:16 2016 +0200
lxc-create: fix -B best option
Until that is merged and SRUd, you can get the fix from ppa:ubuntu-
Hi - could you show the result of
ls -l /dev/kmsg
in the container?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572061
Title:
login sessions hangs in lxc
To manage notifications about this
@ted,
regarding comment #69, if "cgmanager somehow got disabled" that is
different from "cgmanager was installed but not enabled by default."
The latter shouldn't happen and would be a bug, the former would be an
invalid bug.
Regarding later comments, indeed cgmanager and libpam-cgfs are not
Please provide precise reproduction steps to get cgmanager installed but
not enabled.
** Changed in: cgmanager (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, Debian has not yet made this change for libvirt. It was done
in 1.3.1-1ubuntu1 . We've not yet submitted a patch to Debian, but
I'll be doing so soon as I'm working on syncing the packaging.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Quoting jean-christophe manciot (manciot.jeanchristo...@gmail.com):
> Alas! Someone in Canonical decided to change that and now the libraries have
> moved to a different folder:
> dpkg --contents libvirt0_1.3.1-1ubuntu10_amd64.deb | grep so
> -rw-r--r-- root/root 10168 2016-04-15 09:15
>
Quoting Martin Pitt (martin.p...@ubuntu.com):
> So would a namespace aware check for CAP_SYS_AUDIT say "no" then? (The
> audit subsystem isn't namespace aware right now). How would such a check
> look like in userspace?
I suppose a namespace aware check for CAP_SYS_AUDIT would look like an
fcntl
Right you can check whether you have CAP_X targeted at your own user ns,
and you can check whether you are in an init_user_ns (by checking
/proc/self/uid_map). The manpages currently are rarely clear, when they
say you need CAP_X, about which namespace that must be targeted against.
(I just
Hi,
thanks again for reporting this. I simply cannot reproduce this and haven't
found any likely cause. If you can reliably reproduce this in some sort
of cloud instance, i.e. so we could start a digitalocean or amazon instance
with a cloud-init script to set up a bad container, that would be
So given the upstream feedback i will remove the Notify line, and we'll
see if we get any other separate reports. Given comment #11 I've marked
this invallid.
** Changed in: libvirt (Ubuntu)
Status: Fix Released => Invalid
--
You received this bug notification because you are a member
Quoting Martin Pitt (martin.p...@ubuntu.com):
> For the record,
> https://cgit.freedesktop.org/systemd/systemd/commit/?id=da13d4d was
> fixed in 209 already, thus in ≥ vivid. NotifyAccess=all sounds like the
> right solution if child processes from the main process want to send
> "ready" signals
Confirmed this works for me in xenial.
Two notes on the test case in description: 1. cgroup namespaces must be
disabled (in the kernel or in lxc) to reproduce this issue. I'd
forgotten about that, and it seems to change the priority of this for
xenial. 2. the test case must be done using lxc,
This is not a lxd bug. You need the docker source as is packaged in
16.04. To run that in a 14.04 container, you might be able to build
the 16.04 package in a ppa for 14.04, but I've not tried it. Marking
this as affecting docker.io
status invalid
affects docker.io
** Changed in: lxd
Hi,
I'll just drop it to 1s, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571209
Title:
Sockfile check retries too short for a busy system boot
To manage notifications about this bug go
If you have reproduced this recently, please show us exactly how
and on what version of lxc. This should have been fixed as of commits
3b392519: lxcapi_clone: restore the unexpanded config len
and
5eea90e8: clone: clear the rootfs out of unexpanded config
for github issue 694.
status
Can you show the contents of the container's /etc/hosts? Does adding an
entry for
127.0.0.1 kjell
help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572061
Title:
login sessions hangs in lxc
Odd, I wonder why you are getting the re-exec requires full path error,
as execve is clearly getting a full path.
So it seems like an sshd bug, let's see when we get the un-cut strace.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** No longer affects: lxcfs (Ubuntu Wily)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574765
Title:
Newer systemd fails to start due to EINVAL on access to
/sys/fs/cgroup/systemd
To manage
Hi,
just to make sure, did you do a
sudo systemctl daemon-reload
before restarting?
Could you please show the result of:
ps -ef | grep libvirt
sudo systemctl stop libvirt-bin
sudo systemctl start libvirt-bin
sudo journalctl -xe
sudo journalctl -u libvirt-bin
sudo libvirtd
--
You received
** Also affects: lxcfs (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: lxcfs (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
==
Test case:
lxc launch images:debian/jessie/amd64 j1
lxc exec j1
sleep 30s; ps -ef
If you only see 3 tasks, then systemd has failed to properly start. With
the access(2) patches this should be fixed.
Heh.
So the importance of this patch is underscored by the fact that this has
basically turned every 'start libvirt-bin' into a sleep 2s.
So I guess we should drop the number. Or perhaps we should increment the
sleep time on every iteration? start at 0.5 second and go up to a 2s sleep
at the
Thanks, but actually the systemd.service(5) manpage tells me what I
needed.
The fix for you should be to edit your /lib/systemd/system/libvirt-
bin.service file to read:
[Unit]
Description=Virtualization daemon
Before=libvirt-guests.service
** Also affects: libvirt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Precise)
Apr 25 12:38:11 hostname systemd[1]: libvirt-bin.service: Got notification
message from PID 103
8, but reception only permitted for main PID 1003
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574566
Do we need to add NotifyAccess=all to the systemd job?
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Red Hat Bugzilla #1047304
https://bugzilla.redhat.com/show_bug.cgi?id=1047304
--
You received this bug notification because you are a
(After some googling I'm not sure whether this should be considered a
bug in the libvirt-bin upstart job, or a bug in systemd.
https://bugzilla.redhat.com/show_bug.cgi?id=1047304 suggests it may be a
systemd bug. Subscribing systemd to get some professional help :)
--
You received this bug
Apr 25 12:44:52 hostname libvirtd[18673]: Failed to acquire pid file
'/var/run/libvirtd.pid': Resource temporarily unavailable
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574566
Title:
package
Public bug reported:
During reporting of a separate bug (1574566), the following was seen:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line
It might help if you can show a ps -ef and screenshot of top while it is
hanging, or even better yet an strace -f of the sshd. One somewhat
common cause of such hangs is /etc/hosts in the container not having an
entry for the localhost.
** Changed in: lxc (Ubuntu)
Importance: Undecided =>
Thanks - that will need to be synced to ubuntu and the MIRd (depending
on how exactly it is needed).
** 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.
Hi,
when I simply do
sudo lxc-create -t download -n kjell -B zfs -- -d debian -r jessie -a
amd64
the resulting container works for me. I can apt-get install openssh-
server and log in. However, your configuration file shows 'br0' is in
use. Please show how br0 is configured on the host.
** Summary changed:
- [FFE] support query-gic-version QMP command
+ support query-gic-version QMP command
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566564
Title:
support query-gic-version QMP
** Also affects: libvirt (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/1561019
Title:
copied cpu flags don't match host cpu
To manage
Thanks, Stefan!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561019
Title:
copied cpu flags don't match host cpu
To manage notifications about this bug go to:
Please show us the exact commands you used to create, start, and log
into the container, as well as the container configuration file.
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Can you confirm that this still happens with ppa:ubuntu-lxc/daily?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567037
Title:
lxc-attach crashed with SIGSEGV in get_pty_on_host()
To manage
If this happens again (with the same error message, "error calling
aa_change_profile"), please check for any relevant messages in the audit
log (/var/log/audit/auditd.log) or the syslog (if auditd is not
installed).
That error means that the profile was in fact created, because we got
this far.
Quoting guessi (gue...@gmail.com):
> @serge,
>
> no, I don't,
> it's simply shortened the waiting time for service back or down.
Ok - the shorter time itself is probably fine, but printing a
message every 0.2 seconds seemed a bit much. On the other
hand I don't want to complicate the logic to
** 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.
https://bugs.launchpad.net/bugs/1441971
Title:
qemu-system-x86_64 crashed with SIGSEGV
To manage notifications about
** Also affects: qemu
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: New => Triaged
** Changed in: qemu (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ok so the patch which made this change can't be reverted bc there's been
a lot of churn, but the effective equivalent of this would be to remove
the svm line in:
static void pc_compat_2_1(MachineState *machine)
{
pc_compat_2_2(machine);
x86_cpu_change_kvm_default("svm", NULL);
}
--
You
Thanks, @guessi, that patch looks great. The only thing i wonder is
whether sleep 0.5s is a bit too short. I assume you had a rationale for
shortening the sleep time?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please reply if that does solve your problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572288
Title:
Can't upgrade qemu-system-misc
To manage notifications about this bug go to:
201 - 300 of 15549 matches
Mail list logo