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
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
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
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
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
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
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
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
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
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
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
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
** 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
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
** 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
** 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
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
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
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
19 matches
Mail list logo
