Sebastian Reitenbach
2008-Feb-12 12:19 UTC
[Xen-users] san fibrechannel device in HVM domU
Hi, I''m on a HP DL365, amd64, running SLES10sp1, but with kernel and xen of SLES10sp2, therefore using Xen 3.2. The domU shall be a Windows HVM guest. I want use the Qlogic SAN card in a domU. I''m following these instructions: http://www.novell.com/communities/node/2880/assign-dedicated-network-card-or-pci-device-xen-virtual-machine well, there is written that this only works for PVM guests, but that was for 3.0.4, I use 3.2, so I thought, worth a try. However, when I am at the point that I start the domU, the following error message appears: xm create pci=0000:02:01.0 SERVER2003 Using config file "./SERVER2003". Error: Fail to assign device(2:1.0): maybe VT-d is not enabled, or the device is not exist, or it has already been assigned to other domain Without the pci parameter, the domU starts. The device is correctly hidden from the dom0, and no other domU is running. As I am on AMD, there is no VT-d, will this only work with Xen on new Intel machines, or is there anything I can do to get this to work on AMD too? cheers Sebastian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Sebastian,
can you post the vm config file? i saw some problems when i use the long
form:
pci=[ ''0000:01:00.0'',''0000:01:01.0'' ]
in my file i use the short form:
pci=[ ''01:00.0'',''01:01.0'' ]
also i use in /boot/grub/menu.lst:
title XEN -- openSUSE 10.3 - PAE
root (hd0,4)
kernel /xen-pae.gz
module /vmlinuz-2.6.22.13-0.3-xenpae
root=/dev/mapper/nvidia_deihceca_part7 vga=normal
resume=/dev/mapper/nvidia_deihceca_part6 splash=silent showopts
pciback.hide=(0000:01:00.0)(0000:01:01.0)
module /initrd-2.6.22.13-0.3-xenpae
and at least in /etc/init.d/boot.local:
# HFC ISDN PCI Devices remove from Dom0 and also set permissive
modprobe pciback hide=''(01:00.0)(01:01.0)''
echo -n 0000:01:00.0 > sys/bus/pci/drivers/pciback/permissive
echo -n 0000:01:01.0 > sys/bus/pci/drivers/pciback/permissive
well as you see i use ISDN Cards and not HBA''a... but it should work
also
with that.
Mit freundlichen Grüßen / with kind regards
Gerhard Possler
IT Architect
IBM Enterprise Linux Services
ELS Wiki@IBM (only accessible via IBM intranet)
IT-Services and Solutions GmbH
Rathausstr. 7, D-09111 Chemnitz
Geschäftsführung: Rainer Laier, Michael Mai
Sitz der Gesellschaft: Chemnitz
Registergericht: Amtsgericht Chemnitz, HRB 18409
http://www.itsas.de/
gerhard.possler@de.ibm.com
Mobil +49 (0) 160 90578637
"Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de>
Sent by: xen-users-bounces@lists.xensource.com
12.02.2008 13:19
Please respond to
Sebastian Reitenbach <sebastia@l00-bugdead-prods.de>
To
xen-users@lists.xensource.com
cc
Subject
[Xen-users] san fibrechannel device in HVM domU
Hi,
I''m on a HP DL365, amd64, running SLES10sp1, but with kernel and xen of
SLES10sp2, therefore using Xen 3.2. The domU shall be a Windows HVM guest.
I want use the Qlogic SAN card in a domU. I''m following these
instructions:
http://www.novell.com/communities/node/2880/assign-dedicated-network-card-or-pci-device-xen-virtual-machine
well, there is written that this only works for PVM guests, but that was
for
3.0.4, I use 3.2, so I thought, worth a try.
However, when I am at the point that I start the domU, the following error
message appears:
xm create pci=0000:02:01.0 SERVER2003
Using config file "./SERVER2003".
Error: Fail to assign device(2:1.0): maybe VT-d is not enabled, or the
device is not exist, or it has already been assigned to other domain
Without the pci parameter, the domU starts. The device is correctly hidden
from the dom0, and no other domU is running.
As I am on AMD, there is no VT-d, will this only work with Xen on new
Intel
machines, or is there anything I can do to get this to work on AMD too?
cheers
Sebastian
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Sebastian Reitenbach
2008-Feb-12 13:29 UTC
Re: [Xen-users] san fibrechannel device in HVM domU
Hi, Gerhard Possler <gerhard.possler@de.ibm.com> wrote:> Hi Sebastian, > > can you post the vm config file? i saw some problems when i use the long > form: > > pci=[ ''0000:01:00.0'',''0000:01:01.0'' ] > > in my file i use the short form: > > pci=[ ''01:00.0'',''01:01.0'' ]I just tried the short form, as xm create parameter, and in the configuration file, but with the same error message all the time. Here is my domU configuration: ostype="windowsxp" name="SERVER2003" memory=511 vcpus=1 uuid="0a03ad93-9ead-43db-ef0c-09349db88a2e" on_crash="destroy" on_poweroff="destroy" on_reboot="destroy" localtime=1 builder="hvm" extid=0 device_model="/usr/lib/xen/bin/qemu-dm" kernel="/usr/lib/xen/boot/hvmloader" boot="d" pci=[ ''02:01.0'' ] disk=[ ''file:/var/lib/xen/images/SERVER2003/disk0,hda,w'', ''file:/vms/windowsxp.img,hdc:cdrom,r'', ] vif=[ ''mac=00:16:3e:1d:6c:e8,model=rtl8139,type=ioemu'', ] vnc=1 #vncunused=1 vncconsole=1 apic=0 acpi=1 pae=1 usb=1 usbdevice=''tablet'' serial="pty" The Windows domU is booting, without the pci line using above configuration file.> > also i use in /boot/grub/menu.lst: > title XEN -- openSUSE 10.3 - PAE > root (hd0,4) > kernel /xen-pae.gz > module /vmlinuz-2.6.22.13-0.3-xenpae > root=/dev/mapper/nvidia_deihceca_part7 vga=normal > resume=/dev/mapper/nvidia_deihceca_part6 splash=silent showopts > pciback.hide=(0000:01:00.0)(0000:01:01.0) > module /initrd-2.6.22.13-0.3-xenpae > > and at least in /etc/init.d/boot.local: > > # HFC ISDN PCI Devices remove from Dom0 and also set permissive > modprobe pciback hide=''(01:00.0)(01:01.0)'' > echo -n 0000:01:00.0 > sys/bus/pci/drivers/pciback/permissive > echo -n 0000:01:01.0 > sys/bus/pci/drivers/pciback/permissivewhat is this doing? the howto only told me to do: echo -n "<Your PCI ID>" > /sys/bus/pci/drivers/pciback/new_slot echo -n "<Your PCI ID>" > /sys/bus/pci/drivers/pciback/bind I don''t have it hardcoded yet to the grub.conf, just have done all the stuff manually, as in the howto described. The dom0 did not saw the device anymore. However, when starting, the error message below:> > xm create pci=0000:02:01.0 SERVER2003 > Using config file "./SERVER2003". > Error: Fail to assign device(2:1.0): maybe VT-d is not enabled, or the > device is not exist, or it has already been assigned to other domain >> > well as you see i use ISDN Cards and not HBA''a... but it should work also > with that.However, maybe that is the difference, as the error message says I do not have VT-d enabled, what I cannot do, as I am on a AMD based box, or does the AMD Vanderbilt provides equivalents? More on VT-d here: http://softwarecommunity.intel.com/articles/eng/1416.htm Do I have just only the wrong hardware, or should I be able to use a SAN card in a domU in general? thanks Sebastian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
btw... did you tried with Linux in DomU? I meen PVM guest? Mit freundlichen Grüßen / with kind regards Gerhard Possler IT Architect IBM Enterprise Linux Services ELS Wiki@IBM (only accessible via IBM intranet) IT-Services and Solutions GmbH Rathausstr. 7, D-09111 Chemnitz Geschäftsführung: Rainer Laier, Michael Mai Sitz der Gesellschaft: Chemnitz Registergericht: Amtsgericht Chemnitz, HRB 18409 http://www.itsas.de/ gerhard.possler@de.ibm.com Mobil +49 (0) 160 90578637 "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> 12.02.2008 14:29 Please respond to "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> To sebastia@l00-bugdead-prods.de, Gerhard Possler/Germany/IBM@IBMDE cc xen-users@lists.xensource.com Subject Re: [Xen-users] san fibrechannel device in HVM domU Hi, Gerhard Possler <gerhard.possler@de.ibm.com> wrote:> Hi Sebastian, > > can you post the vm config file? i saw some problems when i use the long> form: > > pci=[ ''0000:01:00.0'',''0000:01:01.0'' ] > > in my file i use the short form: > > pci=[ ''01:00.0'',''01:01.0'' ]I just tried the short form, as xm create parameter, and in the configuration file, but with the same error message all the time. Here is my domU configuration: ostype="windowsxp" name="SERVER2003" memory=511 vcpus=1 uuid="0a03ad93-9ead-43db-ef0c-09349db88a2e" on_crash="destroy" on_poweroff="destroy" on_reboot="destroy" localtime=1 builder="hvm" extid=0 device_model="/usr/lib/xen/bin/qemu-dm" kernel="/usr/lib/xen/boot/hvmloader" boot="d" pci=[ ''02:01.0'' ] disk=[ ''file:/var/lib/xen/images/SERVER2003/disk0,hda,w'', ''file:/vms/windowsxp.img,hdc:cdrom,r'', ] vif=[ ''mac=00:16:3e:1d:6c:e8,model=rtl8139,type=ioemu'', ] vnc=1 #vncunused=1 vncconsole=1 apic=0 acpi=1 pae=1 usb=1 usbdevice=''tablet'' serial="pty" The Windows domU is booting, without the pci line using above configuration file.> > also i use in /boot/grub/menu.lst: > title XEN -- openSUSE 10.3 - PAE > root (hd0,4) > kernel /xen-pae.gz > module /vmlinuz-2.6.22.13-0.3-xenpae > root=/dev/mapper/nvidia_deihceca_part7 vga=normal > resume=/dev/mapper/nvidia_deihceca_part6 splash=silent showopts > pciback.hide=(0000:01:00.0)(0000:01:01.0) > module /initrd-2.6.22.13-0.3-xenpae > > and at least in /etc/init.d/boot.local: > > # HFC ISDN PCI Devices remove from Dom0 and also set permissive > modprobe pciback hide=''(01:00.0)(01:01.0)'' > echo -n 0000:01:00.0 > sys/bus/pci/drivers/pciback/permissive > echo -n 0000:01:01.0 > sys/bus/pci/drivers/pciback/permissivewhat is this doing? the howto only told me to do: echo -n "<Your PCI ID>" > /sys/bus/pci/drivers/pciback/new_slot echo -n "<Your PCI ID>" > /sys/bus/pci/drivers/pciback/bind I don''t have it hardcoded yet to the grub.conf, just have done all the stuff manually, as in the howto described. The dom0 did not saw the device anymore. However, when starting, the error message below:> > xm create pci=0000:02:01.0 SERVER2003 > Using config file "./SERVER2003". > Error: Fail to assign device(2:1.0): maybe VT-d is not enabled, or the > device is not exist, or it has already been assigned to other domain >> > well as you see i use ISDN Cards and not HBA''a... but it should workalso> with that.However, maybe that is the difference, as the error message says I do not have VT-d enabled, what I cannot do, as I am on a AMD based box, or does the AMD Vanderbilt provides equivalents? More on VT-d here: http://softwarecommunity.intel.com/articles/eng/1416.htm Do I have just only the wrong hardware, or should I be able to use a SAN card in a domU in general? thanks Sebastian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
to your question: "Permissive mode should only be used as a fall back for unknown devices. I think the correct solution for dealing with these device-specific configuration space registers is to identify them and add the device-specific fields to the overlay. This patch adds a special configuration space handler for network cards based on the tg3 linux network device driver. This handler should allow for reads/writes to all of the configuration space registers that the tg3 driver requires." from: http://lists.xensource.com/archives/html/xen-devel/2006-07/msg00549.html also are you sure that the Dom0 is not using your HBA''s? look also at udev... because you message is:> Error: Fail to assign device(2:1.0): maybe VT-d is not enabled, or the > device is not exist, or it has already been assigned to other domain;-) Mit freundlichen Grüßen / with kind regards Gerhard Possler IT Architect IBM Enterprise Linux Services ELS Wiki@IBM (only accessible via IBM intranet) IT-Services and Solutions GmbH Rathausstr. 7, D-09111 Chemnitz Geschäftsführung: Rainer Laier, Michael Mai Sitz der Gesellschaft: Chemnitz Registergericht: Amtsgericht Chemnitz, HRB 18409 http://www.itsas.de/ gerhard.possler@de.ibm.com Mobil +49 (0) 160 90578637 "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> 12.02.2008 14:29 Please respond to "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> To sebastia@l00-bugdead-prods.de, Gerhard Possler/Germany/IBM@IBMDE cc xen-users@lists.xensource.com Subject Re: [Xen-users] san fibrechannel device in HVM domU Hi, Gerhard Possler <gerhard.possler@de.ibm.com> wrote:> Hi Sebastian, > > can you post the vm config file? i saw some problems when i use the long> form: > > pci=[ ''0000:01:00.0'',''0000:01:01.0'' ] > > in my file i use the short form: > > pci=[ ''01:00.0'',''01:01.0'' ]I just tried the short form, as xm create parameter, and in the configuration file, but with the same error message all the time. Here is my domU configuration: ostype="windowsxp" name="SERVER2003" memory=511 vcpus=1 uuid="0a03ad93-9ead-43db-ef0c-09349db88a2e" on_crash="destroy" on_poweroff="destroy" on_reboot="destroy" localtime=1 builder="hvm" extid=0 device_model="/usr/lib/xen/bin/qemu-dm" kernel="/usr/lib/xen/boot/hvmloader" boot="d" pci=[ ''02:01.0'' ] disk=[ ''file:/var/lib/xen/images/SERVER2003/disk0,hda,w'', ''file:/vms/windowsxp.img,hdc:cdrom,r'', ] vif=[ ''mac=00:16:3e:1d:6c:e8,model=rtl8139,type=ioemu'', ] vnc=1 #vncunused=1 vncconsole=1 apic=0 acpi=1 pae=1 usb=1 usbdevice=''tablet'' serial="pty" The Windows domU is booting, without the pci line using above configuration file.> > also i use in /boot/grub/menu.lst: > title XEN -- openSUSE 10.3 - PAE > root (hd0,4) > kernel /xen-pae.gz > module /vmlinuz-2.6.22.13-0.3-xenpae > root=/dev/mapper/nvidia_deihceca_part7 vga=normal > resume=/dev/mapper/nvidia_deihceca_part6 splash=silent showopts > pciback.hide=(0000:01:00.0)(0000:01:01.0) > module /initrd-2.6.22.13-0.3-xenpae > > and at least in /etc/init.d/boot.local: > > # HFC ISDN PCI Devices remove from Dom0 and also set permissive > modprobe pciback hide=''(01:00.0)(01:01.0)'' > echo -n 0000:01:00.0 > sys/bus/pci/drivers/pciback/permissive > echo -n 0000:01:01.0 > sys/bus/pci/drivers/pciback/permissivewhat is this doing? the howto only told me to do: echo -n "<Your PCI ID>" > /sys/bus/pci/drivers/pciback/new_slot echo -n "<Your PCI ID>" > /sys/bus/pci/drivers/pciback/bind I don''t have it hardcoded yet to the grub.conf, just have done all the stuff manually, as in the howto described. The dom0 did not saw the device anymore. However, when starting, the error message below:> > xm create pci=0000:02:01.0 SERVER2003 > Using config file "./SERVER2003". > Error: Fail to assign device(2:1.0): maybe VT-d is not enabled, or the > device is not exist, or it has already been assigned to other domain >> > well as you see i use ISDN Cards and not HBA''a... but it should workalso> with that.However, maybe that is the difference, as the error message says I do not have VT-d enabled, what I cannot do, as I am on a AMD based box, or does the AMD Vanderbilt provides equivalents? More on VT-d here: http://softwarecommunity.intel.com/articles/eng/1416.htm Do I have just only the wrong hardware, or should I be able to use a SAN card in a domU in general? thanks Sebastian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sebastian Reitenbach
2008-Feb-12 14:32 UTC
Re: [Xen-users] san fibrechannel device in HVM domU
Gerhard Possler <gerhard.possler@de.ibm.com> wrote:> btw... did you tried with Linux in DomU?I just did that, and it starts the PVM domU, well, the driver doesn''t load, because of this error message: QLogic Fibre Channel HBA Driver PCI: Enabling device 0000:00:00.0 (0000 -> 0003) qla2xxx 0000:00:00.0: Found an ISP2422, irq 21, iobase 0xffffc200001c8000 qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2x00_mem_alloc(): **** FAILED **** qla2xxx 0000:00:00.0: [ERROR] Failed to allocate memory for adapter Trying to free free IRQ21 qla2xxx: probe of 0000:00:00.0 failed with error -12 done and then on the domU: lspci | grep Q 00:00.0 Fibre Channel: QLogic Corp. QLA2422 Fibre Channel Adapter (rev 02) shutting down this PVM, and then trying to start the Windows HVM, produces the mentioned error message. kind regards Sebastian> > I meen PVM guest? > > Mit freundlichen Grüßen / with kind regards > > Gerhard Possler > IT Architect > IBM Enterprise Linux Services > ELS Wiki@IBM (only accessible via IBM intranet) > IT-Services and Solutions GmbH > Rathausstr. 7, D-09111 Chemnitz > Geschäftsführung: Rainer Laier, Michael Mai > Sitz der Gesellschaft: Chemnitz > Registergericht: Amtsgericht Chemnitz, HRB 18409 > http://www.itsas.de/ > gerhard.possler@de.ibm.com > Mobil +49 (0) 160 90578637 > > > > > "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> > 12.02.2008 14:29 > Please respond to > "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> > > > To > sebastia@l00-bugdead-prods.de, Gerhard Possler/Germany/IBM@IBMDE > cc > xen-users@lists.xensource.com > Subject > Re: [Xen-users] san fibrechannel device in HVM domU > > > > > > > Hi, > Gerhard Possler <gerhard.possler@de.ibm.com> wrote: > > Hi Sebastian, > > > > can you post the vm config file? i saw some problems when i use the long > > form: > > > > pci=[ ''0000:01:00.0'',''0000:01:01.0'' ] > > > > in my file i use the short form: > > > > pci=[ ''01:00.0'',''01:01.0'' ] > > I just tried the short form, as xm create parameter, and in the > configuration file, but with the same error message all the time. Here is > my > domU configuration: > > ostype="windowsxp" > name="SERVER2003" > memory=511 > vcpus=1 > uuid="0a03ad93-9ead-43db-ef0c-09349db88a2e" > on_crash="destroy" > on_poweroff="destroy" > on_reboot="destroy" > localtime=1 > builder="hvm" > extid=0 > device_model="/usr/lib/xen/bin/qemu-dm" > kernel="/usr/lib/xen/boot/hvmloader" > boot="d" > pci=[ ''02:01.0'' ] > disk=[ ''file:/var/lib/xen/images/SERVER2003/disk0,hda,w'', > ''file:/vms/windowsxp.img,hdc:cdrom,r'', ] > vif=[ ''mac=00:16:3e:1d:6c:e8,model=rtl8139,type=ioemu'', ] > vnc=1 > #vncunused=1 > vncconsole=1 > apic=0 > acpi=1 > pae=1 > usb=1 > usbdevice=''tablet'' > serial="pty" > > The Windows domU is booting, without the pci line using above > configuration > file. > > > > > also i use in /boot/grub/menu.lst: > > title XEN -- openSUSE 10.3 - PAE > > root (hd0,4) > > kernel /xen-pae.gz > > module /vmlinuz-2.6.22.13-0.3-xenpae > > root=/dev/mapper/nvidia_deihceca_part7 vga=normal > > resume=/dev/mapper/nvidia_deihceca_part6 splash=silent showopts > > pciback.hide=(0000:01:00.0)(0000:01:01.0) > > module /initrd-2.6.22.13-0.3-xenpae > > > > and at least in /etc/init.d/boot.local: > > > > # HFC ISDN PCI Devices remove from Dom0 and also set permissive > > modprobe pciback hide=''(01:00.0)(01:01.0)'' > > echo -n 0000:01:00.0 > sys/bus/pci/drivers/pciback/permissive > > echo -n 0000:01:01.0 > sys/bus/pci/drivers/pciback/permissive > what is this doing? the howto only told me to do: > echo -n "<Your PCI ID>" > /sys/bus/pci/drivers/pciback/new_slot > echo -n "<Your PCI ID>" > /sys/bus/pci/drivers/pciback/bind > > > > I don''t have it hardcoded yet to the grub.conf, just have done all the > stuff > manually, as in the howto described. The dom0 did not saw the device > anymore. However, when starting, the error message below: > > > > > xm create pci=0000:02:01.0 SERVER2003 > > Using config file "./SERVER2003". > > Error: Fail to assign device(2:1.0): maybe VT-d is not enabled, or the > > device is not exist, or it has already been assigned to other domain > > > > > > > > well as you see i use ISDN Cards and not HBA''a... but it should work > also > > with that. > However, maybe that is the difference, as the error message says I do not > have VT-d enabled, what I cannot do, as I am on a AMD based box, or does > the > AMD Vanderbilt provides equivalents? > More on VT-d here: > http://softwarecommunity.intel.com/articles/eng/1416.htm > > Do I have just only the wrong hardware, or should I be able to use a SAN > card in a domU in general? > > thanks > Sebastian_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
hmm.... howmany HBA''s do you have in the box? ... because i saw this massage with 2 HBA''s with activated BIOS on both ... i think we solved this problem by disabling the BIOS on one HBA, but i''m not sure anymore. This could be the same problem on Win HVM but you do have /var/log/messages on that... You could also run an Linux in HVM mode but i think you get the same errors. Mit freundlichen Grüßen / with kind regards Gerhard Possler IT Architect IBM Enterprise Linux Services ELS Wiki@IBM (only accessible via IBM intranet) IT-Services and Solutions GmbH Rathausstr. 7, D-09111 Chemnitz Geschäftsführung: Rainer Laier, Michael Mai Sitz der Gesellschaft: Chemnitz Registergericht: Amtsgericht Chemnitz, HRB 18409 http://www.itsas.de/ gerhard.possler@de.ibm.com Mobil +49 (0) 160 90578637 "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> 12.02.2008 15:32 Please respond to "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> To Gerhard Possler/Germany/IBM@IBMDE cc xen-users@lists.xensource.com Subject Re: [Xen-users] san fibrechannel device in HVM domU Gerhard Possler <gerhard.possler@de.ibm.com> wrote:> btw... did you tried with Linux in DomU?I just did that, and it starts the PVM domU, well, the driver doesn''t load, because of this error message: QLogic Fibre Channel HBA Driver PCI: Enabling device 0000:00:00.0 (0000 -> 0003) qla2xxx 0000:00:00.0: Found an ISP2422, irq 21, iobase 0xffffc200001c8000 qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2x00_mem_alloc(): **** FAILED **** qla2xxx 0000:00:00.0: [ERROR] Failed to allocate memory for adapter Trying to free free IRQ21 qla2xxx: probe of 0000:00:00.0 failed with error -12 done and then on the domU: lspci | grep Q 00:00.0 Fibre Channel: QLogic Corp. QLA2422 Fibre Channel Adapter (rev 02) shutting down this PVM, and then trying to start the Windows HVM, produces the mentioned error message. kind regards Sebastian> > I meen PVM guest? > > Mit freundlichen Grüßen / with kind regards > > Gerhard Possler > IT Architect > IBM Enterprise Linux Services > ELS Wiki@IBM (only accessible via IBM intranet) > IT-Services and Solutions GmbH > Rathausstr. 7, D-09111 Chemnitz > Geschäftsführung: Rainer Laier, Michael Mai > Sitz der Gesellschaft: Chemnitz > Registergericht: Amtsgericht Chemnitz, HRB 18409 > http://www.itsas.de/ > gerhard.possler@de.ibm.com > Mobil +49 (0) 160 90578637 > > > > > "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> > 12.02.2008 14:29 > Please respond to > "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> > > > To > sebastia@l00-bugdead-prods.de, Gerhard Possler/Germany/IBM@IBMDE > cc > xen-users@lists.xensource.com > Subject > Re: [Xen-users] san fibrechannel device in HVM domU > > > > > > > Hi, > Gerhard Possler <gerhard.possler@de.ibm.com> wrote: > > Hi Sebastian, > > > > can you post the vm config file? i saw some problems when i use thelong> > form: > > > > pci=[ ''0000:01:00.0'',''0000:01:01.0'' ] > > > > in my file i use the short form: > > > > pci=[ ''01:00.0'',''01:01.0'' ] > > I just tried the short form, as xm create parameter, and in the > configuration file, but with the same error message all the time. Hereis> my > domU configuration: > > ostype="windowsxp" > name="SERVER2003" > memory=511 > vcpus=1 > uuid="0a03ad93-9ead-43db-ef0c-09349db88a2e" > on_crash="destroy" > on_poweroff="destroy" > on_reboot="destroy" > localtime=1 > builder="hvm" > extid=0 > device_model="/usr/lib/xen/bin/qemu-dm" > kernel="/usr/lib/xen/boot/hvmloader" > boot="d" > pci=[ ''02:01.0'' ] > disk=[ ''file:/var/lib/xen/images/SERVER2003/disk0,hda,w'', > ''file:/vms/windowsxp.img,hdc:cdrom,r'', ] > vif=[ ''mac=00:16:3e:1d:6c:e8,model=rtl8139,type=ioemu'', ] > vnc=1 > #vncunused=1 > vncconsole=1 > apic=0 > acpi=1 > pae=1 > usb=1 > usbdevice=''tablet'' > serial="pty" > > The Windows domU is booting, without the pci line using above > configuration > file. > > > > > also i use in /boot/grub/menu.lst: > > title XEN -- openSUSE 10.3 - PAE > > root (hd0,4) > > kernel /xen-pae.gz > > module /vmlinuz-2.6.22.13-0.3-xenpae > > root=/dev/mapper/nvidia_deihceca_part7 vga=normal > > resume=/dev/mapper/nvidia_deihceca_part6 splash=silent showopts > > pciback.hide=(0000:01:00.0)(0000:01:01.0) > > module /initrd-2.6.22.13-0.3-xenpae > > > > and at least in /etc/init.d/boot.local: > > > > # HFC ISDN PCI Devices remove from Dom0 and also set permissive > > modprobe pciback hide=''(01:00.0)(01:01.0)'' > > echo -n 0000:01:00.0 > sys/bus/pci/drivers/pciback/permissive > > echo -n 0000:01:01.0 > sys/bus/pci/drivers/pciback/permissive > what is this doing? the howto only told me to do: > echo -n "<Your PCI ID>" > /sys/bus/pci/drivers/pciback/new_slot > echo -n "<Your PCI ID>" > /sys/bus/pci/drivers/pciback/bind > > > > I don''t have it hardcoded yet to the grub.conf, just have done all the > stuff > manually, as in the howto described. The dom0 did not saw the device > anymore. However, when starting, the error message below: > > > > > xm create pci=0000:02:01.0 SERVER2003 > > Using config file "./SERVER2003". > > Error: Fail to assign device(2:1.0): maybe VT-d is not enabled, or the> > device is not exist, or it has already been assigned to other domain > > > > > > > > well as you see i use ISDN Cards and not HBA''a... but it should work > also > > with that. > However, maybe that is the difference, as the error message says I donot> have VT-d enabled, what I cannot do, as I am on a AMD based box, or does> the > AMD Vanderbilt provides equivalents? > More on VT-d here: > http://softwarecommunity.intel.com/articles/eng/1416.htm > > Do I have just only the wrong hardware, or should I be able to use a SAN> card in a domU in general? > > thanks > Sebastian_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sebastian Reitenbach
2008-Feb-20 08:49 UTC
Re: [Xen-users] san fibrechannel device in HVM domU
Gerhard Possler <gerhard.possler@de.ibm.com> wrote:> hmm.... > > howmany HBA''s do you have in the box? ... because i saw this massage with > 2 HBA''s with activated BIOS on both ... i think we solved this problem by > disabling the BIOS on one HBA, but i''m not sure anymore. This could be thesame problem on Win HVM but you do have /var/log/messages on that... You> could also run an Linux in HVM mode but i think you get the same errors.sorry for my late reply, got a bit sick inbetween. I checked the adapter configuration. The BIOS already was disabled, there is also only one adaptor in the box. I think it''s just that I need that VT-d in the processor. thanks Sebastian> > Mit freundlichen Grüßen / with kind regards > > Gerhard Possler > IT Architect > IBM Enterprise Linux Services > ELS Wiki@IBM (only accessible via IBM intranet) > IT-Services and Solutions GmbH > Rathausstr. 7, D-09111 Chemnitz > Geschäftsführung: Rainer Laier, Michael Mai > Sitz der Gesellschaft: Chemnitz > Registergericht: Amtsgericht Chemnitz, HRB 18409 > http://www.itsas.de/ > gerhard.possler@de.ibm.com > Mobil +49 (0) 160 90578637 > > > > > "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> > 12.02.2008 15:32 > Please respond to > "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> > > > To > Gerhard Possler/Germany/IBM@IBMDE > cc > xen-users@lists.xensource.com > Subject > Re: [Xen-users] san fibrechannel device in HVM domU > > > > > > > Gerhard Possler <gerhard.possler@de.ibm.com> wrote: > > btw... did you tried with Linux in DomU? > > I just did that, and it starts the PVM domU, well, the driver doesn''t > load, > because of this error message: > > QLogic Fibre Channel HBA Driver > PCI: Enabling device 0000:00:00.0 (0000 -> 0003) > qla2xxx 0000:00:00.0: Found an ISP2422, irq 21, iobase 0xffffc200001c8000 > qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx > 0000:00:00.0: > Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation > failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - > rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx > 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: > Memory > Allocation failed - rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - > rlc<4>qla2xxx 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx > 0000:00:00.0: Memory Allocation failed - rlc<4>qla2xxx 0000:00:00.0: > Memory > Allocation failed - rlc<4>qla2x00_mem_alloc(): **** FAILED **** > qla2xxx 0000:00:00.0: [ERROR] Failed to allocate memory for adapter > Trying to free free IRQ21 > qla2xxx: probe of 0000:00:00.0 failed with error -12 > done > and then on the domU: > lspci | grep Q > 00:00.0 Fibre Channel: QLogic Corp. QLA2422 Fibre Channel Adapter (rev 02) > > shutting down this PVM, and then trying to start the Windows HVM, produces > the mentioned error message. > > kind regards > Sebastian > > > > > I meen PVM guest? > > > > Mit freundlichen Grüßen / with kind regards > > > > Gerhard Possler > > IT Architect > > IBM Enterprise Linux Services > > ELS Wiki@IBM (only accessible via IBM intranet) > > IT-Services and Solutions GmbH > > Rathausstr. 7, D-09111 Chemnitz > > Geschäftsführung: Rainer Laier, Michael Mai > > Sitz der Gesellschaft: Chemnitz > > Registergericht: Amtsgericht Chemnitz, HRB 18409 > > http://www.itsas.de/ > > gerhard.possler@de.ibm.com > > Mobil +49 (0) 160 90578637 > > > > > > > > > > "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> > > 12.02.2008 14:29 > > Please respond to > > "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> > > > > > > To > > sebastia@l00-bugdead-prods.de, Gerhard Possler/Germany/IBM@IBMDE > > cc > > xen-users@lists.xensource.com > > Subject > > Re: [Xen-users] san fibrechannel device in HVM domU > > > > > > > > > > > > > > Hi, > > Gerhard Possler <gerhard.possler@de.ibm.com> wrote: > > > Hi Sebastian, > > > > > > can you post the vm config file? i saw some problems when i use the > long > > > form: > > > > > > pci=[ ''0000:01:00.0'',''0000:01:01.0'' ] > > > > > > in my file i use the short form: > > > > > > pci=[ ''01:00.0'',''01:01.0'' ] > > > > I just tried the short form, as xm create parameter, and in the > > configuration file, but with the same error message all the time. Here > is > > my > > domU configuration: > > > > ostype="windowsxp" > > name="SERVER2003" > > memory=511 > > vcpus=1 > > uuid="0a03ad93-9ead-43db-ef0c-09349db88a2e" > > on_crash="destroy" > > on_poweroff="destroy" > > on_reboot="destroy" > > localtime=1 > > builder="hvm" > > extid=0 > > device_model="/usr/lib/xen/bin/qemu-dm" > > kernel="/usr/lib/xen/boot/hvmloader" > > boot="d" > > pci=[ ''02:01.0'' ] > > disk=[ ''file:/var/lib/xen/images/SERVER2003/disk0,hda,w'', > > ''file:/vms/windowsxp.img,hdc:cdrom,r'', ] > > vif=[ ''mac=00:16:3e:1d:6c:e8,model=rtl8139,type=ioemu'', ] > > vnc=1 > > #vncunused=1 > > vncconsole=1 > > apic=0 > > acpi=1 > > pae=1 > > usb=1 > > usbdevice=''tablet'' > > serial="pty" > > > > The Windows domU is booting, without the pci line using above > > configuration > > file. > > > > > > > > also i use in /boot/grub/menu.lst: > > > title XEN -- openSUSE 10.3 - PAE > > > root (hd0,4) > > > kernel /xen-pae.gz > > > module /vmlinuz-2.6.22.13-0.3-xenpae > > > root=/dev/mapper/nvidia_deihceca_part7 vga=normal > > > resume=/dev/mapper/nvidia_deihceca_part6 splash=silent showopts > > > pciback.hide=(0000:01:00.0)(0000:01:01.0) > > > module /initrd-2.6.22.13-0.3-xenpae > > > > > > and at least in /etc/init.d/boot.local: > > > > > > # HFC ISDN PCI Devices remove from Dom0 and also set permissive > > > modprobe pciback hide=''(01:00.0)(01:01.0)'' > > > echo -n 0000:01:00.0 > sys/bus/pci/drivers/pciback/permissive > > > echo -n 0000:01:01.0 > sys/bus/pci/drivers/pciback/permissive > > what is this doing? the howto only told me to do: > > echo -n "<Your PCI ID>" > /sys/bus/pci/drivers/pciback/new_slot > > echo -n "<Your PCI ID>" > /sys/bus/pci/drivers/pciback/bind > > > > > > > > I don''t have it hardcoded yet to the grub.conf, just have done all the > > stuff > > manually, as in the howto described. The dom0 did not saw the device > > anymore. However, when starting, the error message below: > > > > > > > > xm create pci=0000:02:01.0 SERVER2003 > > > Using config file "./SERVER2003". > > > Error: Fail to assign device(2:1.0): maybe VT-d is not enabled, or the > > > device is not exist, or it has already been assigned to other domain > > > > > > > > > > > > > well as you see i use ISDN Cards and not HBA''a... but it should work > > also > > > with that. > > However, maybe that is the difference, as the error message says I do > not > > have VT-d enabled, what I cannot do, as I am on a AMD based box, or does > > the > > AMD Vanderbilt provides equivalents? > > More on VT-d here: > > http://softwarecommunity.intel.com/articles/eng/1416.htm > > > > Do I have just only the wrong hardware, or should I be able to use a SAN > > card in a domU in general? > > > > thanks > > Sebastian > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users