On Wed, Jul 08, 2009 at 01:28:18AM +0200, Csillag Kristof wrote: > > Package: xen-utils-3.4 > Version: 3.4.0-1 > Severity: critical > Justification: breaks unrelated software > > After installing xen-utils-3.4 besides my existing xen-3.2 system, > I could not start xend-3.2 anymore. The message I was getting is this: > > "Failed to initialize dom0 state." > > As far as I know, xen 3.2 and 3.4 are supposed to be able to live > peacefully on the same system. (The hypervisor and the utils are > in differently named packages.) > > However, after the first experiment with 3.4 (which failed because > of a different bug), I could not go back to xen 3.2. > > I rebooted to the correct hypervisor, and ran the current version > of tools, but it did not work any more. (I did not have time > to track down the reason this time.) > > This causes quite a problem, since the new 3.4 version can not > be considered a drop-in replacement of the older 3.2 (HVM support > is disabled, for example), so this caused a sesiour problem, > at least for me. >
What do you mean with HVM support is disabled? Xen 3.4.0 definitely supports HVM guests. -- Pasi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
