Your message dated Sat, 14 Jul 2012 15:12:29 -0600 with message-id <[email protected]> and subject line Re: Bug#641098: VM does not launch has caused the Debian Bug report #641098, regarding xen-hypervisor-4.1-amd64: VM does not launch to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 641098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641098 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: xen-hypervisor-4.1-amd64 Version: 4.1.1-2 Severity: normal Dear Maintainer, I can't launch any VM when I use one of the latest kernel versions (3.1) with the following messages : xm start com-deb30 Error: Failed to query current memory allocation of dom0. While launching through "virt-manager" I get same kind of messages: Erreur lors du démarrage du domaine: POST operation failed: xend_post: error from xen daemon: (xend.err 'Failed to query current memory allocation of dom0.') Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 44, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1050, in startup self._backend.create() File "/usr/lib/python2.6/dist-packages/libvirt.py", line 507, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: POST operation failed: xend_post: error from xen daemon: (xend.err 'Failed to query current memory allocation of dom0.') All is working with all kernel versions < 3.1 Regards JP P -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-rc4 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash xen-hypervisor-4.1-amd64 depends on no packages. Versions of packages xen-hypervisor-4.1-amd64 recommends: ii xen-utils-4.1 4.1.1-2 Versions of packages xen-hypervisor-4.1-amd64 suggests: pn xen-docs-4.1 <none> -- no debconf information
--- End Message ---
--- Begin Message ---On Sat, 2012-07-14 at 17:03 -0400, [email protected] wrote: > That nasty bug does not exists any more with 3.2, 3.3, 3.4 and even > 3.5-rc6 (I try it yesterday). I try all newer kernels without any > problem. I think it was only a 3.1 related bug. > With all newer kernels all VMs are starting as usual. Thanks for checking, I'm therefore closing this bug. Ian.
--- End Message ---
