|
A working libvirt XML formatted DomU would surfice.
I was looking at http://libvirt.org/drvxen.html
And realized that "virsh
domxml-to-native" may be used to convert the domU configuration to native if
necessary.
I am interested in knowing how you incorporated the stubdom-dm loader.
The link above demonstrates Fullyvirtualized guest direct kernel boots,
Fullyvirtualized guest BIOS boots, Paravirtualized guest direct kernel boots,
and Paravirtualized guest bootloader with pygrub examples.
Non of the examples feature the stubdom-dm loader.
I would greatly appreciate it if you could post a complete and working stubdom
HVM domU configuration.
Thanks.
-M
Date: Mon, 15 Mar 2010 17:58:39 -0700
From: andrewe@xxxxxxxxxxxxx
To: mike.viau@xxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Error starting stubdom HVM on Xen-3.4.3-rc4-pre
CC: xen-users@xxxxxxxxxxxxxxxxxxx
On 03/15/10 15:52, Mike Viau wrote:
On
Mon, 15 Mar 2010 15:27:44 -0700 andrewe@xxxxxxxxxxxxx wrote:
<snip>
phy:/full/path/to/dev,DEV,MODE ?
Perhaps you could post a working DomU config???
My config is in libvirt XML form, sorry. Here's an excerpt of the
serialized device config from xend.log:
'07f11f37-944d-bbed-6f56-bf9279b39d9d': (
'vbd', {
'uuid': '07f11f37-944d-bbed-6f56-bf9279b39d9d',
'bootable': 1,
'driver': 'paravirtualised',
'dev': 'hda:disk',
'uname': 'phy:/dev/sys/lv0',
'mode': 'w'
}
),
>You don't say whether you've started fs-backend per the README.
That
would certainly cause problems trying to create a domain.
Indeed. I created a script to start my domU:
#!/bin/sh
mkdir -p /exports/usr/share/xen/qemu
ln -s /usr/share/xen/qemu/keymaps /exports/usr/share/xen/qemu
mkdir -p /exports/var/lib
ln -s /var/lib/xen /exports/var/lib
/usr/sbin/fs-backend &
You might want to sleep a few seconds in here...
xm create (name on domU config)
>I had to build the 2.6.18.8 xen.org dom0 kernel as the RHEL 5 dom0
kernel I normally use doesn't have gntdev, which is necessary for stub
domains to work.
This I did not know. May I ask where you acquired this knowledge?
I was getting this error on the terminal where I'd started fs-backend:
virsh # start cg3.c803.mail.sp2.yahoo.com
Domain cg3.c803.mail.sp2.yahoo.com started
virsh # Path changed backend/vfs/exports/requests/7/0/frontend
Handling connection from dom=7, for export=0
Frontend found at: /local/domain/7/device/vfs/0 (gref=2047, evtchn=4)
ERROR Internal error: Could not open grant table interface (22 =
Invalid argument)
ERROR: Couldn't open gnttab!
Awaiting next connection.
Path changed backend/vfs/exports/requests/7/0/frontend
Awaiting next connection.
Did some web searching on "Could not open grant table interface (22 =
Invalid argument)" and turned up the gntdev.ko solution. grepped the
RHEL 5 dom0 kernel's System.map for gntdev symbols, turned up nothing.
Built/installed/booted 2.6.18.8 from xen-unstable, problem solved.
-Andrew
Thanks
-M
>-Andrew
On 03/10/10 06:45, Mike Viau wrote:
Hi
there,
Last night I was trying to start a HVM domU via stubdom-dm device
model. Initially I did not receive any error to stdout when I did so
with Xen-3.4.2.
My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM
guests). The stubdom-dm guest I was trying to create did not really
operate as I was unable to connect to the VNC console. The output of xm
list showed the DomU was there, but it did not show it was actively
running, almost like it was pause at 0:00:00.
This morning I installed Xen-3.4.3-rc4-pre with the same domU HVM
stubdom configuration and got this message.
localhost:~/XENSTORE/router#xm create router
Using config file "./router".
Error: Device 768 (vbd) could not be connected.
File /root/XENSTORE/router/hd.img is loopback-mounted through
/dev/loop1,
which is mounted in a guest domain,
and so cannot be mounted now.
AND
localhost:/var/log/xen# cat qemu-dm-router-dm.log
domid: 2
Warning: vlan 0 is not connected to host network
Watching /local/domain/0/device-model/2/logdirty/next-active
Watching /local/domain/0/device-model/2/command
char device redirected to /dev/pts/2
/usr/local/src/xen-3.4-testing.hg/tools/ioemu-dir/hw/xen_blktap.c:628:
Init blktap pipes
bind() failed <<-- This was also the last line in the log when
using Xen-3.4.2
AND
localhost:~/XENSTORE/router# xm info
host : localhost.site
release : 2.6.33-xen
version : #2 SMP Sat Mar 6 15:26:37 EST 2010
machine : x86_64
nr_cpus : 8
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 2
cpu_mhz : 2800
hw_caps :
bfebfbff:28100800:00000000:00000340:0098e3fd:00000000:00000001:00000000
virt_caps : hvm
total_memory : 8182
free_memory : 7061
node_to_cpu : node0:0-7
node_to_memory : node0:7061
xen_major : 3
xen_minor : 4
xen_extra : .3-rc4-pre
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : Tue Mar 09 18:15:52 2010 +0000
19924:6e72f8c3c017
cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1)
cc_compile_by : root
cc_compile_domain : site
cc_compile_date : Wed Mar 10 08:46:50 EST 2010
xend_config_format : 4
AND the configuration file
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 1024
name = "router"
vcpus=1
pae=1
acpi=1
apic=1
vif = [ 'type=ioemu, mac=00:16:3e:11:11:01, bridge=br100',
'type=ioemu, mac=00:16:3e:11:11:02, bridge=br101',
'type=ioemu, mac=00:16:3e:11:11:03, bridge=br200',
'type=ioemu, mac=00:16:3e:11:11:04, bridge=br300',
'type=ioemu, mac=00:16:3e:11:11:05, bridge=br400' ]
disk = [ 'file:/root/XENSTORE/router/hd.img,hda,w',
'file:/root/XENSTORE/router/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso,
hdc:cdrom,r' ]
device_model = '/usr/lib/xen/bin/stubdom-dm'
boot="cda"
sdl=0
opengl=1
vnc=1
vnclisten="10.254.2.81"
vncdisplay=0
vncunused=0
vncpasswd='router'
stdvga=0
LASTLY the router-dm file
#This file is autogenerated, edit router instead!
kernel = '/usr/lib/xen/boot/ioemu-stubdom.gz'
vfb = ['sdl=0, opengl=1, xauthority=/root/.Xauthority, vnc=1,
vncdisplay=0, vnclisten=10.254.2.81, vncunused=0, vncpasswd=router']
disk = [
'file:/root/XENSTORE/router/hd.img,hda:disk,w','file:/root/XENSTORE/router/pfSense-1.2.3-RELEASE-LiveCD-Installer.iso,hdc:cdrom,r'
]
vif = [
'mac=00:16:3e:11:11:01,bridge=br100','mac=00:16:3e:11:11:02,bridge=br101','mac=00:16:3e:11:11:03,bridge=br200','mac=00:16:3e:11:11:04,bridge=br300','mac=00:16:3e:11:11:05,bridge=br400'
]
Can someone suggest what I might have done wrong, thanks!
-M
Live connected with Messenger on your phone Learn
more.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
Live connected with Messenger on your phone Learn more.
IM on the go with Messenger on your phone. Try now.
|
Home