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/
Home Products Support Community News


[Xen-devel] Xen hotplug question & issue

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Xen hotplug question & issue
From: jpranevich@xxxxxxxxxxx
Date: Mon, 18 Aug 2008 17:05:32 -0400 (EDT)
Delivery-date: Mon, 18 Aug 2008 14:06:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

I'm on a stock Xen 3.2.1 running on Centos 5.2. Can someone give me a pointer 
to where in the Xend code I should start to debug an issue with hotplugging. In 
short, my block-* script doesn't get called on my Centos 5.2 installation but 
it DOES get called on a SuSE installation. I've adapted the script to work 
under Centos, but I can show with debugging that it is never run and no lines 
are added to the xen-hotplug.log.

In this case, I'm playing with iscsi and my device path is iscsi://IQN instead 
of phy:. I'm expecting it to register the device with the 
/etc/xen/scripts/block-iscsi script, but it never appears to do so. I don't 
know what and where that script is being called, so I've been unable to track 
down what is going on. 

I'm going to keep digging through the code until I find my problem, but any 
pointers that might tell me the right places to look are appreciated.

Joe Pranevich

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Xen hotplug question & issue, jpranevich <=