[Bug 1610762] [NEW] ubi-partman crashed 16.04.1 install
Public bug reported: Got this error attempting to apply automatic partitioning during 16.04.1 install. System is running in legacy bios mode with a raid5 intel rapid storage technology array on a gigabyte GA-170N motherboard. Windows 10 is already installed with 3 existing partitions (boot/recovery, C:\ - system, D:\ - data). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CasperVersion: 1.376 Date: Mon Aug 8 01:15:11 2016 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.2 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610762 Title: ubi-partman crashed 16.04.1 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1610762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574883] Re: libvirt not configured with numad support
Hi James, True that static NUMA placement would work (well, it would if this was fixed: https://bugs.launchpad.net/nova/+bug/1517006). But the issue with the static approach is that it requires flavor definitions and imposes stricter scheduling constraints in order to meet the pre-defined flavor NUMA topology and policy. We're doing science computing and hpc on OpenStack (using libvirt/kvm on ubuntu as hypervisor) and have done a bit of performance testing with strict NUMA policy versus numad. We've done some benchmarking of whole- node VM instances (as would be the case with most hpc workloads) and found that for the most part numad does a near enough job to static pinning (i.e., setting the guest up to mirror the host) that we would prefer to just use numad and get more performance without compromising scheduling flexibility. We'd also do this in our general purpose zones/cells where we have all sorts of mixed research workloads. Hope that helps explain it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574883 Title: libvirt not configured with numad support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1574883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574883] [NEW] libvirt not configured with numad support
Public bug reported: numad is now packaged and shipped by Ubuntu. But Ubuntu libvirt packages (which is presumably where most end-user/admins/deployers would be interested in numad support) are not configured with numad support... curl -s https://launchpadlibrarian.net/253913675/buildlog_ubuntu-xenial-amd64.libvirt_1.3.1-1ubuntu10_BUILDING.txt.gz | gunzip | nl | grep numad 3249 checking for numad... no 3454 configure: numad: no ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: numad xenial ** Summary changed: - not configured with numad support + libvirt not configured with numad support -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574883 Title: libvirt not configured with numad support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1574883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1379340] Re: qemu-kvm guest panic for AMD smp trusty guests
Not keen on providing apport info as this is a production system with multiple tenants and we have no agreement with Canonical. The info here and verification from others indicates this is a simple bug to reproduce and not specific to our systems. -- 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/1379340 Title: qemu-kvm guest panic for AMD smp trusty guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1379340/+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 1379340] Re: qemu-kvm guest panic for AMD smp trusty guests
Here's an example of an affected qemu command, as already pointed out the relevant parts are the -cpu host and -smp n where n1. qemu-system-x86_64 -enable-kvm -name instance-000173d4 -S -machine pc-1.0,accel=kvm,usb=off -cpu host -m 16384 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid e3ec1854-0b89-4384-*** -smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack Nova,version=1-2013.2.2-a101-g1a048c5-1,serial=,uuid=e3ec1854-0b89-4384-*** -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-000173d4.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/nova/instances/e3ec1854-0b89-4384-9771-88c26764eef9/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/var/lib/nova/instances/e3ec1854 -0b89-4384-9771-88c26764eef9/disk.local,if=none,id=drive-virtio-disk1,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1 -drive file=rbd:nova/volume-439f230a-12fa-4538-ab26-01c3f6617ec7:id=nova:key=***==:auth_supported=cephx\;none:mon_host=118.138***,if=none,id=drive-virtio-disk2,format=raw,serial=***,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk2,id=virtio-disk2 -netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=31 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:***,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/var/lib/nova/instances/e3ec1854-0b89-4384-9771-88c26764eef9/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:1 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x 6 -- 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/1379340 Title: qemu-kvm guest panic for AMD smp trusty guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1379340/+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 1379340] Re: qemu-kvm guest panic for AMD smp trusty guests
Not keen on providing apport info as this is a production system with multiple tenants and we have no agreement with Canonical. The info here and verification from others indicates this is a simple bug to reproduce and not specific to our systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1379340 Title: qemu-kvm guest panic for AMD smp trusty guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1379340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1379340] Re: qemu-kvm guest panic for AMD smp trusty guests
Here's an example of an affected qemu command, as already pointed out the relevant parts are the -cpu host and -smp n where n1. qemu-system-x86_64 -enable-kvm -name instance-000173d4 -S -machine pc-1.0,accel=kvm,usb=off -cpu host -m 16384 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid e3ec1854-0b89-4384-*** -smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack Nova,version=1-2013.2.2-a101-g1a048c5-1,serial=,uuid=e3ec1854-0b89-4384-*** -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-000173d4.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/nova/instances/e3ec1854-0b89-4384-9771-88c26764eef9/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/var/lib/nova/instances/e3ec1854 -0b89-4384-9771-88c26764eef9/disk.local,if=none,id=drive-virtio-disk1,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1 -drive file=rbd:nova/volume-439f230a-12fa-4538-ab26-01c3f6617ec7:id=nova:key=***==:auth_supported=cephx\;none:mon_host=118.138***,if=none,id=drive-virtio-disk2,format=raw,serial=***,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk2,id=virtio-disk2 -netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=31 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:***,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/var/lib/nova/instances/e3ec1854-0b89-4384-9771-88c26764eef9/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:1 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x 6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1379340 Title: qemu-kvm guest panic for AMD smp trusty guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1379340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1379340] [NEW] qemu-kvm guest panic for smp trusty guests
Public bug reported: Just upgraded OpenStack compute hosts in our public cloud (using qemu- kvm via libvirt) from Precise to Trusty (14.04.1), now on kernel 3.13.0-36-generic with qemu-kvm 2.0.0+dfsg-2ubuntu1.5. Following the upgrade, whenever we try to start an smp/multicore Trusty guest (existing or new), we run into this panic [1] inside the guest just towards the end of boot. This happens consistently for smp guests using the Trusty kernel (i.e., it also affects earlier Ubuntus using the HWE kernel from Trusty but not their native versions). I didn't have any other distro images to hand with 3.13.x kernels, but none of the others I tested were affected (in the 3.2 - 3.16 kernel range). There are scarce similar reports out there, but the one we did find pointed to a CPU feature as the trigger. We were running these hosts with libvirt cpu mode set to host-passthrough (so qemu starts with -cpu host), on AMD 6200 6300 Opteron hardware. Switching the guest domains to use cpu mode host-model instead works around the issue and is perfectly acceptable for most of our users. We have various other Intel compute hosts and they don't seem to be affected. (1) [ 11.256924] divide error: [#1] SMP [ 11.258133] Modules linked in: kvm_amd kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw lp parport psmouse floppy [ 11.260228] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-36-generic #63-Ubuntu [ 11.260228] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 01/01/2011 [ 11.260228] task: 81c15480 ti: 81c0 task.ti: 81c0 [ 11.260228] RIP: 0010:[8104ed58] [8104ed58] kvm_unlock_kick+0xa8/0x100 [ 11.260228] RSP: 0018:88023fc03c98 EFLAGS: 00010046 [ 11.260228] RAX: 0005 RBX: RCX: 0001 [ 11.260228] RDX: 81eaf408 RSI: RDI: [ 11.260228] RBP: 88023fc03cb8 R08: 81eaf400 R09: [ 11.260228] R10: 880037612cc0 R11: ea0002eb0a00 R12: 8800374a33c0 [ 11.260228] R13: 0020 R14: 0001 R15: 0286 [ 11.260228] FS: 7f1e8b538740() GS:88023fc0() knlGS: [ 11.260228] CS: 0010 DS: ES: CR0: 8005003b [ 11.260228] CR2: 7f1e8ae09d50 CR3: 01c0e000 CR4: 000406f0 [ 11.260228] Stack: [ 11.260228] 0286 0001 0001 00c3 [ 11.260228] 88023fc03cc8 81717ed6 88023fc03ce0 8172641a [ 11.260228] 8800374a33c0 88023fc03d18 810aaeb0 88023295e000 [ 11.260228] Call Trace: [ 11.260228] IRQ [ 11.260228] [81717ed6] __ticket_unlock_slowpath+0x24/0x34 [ 11.260228] [8172641a] _raw_spin_unlock_irqrestore+0x3a/0x40 [ 11.260228] [810aaeb0] __wake_up_sync_key+0x50/0x60 [ 11.260228] [8160ca5a] sock_def_readable+0x3a/0x70 [ 11.260228] [816fda0a] packet_rcv+0x2fa/0x430 [ 11.260228] [816228b0] __netif_receive_skb_core+0x360/0x840 [ 11.260228] [81622da8] __netif_receive_skb+0x18/0x60 [ 11.260228] [81622e13] netif_receive_skb+0x23/0x90 [ 11.260228] [815288d4] virtnet_poll+0x4d4/0x850 [ 11.260228] [81623192] net_rx_action+0x152/0x250 [ 11.260228] [8106cbac] __do_softirq+0xec/0x2c0 [ 11.260228] [8106d0f5] irq_exit+0x105/0x110 [ 11.260228] [817312d6] do_IRQ+0x56/0xc0 [ 11.260228] [81726a6d] common_interrupt+0x6d/0x6d [ 11.260228] EOI [ 11.260228] [8104f596] ? native_safe_halt+0x6/0x10 [ 11.260228] [8101c62f] default_idle+0x1f/0xc0 [ 11.260228] [8101cef6] arch_cpu_idle+0x26/0x30 [ 11.260228] [810bed95] cpu_startup_entry+0xc5/0x290 [ 11.260228] [8170ca77] rest_init+0x77/0x80 [ 11.260228] [81d35f6b] start_kernel+0x433/0x43e [ 11.260228] [81d35941] ? repair_env_string+0x5c/0x5c [ 11.260228] [81d35120] ? early_idt_handlers+0x120/0x120 [ 11.260228] [81d355ee] x86_64_start_reservations+0x2a/0x2c [ 11.260228] [81d35733] x86_64_start_kernel+0x143/0x152 [ 11.260228] Code: 66 44 39 e8 75 bd 0f b6 35 f6 06 e6 00 40 84 f6 75 2a 83 05 06 07 e6 00 01 48 c7 c0 6a b0 00 00 31 db 0f b7 0c 01 b8 05 00 00 00 0f 01 c1 0f 1f 44 00 00 5b 41 5c 41 5d 41 5e 5d c3 89 f0 31 c9 [ 11.260228] RIP [8104ed58] kvm_unlock_kick+0xa8/0x100 [ 11.260228] RSP 88023fc03c98 [ 11.260228] ---[ end trace f1c26ff24745b331 ]--- [ 11.260228] Kernel panic - not syncing: Fatal exception in interrupt [ 11.260228] Shutting down cpus with NMI ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- 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/1379340 Title: qemu-kvm
[Bug 1379340] [NEW] qemu-kvm guest panic for smp trusty guests
Public bug reported: Just upgraded OpenStack compute hosts in our public cloud (using qemu- kvm via libvirt) from Precise to Trusty (14.04.1), now on kernel 3.13.0-36-generic with qemu-kvm 2.0.0+dfsg-2ubuntu1.5. Following the upgrade, whenever we try to start an smp/multicore Trusty guest (existing or new), we run into this panic [1] inside the guest just towards the end of boot. This happens consistently for smp guests using the Trusty kernel (i.e., it also affects earlier Ubuntus using the HWE kernel from Trusty but not their native versions). I didn't have any other distro images to hand with 3.13.x kernels, but none of the others I tested were affected (in the 3.2 - 3.16 kernel range). There are scarce similar reports out there, but the one we did find pointed to a CPU feature as the trigger. We were running these hosts with libvirt cpu mode set to host-passthrough (so qemu starts with -cpu host), on AMD 6200 6300 Opteron hardware. Switching the guest domains to use cpu mode host-model instead works around the issue and is perfectly acceptable for most of our users. We have various other Intel compute hosts and they don't seem to be affected. (1) [ 11.256924] divide error: [#1] SMP [ 11.258133] Modules linked in: kvm_amd kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw lp parport psmouse floppy [ 11.260228] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-36-generic #63-Ubuntu [ 11.260228] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 01/01/2011 [ 11.260228] task: 81c15480 ti: 81c0 task.ti: 81c0 [ 11.260228] RIP: 0010:[8104ed58] [8104ed58] kvm_unlock_kick+0xa8/0x100 [ 11.260228] RSP: 0018:88023fc03c98 EFLAGS: 00010046 [ 11.260228] RAX: 0005 RBX: RCX: 0001 [ 11.260228] RDX: 81eaf408 RSI: RDI: [ 11.260228] RBP: 88023fc03cb8 R08: 81eaf400 R09: [ 11.260228] R10: 880037612cc0 R11: ea0002eb0a00 R12: 8800374a33c0 [ 11.260228] R13: 0020 R14: 0001 R15: 0286 [ 11.260228] FS: 7f1e8b538740() GS:88023fc0() knlGS: [ 11.260228] CS: 0010 DS: ES: CR0: 8005003b [ 11.260228] CR2: 7f1e8ae09d50 CR3: 01c0e000 CR4: 000406f0 [ 11.260228] Stack: [ 11.260228] 0286 0001 0001 00c3 [ 11.260228] 88023fc03cc8 81717ed6 88023fc03ce0 8172641a [ 11.260228] 8800374a33c0 88023fc03d18 810aaeb0 88023295e000 [ 11.260228] Call Trace: [ 11.260228] IRQ [ 11.260228] [81717ed6] __ticket_unlock_slowpath+0x24/0x34 [ 11.260228] [8172641a] _raw_spin_unlock_irqrestore+0x3a/0x40 [ 11.260228] [810aaeb0] __wake_up_sync_key+0x50/0x60 [ 11.260228] [8160ca5a] sock_def_readable+0x3a/0x70 [ 11.260228] [816fda0a] packet_rcv+0x2fa/0x430 [ 11.260228] [816228b0] __netif_receive_skb_core+0x360/0x840 [ 11.260228] [81622da8] __netif_receive_skb+0x18/0x60 [ 11.260228] [81622e13] netif_receive_skb+0x23/0x90 [ 11.260228] [815288d4] virtnet_poll+0x4d4/0x850 [ 11.260228] [81623192] net_rx_action+0x152/0x250 [ 11.260228] [8106cbac] __do_softirq+0xec/0x2c0 [ 11.260228] [8106d0f5] irq_exit+0x105/0x110 [ 11.260228] [817312d6] do_IRQ+0x56/0xc0 [ 11.260228] [81726a6d] common_interrupt+0x6d/0x6d [ 11.260228] EOI [ 11.260228] [8104f596] ? native_safe_halt+0x6/0x10 [ 11.260228] [8101c62f] default_idle+0x1f/0xc0 [ 11.260228] [8101cef6] arch_cpu_idle+0x26/0x30 [ 11.260228] [810bed95] cpu_startup_entry+0xc5/0x290 [ 11.260228] [8170ca77] rest_init+0x77/0x80 [ 11.260228] [81d35f6b] start_kernel+0x433/0x43e [ 11.260228] [81d35941] ? repair_env_string+0x5c/0x5c [ 11.260228] [81d35120] ? early_idt_handlers+0x120/0x120 [ 11.260228] [81d355ee] x86_64_start_reservations+0x2a/0x2c [ 11.260228] [81d35733] x86_64_start_kernel+0x143/0x152 [ 11.260228] Code: 66 44 39 e8 75 bd 0f b6 35 f6 06 e6 00 40 84 f6 75 2a 83 05 06 07 e6 00 01 48 c7 c0 6a b0 00 00 31 db 0f b7 0c 01 b8 05 00 00 00 0f 01 c1 0f 1f 44 00 00 5b 41 5c 41 5d 41 5e 5d c3 89 f0 31 c9 [ 11.260228] RIP [8104ed58] kvm_unlock_kick+0xa8/0x100 [ 11.260228] RSP 88023fc03c98 [ 11.260228] ---[ end trace f1c26ff24745b331 ]--- [ 11.260228] Kernel panic - not syncing: Fatal exception in interrupt [ 11.260228] Shutting down cpus with NMI ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1379340 Title: qemu-kvm guest panic for smp
[Bug 1262641] Re: virsh save and virsh managedsave failed with cpu mode = host-passthrough
Serge, sorry if I've missed an obvious answer to this... but, where did you push the updated libvirt? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262641 Title: virsh save and virsh managedsave failed with cpu mode = host- passthrough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1262641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262641] Re: virsh save and virsh managedsave failed with cpu mode = host-passthrough
Oh I see: https://launchpad.net/ubuntu/+source/libvirt/1.2.1-0ubuntu4 We really need a package compatible with Precise to fix this. We may be able to test the fix if we can cherry-pick the trusty version of libvirt without conflict, however we'll still require a backport to fix this in production. Will perhaps have to build our own package if a Precise backport is unavailable... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262641 Title: virsh save and virsh managedsave failed with cpu mode = host- passthrough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1262641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262641] Re: virsh save and virsh managedsave failed with cpu mode = host-passthrough
I am now thoroughly confused... so, we should try Vlad's patch and ignore Serge's updated package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262641 Title: virsh save and virsh managedsave failed with cpu mode = host- passthrough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1262641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 222163] Re: Xorg crashes when using two monitors set up by aticonfig (BigDesktop mode)
** Also affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New -- Xorg crashes when using two monitors set up by aticonfig (BigDesktop mode) https://bugs.launchpad.net/bugs/222163 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 222163] Re: Xorg crashes when using two monitors set up by aticonfig (BigDesktop mode)
Confirming, as requested, that this bug is still present in Intrepid using xorg-driver-fglrx(2:8.543-0ubuntu4). No surprises there. Also attached ** Attachment added: lspci-vvnn http://launchpadlibrarian.net/19523323/lspci-vvnn -- Xorg crashes when using two monitors set up by aticonfig (BigDesktop mode) https://bugs.launchpad.net/bugs/222163 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 222163] Re: Xorg crashes when using two monitors set up by aticonfig (BigDesktop mode)
** Attachment added: xorg.conf http://launchpadlibrarian.net/19523339/xorg.conf -- Xorg crashes when using two monitors set up by aticonfig (BigDesktop mode) https://bugs.launchpad.net/bugs/222163 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 222163] Re: Xorg crashes when using two monitors set up by aticonfig (BigDesktop mode)
** Attachment added: Xorg.0.log http://launchpadlibrarian.net/19523350/Xorg.0.log -- Xorg crashes when using two monitors set up by aticonfig (BigDesktop mode) https://bugs.launchpad.net/bugs/222163 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 222163] Re: Xorg crashes when using two monitors set up by aticonfig (BigDesktop mode)
Attached Xorg.0.log.old has traceback from a crash caused by this bug. Steps to reproduce: 1. Install any fglrx driver 2. Attach secondary monitor and setup a big desktop using either aticonfig or amdcccle 3. Enable desktop effects 4. Left click anywhere on the secondary display (if another window already had focus a second click may be required) CRASH ** Attachment added: Xorg crash log http://launchpadlibrarian.net/19523395/Xorg.0.log.old -- Xorg crashes when using two monitors set up by aticonfig (BigDesktop mode) https://bugs.launchpad.net/bugs/222163 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 222163] Re: Xorg crashes when using two monitors set up by aticonfig (BigDesktop mode)
I see you've posted this to ATI forums too, here's hoping we get an answer. I've taken to running a maximised window in the background on the second head just to avoid accidentally crashing the xserver. On Wed, Oct 15, 2008 at 12:23 AM, linkx [EMAIL PROTECTED] wrote: Can anyone suggest where to post this bug so that it gets the attention of the appropriate people? I have asked the Compiz-Fusion folk, since it is directly related to Desktop Effects. You can view the thread here: http://forum.compiz-fusion.org/showthread.php?p=66888#post66888 Let's get this fixed in a future release! -- Xorg crashes when using two monitors set up by aticonfig (BigDesktop mode) https://bugs.launchpad.net/bugs/222163 You received this bug notification because you are a direct subscriber of the bug. -- In science one tries to tell people, in such a way as to be understood by everyone, something that no one ever knew before. But in poetry, it's the exact opposite. - Paul Dirac -- Xorg crashes when using two monitors set up by aticonfig (BigDesktop mode) https://bugs.launchpad.net/bugs/222163 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 222163] Re: Xorg crashes when using two monitors set up by aticonfig (BigDesktop mode)
Confirmed here also (X1600 Mobility). I have had this problem with Compiz and fglrx since starting to use them, can also confirm that it persists with the last few driver releases from AMD (Catalyst 8.7,8.8,8.9) and Compiz 0.7.6. Happy to provide more info if somebody is actually going to look into this - why no response since April!? -- Xorg crashes when using two monitors set up by aticonfig (BigDesktop mode) https://bugs.launchpad.net/bugs/222163 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
