Gerhard Possler <gerhard.possler@xxxxxxxxxx> 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@xxxxxxxxxx
> Mobil +49 (0) 160 90578637
>
>
>
>
> "Sebastian Reitenbach" <sebastia@xxxxxxxxxxxxxxxxxxxx>
> 12.02.2008 14:29
> Please respond to
> "Sebastian Reitenbach" <sebastia@xxxxxxxxxxxxxxxxxxxx>
>
>
> To
> sebastia@xxxxxxxxxxxxxxxxxxxx, Gerhard Possler/Germany/IBM@IBMDE
> cc
> xen-users@xxxxxxxxxxxxxxxxxxx
> Subject
> Re: [Xen-users] san fibrechannel device in HVM domU
>
>
>
>
>
>
> Hi,
> Gerhard Possler <gerhard.possler@xxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home