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-users

[Xen-users] Error: Xen 3.0.3 with Vanderpool to boot unmodified Linux

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Error: Xen 3.0.3 with Vanderpool to boot unmodified Linux
From: Martin Bretschneider <martin.bretschneider@xxxxxxxxxxxxxxxxxxx>
Date: Fri, 22 Dec 2006 09:54:17 +0100
Delivery-date: Thu, 28 Dec 2006 02:56:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.9 (Windows/20061207)
Hi,

I have a Intel Xeon 5130 CPU on an Intel Server Board. This CPU does
support the Intel Vanderpool technology. The purpose is providing
several Linux servers. I want to run Debian Linux Etch (currently
Testing but soon Stable) in the 64bit mode (the Debian architecture name
is "amd64" for that). Xen has the version 3.0.3.

I installed the Xen packages and can run other Etch versions as Xen
guests using the normal paravirtualization. There is no problem with
that and it does work:) The xen-tools are very helpful and used seamless
the LVM2 stuff (see attached xen-test11.cfg).

But I do want the hardware assisted virtualisation using Vanderpool. I
took xmexample.hvm and put the lvm stuff there (see attached
xen-test12-hvm-mod2.cfg) and tried to boot but I doesn't work:

# xm list
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0     1347     2 r-----    79.6
ExampleHVMDomain                   8      128     1 ------     0.0

The output of the logfiles in /var/log/xen is also attached
(xend.log.txt and qemu-dm.log.txt). qemu-dm.log.txt says "domctl
operation failed -- need to rebuild the user-space tool set?
xc_get_pfn_list returned error 13".

What does that mean? Can you please help me?

TIA and kind regards from Martin

#  -*- mode: python; -*-
import os, re
arch = os.uname()[4]
if re.search('64', arch):
    arch_libdir = 'lib64'
else:
    arch_libdir = 'lib'
kernel = "/usr/lib/xen-3.0.3-1/boot/hvmloader"
builder='hvm'
memory = 128
shadow_memory = 8
vif = [ 'type=ioemu, bridge=xenbr0' ]
disk    = [ 'phy:hot/xen-test12-hvm-disk,sda1,w', 
'phy:hot/xen-test12-hvm-swap,sda2,w'] 
device_model = '/usr/lib/xen-3.0.3-1/bin/qemu-dm'
sdl=0
vnc=0
stdvga=0
serial='pty'
domid: 15
qemu: the number of cpus is 1
domctl operation failed -- need to rebuild the user-space tool set?
xc_get_pfn_list returned error 13

.....
[2006-12-21 14:17:40 xend.XendDomainInfo 3897] DEBUG (__init__:1072) 
XendDomainInfo.handleShutdownWatch
[2006-12-21 14:17:40 xend 3897] DEBUG (__init__:1072) Waiting for devices vif.
[2006-12-21 14:17:40 xend 3897] DEBUG (__init__:1072) Waiting for 0.
[2006-12-21 14:17:40 xend 3897] DEBUG (__init__:1072) hotplugStatusCallback 
/local/domain/0/backend/vif/8/0/hotplug-
status.
[2006-12-21 14:17:40 xend 3897] DEBUG (__init__:1072) hotplugStatusCallback 
/local/domain/0/backend/vif/8/0/hotplug-
status.
[2006-12-21 14:17:40 xend 3897] DEBUG (__init__:1072) hotplugStatusCallback 1.
[2006-12-21 14:17:40 xend 3897] DEBUG (__init__:1072) Waiting for devices usb.
[2006-12-21 14:17:40 xend 3897] DEBUG (__init__:1072) Waiting for devices vbd.
[2006-12-21 14:17:40 xend 3897] DEBUG (__init__:1072) Waiting for 2049.
[2006-12-21 14:17:40 xend 3897] DEBUG (__init__:1072) hotplugStatusCallback 
/local/domain/0/backend/vbd/8/2049/hotpl
ug-status.
[2006-12-21 14:17:41 xend 3897] DEBUG (__init__:1072) hotplugStatusCallback 
/local/domain/0/backend/vbd/8/2049/hotpl
ug-status.
[2006-12-21 14:17:41 xend 3897] DEBUG (__init__:1072) hotplugStatusCallback 1.
[2006-12-21 14:17:41 xend 3897] DEBUG (__init__:1072) Waiting for 2050.
[2006-12-21 14:17:41 xend 3897] DEBUG (__init__:1072) hotplugStatusCallback 
/local/domain/0/backend/vbd/8/2050/hotpl
ug-status.
[2006-12-21 14:17:41 xend 3897] DEBUG (__init__:1072) hotplugStatusCallback 1.
[2006-12-21 14:17:41 xend 3897] DEBUG (__init__:1072) Waiting for devices irq.
[2006-12-21 14:17:41 xend 3897] DEBUG (__init__:1072) Waiting for devices pci.
[2006-12-21 14:17:41 xend 3897] DEBUG (__init__:1072) Waiting for devices 
ioports.
[2006-12-21 14:17:41 xend 3897] DEBUG (__init__:1072) Waiting for devices tap.
[2006-12-21 14:17:41 xend 3897] DEBUG (__init__:1072) Waiting for devices vtpm.
[2006-12-21 14:17:41 xend 3897] INFO (__init__:1072) Domain ExampleHVMDomain 
(8) unpaused.

kernel  = '/boot/vmlinuz-2.6.17-2-xen-amd64'
ramdisk = '/boot/initrd.img-2.6.17-2-xen-amd64'
memory  = '128'
root    = '/dev/sda1 ro'
disk    = [ 'phy:lvm2/xen-test11-disk,sda1,w', 
'phy:lvm2/xen-test11-swap,sda2,w' ]
name    = 'xen-test11'
dhcp = 'dhcp'
vif  = [ '' ]
on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>