[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 b

[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

[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

[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

[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

[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

[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

[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

[Bug 1551643] [NEW] libvirt-bin should also use provides libvirt-daemon

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

[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)

[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

[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

[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

[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.

[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

[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

[Bug 1538049] [NEW] xenstore crashes with SIGBUS in domain_can_read()

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: S

[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

[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

[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)

[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

[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-> U

[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"

[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

[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

[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 failu

[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:

[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

[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

[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: (u

[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

[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

[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.

[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

[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

[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

[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

[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

[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

[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

[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)

[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

[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

[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:

[Bug 1496057] Re: The dep-8 test of iscsitarget should check the kernel module as well

sty) 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/bug

[Bug 1496057] [NEW] The dep-8 test of iscsitarget should check the kernel module as well

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 ** Chan

[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

[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

[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

[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

[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

[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.

[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:

[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:

[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

[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

[Bug 1483214] Re: ipmi_si module spams kernel log with ipmi_si 00:05: Could not set the global enables: 0xcc.

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

[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.

[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

[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

[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

[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

[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

[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

[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 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

[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

[Bug 1476666] [NEW] [MRE] Rebase Xen-4.4 to upstream stable 4.4.2

** 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

[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

[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: 马文霜 kevin...@tencent.com 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

[Bug 1472500] Re: virt-manager. restore windows vm- Unknown savevm section type 5

) 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

[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

[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

[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

[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

[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

[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

[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:

[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 **

[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

[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

[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 jinsong@intel.com 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

[Bug 1459600] [NEW] libxl guest fails to start due to incorrect emulator setting

) 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

[Bug 1459603] [NEW] libxl: Domain verification on edit fails with Extra element os in interleave

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

[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

[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

[Bug 1425497] [NEW] libvirt update to 1.2.12 causes regressions for libx driver

(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

[Bug 897750] Re: libvirt/kvm problem with disk attach/detach/reattach on running virt

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

[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

[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

[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

[Bug 1394327] Re: unmapping of persistent grants in qemu

SRU justification: Impact: As soon as dom0 starts qemu it will try to locally attach QCOW(2) images in case a PV guest is using those. This results in the described errors and sometimes the whole host is rendered unusable. Fix: Cherry picking an upstream patch (which was done already for Vivid)

[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

[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

[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

[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

[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

[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

[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

[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

  1   2   3   4   >