WARNING - OLD ARCHIVES

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

xen-devel

Re: [Xen-devel] pci hotplug in xcp

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] pci hotplug in xcp
From: Ritu kaur <ritu.kaur.us@xxxxxxxxx>
Date: Thu, 8 Apr 2010 09:44:00 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Dave Scott <Dave.Scott@xxxxxxxxxxxxx>
Delivery-date: Wed, 14 Apr 2010 07:22:23 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=Q0XcuL1MM6OR0n8L47aZjDge3/+x536RLNOGsrXoY6M=; b=FaYQWy2Dfe6sGZddLQ7uE9bkYJCwWMwOrWrFsg12iVdS23iCEmhRlAY+KLE6u9QFUM m+5K041KD9FSp4ybcDKR88lqzSniAvc7CZY03X6htiY/FnGCWZkwLA7JPRbCiA+0D4um oNPhPPbotpwy4KNzmHB3ucL5TTunLZytkU2Z0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=TD0+pXuPA3DP79hozc/WxfugyvkMp4ff487aKgBeBMPDCDdVLTfLsUhpnR5krq1ZSV nz1am4acusKUasc+0Z9cMZ8fzbZ2GrltBuXcCO+lRwBLZ9Lu6VWZzd3XduqHYvf5KvSq TF84MgnlyHMKmM3QDsc6g6yUbzobHDDLixubk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1004081702310.7041@kaball-desktop>
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>
References: <v2p29b32d341004061003ze657beeep69f1a278f3d374b8@xxxxxxxxxxxxxx> <81A73678E76EA642801C8F2E4823AD21565E5542A8@xxxxxxxxxxxxxxxxxxxxxxxxx> <alpine.DEB.2.00.1004071209060.7527@kaball-desktop> <t2o29b32d341004071156s8081041av9f0a8667e932cde9@xxxxxxxxxxxxxx> <alpine.DEB.2.00.1004081153020.7041@kaball-desktop> <m2u29b32d341004080744o26d0b200gc62baf4da2f28c40@xxxxxxxxxxxxxx> <alpine.DEB.2.00.1004081546470.7041@kaball-desktop> <r2l29b32d341004080853x855d9f8cz98dd6d9b37bbace2@xxxxxxxxxxxxxx> <alpine.DEB.2.00.1004081702310.7041@kaball-desktop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
1. Guest OS is Debian Lenny 5.0(with 2.6.32.9 kernel from xen.org)

2. acpiphp module is loaded in guest OS

3. in my xcp dom0 I do not see /tmp/qemu.<domid> files, what I have

# ls -l
total 8
drwx------ 3 root root 4096 Mar 11 10:21 lvm
-rw-r--r-- 1 root root    0 Apr  8 09:25 master
-rw-r--r-- 1 root root  848 Apr  8 09:27 xenguest.log

xenguest.log doesn't reveal anything.

4. attached /var/log/messages.

Thanks


On Thu, Apr 8, 2010 at 9:04 AM, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> wrote:
Please post the qemu logs (in XCP they go to syslog, so
/var/log/messages and /tmp/qemu.$domid), they'll probably reveal
an error.
What is the guest operating system? If it is Linux make sure acpiphp is
loaded.

On Thu, 8 Apr 2010, Ritu kaur wrote:
> Thanks Stefano. It did work fine first time however subsequent attach/detach doesn't work. What I did
>
> 1. (VM has other-config:pci="" as suggested by Ian)
>
> 2. modprobe pciback
>
> 3. echo -n "$pcidev" > /sys/bus/pci/drivers/pciback/new_slot echo -n "$pcidev" > /sys/bus/pci/drivers/pciback/bind
>
> 4. start VM
>
> 5. xl pci-attach 1 0000:08:01.0(Cross checked in VM can see device via lspci)
>
> 6. xl pci-detach 1 0000:08:01.0(Cross checked in VM, no device via lspci)
>
> 7. xl pci-attach 1 0000:08:01.0(lspci in VM doesn't list the device)
>
> 8. xl pci-list 1 in dom0 lists the device
>
> 9. When try to detach I get
> xl pci-detach 1 0000:08:01.0
>
> [0] libxl_device.c:444:libxl_wait_for_backend: Backend /local/domain/0/backend/pci/1/0 not ready
> [3] libxl.c:1881:libxl_device_pci_remove_xenstore: pci backend at /local/domain/0/backend/pci/1/0 is not ready
> [-1] libxl.c:2151:libxl_device_pci_remove: xc_deassign_device failed: Success
>
> dmesg in dom0 has
>
> ...
> pciback: vpci: 0000:08:01.0: assign to virtual slot 0
> pciback: vpci: 0000:08:01.0: assign to virtual slot 0
>
> nothing related to detach. Do I need to run any other command prior to subsequent attach?
>
> Thanks
>
> On Thu, Apr 8, 2010 at 7:47 AM, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> wrote:
>       On Thu, 8 Apr 2010, Ritu kaur wrote:
>       > Thanks Stefano.
>       >
>       > I am having problems binding device to pciback(this is from day1). Driver for this device is not loaded in
>       dom0 so this
>       > device is not bound to any driver.
>       >
>       > #echo $pcidev
>       > 0000:08:01.0
>       >
>       > # echo -n $pcidev > /sys/bus/pci/drivers/pciback/bind
>       > -bash: echo: write error: No such device
>       >
>       > ls -l /sys/bus/pci/drivers/pciback/bind
>       > --w------- 1 root root 4096 Apr  8 07:40 /sys/bus/pci/drivers/pciback/bind
>       >
>       > Any inputs?
>       >
>
> you need to do this:
>
> echo -n "$pcidev" > /sys/bus/pci/drivers/pciback/new_slot
> echo -n "$pcidev" > /sys/bus/pci/drivers/pciback/bind
>
>
>
>

Attachment: msgs
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>