[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] dev/xen/evtchn disappears, HVM fails, xen 4.0.1-1 Debian Squeeze


  • To: "Fajar A. Nugraha" <list@xxxxxxxxx>
  • From: Erik Hjelmås <erik.hjelmas@xxxxxxxxx>
  • Date: Wed, 22 Sep 2010 05:41:01 +0200
  • Cc: Xen User-List <xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 21 Sep 2010 20:42:16 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=O+ODpoQGjtyYN3jeda3kuVRWL6CNfsniGzUJDkbbh/OFmFusxqd/9cVzhF2O5mUPQG Q9NRC5i263YhqwEqSm3SYB7tN55nHZhuxPSzPQuzWINbsZJNAnXRMnyyoiblj3wPDmyz pcQK8VOkLySjnQ7mAyAvofKYcLfIGoPmnvlu4=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>



2010/9/20 Fajar A. Nugraha <list@xxxxxxxxx>
2010/9/20 Erik Hjelmås <erik.hjelmas@xxxxxxxxx>:
>
> Thanks for the reply Fajar,
>
>> > debian packages, everything installed using aptitude) was working fine
>> > for
>> > PV and HVM guest until an aptitude upgrade on Monday,
>>
>> Was it also 4.0.1, or 4.0.0 (before aptitude upgrade)?
>
> it was also 4.0.1 but a release candidate (RC6):

In that case, the easy way is to downgrade using the working package :)
I'd start with downgrading the kernel first, then if doesn't work,
start with other packages. Or compile yourself from source.


I had only attempted downgrading xen last week, yesterday I started downgrading DomO kernels from
http://snapshot.debian.org/archive/debian/20100812T210958Z/pool/main/l/linux-2.6/

and downgrading to 2.6.32-20 did not help, 2.6.32-19 did not help, but finally with 2.6.32-18 from july the problem disappeared.

I think this is very strange, but I have to keep the server running this way until Monday, then I will try to recreate the error and potentially file a bug report at Debian.

btw with this kernel, there's no gntdev in /dev/xen :

erikh@zimbu:~$ ls -l /dev/xen/
total 0
crw------- 1 root root 10, 57 Sep 21 05:44 evtchn


/Erik
 

I have a xen 4.0.1 environment, which (for most part) works as
expected, and not having your problems. So I'd suggest you also ask
Debian guys.

--
Fajar

>
> zimbu:/var/cache/apt/archives# ls -ltr *xen-hypervisor*
> -rw-r--r-- 1 root root 687128 Aug 17 23:32
> xen-hypervisor-4.0-amd64_4.0.1~rc6-1_amd64.deb
> -rw-r--r-- 1 root root 687022 Sep  3 18:32
> xen-hypervisor-4.0-amd64_4.0.1-1_amd64.deb
> zimbu:/var/cache/apt/archives#
>
>>
>> > zimbu:/home/erikh# dpkg -l | grep xen
>> > libxenstore3.0                      4.0.1-1
>> > linux-image-2.6.32-5-xen-amd64      2.6.32-21
>> > xen-hypervisor-4.0-amd64            4.0.1-1
>> > xen-linux-system-2.6.32-5-xen-amd64 2.6.32-21
>> > xen-qemu-dm-4.0                     4.0.1-1
>> > xen-tools                           4.2~rc1-1
>> > xen-utils-4.0                       4.0.1-1
>> > xen-utils-common                    4.0.0-1
>> > xenstore-utils                      4.0.1-1
>>
>> AFAIK you usually need a matching version of hypervisor and tools.
>> Your tools version says 4.2~rc1-1, while hypervisor is 4.0.1-1. That
>> might be the cause.
>
> yes, I was thinking this as well, but I dont think it applies to the
> xen-tools (only to xen, xenstore, and corresponding utils packages) and it
> doesnt look like there has been a 4.0.1 version of xen-tools either
> http://packages.debian.org/changelogs/pool/main/x/xen-tools/xen-tools_4.2~rc1-1/changelog
>
> /Erik
>

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.