[Bug 1028585] Re: Memory allocation problem with ipvsadm
I can confirm it on amd64 using ipvsadm 1.25.clean-1ubuntu5 linux-image-3.2.0-23-generic and linux-image-3.2.0-29-generic -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipvsadm in Ubuntu. https://bugs.launchpad.net/bugs/1028585 Title: Memory allocation problem with ipvsadm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/1028585/+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 1028585] Re: Memory allocation problem with ipvsadm
Further information: ipvsadm -A -t 192.168.10.21:80 -s rr works, while ipvsadm -A -t 192.168.10.21:80 -s -rr (obviously wrong syntax) creates a memory allocation error. Apparently whenever a syntax or semantic error occurs ipvsadm generates an memory allocation error. So generate a virtual server: ipvsadm -A -t 10.131.208.21:80 -rr Add a real server with masquerading: ipvsadm -a -t 10.131.208.21.80 -r 192.168.0.5 -w 1 -m Edit the real server without specifying the -m ipvsadm -e -t 10.131.208.21.80 -r 192.168.0.5 -w 0 -m memory allocation problem ipvsadm -e -t -t 10.131.208.21.80 -r 192.168.0.5 -w 0 -m works. Apparently syntactical errors always generate a memory allocation error. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipvsadm in Ubuntu. https://bugs.launchpad.net/bugs/1028585 Title: Memory allocation problem with ipvsadm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/1028585/+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 904014] Re: [MIR] netcf
Thanks a lot for your great work. Is it possible to make the same move for Precise? Precise being LTS will be much longer around than Quantal. We would really appreciate it if netcf could be moved to main for 12.04.1 as it was planned originally Any thoughts? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to netcf in Ubuntu. https://bugs.launchpad.net/bugs/904014 Title: [MIR] netcf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcf/+bug/904014/+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 614322] Re: libvirt not recognizing NUMA architecture
I have discussed the matter with Guido Günther from the Debian team. After some testing he reenabled the numa feature in the debian package: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648323 Would you like to follow him? ** Bug watch added: Debian Bug tracker #648323 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648323 -- 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/614322 Title: libvirt not recognizing NUMA architecture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/614322/+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 614322] Re: libvirt not recognizing NUMA architecture
I can confirm this and I am very dissapointed that still after more than a year this issue has not been fixed. I am currently running Ubuntu precise (development, the next lts) on HP DL 585 G2 with 4 Dual Cores and thus 4 Numa cells. Numactl shows the hardware: # numactl --show policy: default preferred node: current physcpubind: 0 1 2 3 4 5 6 7 cpubind: 0 1 2 3 nodebind: 0 1 2 3 membind: 0 1 2 3 virsh does not display the numa information: # virsh nodeinfo CPU model: x86_64 CPU(s): 8 CPU frequency: 1000 MHz CPU socket(s): 4 Core(s) per socket: 2 Thread(s) per core: 1 NUMA cell(s):1 Memory size: 32948228 kB # virsh freecell 0 error: this function is not supported by the connection driver: NUMA memory information not available on this platform Just using numactl is no option if the guests are to be migrated. The numa-placement needs to be handled by libvirt! -- 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/614322 Title: libvirt not recognizing NUMA architecture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/614322/+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 614322] Re: libvirt not recognizing NUMA architecture
** Changed in: libvirt (Ubuntu) Status: Opinion = Confirmed -- 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/614322 Title: libvirt not recognizing NUMA architecture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/614322/+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
