ClaesBas wrote: > Could somebody who understand this bit of code > look at connection.py:520. > >>From my ~/.virt-manager/virt-manager.log > > [Mon, 19 May 2008 10:40:55 virt-manager 28993] ERROR (virt-manager:141) > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/details.py", line 675, in > refresh_resources > self.page_refresh(details.get_current_page()) > File "/usr/share/virt-manager/virtManager/details.py", line 693, in > page_refresh > self.refresh_config_cpu() > File "/usr/share/virt-manager/virtManager/details.py", line 730, in > refresh_config_cpu > cpu_max = self.vm.get_connection().get_max_vcpus(self.vm.get_type()) > File "/usr/share/virt-manager/virtManager/connection.py", line 520, in > get_max_vcpus > return virtinst.util.get_max_vcpus(self.vmm, type) > TypeError: get_max_vcpus() takes exactly 1 argument (2 given) > > > I think it should be (connection.py:520): > return virtinst.util.get_max_vcpus(type) > > When I changed to the above, all errors was gone.... > > > Regards > Claes > A function changed in the virtinst library, and virt-manager is making use of the newer version. If you are using upstream virt-manager, its always a good idea to use upstream virtinst, as they are very closely tied. http://hg.et.redhat.com/virt/applications/virtinst--devel - Cole _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/et-mgmt-tools
