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-users

[Xen-users] VT hardware requirements

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] VT hardware requirements
From: "Geoff Gibbs" <geoff.gibbs@xxxxxxxxx>
Date: Tue, 27 May 2008 12:30:07 -0600
Delivery-date: Tue, 27 May 2008 11:30:41 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=1urEauQ6ABjw/2F04ofcutK26jjUU1HIl8jB9SyDTFc=; b=hSRVB5loGoZOfHKOK/7SKQtLK3QH9P7OoHdEZ3xsBi3AjRlWg07CCS4QPPrHkFMufGeinSZaGVCb84yoBqLzU818GipmrIUY6gCKNMUebbVf61a53lJfvSWLo9WRf9gW36Fpr5Oh46QjnHbXHbxSEUDEzWPA7HuQFizO447ZgjY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=l6cuO5TPSC5LWy2o40lSZO8OiD3lNLusU6+eBuTA7nZGeaGwRT5kYRKlm+qhsB0pifsioy4Zpi4ZiupmZStloqitswPOW8BidLrPh3zrkPjNmG3A38sIV1rLSyqsT6CH2Gi8wrXtEPyZlhf1Z3SZwddVpfgBLBqIQYI2csrymRo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
All,

I have been trying to get PCI pass through working for sometime and
need to know if I have a hardware problem (does my hardware support
PCI pass through) or if I am doing something in correct.

1) My BIOS does allow me to enable VT support

2) cat /proc/cpuinfo
processor    : 0
vendor_id    : GenuineIntel
cpu family    : 6
model        : 15
model name    : Intel(R) Xeon(R) CPU            5140  @ 2.33GHz
stepping    : 6
cpu MHz        : 2327.532
cache size    : 4096 KB
physical id    : 0
siblings    : 1
core id        : 0
cpu cores    : 1
fpu        : yes
fpu_exception    : yes
cpuid level    : 10
wp        : yes
flags        : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm
bogomips    : 4658.82
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:

processor    : 1
vendor_id    : GenuineIntel
cpu family    : 6
model        : 15
model name    : Intel(R) Xeon(R) CPU            5140  @ 2.33GHz
stepping    : 6
cpu MHz        : 2327.532
cache size    : 4096 KB
physical id    : 0
siblings    : 1
core id        : 1
cpu cores    : 1
fpu        : yes
fpu_exception    : yes
cpuid level    : 10
wp        : yes
flags        : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm
bogomips    : 4658.82
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:

3) dmesg | grep 0a:0e
Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00 rhgb quiet pciback.hide=(0a:0e.0)(07:00.0) pciback.verbose_request=1 apic=debug pci=routeirq)
Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet pciback.hide=(0a:0e.0)(07:00.0) pciback.verbose_request=1 apic=debug pci=routeirq
ACPI: PCI Interrupt 0000:0a:0e.0[A] -> GSI 18 (level, low) -> IRQ 20
pciback 0000:0a:0e.0: seizing device
ACPI: PCI Interrupt 0000:0a:0e.0[A] -> GSI 18 (level, low) -> IRQ 20
ACPI: PCI interrupt for device 0000:0a:0e.0 disabled

4) cat xen_foo.cfg
name = "xen_foo"
uuid = "cab66c9faa4b7049d5d10293f13bfc7f"
maxmem = 500
memory = 500
vcpus = 1
builder = "hvm"
kernel = "/usr/lib64/xen/boot/hvmloader"
boot = "c"
pae = 1
acpi = 1
apic = 1
>>>device_model = "/usr/lib64/xen/bin/qemu-dm"
sdl = 1
vnc = 0
vncunused = 0
keymap = "en-us"
disk = [ "file:/var/lib/xen/images/xen_reo.img,hda,w" ]
vif = [ "mac=00:16:3e:72:06:c0,bridge=xenbr1,type=ioemu", "mac=00:16:3e:28:51:79,bridge=xenbr1,type=ioemu" ]
serial = "pty"
pci = ['0a:0e.0']


When I create "foo", the system boots, but does not load the kernel module aacraid which is device 0a:0e.0. reports
the following:

Adaptec aacraid driver (1.1-5[2430]custom)
ACPI: PCI Interrupt 0000:00:03.0[A] GSI 28 (level,loq) IRQ 17
aacraid: aac_fib_send: first asynchronous command timed out.
Usually a result of a PCI interrupt routing problem;
Update mother board BIOS or consider utilizing one of the
SAFE model kernel options (acpi, apic etc)
ACPI: PCI interrupt for device 0000:00:03.0 disabled
aacraid: probe of 0000:00:03.0 failed with error -110


I really need some help with this.

Thanks,

Geoff







--
Geoff Gibbs
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] VT hardware requirements, Geoff Gibbs <=