On 11 Sep 2009, at 8:44am, Fajar A. Nugraha wrote:
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
This isn't enough for the the guest to provide backend services -
there should be something for EC_xpvdev or EC_xendev, depending on the
age of your bits.
I'd guess that the packaging re-vamp means that the sysevent script
isn't being added by the SMF service for a guest domain. johnlev -
what did you decide about this?
_______________________________________________
xen-discuss mailing list
[email protected]
