Pkg xen devel - Jun 2013 - Bug#711273: xen-hypervisor-4.2-amd64: Acn't re-create domains after migration from 4.1 to 4.2

Package: xen-hypervisor-4.2-amd64
Version: 4.2.1-2
Severity: critical
Tags: upstream
Justification: breaks the whole system

Dear Maintainer,

After migration from Xen 4.1 to 4.2 all VMs have disapeared and I am unable to
"re-create" my VM from the configfiles.
When I try "xm new com-web" i get a python message :

Using config file "./com-web".
Error: 'NoneType' object has no attribute 'rfind'

Is it a problem of Python version ?

python --version
Python 2.7.5+

Regards

JP P








-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.9.4-x (SMP w/2 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.2-amd64 depends on no packages.

Versions of packages xen-hypervisor-4.2-amd64 recommends:
ii  xen-utils-4.2  4.2.1-2

Versions of packages xen-hypervisor-4.2-amd64 suggests:
ii  xen-docs-4.2  4.2.1-2

-- no debconf information

severity -1 important

On Thu, Jun 06, 2013 at 12:57:56AM +0200, JP Pozzi
wrote:
> Severity: critical
> Justification: breaks the whole system
Please explain how it breaks the system and not only itself?
> After migration from Xen 4.1 to 4.2 all VMs have disapeared and I am unable
to
> "re-create" my VM from the configfiles.
> When I try "xm new com-web" i get a python message :
Please provide the config file in question and the contents of
/var/log/xen/xend.log.
> Is it a problem of Python version ?
Unlikely.

The easiest fix is to use the new stack called xl by modifying
/etc/default/xen with TOOLSTACK=xl. This will get the default in the
near future.

Bastian

-- 
	"What terrible way to die."
	"There are no good ways."
		-- Sulu and Kirk, "That Which Survives", stardate unknown