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] hvm guest direct kernel boot

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] hvm guest direct kernel boot
From: William Dauchy <wdauchy@xxxxxxxxx>
Date: Thu, 11 Aug 2011 14:56:55 +0200
Delivery-date: Thu, 11 Aug 2011 05:59:43 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; bh=J1MNfIoJMmMtulkxjrZRKB1MIQ9CkaKRVpIvWdYJqTg=; b=CbMbiEQd9ggNrjpw8Ed6tLAVBfA1Iv/QPAqzHLE9m/fH6PfC2JE18WjhHyqjPyXf5o 0rG0BwQgIEINoG9GJnMc9oFJXhpIsySC68zAUmo3h7/Dh+NY1z6L6HZUr7yQsZMg/hJl SSAewVP9Qkz0vY1NMaP/TunvxHxWWPq15a8Q0=
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

I'm trying to boot a hvm guest directly on a linux kernel.
Here is my config file:

name='test'
builder='hvm'
memory = 512
vcpus=1
cpus = ['1']
disk = ['phy:/dev/iscsi/hosting-2253:0,hda,w']
device_model = '/usr/lib/xen/bin/qemu-dm'
loader='/usr/lib/xen/boot/hvmloader'
kernel='/boot/bzImage'
serial='pty'
apic=0
acpi=1
pae=0
videoram=4
stdvga=0
nographic=1
sdl=0
isa=0
display=0
vncdisplay=0

I'm using Xen 4.1.1 with an upstream linux 3.1-rc1 for the dom0.

The console is not working and the qemu-dm process is dying after a while
Here are the qemu-dm log:

# cat /var/log/xen/qemu-dm-test.log
domid: 58
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
Using file /dev/iscsi/hosting-2253:0 in read-write mode
Watching /local/domain/0/device-model/58/logdirty/cmd
Watching /local/domain/0/device-model/58/command
Watching /local/domain/58/cpu
char device redirected to /dev/pts/1
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = fa5d2eb8-d026-9f66-8ccc-3f89f1545517
Time offset set 0
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/58/xen_extended_power_mgmt): read error
Log-dirty: no command yet.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
(qemu) vcpu-set: watch node error.
char device redirected to /dev/pts/2
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xs_read(/local/domain/58/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/58/log-throttling'
medium change watch on `/local/domain/58/log-throttling' - unknown
device, ignored
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
xen be: console-0: xen be: console-0: initialise() failed
initialise() failed
cirrus vga map change while on lfb mode
mapping vram to f0000000 - f0400000
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.

I was wondering how could I fix the following errors:
xs_read(/local/domain/0/device-model/58/xen_extended_power_mgmt): read error
qemu: ignoring not-understood drive `/local/domain/58/log-throttling'
xen be: console-0: xen be: console-0: initialise() failed

I can't see what I forgot to make it boot on the kernel and make the
console working.

Regards,

-- 
William

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

<Prev in Thread] Current Thread [Next in Thread>