On Thu, Sep 10, 2009 at 10:02 PM, David Edmondson <d...@sun.com> wrote:
>
> On 10 Sep 2009, at 2:45am, Fajar A. Nugraha wrote:
>>
>> Error: Device 51728 (vbd) could not be connected. Hotplug scripts not
>> working.
>> Usage: xm block-attach <Domain> <BackDev> <FrontDev> <Mode> [BackDomain]
>
> What is the output of 'syseventadm list' in the domU?
>
>
So I try again with this command
# xm block-attach osol2 phy:/dev/zvol/dsk/rpool/vbd/test1 xvdc w osol
Error: Device 51744 (vbd) could not be connected. Hotplug scripts not working.
Usage: xm block-attach <Domain> <BackDev> <FrontDev> <Mode> [BackDomain]
Create a new virtual block device.
The output of syseventadm list is the same in both backend and
frontend (the one that gets the new block device) domU:
# syseventadm list
vendor=SUNW publisher=pcieb class=EC_dr subclass=ESC_dr_req
/usr/lib/pci/pcidr class=$class subclass=$subclass
publisher=$publisher dr_request_type=$dr_request_type
dr_ap_id=$dr_ap_id
vendor=SUNW publisher=pcieb_bcm class=EC_dr subclass=ESC_dr_req
/usr/lib/pci/pcidr class=$class subclass=$subclass
publisher=$publisher dr_request_type=$dr_request_type
dr_ap_id=$dr_ap_id
vendor=SUNW class=EC_dev_status subclass=ESC_dev_dle
/usr/lib/fs/zfs/zfsdle $phys_path
When I execute the block-attach, the frontend domU got these on
/var/adm/messages:
Sep 11 14:40:22 os-pv xpvd: [ID 395608 kern.info] x...@51744, xdf2
Sep 11 14:40:22 os-pv genunix: [ID 936769 kern.info] xdf2 is /xpvd/x...@51744
Sep 11 14:40:22 os-pv genunix: [ID 408114 kern.info] /xpvd/x...@51744
(xdf2) online
Sep 11 14:40:22 os-pv xpvd: [ID 395608 kern.info] domc...@0, domcaps0
Sep 11 14:40:22 os-pv genunix: [ID 936769 kern.info] domcaps0 is /xpvd/domc...@0
and format shows this
AVAILABLE DISK SELECTIONS:
0. c7t0d0 <DEFAULT cyl 3915 alt 0 hd 255 sec 63>
/xpvd/x...@51712
1. c7t2d0 <drive type unknown>
/xpvd/x...@51744
c7t2d0 is the new drive. Selecting "1" hangs until I press ctrl-C
though, so I guess something is still wrong.
Both frontend and backend domU are opensolaris snv_122, dom0 is RHEL
running Xen 3.4.1. Perhaps the dom0 matters? WIll using opensolaris
dom0 make this work?
--
Fajar
_______________________________________________
xen-discuss mailing list
xen-discuss@opensolaris.org
