The way your patch + zfs-24 patch work for me ( Nexenta 3.0 Xen Sample Image and profile)
root@LucidSRV:~/NexentaStor-Community-3.0.2# cat *.cfg
# This config file use for boot installation guest domain NexentaStor, hereinafter referred to as DomU
# Work directory
# work_dir = '/full/path/to/directory/with/unpacked/nexentastor-xen-image'
work_dir = '/root/NexentaStor-Community-3.0.2'
# Names of disks
disk_1_name = 'syspool.img'
disk_2_name = 'data_disk1.img'
disk_3_name = 'data_disk2.img'
disk_4_name = 'data_disk3.img'
# Bootloader for boot DomU
bootloader = "/usr/local/bin/pygrub"
# Memory for DomU, in MB
memory = 1024
# Name of DomU
name = "NexentaStor-Community-3.0.2"
# Network interfaces for DomU
# You can change the mac address of your own needs.
#
mac=00:16:3E:xx:xx:xx
vif = [
'mac=00:16:3E:00:00:01',
'mac=00:16:3E:00:00:02'
]
# vif=['bridge=eth0']
# Disk's for guest domain.
# Format for added disk:
# for file devices disk:
# 'file:/full/path/to/disk_in_file,num_disk_in_DomU,access_mode_for_disk_in_DomU'
# for tap device disk (for example VHD):
# 'tap:tapdisk:vhd:/full/path/to/disk_in_file,num_disk_in_DomU,access_mode_for_disk_in_DomU'
# for physical devices disk:
# 'phy:/dev/physical_devices_in_Dom0,num_disk_in_DomU,access_mode_for_disk_in_DomU'
# num_disk_in_DomU = xvda,xvdb,xvdc,xvde,...
# access_mode_for_disk_in_DomU = w - read-write mode, r = read-only mode
#
# We recommend using the VHD disc format (blktap2 device driver).
#
http://wiki.xensource.com/xenwiki/blktap2disk = [
'tap:tapdisk:vhd:' + work_dir + '/' + disk_1_name + ',xvda,w',
'tap:tapdisk:vhd:' + work_dir + '/' + disk_2_name + ',xvdb,w',
'tap:tapdisk:vhd:' + work_dir + '/' + disk_3_name + ',xvdc,w',
'tap:tapdisk:vhd:' + work_dir + '/' + disk_4_name + ',xvde,w',
]
# Configure the behaviour when a domain exits. There are three 'reasons'
# for a domain to stop: poweroff, reboot, and crash. For each of these you
# may specify:
#
# "destroy", meaning that the domain is cleaned up as normal;
# "restart", meaning that a new domain is started in place of the old
# one;
#
"preserve", meaning that no clean-up is done until the domain is
# manually destroyed (using xm destroy, for example); or
# "rename-restart", meaning that the old domain is not cleaned up, but is
# renamed and a new domain started in its place.
#
# In the event a domain stops due to a crash, you have the additional options:
#
# "coredump-destroy", meaning dump the crashed domain's core and then destroy;
# "coredump-restart', meaning dump the crashed domain's core and the restart.
>>>
root@LucidSRV:~/NexentaStor-Community-3.0.2# xm create -c
nexentastor-community-3.0.2-xen.cfg
Using config file "./nexentastor-community-3.0.2-xen.cfg".
root@LucidSRV:~/NexentaStor-Community-3.0.2# Error: Device 51952 not connected
^C
Home