Xen project Mailing List

ii libxenstore3.0 4.0.1-4 Xenstore communications library for Xen

ii linux-image-2.6.32-5-xen-amd64 2.6.32-45 Linux 2.6.32 for 64-bit PCs, Xen dom0 support

ii xen-hypervisor-4.0-amd64 4.0.1-4 The Xen Hypervisor on AMD64

ii xen-linux-system-2.6-xen-amd64 2.6.32+29 Xen system with Linux 2.6 for 64-bit PCs (meta-package)

ii xen-linux-system-2.6.32-5-xen-amd64 2.6.32-45 Xen system with Linux 2.6.32 on 64-bit PCs (meta-package)

ii xen-qemu-dm-4.0 4.0.1-2+squeeze1 Xen Qemu Device Model virtual machine hardware emulator

ii xen-utils-4.0 4.0.1-4 XEN administrative tools

ii xen-utils-common 4.0.0-1 XEN administrative tools - common files

ii xenstore-utils 4.0.1-4 Xenstore utilities for Xen

root@cyrax:~# uname -a

Linux cyrax 2.6.32-5-xen-amd64 #1 SMP Sun May 6 08:57:29 UTC 2012 x86_64 GNU/Linux

working domU (centos)

[root@sektor ~]# cat /etc/redhat-release

CentOS release 5.5 (Final)

[root@sektor ~]# uname -a

Linux sektor 2.6.18-194.3.1.el5 #1 SMP Thu May 13 13:08:30 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux

[root@sektor ~]# lspci | grep Xen

00:03.0 Class ff80: XenSource, Inc. Xen Platform Device (rev 01)

[root@sektor ~]# lsmod | grep xen

xen_vnif 58817 0 [permanent]

xen_vbd 50345 0

xen_balloon 45641 1 xen_vnif,[permanent]

xen_platform_pci 117741 3 xen_vnif,xen_vbd,xen_balloon,[permanent]

As you can see above the platform pci device shows in lspci and you can see in lsmod that the pv interfaces are being detected and used

New box (wheezy, nonworking)

root@barium:~# dpkg -l | grep xen

ii libxen-4.1 4.1.3-1 amd64 Public libs for Xen

ii libxenstore3.0 4.1.3-1 amd64 Xenstore communications library for Xen

ii xen-hypervisor-4.1-amd64 4.1.3-1 amd64 Xen Hypervisor on AMD64

ii xen-system-amd64 4.1.3-1 amd64 Xen System on AMD64 (meta-package)

ii xen-utils-4.1 4.1.3-1 amd64 XEN administrative tools

ii xen-utils-common 4.1.3-1 all Xen administrative tools - common files

ii xenstore-utils 4.1.3-1 amd64 Xenstore utilities for Xen

root@barium:~# uname -a

Linux barium 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux

domU (centos)

[root@baraka ~]# cat /etc/redhat-release

CentOS release 5.5 (Final)

[root@baraka ~]# uname -a

Linux baraka 2.6.18-194.3.1.el5 #1 SMP Thu May 13 13:08:30 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux

[root@baraka ~]# lspci | grep Xen

00:03.0 Class ff80: XenSource, Inc. Xen Platform Device (rev 01)

[root@baraka ~]# lsmod | grep xen

xen_platform_pci 117741 0 [permanent]

So as you can see the domU is identical kernel in both cases however when the domU is running on the wheezy dom0 even despite that the platform pci device appears exactly the same in lspci

I've attached the configs and logs that you asked for

Any ideas how to debug further? The difference between the working scenario and nonworking is the dom0 distro (squeeze vs wheezy), dom0 kernel and dom0 hypervisor

Testing with both scenario's was done with the exact same domU so I cant see how it could be a domU issue.

thanks

chris

On Wed, Aug 29, 2012 at 4:41 AM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:

On Tue, 2012-08-28 at 18:52 +0100, chris wrote:
> the issue seems to be with wheezy not squeeze im just trying to figure
> out why with wheezy with newer versions of everything pvhvm is not
> working.

I upgraded my test Squeeze VM to Wheezy and PVHVM continued working
(this is on a fresh Wheezy dom0).

> and in domU's I compared the lspci of the xen platform pci device to
> the lspci output from a working pvhvm domU that resides on a squeeze
> dom0.

And they were identical?

> so my guess is that its related to hypervisor?

I don't think we have enough evidence to decide one way or the other.

Can you provide the logs and guest configurations which I asked for
please.

Ian.

Re: [Xen-users] pvhvm on debian