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

Re: [Xen-users] HVM with stub domains fails at startup: ERROR Internal e

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] HVM with stub domains fails at startup: ERROR Internal error: Could not open grant table interface (22 = Invalid argument)
From: "John" <lists.xen@xxxxxxxxxxxxxxxxxx>
Date: Fri, 2 Oct 2009 10:30:36 -0700
Delivery-date: Fri, 02 Oct 2009 10:31:25 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <850201601@xxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Martin,

1. start fs-backend in the background (as user root)
/usr/sbin/fs-backend
2. start VM with xm create -c hvm_stub.conf
3. error logs on command line, both DomUs are listed by xm, but stay with 0 CPU time

I have seen a similar problem here, running the latest pv_ops and xen-unstable. In my case, I am trying to run Windows Server x64 HVM and stubdom messages print to /var/log/xen/qemu-dm-testvds-dm.log:

domid: 101
Warning: vlan 0 is not connected to host network
Watching /local/domain/0/device-model/101/logdirty/cmd
Watching /local/domain/0/device-model/101/command
char device redirected to /dev/pts/10
char device redirected to /dev/pts/11
/usr/src/xen-unstable.hg/tools/ioemu-dir/hw/xen_blktap.c:628: Init blktap pipes ERROR Internal error: Could not open grant table interface (22 = Invalid argument)
xen be core: xen be core: can't open gnttab device
can't open gnttab device
ERROR Internal error: Could not open grant table interface (22 = Invalid argument)
xen be core: xen be core: can't open gnttab device
can't open gnttab device
Log-dirty: no command yet.

Maybe we're doing the same thing wrong here?

Have you tried with a LVM or file: backing store? Do normal HVM and PV domains work properly for you?

-John

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