similar to: FC-HBA assigned to guest domain does not work.

On 32e, we create one guest, then hotplug attach one NIC to guest, guest can not get IP address via dhcp, guest qemu log shows "libpci read error. No emulation ". Here is the bug entry: One 32e, hotplug attaching VT-d NIC to guest failed. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1316. -- haicheng _______________________________________________ Xen-devel mailing list

I am submitting the patch which supports more Capability Structures and Device Specific Registers for passthrough device. In Xen 3.3 unstable, qemu-dm supports Configuration Header, MSI Capability Structure, and MSI-X Capability Structure. But qemu-dm does not support PCI Express Capability Structure, Device Specific Registers, etc (writing them is ignored). To support various I/O devices, I

The memory relating guest domain should be allocated from NUMA node on which the guest runs. Because the latency of the same NUMA node is faster than that of a different one. This patch fixes memory allocation for Address Translation Structure of VT-d. VT-d uses two types of Structures for DMA address translation. The one is Device Assignment Structure. The other is Address Translation

This patch adds the function that reassign page-aligned memory resources, to dom0 linux. The function is useful when we assign I/O device to HVM domain using pci passthrough. When we assign a device to HVM domain using pci passthrough, the device needs to be assigned page-aligned memory resources. If the memory resource is not page-aligned, following error occurs. Error: pci: 0000:00:1d.7:

Hi, all, The attached patches try to improve the current FLR logic. The idea is: removing the FLR logic from hypervisor and adding the improved logic in Control Panel. The current FLR logic in hypervisor has some issues: 1) Dstate transition is not guaranteed to properly clear the device state; 2) the current code for PCIe FLR is actually buggy: PCI_EXP_DEVSTA_TRPND doesn''t mean the

I have inherited an Oracle system which we have installed on a client site with the specs below. There was a kernel upgrade done by the patch management team at their site which broke the cluster. Once the kernel was reverted the system came back up. Am somewhat of a newbie to ocfs, etc and am trying to verify something. To do a kernel upgrade the ocfs2 (CRS) and ASM would have to be upgraded

On Xen-3.3.0, domain0 Megaraid SAS (SAS 1068 controller) driver is not loading correctly if vtd support in Xen is enabled. It fails at the point of initializing firmware. I wasn''t seeing this error with Xen-3.2.2-rc3 (Unstable version), though with vtd disabled in Xen-3.3.0, it is working. Looks like a degrade problem. Any clues? Thx, Venkat

This patch enables PCI passthrough with stub domain. PCI passthrough with stub domain has failed in the past. The primary reason is that hypercalls from qemu in stub domain are rejected. This patch allows qemu in stub domain to call the hypercalls which is needed for PCI passthrough. For security, if target domain of hypercall is different from that of stub domain, it rejects hypercall. To use

This patch fixes compilation error when CONFIG_PCI_REASSIGN is not set. The patch depends on following patches I have sent. [PATCH] dom0 linux: Fix issue on reassigning resources to PCI-PCI bridge [PATCH] dom0 linux: remove "reassign_resources" option. Thanks, -- Yuji Shimada Signed-off-by: Yuji Shimada <shimada-yxb@necst.nec.co.jp> diff -r fac93b1081da drivers/pci/pci.h ---

This patch fixes libpci error handling. It can be applied to both ioemu-remote and ioemu. libpci returns ALL F when error occurs. Currently, if libpci returns ALL F, emulation stops. But it is possible that the field of real register which is read by guest software is ALL F. After applying this patch, if libpci returns ALL F, ioemu will log warning message and continue the emulation.

Does anyone have any experience with Emulex HBA cards (LP10000) using OCFS2, Linux AS4 U4 x86_64 AMD? I'm trying to find out whether this is a verified combination, if anyone has successfully used it. I have that hardware/sofware combination, and am experiencing stability/performance/panic/hang issues with OCFS2. -------------- next part -------------- An HTML attachment was scrubbed... URL:

This patch exposes HID,UID,SEG,BBN of PCI root bridge via sysfs. Thanks, -- Yuji Shimada. Signed-off-by: Yuji Shimada <shimada-yxb@necst.nec.co.jp> diff -r 618fc299e2f1 -r 4769a6db78f5 drivers/acpi/pci_root.c --- a/drivers/acpi/pci_root.c Thu Dec 18 11:51:36 2008 +0000 +++ b/drivers/acpi/pci_root.c Thu Dec 25 10:37:52 2008 +0900 @@ -151,6 +151,36 @@ return AE_OK; } +ssize_t

Hi, When I want to use NPIV for a FC HBA in my Linux machine, I got the below error msg in virsh: virsh # nodedev-create /home/kvm/vHBA.xml error: Failed to create node device from /home/kvm/vHBA.xml error: internal error Parent device scsi_host20 is not capable of vport operations I checked the /sys/class folder for my HBA device that I want to use its NPIV feature, it's there:

Hi Everyone I am looking at setting up a File Server that uses ISCSI storage. It is the first time I have done this, so I am wanting to get peoples thoughts on whether for CentOS systems you should use Hardware based ISCSI HBA's? If so do I need to be careful about what HBA I use ? Currently I am looking at purchasing a Dell System using Broadcom ethernet cards/ ISCSI HBA. From

Forwarding to the list for Jay or Scott to have a look. Ignazio, do you see any more details (traceback or something) in the rails log? -------------- next part -------------- An embedded message was scrubbed... From: ignazio.cassano at provincia.torino.it Subject: Re: [Ovirt-devel] [PATCH node-image] keep NIC and HBA firmwares Date: Wed, 16 Sep 2009 16:48:47 +0200 Size: 4031 URL:

Hi. I'm looking at a qlogic qle2462 hba for my dl360 g5. The thread http://www.mail-archive.com/freebsd-stable@freebsd.org/msg99497.html mentions a deadlock when system is loaded. Has this issue been resolved? Are there other PCI Express hba's which are known to work with freebsd stable and dl360 g5? -- regards Claus When lenity and cruelty play for a kingdom, the gentler gamester is

Hi, I have a host which is connected to SAN via single Fibre channel HBA (qlogic). I have several LUNS assigned to this (sdc, sdd). I added another single port HBA to this host. I can now see two world wide names. Now the confusion is which world wide name does sdc and sdd is/was using. scsi_id -g -u -s /block/sdc only gives wwid but I need the wwn for sdc and sdd. Thanks Paras.

I''m having trouble actually seeing a PCI device in my VMs. I''ve resolved several of my issues using previous posts and using the VTdHowTo wiki page. I have both VT and VTd BIOS options enabled. I have pciback hiding the devices and xm can list and assign the devices to VMs. I don''t see the PCI devices in my VMs though. I have tried a windows and a Linux vm, without

# cat /etc/redhat-release CentOS Linux release 7.1.1503 (Core) # uname -r 3.10.0-123.20.1.el7.x86_64 Hi, We use iSCSI over a 10G Ethernet Adapter and SRP over an Infiniband adapter to provide multipathing to our storage: # lspci | grep 10-Gigabit 81:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) 81:00.1 Ethernet controller: Intel Corporation

Hi, I got few servers (IBM HS20,HS21 blades, IBM xSeries 3650 & others) connected to a dual fabric san throught Qlogic HBA's (23xx, 24xx). Multipathing is done with device-mapper-multipath. On CentOS 4.x i can scan for new scsi devices without any problems, get them up with multipathing & use them without any problems. However, after i started installing CentOS 5.1 (did not