[Bug 1424780] Re: iscsitarget crash in 3.19 backport
This should be resolved long by now. Though I cannot remember how and when exactly. ** Changed in: iscsitarget (Ubuntu) Status: In Progress => Fix Released ** Changed in: iscsitarget (Ubuntu) Assignee: Stefan Bader (smb) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1424780 Title: iscsitarget crash in 3.19 backport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1424780/+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 1551351] Re: dhclient does not renew leases
We have some testing packages that can be obtained by adding Lamont's PPA (sudo apt-add-ppa ppa:lamont/ppa). From local testing this looks to be solving at least the lease renewals. At least for me a normal kill still seems not enough to end the dhclient daemon. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1551351 Title: dhclient does not renew leases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1551351/+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 1546978] Re: apparmor does not allow to run qemu-dm executable
I guess as the binary is still there it has to be enabled in apparmor. Though on the other hand, qemu-dm is the old device-model which would/should only be used when the old xm/xend toolstack is used. And Trusty was the last release that had that code in at all and I tried hard to get users switched over to xl/libxl (which would use the standard qemu-system-i386 instead). So I am maybe a little hesitant here... ** Changed in: libvirt (Ubuntu) Status: New => Invalid ** Changed in: libvirt (Ubuntu Trusty) Status: New => Confirmed ** Changed in: libvirt (Ubuntu Trusty) Importance: Undecided => Medium -- 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/1546978 Title: apparmor does not allow to run qemu-dm executable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1546978/+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 1551351] Re: dhclient does not renew leases
I believe I got a vague feeling about what is going wrong. So the isc library which now is shared for bind9 and dhcp is compiled (because bind9 is rather wanted that way) with threads enabled. Before that the export version of the library was not. So an isc_app which dhclient creates and runs was more or less a loop handling events. Now this creates a series of threads. The problem looks to be that dhclient (and probably dhcpd, too) set up the isc_app context and then do a fork() (in daemon mode). The man page of fork() clearly states that the child will be single threaded. So when dhclient calls dispatch() to run the isc_app this probably only runs a single control loop more or less waiting for the threads (which do not run, maybe not even exist anymore) to do the work. The signal handling might be related to that as well. With threads only one of them should handle signals and somehow synchronize with the rest. Maybe the new library is not handling that correctly. Since this does not work regardless of running as daemon or not. But I have not understood all the details there. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1551351 Title: dhclient does not renew leases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1551351/+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 1551351] Re: dhclient does not renew leases
So maybe we should un-duplicate bug 1551415 as not acting on SIGHUP likely is something that could be different and also affect the network- manager case. I think I saw some comment there about shutdown/reboot times being increased. The problem of not keeping leases active is limited to systems using ifup/-down (or anything that starts dhclient in daemon mode). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1551351 Title: dhclient does not renew leases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1551351/+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 1551351] Re: dhclient does not renew leases
Hm, of course, if one starts dhclient in debug mode (foreground) by adding a "-d", everything does work. :/ Interestingly when I attach to it with strace, I see "strace: Process attached with 4 threads". The foreground process does not act on ctrl-c which at least is consistent with the broken behaviour. When not working (in the background) strace will not find/report any threads running. The other thing to note (it was mentioned before) is that looking at /proc//fd the process has a file handle for the lease file, but looking at the time stamps it does not get updated. Likely because that is something that one of the threads would do. This also explains why dhclient under network-manager control works. Network-manager starts it in foreground/debug mode (with -d). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1551351 Title: dhclient does not renew leases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1551351/+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 1551351] Re: dhclient does not renew leases
For more data points on this, someone mentioned today that for him the
leases get renewed (with dhclient started by network-manager). The
command line is slightly different there:
/sbin/dhclient -d -q -sf -pf -lf
-cf
while on an ifupdown system where I see the stall it is:
/sbin/dhclient -1 -v -pf -lf -I -df
though it is the same command line used for ifupdown before. I got another
Xenial/ifupdown based VM which was not recently updated (so leases get renewed
still). I was able to attach to the daemon with "strace -p -ff" and could
see that the main thread is in "select(7, [5 6], [], NULL, {276, 557923}". But
there is other activity as well from time to time.
On the broken system the dhclient main thread is in "futex(0x7fb54906b0a4,
FUTEX_WAIT_PRIVATE, 5, NULL" and there is no other activity. As a result the
lease gets dropped which I can see on the server side as that is configured to
do DNS updates when DHCP leases become active or inactive.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1551351
Title:
dhclient does not renew leases
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1551351/+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 1551351] Re: dhclient does not renew leases
** Also affects: bind9 (Ubuntu) Importance: Undecided Status: New ** Changed in: bind9 (Ubuntu Xenial) Status: New => Confirmed ** Changed in: bind9 (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1551351 Title: dhclient does not renew leases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1551351/+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 1551643] [NEW] libvirt-bin should also use provides libvirt-daemon
Public bug reported: Other packages which are synced from Debian likely moved (or will move) to the new naming for their dependencies. We decided to stick with libvirt-bin fo Xenial/16.04 in order to avoid breaking things but should have an additional provides statement for libvirt-bin in the control file. ** Affects: libvirt (Ubuntu) Importance: Medium Assignee: Stefan Bader (smb) Status: Triaged ** Tags: xenial -- 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/1551643 Title: libvirt-bin should also use provides libvirt-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1551643/+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 1551636] [NEW] MaaS on older releases need support for newer curtin images
Public bug reported: This came up when we chatted about problems using Xenial images on Maas this morning. And it will likely become a big problem when Xenial is released. Server environments do not change that quickly, so we should expect hosts running Trusty (cloud-archive or maas from the PPA) trying to provision Xenial. This currently is broken because the smarts of the curtin installer seems to have changed and the rootfs-tgz (the base filesystem used) no longer comes with the kernel (and modules) pre-installed. But the init phase of older curtin versions does not include steps to download a kernel from the archive. So we end up with a client that starts the final reboot without any kernel installed. ** Affects: curtin (Ubuntu) Importance: Critical Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1551636 Title: MaaS on older releases need support for newer curtin images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1551636/+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 1550254] [NEW] [Xenial] openvswitch-switch installs dpdk on upgrade
Public bug reported: Not really a bug but could potentially confuse upgraders. After DPDK is in main, openvswitch-switch itself now (most recent upload) includes both binaries. So for someone who did not have explicitly installed the openvswitch-switch-dpdk package (supposed to be removed) in the past it may look like the DPDK variant suddenly gets activated. Not sure could be other impact, too. So this bug report probably is more to serve as a reminder to think about it... ** Affects: openvswitch (Ubuntu) Importance: Low Assignee: James Page (james-page) Status: Confirmed -- 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/1550254 Title: [Xenial] openvswitch-switch installs dpdk on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1550254/+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 1538049] Re: xenstore crashes with SIGBUS in domain_can_read()
The 4.4 kernel is now available and shows no issues. ** Changed in: xen (Ubuntu Xenial) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1538049 Title: xenstore crashes with SIGBUS in domain_can_read() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1538049/+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 1543025] [NEW] Wrong UTC zoneinfo in cloud-images
Public bug reported: ADT runs use cloud-images to create test VM environments. For the Xenial cloud-images I observed a weird issue where libvirt suddenly fails its build-time tests on a time offset test on UTC. Looking at the prepared image (cloud-init did already run there), I found that indeed a command-line of TZ=UTC date reports a CET based time. Looking further this seems to drill down into /usr/share/zoneinfo/UTC -> Zulu and that (Zulu another term for UTC) Zulu file looks quite bigger that the same on other hosts and contains the CET string as well (normal ~128b, wrong size 2335). Forcing a reinstall of tzdata will fix the file and also allows the libvirt test to pass. So I am not sure this is wrong in the initial image base or gets in some way broken during cloud-init. Thats why I start reporting it against cloud-init. ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1543025 Title: Wrong UTC zoneinfo in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1543025/+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 1538049] Re: xenstore crashes with SIGBUS in domain_can_read()
Hint from upstream. Sounds plausible that this might be the upstream fix: 9c17d96500f78 "xen/gntdev: Grant maps should not be subject to NUMA balancing" I guess 4.3 started to be more aggressive there since I never saw this before 4.3 and there even on a non-NUMA system. But having a grant-table mapping taken away from the dom0 kernel without xenstored being involved would explain it tripping over that now bad pointer. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1538049 Title: xenstore crashes with SIGBUS in domain_can_read() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1538049/+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 1538049] Re: xenstore crashes with SIGBUS in domain_can_read()
Installed a system with Debian testing and the crash does not happen there. That left two things: the additional security fixes we got or the kernel. And it was not the security fixes... Should have tried a different kernel sooner. Neither an old 4.2 based one nor the pending 4.4 are causing this. Only the current 4.3 based one. Maybe some Xen related stable patches did get mis-applied or not applied at all. Who knows. Will concentrate on the coming 4.4 and if I am happy, close this report. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1538049 Title: xenstore crashes with SIGBUS in domain_can_read() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1538049/+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 1538049] Re: xenstore crashes with SIGBUS in domain_can_read()
Crash also happens if dom0 is restricted to a single, pinned vCPU. So I guess it isn't an inconsistency. Only vague explanation I can think of is that the hypervisor for some reason invalidates the mapping without dom0(and xenstored running there) realizing. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1538049 Title: xenstore crashes with SIGBUS in domain_can_read() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1538049/+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 1538049] Re: xenstore crashes with SIGBUS in domain_can_read()
Not sure this has some meaning or is just a red herring but comparing the grant-rable debug output with Wily (Xen-4.5) it looks mostly similar except the entry #8 which has back then the same pin number as the other two... (XEN) active shared (XEN) [ref] localdom mfn pin localdom gmfn flags (XEN) grant-table for remote domain:1 (v1) (XEN) [ 0]0 0x8091ff 0x0002 0 0x8091ff 0x19 (XEN) [ 1]0 0x809200 0x0002 0 0x809200 0x19 (XEN) [ 8]0 0x5353ba 0x0002 0 0x5353ba 0x19 Reading the code #0 is related to console and #1 to xenstore. Not sure what that #8 is. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1538049 Title: xenstore crashes with SIGBUS in domain_can_read() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1538049/+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 1538049] Re: xenstore crashes with SIGBUS in domain_can_read()
For the recent crashes the pointer seemed always consistent with previous mappings. Wondering whether the mapping might be invalidated by the hypervisor side. For additional information, when I start the domU, grant table debug shows the following at the beginning: (XEN) grant-table for remote domain:1 (v1) (XEN) [ 0]0 0x212992 0x0002 0 0x212992 0x19 (XEN) [ 1]0 0x212991 0x0002 0 0x212991 0x19 (XEN) [ 8]0 0x1d26b7 0x0001 0 0x1d26b7 0x19 when xenstored crashes, the middle entry goes away. But its impossible to say whether it goes away before the crash or just as a result of it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1538049 Title: xenstore crashes with SIGBUS in domain_can_read() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1538049/+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 1538049] Re: xenstore crashes with SIGBUS in domain_can_read()
Hm, when repeating with a xenstored that prints additional trace
messages about domain->interface values, I now got a case where the
SIGBUS seems to have happened while the interface pointer looks valid.
(gdb) where
#0 domain_can_read (conn=conn@entry=0x8eb890) at xenstored_domain.c:261
#1 0x00402718 in main (argc=, argv=)
at xenstored_core.c:2145
(gdb) p *((struct connection *) 0x8eb890)
$1 = {list = {next = 0x8eca60, prev = 0x8ecdf0}, fd = -1, pollfd_idx = -1,
id = 1, can_write = true, in = 0x8ef290, out_list = {next = 0x8eb8b8,
prev = 0x8eb8b8}, transaction = 0x0, transaction_list = {next = 0x8eb8d0,
prev = 0x8eb8d0}, next_transaction_id = 10, transaction_started = 0,
domain = 0x8eced0, target = 0x0, watches = {next = 0x8edd30,
prev = 0x8ee9a0}, write = 0x406140 , read = 0x406240 }
(gdb) p *((struct domain *) 0x8eced0)
$2 = {list = {next = 0x8e81b0, prev = 0x6145a0 }, domid = 1,
port = 48, remote_port = 1, mfn = 2173329,
path = 0x8ec460 "/local/domain/1", interface = 0x7fc8acb0f000,
conn = 0x8eb890, shutdown = 0, nbentry = 44, nbwatch = 9}
** Attachment added: "Log of xenstored with additional debugging enabled."
https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1538049/+attachment/4556767/+files/xenstored.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xen in Ubuntu.
https://bugs.launchpad.net/bugs/1538049
Title:
xenstore crashes with SIGBUS in domain_can_read()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1538049/+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 1538049] [NEW] xenstore crashes with SIGBUS in domain_can_read()
Public bug reported: Problem got introduced by xen-4.6 in Xenial. Older versions are unaffected. Testcase: - Start one additional domU (PV or HVM does not matter) - Repeatedly execute "xenstore-ls" Eventually the xenstore-ls call locks up while xenstored crashes when it tries to access memory in tools/xenstore/xenstored_domain.c:255 domain_can_read(struct connection *conn) Debugging shows that conn->domain->interface at the time of crash returns a completely different address than before (there should only be one per running domain, so 2). ** Affects: xen (Ubuntu) Importance: Critical Assignee: Stefan Bader (smb) Status: In Progress ** Affects: xen (Ubuntu Xenial) Importance: Critical Assignee: Stefan Bader (smb) Status: In Progress ** Also affects: xen (Ubuntu Xenial) Importance: Critical Assignee: Stefan Bader (smb) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1538049 Title: xenstore crashes with SIGBUS in domain_can_read() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1538049/+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 1525676] Re: qemu runas and sandbox option incompatible, process will hang in futex after setgid
Yes, it looks like that discussion is related. Though I also got the impression that there is currently still some decision going on how exactly to fix this. So it feels like we should wait with any fix until this decision is made (and a fix is committed into qemu's upstream repo)... -- 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/1525676 Title: qemu runas and sandbox option incompatible, process will hang in futex after setgid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1525676/+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 1472500] Re: virt-manager. restore windows vm-> Unknown savevm section type 5
** Changed in: qemu (Ubuntu) Assignee: Stefan Bader (smb) => (unassigned) -- 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/1472500 Title: virt-manager. restore windows vm-> Unknown savevm section type 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1472500/+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 1516005] Re: iscsitarget: build failures against kernel 4.3
** Patch added: "Debdiff including bug reference." https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1516005/+attachment/4524713/+files/iscsitarget.debdiff ** Patch removed: "Proposed changes" https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1516005/+attachment/4524269/+files/iscsitarget.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1516005 Title: iscsitarget: build failures against kernel 4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1516005/+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 1516005] Re: iscsitarget: build failures against kernel 4.3
Note that I forgot to add a bug reference in the proposed changes. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1516005 Title: iscsitarget: build failures against kernel 4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1516005/+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 1516005] Re: iscsitarget: build failures against kernel 4.3
Proposed fixes for 4.3 (currently only compile tested) ** Changed in: iscsitarget (Ubuntu) Status: New => In Progress ** Patch added: "Proposed changes" https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1516005/+attachment/4524269/+files/iscsitarget.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1516005 Title: iscsitarget: build failures against kernel 4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1516005/+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 1516005] Re: iscsitarget: build failures against kernel 4.3
** Changed in: iscsitarget (Ubuntu) Assignee: (unassigned) => Stefan Bader (smb) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1516005 Title: iscsitarget: build failures against kernel 4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1516005/+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 931350] Re: vms missing after upgrade from Lucid to Precise
Lucid is no longer supported and so I would close this. There has been some work-around as far as I can see and by now probably all known vms are likely Precise or newer. ** Changed in: libvirt (Ubuntu) Status: Triaged => Won't Fix ** Changed in: libvirt (Ubuntu Precise) Status: Triaged => Won't Fix ** Changed in: virt-manager (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: virt-manager (Ubuntu Precise) Status: Confirmed => Won't Fix -- 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/931350 Title: vms missing after upgrade from Lucid to Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/931350/+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 1323758] Re: Mouse stops working when connected usb-storage-device
** 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/1323758 Title: Mouse stops working when connected usb-storage-device To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1323758/+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 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed
** Changed in: qemu (Ubuntu Vivid)
Status: New => In Progress
** Changed in: qemu (Ubuntu Trusty)
Status: New => In Progress
** Changed in: qemu (Ubuntu Trusty)
Assignee: (unassigned) => Stefan Bader (smb)
** Changed in: qemu (Ubuntu Vivid)
Assignee: (unassigned) => Stefan Bader (smb)
** Changed in: qemu (Ubuntu)
Assignee: Stefan Bader (smb) => (unassigned)
** Changed in: qemu (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: qemu (Ubuntu Vivid)
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/1465935
Title:
kvm_irqchip_commit_routes: Assertion `ret == 0' failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1465935/+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 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed
@Li Chengyuan, thank you for the clarification. So just formally I will mark the Precise task of this report as invalid (since the qemu in Precise is actually a different source package and also not affected as far as I can tell). I will need to figure out how to ensure this fix is also pulled into the cloud-archive after it landed in the Trusty/Vivid main archive. ** Changed in: qemu (Ubuntu Precise) Status: New => Invalid -- 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/1465935 Title: kvm_irqchip_commit_routes: Assertion `ret == 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1465935/+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 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed
@Li Chengyuan, is your host OS really 12.04 (aka Precise)? Because in 12.04 the qemu version is 1.0 and the fix would not apply. I am not sure that old qemu is even affected since the code is very different. Backports of the fix seem only to make sense up (or back) to 14.04 (aka Trusty) which would also match the qemu version 2.0 which you mentioned. -- 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/1465935 Title: kvm_irqchip_commit_routes: Assertion `ret == 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1465935/+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 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed
Just saw kernel version 3.2 mentioned. So this seems to be a mix of older base OS (Precise) and a more recent qemu (maybe from Trusty). I am trying to clarify how far this needs to be backported. So I think the original qemu version in Precise is unaffected. -- 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/1465935 Title: kvm_irqchip_commit_routes: Assertion `ret == 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1465935/+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 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed
SRU Justification: Impact: Moving around interrupt handling on SMP (like irqbalance does) in qemu instances can cause the qemu guest to crash due to an internal accounting mismatch. Fix: Backported patch from upstream qemu Testcase: See above. Verified for Trusty with provided test qemu package(s). -- 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/1465935 Title: kvm_irqchip_commit_routes: Assertion `ret == 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1465935/+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 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed
Utopic is out of support now. ** Changed in: qemu (Ubuntu Utopic) Status: New => Won't Fix ** Changed in: qemu (Ubuntu) Status: Incomplete => Fix Committed -- 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/1465935 Title: kvm_irqchip_commit_routes: Assertion `ret == 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1465935/+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 457092] Re: starting a VM with an SDL display hangs virtmanager and virsh
Reading the comments this sounds like it might have been an issue in the Jaunty/9.04 version of virt-manager but fixed in Karmic/9.10. Jaunty would be no longer supported, so I close this as fix-released. ** Changed in: libvirt (Ubuntu) Status: Triaged => 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/457092 Title: starting a VM with an SDL display hangs virtmanager and virsh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/457092/+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 1494602] Re: qemu-system-x86 nested virtualisation is broken on AMD system
Managed to verify that switching between pc-i440fx-trusty and -utopic will cause the svm flag to be dropped (as long as it is not forcefully enabled in the libvirt config). And my special failure seems to be caused by another oddness in qemu: while a Opteron_G4 is too recent and I would have to disable things, the Opteron_G3 which normally gets picked as a base is far too old. (the G4 is based on 62xx but G3 is based on 23xx, while I got a 61xx). The better match for my case seems "phenom" which at least sets the right cpuid_level and xlevel. -- 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/1494602 Title: qemu-system-x86 nested virtualisation is broken on AMD system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1494602/+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 1494602] Re: qemu-system-x86 nested virtualisation is broken on AMD system
So this quite likely might be a "feature" that got introduced with qemu 2.2: commit 75d373ef9729bd22fbc46bfd8dcd158cbf6d9777 Author: Eduardo Habkost Date: Fri Oct 3 16:39:51 2014 -0300 target-i386: Disable SVM by default in KVM mode Make SVM be disabled by default on all CPU models when in KVM mode. Nested SVM is enabled by default in the KVM kernel module, but it is probably less stable than nested VMX (which is already disabled by default). Add a new compat function, x86_cpu_compat_kvm_no_autodisable(), to keep compatibility on previous machine-types. I saw both machine types (pc-i440fx-trusty and pc-i440fx-utopic) mentioned in some xml configs. Not sure which is which. Might be worth checking the config in the currently not working case and if that is not trusty, try to replace it with that. -- 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/1494602 Title: qemu-system-x86 nested virtualisation is broken on AMD system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1494602/+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 1494602] Re: qemu-system-x86 nested virtualisation is broken on AMD system
Did I understand this right to be a combination of roughly 14.04 (Trusty) as base with (probably both through the cloud archive) a libvirt version that appears to closest match with 15.04 (Vivid) and qemu at 15.10 (Wily) level? Unfortunately I cannot recreate the same results as I only got a fam 10h model 09h host. For that I get the svm flag inside the guest on native Trusty, Vivid, and Wily. However nested is actually broken for all as cpuid function 800a seems not implemented in any qemu version (2.0.0 +dfsg-2ubuntu1.18 ... 1:2.3+dfsg-5ubuntu6). I have to check what the G4 type (from fam 16h model 02h) would yield. Just also wondering whether in the case of not dropping svm the kvm module actually loads or also fails on cpuid 800Ah. -- 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/1494602 Title: qemu-system-x86 nested virtualisation is broken on AMD system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1494602/+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 1336801] Re: 12.04 guest hangs on a 14.04 host server with cirrus graphics
The errors about the frame buffer device happen because grub is started in graphical mode and then the boot wants to replace the framebuffer device/driver while plymouth still holds it. I thought we should have fixed this before release by adding cirrus to the list of graphics that should get initialized late. So are people still having this issue with the latest updates? A work around if this really still happens is to change /etc/default/grub and uncomment the console mode. Not ultimately nice but should be working. ** Changed in: qemu (Ubuntu) Status: Triaged => Incomplete -- 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/1336801 Title: 12.04 guest hangs on a 14.04 host server with cirrus graphics To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1336801/+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 1473282] Re: Redhat guest hang when iotest on qemu 1:2.2+dfsg-5expubuntu9.2
** Changed in: qemu (Ubuntu) Status: In Progress => Incomplete -- 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/1473282 Title: Redhat guest hang when iotest on qemu 1:2.2+dfsg-5expubuntu9.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1473282/+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 1472500] Re: virt-manager. restore windows vm-> Unknown savevm section type 5
** Changed in: qemu (Ubuntu) Status: Triaged => Incomplete -- 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/1472500 Title: virt-manager. restore windows vm-> Unknown savevm section type 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1472500/+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 1465034] Re: Guest shows black screen after woken up from "pmsuspended"
We were not able to reproduce this locally. The change the Redhat bug refers to looks to be included in the version of qemu that is in 14.04. Could you please try to verify with the host and guest updated and let us know whether this really still is an issue? Thanks. ** 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://bugs.launchpad.net/bugs/1465034 Title: Guest shows black screen after woken up from "pmsuspended" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1465034/+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 1496057] Re: The dep-8 test of iscsitarget should check the kernel module as well
The dep-8 adt testing now completed for 3.13 and 3.19 kernels in Trusty. The module was test loaded for both combinations. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1496057 Title: The dep-8 test of iscsitarget should check the kernel module as well To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1496057/+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 1483415] Re: iscsitarget-dkms fails to build on 14.04
I checked the ADT logs and the 1.4.20.3+svn499-0ubuntu2.1 package in trusty was successfully compiling for both 3.13 and 3.19 (plus positive feedback for the test package which was the same except the additional changes for testing). ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1483415 Title: iscsitarget-dkms fails to build on 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1483415/+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 1496057] Re: The dep-8 test of iscsitarget should check the kernel module as well
** Description changed: Right now the dep-8 test checks whether the daemon can be started. - Practically the daemon can even without the dkms kernel module + Practically the daemon can, even without the dkms kernel module available, though it makes not that much sense as for being useful this is also required. The module is already build but the outcome of that stage is not verified. Make this more useful by modprobing the module as part of the test. ** Changed in: iscsitarget (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: iscsitarget (Ubuntu Trusty) Status: New => In Progress ** Changed in: iscsitarget (Ubuntu Trusty) Assignee: (unassigned) => Stefan Bader (smb) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1496057 Title: The dep-8 test of iscsitarget should check the kernel module as well To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1496057/+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 1496057] [NEW] The dep-8 test of iscsitarget should check the kernel module as well
Public bug reported: Right now the dep-8 test checks whether the daemon can be started. Practically the daemon can even without the dkms kernel module available, though it makes not that much sense as for being useful this is also required. The module is already build but the outcome of that stage is not verified. Make this more useful by modprobing the module as part of the test. ** Affects: iscsitarget (Ubuntu) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Changed in: iscsitarget (Ubuntu) Importance: Undecided => Medium ** Changed in: iscsitarget (Ubuntu) Status: New => In Progress ** Changed in: iscsitarget (Ubuntu) Assignee: (unassigned) => Stefan Bader (smb) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1496057 Title: The dep-8 test of iscsitarget should check the kernel module as well To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1496057/+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 1483415] Re: iscsitarget-dkms fails to build on 14.04
** Attachment added: "iscsitarget-dkms_1.4.20.3+svn499-0ubuntu2.1_all.deb" https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1483415/+attachment/4464127/+files/iscsitarget-dkms_1.4.20.3%2Bsvn499-0ubuntu2.1_all.deb -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1483415 Title: iscsitarget-dkms fails to build on 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1483415/+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 1483415] Re: iscsitarget-dkms fails to build on 14.04
Unfortunately there are a lot of variations with HWE kernels, so I also got hit by not noticing there is the correct testing missing for 14.04 userspace/dkms with the 3.19 kernel. Sorry about that. Only good here is that iscsitarget is universe, so it is not part of the iso. Just that a fix needs to be done for the archive. Could someone give the two debs a go before I try to get the source uploaded? ** Attachment added: "iscsitarget_1.4.20.3+svn499-0ubuntu2.1_amd64.deb" https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1483415/+attachment/4464126/+files/iscsitarget_1.4.20.3%2Bsvn499-0ubuntu2.1_amd64.deb -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1483415 Title: iscsitarget-dkms fails to build on 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1483415/+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 1297224] Re: Improve xen packages and hvm domUs support
Thanks James, unfortunately its the build-dependency on edk2/ovmf which prevents me from picking this right now (ovmf is multiverse and at least xen source is main). And really sorry Fantu, this cycle I had no time at all to do realistic improvements to the packaging at all. The only thing I am getting to is pulling in the latest stable (4.5.1). For 16.04 I hope to spend more time as this also should make the jump to 4.6 hopefully. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1297224 Title: Improve xen packages and hvm domUs support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1297224/+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 1483415] Re: iscsitarget-dkms fails to build on 14.04
Right you are runnint 3.19.0-25* not 3.19.0-26*. Cannot give you a link, but internal testing has this version as working: iscsitarget, 1.4.20.3+svn502, 3.19.0-26-generic, x86_64: installed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1483415 Title: iscsitarget-dkms fails to build on 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1483415/+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 1483415] Re: iscsitarget-dkms fails to build on 14.04
Could you try updating the HWE kernel. This should be fixed in 3.19.0-26* onwards. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1483415 Title: iscsitarget-dkms fails to build on 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1483415/+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 1476666] Re: [MRE] Rebase Xen-4.4 to upstream stable 4.4.2
Re-ran the testing with the proposed build re-installed: same results. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/147 Title: [MRE] Rebase Xen-4.4 to upstream stable 4.4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/147/+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 1448985] Re: llvmpipe i386 crashes when running on qemu64 cpu
Since a simple work-around exists I think the importance can be lowered.
** Summary changed:
- Ubuntu 14.04 LTS, 14.10, 15.04, 15.10 guests do not boot to Unity from
QEMU-KVM Ubuntu 14.04 LTS, 14.10, 15.04 hosts
+ llvmpipe i386 crashes when running on qemu64 cpu
** Description changed:
STEPS TO REPRODUCE:
1. Install Ubuntu 14.04.2 LTS or Ubuntu 14.10 or Ubuntu 15.04 with all
updates (it is a host system).
2. Download one (or all) isos:
* Ubuntu 14.0.4.2 i386 iso (ubuntu-14.04.2-desktop-i386.iso, MD5SUM =
a8a14f1f92c1ef35dae4966a2ae1a264).
* Ubuntu 14.10 i386 iso (ubuntu-14.10-desktop-i386.iso, MD5SUM =
4a3c4b8421af51c29c84fb6f4b3fe109)
* Ubuntu 15.04 i386 iso (ubuntu-15.04-desktop-i386.iso, MD5SUM =
6ea04093b767ad6778aa245d53625612)
3. Boot one (or all) isos with as QEMU-KVM guest with the following
commands:
* sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso
* sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso -vga std
* sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso -vga vmware
* or from usb-creator-gtk via "Test disk" button
4. Click on "Try Ubuntu"
EXPECTED RESULTS:
ISO is booted to Unity desktop, user can test and use it.
ACTUAL RESULTS:
In 14.04 and 14.10 guests can see empty purple desktop or purple desktop
with two shortcuts ("Examples" and "Install Ubuntu ...").
15.10 guest does not boot or boot to safe graphic mode (it is bug 1437740).
+ The reason for this is that unity requires gfx acceleration which is
+ done via llvmpipe on non accelerated gfx chipsets (as VMs use by
+ default). The error message is hidden away but is:
+
+ LLVM ERROR: Do not know how to split the result of this operator!
+
+ The cause is that KVM VMs by default use the qemu64 cpu model which
+ seems to be inconsistent in some way between claimed features and actual
+ results when using those features. A work-around for running i386 isos
+ is to use a cpu model like core2duo or kvm64.
+
This bug should be confirmed and fixed.
Users may want to run Ubuntu in QEMU/KVM, not just VirtualBox.
** Also affects: llvm-toolchain-3.6 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Importance: High => Medium
--
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/1448985
Title:
llvmpipe i386 crashes when running on qemu64 cpu
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1448985/+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 1481294] Re: 14.04.3: in kvm install full disk from the i386 install when you go to login it returns you to the login page
*** This bug is a duplicate of bug 1448985 *** https://bugs.launchpad.net/bugs/1448985 Or actually kvm64 as model. I would be duping this bug report against the one I was looking into before as I think we got more details in that by now. ** This bug has been marked a duplicate of bug 1448985 llvmpipe i386 crashes when running on qemu64 cpu -- 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/1481294 Title: 14.04.3: in kvm install full disk from the i386 install when you go to login it returns you to the login page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.6/+bug/1481294/+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 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed
Marking as incomplete while waiting for test feedback. ** Changed in: qemu (Ubuntu) Status: Confirmed => Incomplete -- 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/1465935 Title: kvm_irqchip_commit_routes: Assertion `ret == 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1465935/+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 1483214] Re: ipmi_si module spams kernel log with "ipmi_si 00:05: Could not set the global enables: 0xcc."
SRU Justtification Impact: The driver code changed in 3.19 to do periodic checks on irq and message settings commit d9b7e4f717a167610a49ceb9e5969e80146c89a8 ipmi: Periodically check to see if irqs and messages are set right This causes repeated error messages in the logs for certain BMCs which do not allow to disable the irq mode in the global config even when they do not support irqs. Fix: Cherry-pick upstream commit 1e7d6a45f6b10bc48a1453bca3d829e210546571 which adds a quirk to detect this situation and avoids touching those bits. This was done in 4.0, so the only affected kernel is 3.19. Testcase: With an affected BMC and without the patch, errors repeatedly get logged. With the patch applied, there will be only a single message in the log. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1483214 Title: ipmi_si module spams kernel log with "ipmi_si 00:05: Could not set the global enables: 0xcc." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1483214/+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 1483214] Re: ipmi_si module spams kernel log with "ipmi_si 00:05: Could not set the global enables: 0xcc."
With that kernel you should get an error message once about the BMC needing fixing. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1483214 Title: ipmi_si module spams kernel log with "ipmi_si 00:05: Could not set the global enables: 0xcc." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1483214/+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 1483214] Re: ipmi_si module spams kernel log with "ipmi_si 00:05: Could not set the global enables: 0xcc."
Test kernel (download all *.deb files and install with "sudo dpkg -i *.deb") can be found at: http://people.canonical.com/~smb/lp1483214/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1483214 Title: ipmi_si module spams kernel log with "ipmi_si 00:05: Could not set the global enables: 0xcc." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1483214/+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 1483214] Re: ipmi_si module spams kernel log with "ipmi_si 00:05: Could not set the global enables: 0xcc."
The fix released is for the development branch (Wily/15.10) which is using kernel 4.1 currently. Not sure how launchpad decides what use as summary for the link. The fix looks to be backportable. Might just be a few iterations to go through the process. Right now I would prepare a replacement 3.19 HWE kernel for Trusty/14.04 for you to try. I let you know where to get that from when it is ready. ** Changed in: linux (Ubuntu Vivid) Assignee: (unassigned) => Stefan Bader (smb) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1483214 Title: ipmi_si module spams kernel log with "ipmi_si 00:05: Could not set the global enables: 0xcc." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1483214/+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 1483214] Re: ipmi_si module spams kernel log with "ipmi_si 00:05: Could not set the global enables: 0xcc."
** Package changed: linux-meta-lts-vivid (Ubuntu) => linux (Ubuntu) ** Also affects: openipmi (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Vivid) Status: New => Triaged ** Changed in: openipmi (Ubuntu) Status: New => Invalid ** Changed in: openipmi (Ubuntu Vivid) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1483214 Title: ipmi_si module spams kernel log with "ipmi_si 00:05: Could not set the global enables: 0xcc." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1483214/+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 1448985] Re: Ubuntu 14.04 LTS, 14.10, 15.04, 15.10 guests do not boot to Unity from QEMU-KVM Ubuntu 14.04 LTS, 14.10, 15.04 hosts
Maybe not exactly the cpuid flags seen but in a weird way how qemu builds some structures. I have to dig more there. But it is strange that qemu64 (which is the default cpu type if nothing else is specified) is defined as something based on a AMD cpu, while all of qemu32, kvm64, and kvm32 use a Intel base. -- 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/1448985 Title: Ubuntu 14.04 LTS, 14.10, 15.04, 15.10 guests do not boot to Unity from QEMU-KVM Ubuntu 14.04 LTS, 14.10, 15.04 hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1448985/+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 1448985] Re: Ubuntu 14.04 LTS, 14.10, 15.04, 15.10 guests do not boot to Unity from QEMU-KVM Ubuntu 14.04 LTS, 14.10, 15.04 hosts
Finally with a little help on debugging unity, I think I see what is going on. The obvious part seemed to be that compiz seems to fail starting. Which turns out to be LLVM-pipe bailing with an obscure error message: LLVM ERROR: Do not know how to split the result of this operator! This made me think about the emulated CPU, even more because Xen HVM guests do work with the i386 isos. And really this is the actual problem! So one quick work-around is to force qemu to use a different CPU type. In my test I used the Wily i386 iso and changed the CPU type from the default (QEMU Virtual CPU v2.0.0) into core2duo. And suddenly the live session works. So next, what is the difference. Beside of name, model, and stepping, it seems the cpuid flags: Core(TM)2 Duo CPU (emulated)QEMU Virtual CPU v2.0.0 model 15model 6 stepping 11 stepping 3 cpuid level 10 cpuid level 4 ore(TM)2 Duo CPU (emulated) QEMU Virtual CPU v2.0.0 model 15model 6 stepping 11 stepping 3 cpuid level 10 cpuid level 4 -->fpu vme de pse tsc msr pae mce fpu de pse tsc msr pae mce <-- -->cx8 apic sep mtrr pge mca cmov cx8 apic sep mtrr pge mca cmov <-- -->pat pse36 clflush mmx fxsr sse pse36 clflush mmx fxsr sse <-- -->sse2 ss syscall nx lm sse2syscall nx lm <-- -->constant_tsc pni vmx ssse3 pni vmx <-- -->cx16 x2apic hypervisor cx16 x2apic popcnt hypervisor <-- -->lahf_lm vnmi ept lahf_lm vnmi ept<-- So QEMU CPU misses: vme, pat, ss, constant_tsc, and ssse3 but has popcnt. A different host running Xen was also missing ss, constant_tsc, ssse3, and popct. But it had vme and pat and was working with the i386 iso. That sounds a bit like either vme or pat missing could cause the i386 build of llvmpipe to fail while the exact same cpuid configuration works with the amd64 version of llvmpipe. -- 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/1448985 Title: Ubuntu 14.04 LTS, 14.10, 15.04, 15.10 guests do not boot to Unity from QEMU-KVM Ubuntu 14.04 LTS, 14.10, 15.04 hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1448985/+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 1481038] Re: iproute2 crashes being reported since kernel version 3.13-0-59-generic
Maybe we should make sure that this remains a problem with the latest kernel *-61.100. The -59 kernel caused a lot of other problems. Usually those were related to executing a 64bit binary from a 32bit binary. But I would not completely rule out other odd failures. So if all the reports are with -59 and the numbers again go down it is probably related to that. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1481038 Title: iproute2 crashes being reported since kernel version 3.13-0-59-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1481038/+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 1480996] [NEW] maas memory rounding seems wrong
Public bug reported: Just a minor little detail. When looking at the web interface of maas (1.8.0+bzr4001-0ubuntu2): - a VM guest with exactly 1024M of memory shows up as having 1.0 (G) of memory - a VM guest with 2040M of memory however shows up as having 1 (G) of memory (not 1.9) The fact that the fraction part is stripped when it is not 0 seems to be the wrong way around. ** Affects: maas (Ubuntu) Importance: Low Status: New -- 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/1480996 Title: maas memory rounding seems wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1480996/+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 1476666] Re: [MRE] Rebase Xen-4.4 to upstream stable 4.4.2
Except the one failure in dom0 (which is a known problem with the test itself) all tests were ok. ** Attachment added: "Regression test report (Intel CPU)" https://bugs.launchpad.net/ubuntu/+source/xen/+bug/147/+attachment/4432495/+files/i-xen-regression-test.report -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/147 Title: [MRE] Rebase Xen-4.4 to upstream stable 4.4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/147/+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 1476666] Re: [MRE] Rebase Xen-4.4 to upstream stable 4.4.2
All tests completed ok. ** Attachment added: "Regression test report (AMD CPU)" https://bugs.launchpad.net/ubuntu/+source/xen/+bug/147/+attachment/4432496/+files/a-xen-regression-test.report -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/147 Title: [MRE] Rebase Xen-4.4 to upstream stable 4.4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/147/+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 1476666] [NEW] [MRE] Rebase Xen-4.4 to upstream stable 4.4.2
Public bug reported:
SRU Justification:
Impact: Upstream Xen has released a stable update to 4.4.2. Since Trusty
based on 4.4 it would be gaining us bug fixes without waiting for people
to run into them. Like we do with upstream stable on the kernel. Utopic
would have been 4.4 based as well but more or less has reached EOL.
Fix: Replaced the orig tarballs with the contents of the upstream stable
release. Dropping patches we have picked up already.
Testcase: Basic regression testing after upgrading.
MRE discussion: http://irclogs.ubuntu.com/2013/07/22/%23ubuntu-
meeting.html#t20:33
** Affects: xen (Ubuntu)
Importance: Medium
Status: Invalid
** Affects: xen (Ubuntu Trusty)
Importance: Medium
Assignee: Stefan Bader (smb)
Status: In Progress
** Also affects: xen (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: xen (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: xen (Ubuntu Trusty)
Status: New => In Progress
** Changed in: xen (Ubuntu Trusty)
Assignee: (unassigned) => Stefan Bader (smb)
** Changed in: xen (Ubuntu)
Status: New => Invalid
** Changed in: xen (Ubuntu)
Assignee: Stefan Bader (smb) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xen in Ubuntu.
https://bugs.launchpad.net/bugs/147
Title:
[MRE] Rebase Xen-4.4 to upstream stable 4.4.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xen/+bug/147/+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 1476666] Re: [MRE] Rebase Xen-4.4 to upstream stable 4.4.2
This is the delta between the current Ubuntu 4.4.1 (with all patches applied) and the 4.4.2 (also with all patches applied, excluding ./debian and ./.pc. ** Patch added: "Delta between xen-4.4.1 and 4.4.2" https://bugs.launchpad.net/ubuntu/+source/xen/+bug/147/+attachment/4431996/+files/xen-4.4.1to2-delta.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/147 Title: [MRE] Rebase Xen-4.4 to upstream stable 4.4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/147/+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 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed
Unfortunately I seem to be unable to get this bug triggered with the reproducer. It could be a detail of the guest setup I am missing. Since I do not have access to RHEL I used CentOS 6.3 in a 8core guest with 2 virtio disks. Host was 14.04. Left the script running for quite a bit but no crash happened. So it would be up to you to confirm that with a current 14.04 host you still can trigger the bug and with the patched version of qemu from http://people.canonical.com/~smb/lp1465935/ it would be gone. Thanks. -- 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/1465935 Title: kvm_irqchip_commit_routes: Assertion `ret == 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1465935/+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 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed
The proposed fix seems not yet part of any qemu release but applied as commit bdf026317daa3b9dfa281f29e96fbb6fd48394c8 Author: 马文霜 Date: Wed Jul 1 15:41:41 2015 +0200 Fix irq route entries exceeding KVM_MAX_IRQ_ROUTES to v2.4.0-rc0. So this would affect all current releases and the current development release (Wily/15.10). I would start there with reproduction/verification and work backwards from there. -- 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/1465935 Title: kvm_irqchip_commit_routes: Assertion `ret == 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1465935/+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 1472500] Re: virt-manager. restore windows vm-> Unknown savevm section type 5
The thread in the initial description pointed to a fix for a certain emulated realtime clock. Might be that setting up Windows guests tweaks the base hardware. So I picked that and build a 15.04 set of qemu packages with that applied. The packages can be found at: http://people.canonical.com/~smb/lp1472500/ Can you check whether that helps in your case? Btw, you only need to download and install those debs which you already got. Or download them all into an empty directory and then install with "sudo dpkg -iO *.deb" which automatically skips any packages which are not installed. For reference the applied patch is: commit bb426311901776b95b021cece831b69dce4ef5ee fix mc146818rtc wrong subsection name to avoid vmstate_subsection_load() fail during incoming migration or loadvm. ** Changed in: qemu (Ubuntu) Importance: Undecided => Medium ** Changed in: qemu (Ubuntu) Status: New => Triaged ** Changed in: qemu (Ubuntu) Assignee: (unassigned) => Stefan Bader (smb) -- 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/1472500 Title: virt-manager. restore windows vm-> Unknown savevm section type 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1472500/+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 1472115] Re: autofs start fails: segfault at 0 ip 00007f738cb881bb sp 00007ffeff888f70 error 4 in lookup_file.so[7f738cb76000+2b000]
Its not only that call site. I get the feeling that the daemon does not inherit the dynamically allocated structures across fork(). At least it does do a defaults_read_config() before the fork which does not seem to survive. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1472115 Title: autofs start fails: segfault at 0 ip 7f738cb881bb sp 7ffeff888f70 error 4 in lookup_file.so[7f738cb76000+2b000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1472115/+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 1472115] Re: autofs start fails: segfault at 0 ip 00007f738cb881bb sp 00007ffeff888f70 error 4 in lookup_file.so[7f738cb76000+2b000]
Seems that defaults_read_config(), defaults_get_searchdns() or at least conf_init() needs to be called before trying conf_get_yesno() in defaults_get_browse_mode(). Otherwise the config pointer is still NULL when accessing the hash table indirectly. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1472115 Title: autofs start fails: segfault at 0 ip 7f738cb881bb sp 7ffeff888f70 error 4 in lookup_file.so[7f738cb76000+2b000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1472115/+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 1472115] Re: autofs start fails: segfault at 0 ip 00007f738cb881bb sp 00007ffeff888f70 error 4 in lookup_file.so[7f738cb76000+2b000]
#0 0x7fab78969e10 in conf_lookup_key () from /usr/lib/x86_64-linux-gnu/autofs/lookup_file.so #1 0x7fab78969ece in conf_lookup () from /usr/lib/x86_64-linux-gnu/autofs/lookup_file.so #2 0x7fab7896b246 in conf_get_yesno () from /usr/lib/x86_64-linux-gnu/autofs/lookup_file.so #3 0x7fab7896bc95 in defaults_get_browse_mode () from /usr/lib/x86_64-linux-gnu/autofs/lookup_file.so #4 0x7fab78963660 in local_init_vars () from /usr/lib/x86_64-linux-gnu/autofs/lookup_file.so #5 0x7fab78963a43 in master_parse_entry () from /usr/lib/x86_64-linux-gnu/autofs/lookup_file.so #6 0x7fab7895b7b5 in lookup_read_master () from /usr/lib/x86_64-linux-gnu/autofs/lookup_file.so #7 0x7fab7bfb6371 in do_read_master () #8 0x7fab7bfb6861 in lookup_nss_read_master () #9 0x7fab780afa63 in include_file () from /usr/lib/x86_64-linux-gnu/autofs/lookup_dir.so #10 0x7fab780afc92 in lookup_read_master () from /usr/lib/x86_64-linux-gnu/autofs/lookup_dir.so #11 0x7fab7bfb6371 in do_read_master () #12 0x7fab7bfb6b99 in lookup_nss_read_master () #13 0x7fab7895b61e in lookup_read_master () from /usr/lib/x86_64-linux-gnu/autofs/lookup_file.so #14 0x7fab7bfb6371 in do_read_master () #15 0x7fab7bfb6861 in lookup_nss_read_master () #16 0x7fab7bfcf797 in master_read_master () #17 0x7fab7bfaa579 in main () -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1472115 Title: autofs start fails: segfault at 0 ip 7f738cb881bb sp 7ffeff888f70 error 4 in lookup_file.so[7f738cb76000+2b000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1472115/+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 1472115] Re: autofs start fails: segfault at 0 ip 00007f738cb881bb sp 00007ffeff888f70 error 4 in lookup_file.so[7f738cb76000+2b000]
/etc/autofs.conf: master_map_name = /etc/auto.master /etc/auto.master: +dir:/etc/auto.master.d +auto.master /etc/auto.master.d/import.autofs: /import file:/etc/auto.import /etc/auto.import: isos-ro,soft,intr,nfsvers=3 nano:/srv/images/iso cloud-images-ro,soft,intr,nfsvers=3 nano:/srv/images/cloudimg tests -rw,soft,intr,nfsvers=3 nano:/home/tests The /import directory exists. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1472115 Title: autofs start fails: segfault at 0 ip 7f738cb881bb sp 7ffeff888f70 error 4 in lookup_file.so[7f738cb76000+2b000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1472115/+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 1472115] [NEW] autofs start fails: segfault at 0 ip 00007f738cb881bb sp 00007ffeff888f70 error 4 in lookup_file.so[7f738cb76000+2b000]
Public bug reported: Wily server 64bit installation, after dist-upgrade, restart of autofs.service fails and dmesg shows those errors: [ 1030.673473] automount[3276]: segfault at 0 ip 7f738cb881bb sp 7ffeff888f70 error 4 in lookup_file.so[7f738cb76000+2b000] ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: autofs 5.1.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 Date: Tue Jul 7 07:11:13 2015 SourcePackage: autofs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: autofs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1472115 Title: autofs start fails: segfault at 0 ip 7f738cb881bb sp 7ffeff888f70 error 4 in lookup_file.so[7f738cb76000+2b000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1472115/+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 1472115] Re: autofs start fails: segfault at 0 ip 00007f738cb881bb sp 00007ffeff888f70 error 4 in lookup_file.so[7f738cb76000+2b000]
Segfault persists after reboot into latest kernel: Ubuntu 4.0.0-4.6-generic 4.0.7. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1472115 Title: autofs start fails: segfault at 0 ip 7f738cb881bb sp 7ffeff888f70 error 4 in lookup_file.so[7f738cb76000+2b000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1472115/+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 1468897] Re: multipath creates binding for Removable(USB) drives
This is a problem that comes from USB and (S)ATA devices showing up as
SCSI disks and the default multipath not really expecting those mixed
environments. The best way to handle this is to add blacklisting in
/etc/multipath.conf and the most flexible seems to key on vendor/product
like this:
blacklist {
device {
vendor "*"
product "*"
}
}
blacklist_exceptions {
device {
vendor "IBM"
product "*"
}
}
Possibly with a bit more detail in the exceptions allowing only certain
models or so...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1468897
Title:
multipath creates binding for Removable(USB) drives
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1468897/+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 1464860] Re: libsys-virt-perl FTBFS due to missing dependency libvirt-daemon in Ubuntu
For now this would be fixed by changing the dependency of libsys-virt- perl. ** Changed in: libvirt (Ubuntu) Status: New => Invalid ** Changed in: libsys-virt-perl (Ubuntu) Importance: Undecided => Medium ** Changed in: libsys-virt-perl (Ubuntu) Status: New => Confirmed ** Changed in: libsys-virt-perl (Ubuntu) Status: Confirmed => Triaged -- 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/1464860 Title: libsys-virt-perl FTBFS due to missing dependency libvirt-daemon in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsys-virt-perl/+bug/1464860/+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 1448985] Re: Ubuntu 14.04 LTS, 14.10, 15.04 guests do not boot to Unity from QEMU-KVM Ubuntu 14.04 LTS, 14.10, 15.04 hosts
I can reproduce this on a Trusty/14.04 host when using the i386 isos. The amd64 isos work. Also the i386 isos seem to work when not using kvm directly, but through libvirt. The main difference would be that this uses a VNX display instead of direct graphics using SDL (I believe). -- 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/1448985 Title: Ubuntu 14.04 LTS, 14.10, 15.04 guests do not boot to Unity from QEMU- KVM Ubuntu 14.04 LTS, 14.10, 15.04 hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1448985/+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 1426893] Re: qemu-kvm virtual machines crash with some but not all ubuntu flavors when vmvga video is selected
Initially it sounded a bit like some part of the graphics causes issues. But then this would hang or drop to a textual mode and not shut off the VM. If this is still happening, is the shut down immediate (like ripping out power) or slightly delayed (doing a shutdown sequence like if the power button was pressed on a real system)? There might be further info on the host in /var/log/syslog, /var/log/libvirt/libvirtd.log, and in a qemu log named after the VM name under /var/log/libvirt/qemu/. If you can still reproduce, the shutdown still, please attach the above logs here. Thanks. ** 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://bugs.launchpad.net/bugs/1426893 Title: qemu-kvm virtual machines crash with some but not all ubuntu flavors when vmvga video is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1426893/+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 1465034] Re: Guest shows black screen after woken up from "pmsuspended"
I think the RH bug talks about this fix: commit 4bc78a877252d772b983810a7d2c0be00e9be70e Author: Liu, Jinsong Date: Wed Sep 25 16:38:29 2013 + qemu: Adjust qemu wakeup -- 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/1465034 Title: Guest shows black screen after woken up from "pmsuspended" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1465034/+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 1459603] [NEW] libxl: Domain verification on edit fails with "Extra element os in interleave"
Public bug reported: Error reporting for XML validation is hopeless. What causes this is the fact that for HVM guests we have a loader element which is set to "hvmloader". But upstream wants this to be an absolute path to the binary. To make things a bit more "funny", the XML validation is only enabled by default for edit, not create. We need to replace "hvmloader" in the config by the full path, which is a bit complicated because the binary is provided in a versioned subdirectory. Since libvirt is only compiled against *one* version, we always have to try replacing older paths by newer ones as well as options without path by the current full path. To help with this upstream libvirt started to set LIBXL_FIRMWARE_DIR through dpk-config, but the current Xen (4.5) does not provide a xenlight.pc file. So we need to ensure the value is set by other means and then add code to change paths when post processing the configs. ** Affects: libvirt (Ubuntu) Importance: Medium Assignee: Stefan Bader (smb) Status: Triaged -- 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/1459603 Title: libxl: Domain verification on edit fails with "Extra element os in interleave" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1459603/+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 1459600] [NEW] libxl guest fails to start due to incorrect emulator setting
Public bug reported: Recent versions of libvirt are using the contents of the emulator option in the devices section. For a while we were using qemu-dm which was correct when the deprecated xm toolstack was in use. Since the option was not really used, there was no need to change this and using the xl stack (through libxl) was automatically picking up the right qemu path. But now we have to be correct. Upstream assumes a Xen specific binary and path which will at some point be provided through the pkg-config mechanism by libxen-dev. This is not needed for Deabian/Ubuntu because we make use of the qemu binary provided by the qemu package. So we only need to change two things (and they are not upstream-able because they are special): 1. for new configs always use /usr/bin/qemu-system-i386 2. when loading old configs replace qemu-dm by the new path ** Affects: libvirt (Ubuntu) Importance: High Assignee: Stefan Bader (smb) Status: Triaged ** Package changed: ubuntu => libvirt (Ubuntu) -- 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/1459600 Title: libxl guest fails to start due to incorrect emulator setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1459600/+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 1371634] Re: block devices appear twice
Quickly reading over the report I would think this is a result of the installer bug I reported as bug #1447167. The problem is that if you configure a system for multipath, it will present each path as an independent drive. And that causes a lot of confusion when a system has data on those and comes up without the multipath tools installed. To the OS this looks like multiple disks having the same filesystem UUIDs which conflict when creating disk-by/... links in /dev. Even worse LVM finds two PVs with the same ID and bails (iirc). I theory (with a lot knowledge and care) it is possible to install single-path and convert the whole system to multipath later. But frankly I think when the installer was told to enable multipath detect, it should automatically install the tools. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+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 1313450] Re: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default configuration
Please open a new bug report using "ubuntu-bug linux" if the problem involves the same stacktrace in dmesg. If not it is even more likely a different problem and you should start with "ubuntu-bug vsftp" (in any case the command should be run on the affected server). Also note, that this bug here was restricted to server installs running as paravirtualized guests on Xen. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/1313450 Title: Unable to start vsftpd on Ubuntu 14.04 (Amazon/EC2 or Xen) with default configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313450/+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 1425497] [NEW] libvirt update to 1.2.12 causes regressions for libx driver
Public bug reported: The move from libvirt 1.2.8 to 1.2.12 is causing two problems with the libxl driver: 1. xml validation will fail for loader and bootloader without full pathnames 2. the driver tries to identify the device model version by calling the emulator binary which was previously ignored Fixing this for now by allowing non absolute pathnames (starting with /) for loader and bootloader and fixing up configurations to use /usr/bin /qemu-system-i386 instead of qemu-dm (which does not exist anymore). This was done before while ignoring the emulator setting. ** Affects: libvirt (Ubuntu) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress -- 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/1425497 Title: libvirt update to 1.2.12 causes regressions for libx driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1425497/+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 897750] Re: libvirt/kvm problem with disk attach/detach/reattach on running virt
Serge, Scott, somehow I think we all left here in a confused state and I do not think we still have the problem (at least not Trusty). From my last comment it seems I did not even find something that I could change for Precise. For now I would unassign myself and maybe this report should be closed if Justin has no objections. ** Changed in: qemu-kvm (Ubuntu) Assignee: Stefan Bader (smb) => (unassigned) -- 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/897750 Title: libvirt/kvm problem with disk attach/detach/reattach on running virt To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/897750/+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 931425] Re: Cannot specify a default bridge with xen xl stack
Closing because this is actually fixed by now. Just forgot about that bug. ** Changed in: xen (Ubuntu) Status: Triaged => Fix Released ** Changed in: xen (Ubuntu) Assignee: Stefan Bader (smb) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/931425 Title: Cannot specify a default bridge with xen xl stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/931425/+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 1394327] Re: unmapping of persistent grants in qemu
Upgraded a Trusty and Utopic host with qemu from proposed (after also upgrading xen for bug #1396068). After that defined a PV guest using a qcow2 image and booted that. No errors in dmesg and both VMs started. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1394327 Title: unmapping of persistent grants in qemu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1394327/+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 1396068] Re: [Xen/xl] dom0 needs to run qemu for qcow access
Upgraded a Trusty and Utopic host to the proposed version and verified that the qemu process was running in dom0 after that. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1396068 Title: [Xen/xl] dom0 needs to run qemu for qcow access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1396068/+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 1401148] Re: Re/starting an lxc container corrupts all network namespaces on the same physical host
I would have assumed systemd is on neither. Since it seems to be the same all the way since Trusty (at least). -- 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/1401148 Title: Re/starting an lxc container corrupts all network namespaces on the same physical host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401148/+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 1401148] Re: Re/starting an lxc container corrupts all network namespaces on the same physical host
lxc-start.strace.3093:clone(child_stack=0x7fff7fbc0290,
flags=CLONE_NEWNS|CLONE_NEWUTS|CLONE_NEWIPC|CLONE_NEWPID|CLONE_NEWNET|SIGCHLD)
= 3131
lxc-start.strace.3093:open("/proc/3131/ns/net", O_RDONLY) = 16
lxc-start.strace.3093:waitid(P_PID, 3131, {}, WNOHANG|WEXITED|WNOWAIT, NULL) =
--
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/1401148
Title:
Re/starting an lxc container corrupts all network namespaces on the
same physical host
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401148/+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 1401148] Re: Re/starting an lxc container corrupts all network namespaces on the same physical host
This is the output of "apparmor_parser -p /etc/apparmor.d/usr.bin.lxc- start" on Vivid with 3.16 kernel. ** Attachment added: "aa-parser.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401148/+attachment/4278746/+files/aa-parser.txt -- 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/1401148 Title: Re/starting an lxc container corrupts all network namespaces on the same physical host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401148/+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 1401148] Re: Re/starting an lxc container corrupts all network namespaces on the same physical host
When stracing lxc-start one of the sub-processes is doing the access. This is the strace of that sub-process. ** Attachment added: "lxc-start.strace.3131" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401148/+attachment/4278745/+files/lxc-start.strace.3131 -- 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/1401148 Title: Re/starting an lxc container corrupts all network namespaces on the same physical host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401148/+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 1401148] Re: Re/starting an lxc container corrupts all network namespaces on the same physical host
Stop the bot. -- 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/1401148 Title: Re/starting an lxc container corrupts all network namespaces on the same physical host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401148/+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 1401148] Re: Re/starting an lxc container corrupts all network namespaces on the same physical host
Stop the bot. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1401148 Title: Re/starting an lxc container corrupts all network namespaces on the same physical host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401148/+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 1401148] Re: Re/starting an lxc container corrupts all network namespaces on the same physical host
So for now I added also a task for the kernel, though the truth (if such a thing exists) could be somewhere between. Serge, Stephane, what we probably need to figure out is what exactly lxc-start tries to get done when slave mounting /run/netns. And somehow it might be possible that it needs improvement for the case that this is denied or fails. Looking at it from the outside it feels like going on assuming it got its own space but actually continuing to use the host space. The other thing would be that this sound like lxc-start would require a rule to actually allow it to do that mount of /run/netns. -- 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/1401148 Title: Re/starting an lxc container corrupts all network namespaces on the same physical host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401148/+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 1401148] Re: Re/starting an lxc container corrupts all network namespaces on the same physical host
** Also affects: linux (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/1401148 Title: Re/starting an lxc container corrupts all network namespaces on the same physical host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401148/+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 1396068] Re: [Xen/xl] dom0 needs to run qemu for qcow access
SRU justification: Impact: Without starting a QEMU instance for dom0 it is not possible to use advanced disk image types for PV guests because pygrub then cannot peek into them to pick kernel images to start. However this setup is the default for nova-xen (openstack). Fix: Picking up changes from Debian (and now also in Vivid already) to the init script which starts and stops QEMU for dom0. Testcase: After package upgrade and subsequent reboots there is a qemu- system-i386 process attached to dom0. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1396068 Title: [Xen/xl] dom0 needs to run qemu for qcow access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1396068/+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
