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

Re: [Xen-users] Re: [Xen-devel] Failure to create HVM DomU at Xen 4.1 (

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] Re: [Xen-devel] Failure to create HVM DomU at Xen 4.1 ( kernel 3.0.0-5-generic) Ubuntu 11.10 (alpha 2)
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Mon, 18 Jul 2011 06:41:20 -0700 (PDT)
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Mon, 18 Jul 2011 06:42:11 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1310996480; bh=+HctWODNiFERR0xeXZthVoOSwGmNAcQez2mwtB/2NqY=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=ztFkIOk392MPTy8SblDkJS5vk0Eni6+xZDFDnZKFsVGAu0o9EIkoOHf+3iVmHEw5TJeq6hK0i9PoQcIPfQeBg78l5k7twQ5b4yzHPNkkyjWwsD+zE9E7QG1X2f8CdqaZZi0vX9/V1L/pfbJ/ckbfvyaFluddfEZmIUXG7zUDEBQ=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=PfR7jGPq83s+zs9U6/XLtSdQ1sKBxlf0L41BoMADwnRo+WsWpGvGvQpq/muTn0Wo2pOp2TKcZQDxVN1hJUwTkLFFVzrdg55hh4au0pzHB9XpYOU4K7u8LiL7x124rvre4pmZCX5gtm5LFSLT4XQvlLLt4qQTdfXvb4vKVlEv4+Q=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1107181338100.12963@kaball-desktop>
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
Keymaps installed

Now:

root@boris-P5Q-E:~/vms/natty# xl create f14.hvm
Parsing config file f14.hvm
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000017b150
  TOTAL:         0000000000000000->000000007f800000
  ENTRY ADDRESS: 0000000000101580
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000003fb
  1GB PAGES: 0x0000000000000000
Daemon running with PID 32668
root@boris-P5Q-E:~/vms/natty# vncviewer localhost:0

VNC Viewer Free Edition 4.1.1 for X - built Apr  9 2010 18:41:55
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.

Mon Jul 18 17:36:33 2011
 main:        unable to connect to host: Connection refused (111)

root@boris-P5Q-E:/var/log/xen# cat qemu-dm-F14HVM.log
domid: 236
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
Using file /dev/sda5 in read-write mode
Using file /dev/loop0 in read-only mode
Watching /local/domain/0/device-model/236/logdirty/cmd
Watching /local/domain/0/device-model/236/command
Watching /local/domain/236/cpu
char device redirected to /dev/pts/3
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = b5a57be5-1097-4021-b3a7-56133c229c16
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/236/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error. /vm/b5a57be5-1097-4021-b3a7-56133c229c16/vncpasswd.
medium change watch on `hdc' (index: 1): /dev/loop0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Log-dirty: no command yet.
vcpu-set: watch node error.
xs_read(/local/domain/236/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/236/log-throttling'
medium change watch on `/local/domain/236/log-throttling' - unknown device, ignored

Boris



--- On Mon, 7/18/11, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> wrote:

From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: [Xen-users] Re: [Xen-devel] Failure to create HVM DomU at Xen 4.1 ( kernel 3.0.0-5-generic) Ubuntu 11.10 (alpha 2)
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>, "Stefano Stabellini" <Stefano.Stabellini@xxxxxxxxxxxxx>
Date: Monday, July 18, 2011, 8:39 AM

On Mon, 18 Jul 2011, Boris Derzhavets wrote:
> domid: 1
> -videoram option does not work with cirrus vga device model. Videoram set to 4M.
> Using file /dev/sda5 in read-write mode
> Using file /dev/loop0 in read-only mode
> Watching /local/domain/0/device-model/1/logdirty/cmd
> Watching /local/domain/0/device-model/1/command
> Watching /local/domain/1/cpu
> char device redirected to /dev/pts/2
> qemu_map_cache_init nr_buckets = 10000 size 4194304
> shared page at pfn feffd
> buffered io page at pfn feffb
> Guest uuid = 4de22a31-1735-4d06-be4d-3887eba949ee
> 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/1/xen_extended_power_mgmt): read error
> Could not read keymap file: '/usr/share/qemu/keymaps/en-us'
>

as you can see from the last line of the logs, you are missing the
keymap files (see keymaps directory under qemu-xen-4.1-testing).


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>