Pkg xen devel - Sep 2006 - Bug#385934: Fixed by using xen-hypervisor-3.0-unstable-1-i386

Hi,

I got exactly, the same problem. I tryed installing 
xen-hypervisor-3.0-unstable-1-i386. It seems to have fixed the problem.

I have no idea what the original issue is but this might be of use to
people that need to get going again.

Regards
--
Tom

Hello!

On Thu, Sep 07, 2006 at 01:35:52PM +0100, Thomas Stewart
wrote:
> I got exactly, the same problem. I tryed installing 
> xen-hypervisor-3.0-unstable-1-i386. It seems to have fixed the problem.
Hm.  More like ``worked around that problem'', I'd say.

> I have no idea what the original issue is but this might be of use to
> people that need to get going again.
Indeed I can confirm that `xen-hypervisor-3.0-unstable-1-i386' together
with `linux-image-2.6.17-2-xen-686' gets the Dom0 going again.  So far, I
had no luck to get a DomU running, however:

#v+
thomas@taylor:~ $ sudo /etc/init.d/xendomains restart
Shutting down Xen domains:Starting auto Xen domains: riemannError: Device 0
(vif) could not be connected. Hotplug scripts not working.
#v-

Perhaps the syntax for the /etc/xen/DOMAIN files has changed?


Regards,
 Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url :
http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20060907/4089ec68/attachment.pgp