WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] 2.6.37 PV on HVM issues

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] 2.6.37 PV on HVM issues
From: Alex Bligh <alex@xxxxxxxxxxx>
Date: Thu, 02 Dec 2010 15:23:16 +0000
Cc: Alex Bligh <alex@xxxxxxxxxxx>
Delivery-date: Thu, 02 Dec 2010 07:23:52 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Reply-to: Alex Bligh <alex@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I'm running Ubuntu's current kernel from Natty which I believe
to be 2.6.37-rc1, and hoping to get PV drivers on HVM working.
I think I must be missing something as despite a helpful dmesg
I can't actually see any PV devices (or think I can't).

I see this:

# uname -a ; dmesg | egrep -i '(pv|xen|hvm)'
Linux 109-231-66-11 2.6.37-7-virtual #19-Ubuntu SMP Wed Dec 1 02:15:20 UTC 2010 x86_64 GNU/Linux
[    0.000000] DMI: /HVM domU, BIOS 3.3.1 02/02/2009
[    0.000000] Hypervisor detected: Xen HVM       <-----********************
[    0.000000] Xen version 3.3.
[    0.000000] Xen Platform PCI: unrecognised magic value  <--- ++++++++++++
[    0.000000] HVMOP_pagetable_dying not supported
[    0.000000] ACPI: RSDP 00000000000ea010 00024 (v02    Xen)
[ 0.000000] ACPI: XSDT 000000001fff8b70 00034 (v01 Xen HVM 00000000 HVML 00000000) [ 0.000000] ACPI: FACP 000000001fff8a00 000F4 (v04 Xen HVM 00000000 HVML 00000000) [ 0.000000] ACPI: DSDT 000000001fff7840 01132 (v02 Xen HVM 00000000 INTL 20060707) [ 0.000000] ACPI: APIC 000000001fff8b00 00068 (v02 Xen HVM 00000000 HVML 00000000)
[    0.000000] Booting paravirtualized kernel on Xen <---*******************
[    0.800582] Initialising Xen virtual ethernet driver.
[   13.980075] eth0: no IPv6 routers present

The lines marked with asterisks are confusing to me as they appear to be
in contradiction.

Should I be worried about the line marked +++++?

Moreover, despite the line re "initialising Xen virtual ethernet driver"
I see one ethernet device (eth0), and one block device (sda). I was
expecting to see eth1 and either vbda or xvdba.

$ ls -lad /sys/block/sda
lrwxrwxrwx 1 root root 0 2010-12-02 14:18 /sys/block/sda -> ../devices/pci0000:00/0000:00:01.1/host0/target0:0:0/0:0:0:0/block/sda
$ ls -lad /sys/class/net/eth0
lrwxrwxrwx 1 root root 0 2010-12-02 14:03 /sys/class/net/eth0 -> ../../devices/pci0000:00/0000:00:04.0/net/eth0

This suggests they are not paravirtualised.

# egrep _XEN_ /boot/config-2.6.37-7-virtual
CONFIG_XEN_DOM0=y
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_PVHVM=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=128
CONFIG_XEN_SAVE_RESTORE=y
# CONFIG_XEN_DEBUG_FS is not set
CONFIG_XEN_PCIDEV_FRONTEND=m
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_NETDEV_FRONTEND=y
CONFIG_XEN_KBDDEV_FRONTEND=m
CONFIG_XEN_FBDEV_FRONTEND=m
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=m
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y
CONFIG_XEN_PLATFORM_PCI=m

That would seem to be right to me.

--
Alex Bligh

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