[Bug 614322] Re: libvirt not recognizing NUMA architecture

2011-11-10 Thread Ralf Spenneberg
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

[Bug 614322] Re: libvirt not recognizing NUMA architecture

2011-11-10 Thread Ralf Spenneberg
** 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

[Bug 614322] Re: libvirt not recognizing NUMA architecture

2011-11-14 Thread Ralf Spenneberg
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

[Bug 904014] Re: [MIR] netcf

2012-08-08 Thread Ralf Spenneberg
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

[Bug 1028585] Re: Memory allocation problem with ipvsadm

2012-08-15 Thread Ralf Spenneberg
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

[Bug 1028585] Re: Memory allocation problem with ipvsadm

2012-08-15 Thread Ralf Spenneberg
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