Franz Regensburger
2008-Oct-23 07:25 UTC
[Xen-users] Problem with VT-d on Mainboard Intel DQ45CB
Hello all,
this mail is related to a post by Axel Schöner that I found at
http://article.gmane.org/gmane.comp.emulators.xen.user/40621
when I was searching the WEB about solutions to my problem.
I would like to confirm that VT-d with XEN 3.3 kernel 2.6.18.8 on mainboard
Intel DQ45CB seems to be broken.
Survey (details are down below)
---------------------------------------
Whenever I boot my Xen 2.6.18.8 (Xen 3.3) with kernel parameter iommu=1
the boot process freezes.
I see:
...
(XEN) Intel VT-d has been enabled
...
(XEN) HVM: VMX enabled
...
(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests disabled
Here the boot process freezes
Does anybody else suffer from the same problem (VT-d with Intel board DQ45CB)?
Any suggestions about a solution?
Regards,
Franz
Details about my setup
----------------------------
Hardware:
Mainboard Intel DQ45CB
CPU: Intel Core 2 Quad 9550
RAM: 8GB
OS: Debian Linux Etch 4.0 R3
The plain standard with kernel 2.6.18, the 64bit flavour
XEN: (compiled from the soruces)
Mercurial:
dpkg -i ./mercurial-common_1.0.1-5.1~bpo40+1_all.deb
dpkg -i ./mercurial_1.0.1-5.1~bpo40+1_amd64.deb
Xen source:
wget http://bits.xensource.com/oss-xen/release/3.3.0/xen-3.3.0.tar.gz
Xen kernel tree:
hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg
Kernel Config:
Defaults apart from
make linux-2.6-xen-config CONFIGMODE=menuconfig
change XEN->"PCI-device backend driver" from "M"
to "*".
According to messages on the WEB compiling the backend driver fixed into the
kernel is required
in order to get pciback.hide running via kernel parameter.
GRUB config:
title Xen 3.3.0 / kernel 2.6.18.8-xen backhide the ATI Radeon
root (hd0,0)
#kernel /xen-3.3.0.gz console=vga noreboot max_loop=128 dom0_mem=1024M
iommu=1
kernel /xen-3.3.0.gz console=vga noreboot max_loop=128 dom0_mem=1024M
module /vmlinuz-2.6.18.8-xen root=/dev/mapper/RootVG-root ro
console=tty0 pciback.hide=(01:00.0)(01:00.1)
module /initrd-2.6.18.8-xen.img
savedefault
Output of ''xm dmesg'' after booting without
''iommu=1''
susi:/boot/grub# xm dmesg
__ __ _____ _____ ___
\ \/ /___ _ __ |___ / |___ / / _ \
\ // _ \ ''_ \ |_ \ |_ \| | | |
/ \ __/ | | | ___) | ___) | |_| |
/_/\_\___|_| |_| |____(_)____(_)___/
(XEN) Xen version 3.3.0 (root@wire.laim) (gcc version 4.1.2 20061115
(prerelease) (Debian 4.1.1-21)) Tue Oct 21 16:22:47 CEST 2008
(XEN) Latest ChangeSet: unavailable
(XEN) Command line: console=vga noreboot max_loop=128 dom0_mem=1024M
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN) EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN) Found 2 MBR signatures
(XEN) Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 0000000000095c00 (usable)
(XEN) 0000000000095c00 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000bd6e0000 (usable)
(XEN) 00000000bd6e0000 - 00000000bd722000 (ACPI NVS)
(XEN) 00000000bd722000 - 00000000bd840000 (reserved)
(XEN) 00000000bd840000 - 00000000bd843000 (ACPI NVS)
(XEN) 00000000bd843000 - 00000000bd943000 (reserved)
(XEN) 00000000bd943000 - 00000000bd944000 (ACPI NVS)
(XEN) 00000000bd944000 - 00000000bd949000 (reserved)
(XEN) 00000000bd949000 - 00000000bd951000 (ACPI data)
(XEN) 00000000bd951000 - 00000000bd96c000 (ACPI NVS)
(XEN) 00000000bd96c000 - 00000000bd98a000 (reserved)
(XEN) 00000000bd98a000 - 00000000bd990000 (ACPI NVS)
(XEN) 00000000bd990000 - 00000000bdb00000 (usable)
(XEN) 00000000bdc00000 - 00000000c0000000 (reserved)
(XEN) 00000000fed1c000 - 00000000fed20000 (reserved)
(XEN) 00000000ff000000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 000000023c000000 (usable)
(XEN) System RAM: 8087MB (8282004kB)
(XEN) ACPI: RSDP 000F03C0, 0024 (r2 INTEL)
(XEN) ACPI: XSDT BD94FE18, 005C (r1 INTEL DQ45CB 3B MSFT 10013)
(XEN) ACPI: FACP BD94ED98, 00F4 (r4 INTEL A M I 6222004 MSFT 10013)
(XEN) ACPI: DSDT BD949018, 4E98 (r1 INTEL DQ45CB 3B INTL 20051117)
(XEN) ACPI: FACS BD957F40, 0040
(XEN) ACPI: APIC BD94EF18, 006C (r2 INTEL DQ45CB 3B MSFT 10013)
(XEN) ACPI: MCFG BD959E18, 003C (r1 INTEL DQ45CB 3B MSFT 97)
(XEN) ACPI: ASF! BD958D18, 00A0 (r32 INTEL DQ45CB 3B TFSM F4240)
(XEN) ACPI: SPCR BD959D18, 0050 (r1 INTEL DQ45CB 3B AMI. 3)
(XEN) ACPI: TCPA BD959C98, 0032 (r2 INTEL DQ45CB 3B MSFT 1000013)
(XEN) ACPI: DMAR BD943C18, 0120 (r1 INTEL DQ45CB 3B INTL 1)
(XEN) Xen heap: 14MB (14496kB)
(XEN) Domain heap initialised
(XEN) Processor #0 7:7 APIC version 20
(XEN) Processor #1 7:7 APIC version 20
(XEN) Processor #2 7:7 APIC version 20
(XEN) Processor #3 7:7 APIC version 20
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2833.050 MHz processor.
(XEN) HVM: VMX enabled
(XEN) CPU0: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz stepping 07
(XEN) Booting processor 1/1 eip 8c000
(XEN) CPU1: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz stepping 07
(XEN) Booting processor 2/2 eip 8c000
(XEN) CPU2: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz stepping 07
(XEN) Booting processor 3/3 eip 8c000
(XEN) CPU3: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz stepping 07
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 3.579MHz ACPI PM Timer
(XEN) Brought up 4 CPUs
(XEN) I/O virtualisation disabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 ->
0xffffffff805c050c
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000232000000->0000000234000000 (253952 pages to be
allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff80200000->ffffffff805c050c
(XEN) Init. ramdisk: ffffffff805c1000->ffffffff81506800
(XEN) Phys-Mach map: ffffffff81507000->ffffffff81707000
(XEN) Start info: ffffffff81707000->ffffffff817074a4
(XEN) Page tables: ffffffff81708000->ffffffff81717000
(XEN) Boot stack: ffffffff81717000->ffffffff81718000
(XEN) TOTAL: ffffffff80000000->ffffffff81800000
(XEN) ENTRY ADDRESS: ffffffff80200000
(XEN) Dom0 has maximum 4 VCPUs
(XEN) Scrubbing Free RAM:
......................................................................done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch input to Xen)
(XEN) Freed 108kB init memory.
Additional problem respectively disappointments with the board DB45CB
---------------------------------------------------------------------------------------
Now, I just need to get rid of my frustrations. Of course, some or all of them
might be caused by my
personal lack of Linux or Xen experience ...
- I am not able to configure the onboard GB ethernet adapter on Linux.
Even the e1000e driver
susi:/lib/modules/2.6.26-bpo.1-amd64/kernel/drivers/net/e1000e
of newer kernels does not seam to support that adapter.
As a fix I run addtional NICs in PCI and PCIe slots (inetl 1000 pro, various
brands)
The onboard LAN is unused.
- I was not able to make any use of the remote management features of the board.
On my DHCP server I see that the onboard NIC applies for an IP address and
gets
one from the DHCP server.
There do not seem to be any management clients available for Linux.
The Intel AMT was one reason why I bought that board. However, I do not like
to use
any windows clients for the remote management.
- I am not able to get Xorg running with the onboard graphics adapter.
There is no support for the Q45 Chipset (at least not in the 2.6.18-6, 2.6.24
and of course not in the xen kernels)
- When I insert a PCIe x16 Graphics card (ATI Radeon HD 2400 Pro) the BIOS menu
display somehow becomes slow.
The experience is like if you use a 300 Baut serial line connection.
I was able to configure xorg including 3D with the fglrx driver from ATI
ati-driver-installer-8-5-x86.x86_64.run
xserver-xorg-core 1.1.1-21etch5
and running it on the non-Xen kernel vmlinuz-2.6.18-6-amd64 (Etch)
Although the BIOS menus are slow, the system boots and X11 is functional with
3D.
I don''t know whether the ATI Radeon HD 2400 Pro is performing as fast
as it should but
the experience is not too bad.
However, if I boot the xen kernel vmlinuz-2.6.18.8-xen the system becomes very
very slow.
The system needs about 15 minutes to boot and is unusable.
As a result I switched back to the onboard graphics adapter (Intel) and run my
Xen host without X11.
I plan to test another PCIe x16 graphics adaptor (NVIDIA GeForce 8400GS).
I am just curious whether the problem with the PCIe x16 graphics adapter is
caused by the RADEON card
or whether it is an issue of the mainboard.
- After I ran into the problem with the graphics adapter I planned to test the
VT-d with a HVM Windows guest
and PCI backend hide. However, with the mandatory iommu=1 the Xen-Kernel
freezes.
This wracks another option :-(
In summary I am rather disappointed by the board DB45CB as a platform for XEN.
- VT-d broken. No PCI backend hiding with HVM guest possible
- no onboard LAN on linux
- no remote management from linux
- no onboard graphics on linux
- PCIe x16 graphics with Xen kernel broken
On the positive side I can state the following results:
- Xen host without X11 (xorg) runs perfectly (especially fast).
- I was able to configure and run a WinXP HVM guest (although without VT-d and
PCI backend hiding)
Is there someone out who can show me light at the end of the tunnel?
Hello Intel developers at xen-users:
Is there a chance that some BIOS update for the DB45CB may fix the problems?
What can I do to support such a fix? Provide further evidence, run tests?
Hello Xen developers at xen-users:
Is there a change that some updates of the Xen sources or Xen kernel will fix
the problems?
What can I do to support such a fix? Provide further evidence, run tests?
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
James550
2008-Oct-24 04:18 UTC
Re: [Xen-users] Problem with VT-d on Mainboard Intel DQ45CB
I am having the same problem w/a DQ45CB, Q9300, and 8GB RAM. CentOS 5.2 and Xen 3.3.0. I would LOVE to know why it will continue to hang at that same point w/iommu at 1. Sorry that I am currently without any help to offer. Hopefully someone will point out that one little obvious bit of info that makes it all better. Jon Franz Regensburger wrote:> > Hello all, > > this mail is related to a post by Axel Schöner that I found at > http://article.gmane.org/gmane.comp.emulators.xen.user/40621 > when I was searching the WEB about solutions to my problem. > > I would like to confirm that VT-d with XEN 3.3 kernel 2.6.18.8 on > mainboard > Intel DQ45CB seems to be broken. > > Survey (details are down below) > --------------------------------------- > > Whenever I boot my Xen 2.6.18.8 (Xen 3.3) with kernel parameter iommu=1 > the boot process freezes. > > I see: > ... > (XEN) Intel VT-d has been enabled > ... > (XEN) HVM: VMX enabled > ... > (XEN) I/O virtualisation enabled > (XEN) I/O virtualisation for PV guests disabled > Here the boot process freezes > > Does anybody else suffer from the same problem (VT-d with Intel board > DQ45CB)? > Any suggestions about a solution? > > Regards, > > Franz > > Details about my setup > ---------------------------- > > Hardware: > Mainboard Intel DQ45CB > CPU: Intel Core 2 Quad 9550 > RAM: 8GB > > OS: Debian Linux Etch 4.0 R3 > The plain standard with kernel 2.6.18, the 64bit flavour > > XEN: (compiled from the soruces) > > Mercurial: > dpkg -i ./mercurial-common_1.0.1-5.1~bpo40+1_all.deb > dpkg -i ./mercurial_1.0.1-5.1~bpo40+1_amd64.deb > > Xen source: > wget http://bits.xensource.com/oss-xen/release/3.3.0/xen-3.3.0.tar.gz > > Xen kernel tree: > hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg > > Kernel Config: > Defaults apart from > make linux-2.6-xen-config CONFIGMODE=menuconfig > change XEN->"PCI-device backend driver" from "M" to "*". > > According to messages on the WEB compiling the backend driver fixed into > the kernel is required > in order to get pciback.hide running via kernel parameter. > > GRUB config: > > title Xen 3.3.0 / kernel 2.6.18.8-xen backhide the ATI Radeon > root (hd0,0) > #kernel /xen-3.3.0.gz console=vga noreboot max_loop=128 > dom0_mem=1024M iommu=1 > kernel /xen-3.3.0.gz console=vga noreboot max_loop=128 > dom0_mem=1024M > module /vmlinuz-2.6.18.8-xen root=/dev/mapper/RootVG-root ro > console=tty0 pciback.hide=(01:00.0)(01:00.1) > module /initrd-2.6.18.8-xen.img > savedefault > > Output of ''xm dmesg'' after booting without ''iommu=1'' > > susi:/boot/grub# xm dmesg > __ __ _____ _____ ___ > \ \/ /___ _ __ |___ / |___ / / _ \ > \ // _ \ ''_ \ |_ \ |_ \| | | | > / \ __/ | | | ___) | ___) | |_| | > /_/\_\___|_| |_| |____(_)____(_)___/ > > (XEN) Xen version 3.3.0 (root@wire.laim) (gcc version 4.1.2 20061115 > (prerelease) (Debian 4.1.1-21)) Tue Oct 21 16:22:47 CEST 2008 > (XEN) Latest ChangeSet: unavailable > (XEN) Command line: console=vga noreboot max_loop=128 dom0_mem=1024M > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds > (XEN) EDID info not retrieved because no DDC retrieval method detected > (XEN) Disc information: > (XEN) Found 2 MBR signatures > (XEN) Found 2 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 0000000000095c00 (usable) > (XEN) 0000000000095c00 - 00000000000a0000 (reserved) > (XEN) 00000000000e0000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 00000000bd6e0000 (usable) > (XEN) 00000000bd6e0000 - 00000000bd722000 (ACPI NVS) > (XEN) 00000000bd722000 - 00000000bd840000 (reserved) > (XEN) 00000000bd840000 - 00000000bd843000 (ACPI NVS) > (XEN) 00000000bd843000 - 00000000bd943000 (reserved) > (XEN) 00000000bd943000 - 00000000bd944000 (ACPI NVS) > (XEN) 00000000bd944000 - 00000000bd949000 (reserved) > (XEN) 00000000bd949000 - 00000000bd951000 (ACPI data) > (XEN) 00000000bd951000 - 00000000bd96c000 (ACPI NVS) > (XEN) 00000000bd96c000 - 00000000bd98a000 (reserved) > (XEN) 00000000bd98a000 - 00000000bd990000 (ACPI NVS) > (XEN) 00000000bd990000 - 00000000bdb00000 (usable) > (XEN) 00000000bdc00000 - 00000000c0000000 (reserved) > (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) > (XEN) 00000000ff000000 - 0000000100000000 (reserved) > (XEN) 0000000100000000 - 000000023c000000 (usable) > (XEN) System RAM: 8087MB (8282004kB) > (XEN) ACPI: RSDP 000F03C0, 0024 (r2 INTEL) > (XEN) ACPI: XSDT BD94FE18, 005C (r1 INTEL DQ45CB 3B MSFT > 10013) > (XEN) ACPI: FACP BD94ED98, 00F4 (r4 INTEL A M I 6222004 MSFT > 10013) > (XEN) ACPI: DSDT BD949018, 4E98 (r1 INTEL DQ45CB 3B INTL > 20051117) > (XEN) ACPI: FACS BD957F40, 0040 > (XEN) ACPI: APIC BD94EF18, 006C (r2 INTEL DQ45CB 3B MSFT > 10013) > (XEN) ACPI: MCFG BD959E18, 003C (r1 INTEL DQ45CB 3B MSFT > 97) > (XEN) ACPI: ASF! BD958D18, 00A0 (r32 INTEL DQ45CB 3B TFSM > F4240) > (XEN) ACPI: SPCR BD959D18, 0050 (r1 INTEL DQ45CB 3B AMI. > 3) > (XEN) ACPI: TCPA BD959C98, 0032 (r2 INTEL DQ45CB 3B MSFT > 1000013) > (XEN) ACPI: DMAR BD943C18, 0120 (r1 INTEL DQ45CB 3B INTL > 1) > (XEN) Xen heap: 14MB (14496kB) > (XEN) Domain heap initialised > (XEN) Processor #0 7:7 APIC version 20 > (XEN) Processor #1 7:7 APIC version 20 > (XEN) Processor #2 7:7 APIC version 20 > (XEN) Processor #3 7:7 APIC version 20 > (XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23 > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Detected 2833.050 MHz processor. > (XEN) HVM: VMX enabled > (XEN) CPU0: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz stepping 07 > (XEN) Booting processor 1/1 eip 8c000 > (XEN) CPU1: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz stepping 07 > (XEN) Booting processor 2/2 eip 8c000 > (XEN) CPU2: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz stepping 07 > (XEN) Booting processor 3/3 eip 8c000 > (XEN) CPU3: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz stepping 07 > (XEN) Total of 4 processors activated. > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using new ACK method > (XEN) checking TSC synchronization across 4 CPUs: passed. > (XEN) Platform timer is 3.579MHz ACPI PM Timer > (XEN) Brought up 4 CPUs > (XEN) I/O virtualisation disabled > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> > 0xffffffff805c050c > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000000232000000->0000000234000000 (253952 pages to > be allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff80200000->ffffffff805c050c > (XEN) Init. ramdisk: ffffffff805c1000->ffffffff81506800 > (XEN) Phys-Mach map: ffffffff81507000->ffffffff81707000 > (XEN) Start info: ffffffff81707000->ffffffff817074a4 > (XEN) Page tables: ffffffff81708000->ffffffff81717000 > (XEN) Boot stack: ffffffff81717000->ffffffff81718000 > (XEN) TOTAL: ffffffff80000000->ffffffff81800000 > (XEN) ENTRY ADDRESS: ffffffff80200000 > (XEN) Dom0 has maximum 4 VCPUs > (XEN) Scrubbing Free RAM: > ......................................................................done. > (XEN) Xen trace buffers: disabled > (XEN) Std. Loglevel: Errors and warnings > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) > (XEN) Xen is relinquishing VGA console. > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input > to Xen) > (XEN) Freed 108kB init memory. > > > Additional problem respectively disappointments with the board DB45CB > --------------------------------------------------------------------------------------- > > Now, I just need to get rid of my frustrations. Of course, some or all of > them might be caused by my > personal lack of Linux or Xen experience ... > > - I am not able to configure the onboard GB ethernet adapter on Linux. > Even the e1000e driver > susi:/lib/modules/2.6.26-bpo.1-amd64/kernel/drivers/net/e1000e > of newer kernels does not seam to support that adapter. > As a fix I run addtional NICs in PCI and PCIe slots (inetl 1000 pro, > various brands) > The onboard LAN is unused. > > - I was not able to make any use of the remote management features of the > board. > On my DHCP server I see that the onboard NIC applies for an IP address > and gets > one from the DHCP server. > There do not seem to be any management clients available for Linux. > The Intel AMT was one reason why I bought that board. However, I do not > like to use > any windows clients for the remote management. > > - I am not able to get Xorg running with the onboard graphics adapter. > There is no support for the Q45 Chipset (at least not in the 2.6.18-6, > 2.6.24 and of course not in the xen kernels) > > - When I insert a PCIe x16 Graphics card (ATI Radeon HD 2400 Pro) the BIOS > menu display somehow becomes slow. > The experience is like if you use a 300 Baut serial line connection. > > I was able to configure xorg including 3D with the fglrx driver from ATI > ati-driver-installer-8-5-x86.x86_64.run > xserver-xorg-core 1.1.1-21etch5 > and running it on the non-Xen kernel vmlinuz-2.6.18-6-amd64 (Etch) > > Although the BIOS menus are slow, the system boots and X11 is functional > with 3D. > I don''t know whether the ATI Radeon HD 2400 Pro is performing as fast as > it should but > the experience is not too bad. > > However, if I boot the xen kernel vmlinuz-2.6.18.8-xen the system > becomes very very slow. > The system needs about 15 minutes to boot and is unusable. > > As a result I switched back to the onboard graphics adapter (Intel) and > run my Xen host without X11. > > I plan to test another PCIe x16 graphics adaptor (NVIDIA GeForce > 8400GS). > I am just curious whether the problem with the PCIe x16 graphics adapter > is caused by the RADEON card > or whether it is an issue of the mainboard. > > - After I ran into the problem with the graphics adapter I planned to test > the VT-d with a HVM Windows guest > and PCI backend hide. However, with the mandatory iommu=1 the Xen-Kernel > freezes. > This wracks another option :-( > > In summary I am rather disappointed by the board DB45CB as a platform for > XEN. > - VT-d broken. No PCI backend hiding with HVM guest possible > - no onboard LAN on linux > - no remote management from linux > - no onboard graphics on linux > - PCIe x16 graphics with Xen kernel broken > > On the positive side I can state the following results: > > - Xen host without X11 (xorg) runs perfectly (especially fast). > - I was able to configure and run a WinXP HVM guest (although without VT-d > and PCI backend hiding) > > Is there someone out who can show me light at the end of the tunnel? > > Hello Intel developers at xen-users: > Is there a chance that some BIOS update for the DB45CB may fix the > problems? > What can I do to support such a fix? Provide further evidence, run tests? > > Hello Xen developers at xen-users: > Is there a change that some updates of the Xen sources or Xen kernel will > fix the problems? > What can I do to support such a fix? Provide further evidence, run tests? > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >-- View this message in context: http://www.nabble.com/Problem-with-VT-d-on-Mainboard-Intel-DQ45CB-tp20125720p20140546.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Todd Deshane
2008-Oct-26 00:10 UTC
Re: [Xen-users] Problem with VT-d on Mainboard Intel DQ45CB
Hi. Some questions and comments inline. On Thu, Oct 23, 2008 at 3:25 AM, Franz Regensburger <Franz.Regensburger@odorf.de> wrote:> Hello all, > > this mail is related to a post by Axel Schöner that I found at > http://article.gmane.org/gmane.comp.emulators.xen.user/40621 > when I was searching the WEB about solutions to my problem. > > I would like to confirm that VT-d with XEN 3.3 kernel 2.6.18.8 on mainboard > Intel DQ45CB seems to be broken. > > Survey (details are down below) > --------------------------------------- > > Whenever I boot my Xen 2.6.18.8 (Xen 3.3) with kernel parameter iommu=1 > the boot process freezes. > > I see: > ... > (XEN) Intel VT-d has been enabled > ... > (XEN) HVM: VMX enabled > ... > (XEN) I/O virtualisation enabled > (XEN) I/O virtualisation for PV guests disabled > Here the boot process freezes >I am surprised it freezes here. A serial console debug might be of help here see: http://xen.markmail.org/search/?q=serial%20console%20debugging#query:serial%20console%20debugging+page:1+mid:scjkellgexgofu6d+state:results> Does anybody else suffer from the same problem (VT-d with Intel board DQ45CB)? > Any suggestions about a solution? >This VT-d stuff is quite new and the Intel developers really need help testing and debugging.>From the VTdHowTo on the Xen wiki I see:kernel /boot/xen.gz com1=115200,8n1 console=com1 iommu=1 module /boot/vmlinuz-2.6.18.8-xen root=LABEL=/ ro xencons=ttyS console=tty0 console=ttyS0, pciback.hide=(01:00.0)(03:00.0) module /boot/initrd-2.6.18-xen.img There are some differences in the console''s used with yours.> title Xen 3.3.0 / kernel 2.6.18.8-xen backhide the ATI Radeon > root (hd0,0) > #kernel /xen-3.3.0.gz console=vga noreboot max_loop=128 dom0_mem=1024M iommu=1 > kernel /xen-3.3.0.gz console=vga noreboot max_loop=128 dom0_mem=1024M > module /vmlinuz-2.6.18.8-xen root=/dev/mapper/RootVG-root ro console=tty0 pciback.hide=(01:00.0)(01:00.1) > module /initrd-2.6.18.8-xen.img > savedefault> Additional problem respectively disappointments with the board DB45CB > --------------------------------------------------------------------------------------- > > Now, I just need to get rid of my frustrations. Of course, some or all of them might be caused by my > personal lack of Linux or Xen experience ... > > - I am not able to configure the onboard GB ethernet adapter on Linux. > Even the e1000e driverThis works for me in Ubuntu (not Xen in my experience yet).> susi:/lib/modules/2.6.26-bpo.1-amd64/kernel/drivers/net/e1000e > of newer kernels does not seam to support that adapter. > As a fix I run addtional NICs in PCI and PCIe slots (inetl 1000 pro, various brands) > The onboard LAN is unused. >> - I am not able to get Xorg running with the onboard graphics adapter. > There is no support for the Q45 Chipset (at least not in the 2.6.18-6, 2.6.24 and of course not in the xen kernels) >I would try the latest Ubuntu --Intrepid is at RC now-- (even just the liveCD here for testing)> In summary I am rather disappointed by the board DB45CB as a platform for XEN. > - VT-d broken. No PCI backend hiding with HVM guest possible > - no onboard LAN on linux > - no remote management from linux > - no onboard graphics on linux > - PCIe x16 graphics with Xen kernel broken >Living on the cutting edge is like this sometimes, it will only get better.> On the positive side I can state the following results: > > - Xen host without X11 (xorg) runs perfectly (especially fast). > - I was able to configure and run a WinXP HVM guest (although without VT-d and PCI backend hiding) > > Is there someone out who can show me light at the end of the tunnel? >Here are my suggestions and things to watch for. The Intel developers are quite good and responsive on xen-devel, provided that you are willing to do some testing/debugging and applying patches etc. To get to the point where you can be helpful, you will need to get the latest xen-unstable. hg clone http://xenbits.xensource.com/xen-unstable.hg hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg cd xen-unstable make world Follow these again http://wiki.xensource.com/xenwiki/VTdHowTo Do you testing again and send a shorter, less verbose email to xen-devel. Give the key results and the most descriptive and useful snippets of the appropriate logs. They will work likely work with you, especially since there are quite a few others that are running up against this problem and are also likely to help with testing. The Light at the end of the tunnel on the Xen/Linux side of things will happen as the Xen dom0 gets into mainline. Progress on this seems to be going pretty well. see: http://wiki.xensource.com/xenwiki/XenParavirtOps http://xenbits.xensource.com/paravirt_ops/patches.hg Hope that gives you a better sense and gets the debugging process underway. Best Regards, Todd -- Todd Deshane http://todddeshane.net http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Franz Regensburger
2008-Oct-27 11:04 UTC
Re: [Xen-users] Problem with VT-d on Mainboard Intel DQ45CB
Hello Todd, thank you for your comments. I did not have time yet to follow your suggestions (I certainly will).> To get to the point where you can be helpful, you will need to get the > latest xen-unstable. > > hg clone http://xenbits.xensource.com/xen-unstable.hg > hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg > cd xen-unstable > make worldHowever, yesterday I was able to make some progress with respect to the Intel board DQ45CB that solves most of my problems. It seems that most problems were caused by the board and not Xen! I think it is important to share my new experience as early as possible in order to prevent others for suffering in vain or doing unneccessary error analysis. Some days ago Intel put a new firmware for the board onto their WEB-site CBQ4510H.86A.0061.BI.ZIP I upgraded my board from CBQ4510H.86A.0059 with that new BIOS and the following problems seem to have vanished: Summary: =======Update to BIOS CBQ4510H.86A.0061.BI.ZIP solved the following issues: - Whenever I boot my Xen 2.6.18.8 (Xen 3.3) with kernel parameter iommu=1 the boot process freezes. SOLVED (details below) and related to that - VT-d broken. No PCI backend hiding with HVM guest possible SOLVED (details below) - When I insert a PCIe x16 Graphics card (ATI Radeon HD 2400 Pro) the BIOS menu display somehow becomes slow. The experience is like if you use a 300 Baut serial line connection. SOLVED (details below) - PCIe x16 graphics with Xen kernel broken SOLVED (details below) I will also post the above short note on xen-devel Regards, Franz ############################## Details: My current setup: Xen Source: http://bits.xensource.com/oss-xen/release/3.3.0/xen-3.3.0.tar.gz Xen Kernel: hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg Details for the solved issues: ===================== - Whenever I boot my Xen 2.6.18.8 (Xen 3.3) with kernel parameter iommu=1 the boot process freezes. (SOLVED) After the BIOS update the Xen kernel boots without problems even if I use the iommu=1 #---------------------------- - VT-d broken. No PCI backend hiding with HVM guest possible (SOLVED) PCI backend hideing and VT-d seem to work now! The functionality ''pciback'' is compiled fixed into my kernel (not a module). I use the following grub config title Xen 3.3.0 / kernel 2.6.18.8-xen with IOMMU=1 and backhide 1G NIC root (hd0,0) kernel /xen-3.3.0.gz console=vga noreboot max_loop=128 dom0_mem=1024M iommu=1 module /vmlinuz-2.6.18.8-xen root=/dev/mapper/RootVG-root ro pciback.hide=(03:00.0) module /initrd-2.6.18.8-xen.img The messages/dmesg show kernel: Bootdata ok (command line is root=/dev/mapper/RootVG-root ro pciback.hide=(03:00.0)) ... kernel: pciback 0000:03:00.0: seizing device The xm dmesg shows: (XEN) Xen version 3.3.0 (root@wire.laim) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) Tue Oct 21 16:22:47 CEST 2008 (XEN) Latest ChangeSet: unavailable (XEN) Command line: console=vga noreboot max_loop=128 dom0_mem=1024M iommu=1 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) EDID info not retrieved because of reasons unknown (XEN) Disc information: (XEN) Found 2 MBR signatures (XEN) Found 2 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 0000000000096400 (usable) (XEN) 0000000000096400 - 00000000000a0000 (reserved) (XEN) 00000000000e0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 00000000bfade000 (usable) (XEN) 00000000bfade000 - 00000000bfb21000 (ACPI NVS) (XEN) 00000000bfb21000 - 00000000bfc3f000 (reserved) (XEN) 00000000bfc3f000 - 00000000bfc42000 (ACPI NVS) (XEN) 00000000bfc42000 - 00000000bfd42000 (reserved) (XEN) 00000000bfd42000 - 00000000bfd43000 (ACPI NVS) (XEN) 00000000bfd43000 - 00000000bfd48000 (reserved) (XEN) 00000000bfd48000 - 00000000bfd50000 (ACPI data) (XEN) 00000000bfd50000 - 00000000bfd6b000 (ACPI NVS) (XEN) 00000000bfd6b000 - 00000000bfd8a000 (reserved) (XEN) 00000000bfd8a000 - 00000000bfd90000 (ACPI NVS) (XEN) 00000000bfd90000 - 00000000bff00000 (usable) (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) (XEN) 00000000ff000000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 000000023c000000 (usable) (XEN) System RAM: 8123MB (8318864kB) (XEN) ACPI: RSDP 000F03C0, 0024 (r2 INTEL) (XEN) ACPI: XSDT BFD4EE18, 005C (r1 INTEL DQ45CB 3D MSFT 10013) (XEN) ACPI: FACP BFD4DD98, 00F4 (r4 INTEL A M I 6222004 MSFT 10013) (XEN) ACPI: DSDT BFD48018, 4E9A (r1 INTEL DQ45CB 3D INTL 20051117) (XEN) ACPI: FACS BFD56F40, 0040 (XEN) ACPI: APIC BFD4DF18, 006C (r2 INTEL DQ45CB 3D MSFT 10013) (XEN) ACPI: MCFG BFD58E18, 003C (r1 INTEL DQ45CB 3D MSFT 97) (XEN) ACPI: ASF! BFD57D18, 00A0 (r32 INTEL DQ45CB 3D TFSM F4240) (XEN) ACPI: SPCR BFD58D18, 0050 (r1 INTEL DQ45CB 3D AMI. 3) (XEN) ACPI: TCPA BFD58C98, 0032 (r2 INTEL DQ45CB 3D MSFT 1000013) (XEN) ACPI: DMAR BFD42F18, 00D8 (r1 INTEL DQ45CB 3D INTL 1) (XEN) Xen heap: 14MB (14496kB) (XEN) Domain heap initialised (XEN) Processor #0 7:7 APIC version 20 (XEN) Processor #1 7:7 APIC version 20 (XEN) Processor #2 7:7 APIC version 20 (XEN) Processor #3 7:7 APIC version 20 (XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Intel VT-d has been enabled (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2833.076 MHz processor. (XEN) HVM: VMX enabled (XEN) CPU0: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz stepping 07 (XEN) Booting processor 1/1 eip 8c000 (XEN) CPU1: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz stepping 07 (XEN) Booting processor 2/2 eip 8c000 (XEN) CPU2: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz stepping 07 (XEN) Booting processor 3/3 eip 8c000 (XEN) CPU3: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz stepping 07 (XEN) Total of 4 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) checking TSC synchronization across 4 CPUs: passed. (XEN) Platform timer is 3.579MHz ACPI PM Timer (XEN) Brought up 4 CPUs (XEN) I/O virtualisation enabled (XEN) I/O virtualisation for PV guests disabled (XEN) mtrr: your CPUs had inconsistent fixed MTRR settings (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> 0xffffffff805c050c (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000230000000->0000000232000000 (253952 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff80200000->ffffffff805c050c (XEN) Init. ramdisk: ffffffff805c1000->ffffffff81506800 (XEN) Phys-Mach map: ffffffff81507000->ffffffff81707000 (XEN) Start info: ffffffff81707000->ffffffff817074a4 (XEN) Page tables: ffffffff81708000->ffffffff81717000 (XEN) Boot stack: ffffffff81717000->ffffffff81718000 (XEN) TOTAL: ffffffff80000000->ffffffff81800000 (XEN) ENTRY ADDRESS: ffffffff80200000 (XEN) Dom0 has maximum 4 VCPUs (XEN) Scrubbing Free RAM: .....................................................................done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen) (XEN) Freed 108kB init memory. (XEN) mtrr: type mismatch for c0000000,10000000 old: write-back new: write-combining In the config of the HVM WinXP guest I use: pci=[ ''03:00.0'' ] In the running guest I see a new (native) 1Gbit NIC. I did not do any performance test yet. However the VT-d/PCI backend hide mechanism seems to work :-) #---------------------------- - When I insert a PCIe x16 Graphics card (ATI Radeon HD 2400 Pro) the BIOS menu display somehow becomes slow. The experience is like if you use a 300 Baut serial line connection. (SOLVED) Details see next paragraph - PCIe x16 graphics with Xen kernel broken SOLVED After the BIOS update I tested two PCIe x16 graphics adapters: - ATI Radeon HD 2400 Pro - MSI NX 8400GS (Nvidia 8400GS) Both cards run now without problems on a non-Xen standard Debian etch 2.6.18.6 kernel. Especially, the BIOS menus are no longer slowed down. 3D runs perfectly with the propriatary drivers ATI: ati-driver-installer-8-5-x86.x86_64.run NVIDIA: NVIDIA-Linux-x86_64-177.80-pkg2.run Caveat: after testing the Nvida Card/Driver you need to remove some links that point to NVIDIA drivers before you test again the ATI card/driver. Search /usr/lib for files like with ''*177.80*'' in them. With the xen-kernel 2.6.18.8 booted (details about version above) I was able to configure the ATI card for X11 by using the ATI driver ati-driver-installer-8-5-x86.x86_64.run. However, 3D s broken due to a problem with symbols Oct 27 10:09:09 susi kernel: fglrx: Unknown symbol xen_invlpg_mask With the xen-kernel 2.6.18.8 booted (details about version above) I was not able to compile the NVIDIA driver NVIDIA-Linux-x86_64-177.80-pkg2.run The build script from NVIDIA expclicitly states that it won''t not run on a XEN-kernel #----------------------- Details about BIOS update I download the archive CBQ4510H.86A.0061.BI.ZIP from the Intel page I had quite some hard time to install the update via the DOS-Utility IFLASH.EXE on a host without FD-drive and only linux installed on the HDs. After frantically searching for some old Win boot media I came up with a good old Win98SE2 boot CD. It has the nice feature to recognize USB sticks as FD disk drive B: Then I proceeded as follows. (Shame on me that I do not know how to do it better with purely Linux and freeDos basis Is anybody out there who can educate me?) Unpack the zip archive. This yields CB0061.BIO CB0061.ITK IFLASH.EXE Copy these files to a USB stick with FAT FS Reboot the host and enter BIOS Set Advanced/Drives Disk mode from RAID to IDE This allows for a proper Win98SE2 boot from CD Boot a Win98SE2 CD. It will recognize the USB stick as drive b: b: iflash /PF CB0061.BIO When prompted - remove CD - remove USB stick type return an wait until BIOS flash has finished It takes about 3-5 minutes _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andrew Lyon
2008-Oct-27 19:43 UTC
Re: [Xen-users] Problem with VT-d on Mainboard Intel DQ45CB
On Mon, Oct 27, 2008 at 11:04 AM, Franz Regensburger <Franz.Regensburger@odorf.de> wrote:> Hello Todd, > > thank you for your comments. > I did not have time yet to follow your suggestions (I certainly will). >> To get to the point where you can be helpful, you will need to get the >> latest xen-unstable. >> >> hg clone http://xenbits.xensource.com/xen-unstable.hg >> hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg >> cd xen-unstable >> make world > > However, yesterday I was able to make some progress with respect to the Intel board DQ45CB that > solves most of my problems. > > It seems that most problems were caused by the board and not Xen! > I think it is important to share my new experience as early as possible in order to prevent others for > suffering in vain or doing unneccessary error analysis. > > Some days ago Intel put a new firmware for the board onto their WEB-site > CBQ4510H.86A.0061.BI.ZIP > > I upgraded my board from CBQ4510H.86A.0059 with that new BIOS and the following problems seem to have vanished: > > Summary: > =======> Update to BIOS CBQ4510H.86A.0061.BI.ZIP solved the following issues: > > - Whenever I boot my Xen 2.6.18.8 (Xen 3.3) with kernel parameter iommu=1 > the boot process freezes. > SOLVED (details below) > > and related to that > > - VT-d broken. No PCI backend hiding with HVM guest possible > SOLVED (details below) > > - When I insert a PCIe x16 Graphics card (ATI Radeon HD 2400 Pro) the BIOS menu display > somehow becomes slow. The experience is like if you use a 300 Baut serial line connection. > SOLVED (details below) > > - PCIe x16 graphics with Xen kernel broken > SOLVED (details below) > > > I will also post the above short note on xen-devel > > Regards, > > Franz > > ############################## > > Details: > > My current setup: > Xen Source: http://bits.xensource.com/oss-xen/release/3.3.0/xen-3.3.0.tar.gz > Xen Kernel: hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg > > Details for the solved issues: > =====================> > - Whenever I boot my Xen 2.6.18.8 (Xen 3.3) with kernel parameter iommu=1 > the boot process freezes. (SOLVED) > > After the BIOS update the Xen kernel boots without problems even if I use the iommu=1 > > #---------------------------- > > - VT-d broken. No PCI backend hiding with HVM guest possible (SOLVED) > > PCI backend hideing and VT-d seem to work now! > > The functionality ''pciback'' is compiled fixed into my kernel (not a module). > > I use the following grub config > > title Xen 3.3.0 / kernel 2.6.18.8-xen with IOMMU=1 and backhide 1G NIC > root (hd0,0) > kernel /xen-3.3.0.gz console=vga noreboot max_loop=128 dom0_mem=1024M iommu=1 > module /vmlinuz-2.6.18.8-xen root=/dev/mapper/RootVG-root ro pciback.hide=(03:00.0) > module /initrd-2.6.18.8-xen.img > > The messages/dmesg show > > kernel: Bootdata ok (command line is root=/dev/mapper/RootVG-root ro pciback.hide=(03:00.0)) > ... > kernel: pciback 0000:03:00.0: seizing device > > The xm dmesg shows: > (XEN) Xen version 3.3.0 (root@wire.laim) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) Tue Oct 21 16:22:47 CEST 2008 > (XEN) Latest ChangeSet: unavailable > (XEN) Command line: console=vga noreboot max_loop=128 dom0_mem=1024M iommu=1 > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds > (XEN) EDID info not retrieved because of reasons unknown > (XEN) Disc information: > (XEN) Found 2 MBR signatures > (XEN) Found 2 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 0000000000096400 (usable) > (XEN) 0000000000096400 - 00000000000a0000 (reserved) > (XEN) 00000000000e0000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 00000000bfade000 (usable) > (XEN) 00000000bfade000 - 00000000bfb21000 (ACPI NVS) > (XEN) 00000000bfb21000 - 00000000bfc3f000 (reserved) > (XEN) 00000000bfc3f000 - 00000000bfc42000 (ACPI NVS) > (XEN) 00000000bfc42000 - 00000000bfd42000 (reserved) > (XEN) 00000000bfd42000 - 00000000bfd43000 (ACPI NVS) > (XEN) 00000000bfd43000 - 00000000bfd48000 (reserved) > (XEN) 00000000bfd48000 - 00000000bfd50000 (ACPI data) > (XEN) 00000000bfd50000 - 00000000bfd6b000 (ACPI NVS) > (XEN) 00000000bfd6b000 - 00000000bfd8a000 (reserved) > (XEN) 00000000bfd8a000 - 00000000bfd90000 (ACPI NVS) > (XEN) 00000000bfd90000 - 00000000bff00000 (usable) > (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) > (XEN) 00000000ff000000 - 0000000100000000 (reserved) > (XEN) 0000000100000000 - 000000023c000000 (usable) > (XEN) System RAM: 8123MB (8318864kB) > (XEN) ACPI: RSDP 000F03C0, 0024 (r2 INTEL) > (XEN) ACPI: XSDT BFD4EE18, 005C (r1 INTEL DQ45CB 3D MSFT 10013) > (XEN) ACPI: FACP BFD4DD98, 00F4 (r4 INTEL A M I 6222004 MSFT 10013) > (XEN) ACPI: DSDT BFD48018, 4E9A (r1 INTEL DQ45CB 3D INTL 20051117) > (XEN) ACPI: FACS BFD56F40, 0040 > (XEN) ACPI: APIC BFD4DF18, 006C (r2 INTEL DQ45CB 3D MSFT 10013) > (XEN) ACPI: MCFG BFD58E18, 003C (r1 INTEL DQ45CB 3D MSFT 97) > (XEN) ACPI: ASF! BFD57D18, 00A0 (r32 INTEL DQ45CB 3D TFSM F4240) > (XEN) ACPI: SPCR BFD58D18, 0050 (r1 INTEL DQ45CB 3D AMI. 3) > (XEN) ACPI: TCPA BFD58C98, 0032 (r2 INTEL DQ45CB 3D MSFT 1000013) > (XEN) ACPI: DMAR BFD42F18, 00D8 (r1 INTEL DQ45CB 3D INTL 1) > (XEN) Xen heap: 14MB (14496kB) > (XEN) Domain heap initialised > (XEN) Processor #0 7:7 APIC version 20 > (XEN) Processor #1 7:7 APIC version 20 > (XEN) Processor #2 7:7 APIC version 20 > (XEN) Processor #3 7:7 APIC version 20 > (XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23 > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) Intel VT-d has been enabled > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Detected 2833.076 MHz processor. > (XEN) HVM: VMX enabled > (XEN) CPU0: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz stepping 07 > (XEN) Booting processor 1/1 eip 8c000 > (XEN) CPU1: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz stepping 07 > (XEN) Booting processor 2/2 eip 8c000 > (XEN) CPU2: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz stepping 07 > (XEN) Booting processor 3/3 eip 8c000 > (XEN) CPU3: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz stepping 07 > (XEN) Total of 4 processors activated. > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using new ACK method > (XEN) checking TSC synchronization across 4 CPUs: passed. > (XEN) Platform timer is 3.579MHz ACPI PM Timer > (XEN) Brought up 4 CPUs > (XEN) I/O virtualisation enabled > (XEN) I/O virtualisation for PV guests disabled > (XEN) mtrr: your CPUs had inconsistent fixed MTRR settings > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> 0xffffffff805c050c > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000000230000000->0000000232000000 (253952 pages to be allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff80200000->ffffffff805c050c > (XEN) Init. ramdisk: ffffffff805c1000->ffffffff81506800 > (XEN) Phys-Mach map: ffffffff81507000->ffffffff81707000 > (XEN) Start info: ffffffff81707000->ffffffff817074a4 > (XEN) Page tables: ffffffff81708000->ffffffff81717000 > (XEN) Boot stack: ffffffff81717000->ffffffff81718000 > (XEN) TOTAL: ffffffff80000000->ffffffff81800000 > (XEN) ENTRY ADDRESS: ffffffff80200000 > (XEN) Dom0 has maximum 4 VCPUs > (XEN) Scrubbing Free RAM: .....................................................................done. > (XEN) Xen trace buffers: disabled > (XEN) Std. Loglevel: Errors and warnings > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) > (XEN) Xen is relinquishing VGA console. > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen) > (XEN) Freed 108kB init memory. > (XEN) mtrr: type mismatch for c0000000,10000000 old: write-back new: write-combining > > In the config of the HVM WinXP guest I use: > > pci=[ ''03:00.0'' ] > > In the running guest I see a new (native) 1Gbit NIC. > I did not do any performance test yet. > However the VT-d/PCI backend hide mechanism seems to work :-) > > #---------------------------- > > - When I insert a PCIe x16 Graphics card (ATI Radeon HD 2400 Pro) the BIOS menu display > somehow becomes slow. The experience is like if you use a 300 Baut serial line connection. > (SOLVED) > Details see next paragraph > > - PCIe x16 graphics with Xen kernel broken > SOLVED > > After the BIOS update I tested two PCIe x16 graphics adapters: > - ATI Radeon HD 2400 Pro > - MSI NX 8400GS (Nvidia 8400GS) > Both cards run now without problems on a non-Xen standard Debian etch 2.6.18.6 kernel. > Especially, the BIOS menus are no longer slowed down. > 3D runs perfectly with the propriatary drivers > ATI: ati-driver-installer-8-5-x86.x86_64.run > NVIDIA: NVIDIA-Linux-x86_64-177.80-pkg2.run > > Caveat: after testing the Nvida Card/Driver you need to remove some links that point to > NVIDIA drivers before you test again the ATI card/driver. > Search /usr/lib for files like with ''*177.80*'' in them. > > With the xen-kernel 2.6.18.8 booted (details about version above) I was able to configure the ATI card for X11 > by using the ATI driver ati-driver-installer-8-5-x86.x86_64.run. > However, 3D s broken due to a problem with symbols > > Oct 27 10:09:09 susi kernel: fglrx: Unknown symbol xen_invlpg_mask > > With the xen-kernel 2.6.18.8 booted (details about version above) I was not able to compile the NVIDIA driver > NVIDIA-Linux-x86_64-177.80-pkg2.run > The build script from NVIDIA expclicitly states that it won''t not run on a XEN-kernelThe build script can be told to ignore Xen, I am running 177.80 on 2.6.27.3 (kernel.org + modified suse xen patches) with a single 9500GT driving two 1920x1200 TFT''s (not xinerama), I have a non xen kernel of the same version installed so when I need to install nvidia drivers I do the following: rm /usr/src/linux ln -s /usr/src/linux-2.6.27 /usr/src/linux emerge nvidia-drivers #substitute the appropriate command for your distro rm /usr/src/linux ln -s /usr/src/linux-2.6.27-xen /usr/src/linux cd /usr/src sh /home/andy/Desktop/NVIDIA-Linux-x86_64-177.80-pkg2.run -x cd NVIDIA-Linux-x86_64-177.80-pkg2/usr/src/nv/ IGNORE_XEN_PRESENCE=y SYSSRC=/usr/src/linux make module IGNORE_XEN_PRESENCE=y SYSSRC=/usr/src/linux make install modprobe nvidia The drivers seem to work quite well under Xen, I can''t really say they are stable as my system occasionally locks up, but that happens without the nvidia module/drivers loaded or X running at all and it doesn''t happen more frequently with them loaded so I think they are probably ok. Andy> > #----------------------- > > Details about BIOS update > > I download the archive > CBQ4510H.86A.0061.BI.ZIP > from the Intel page > > I had quite some hard time to install the update via the DOS-Utility IFLASH.EXE on a host without FD-drive > and only linux installed on the HDs. After frantically searching for some old Win boot media I came up with > a good old Win98SE2 boot CD. It has the nice feature to recognize USB sticks as FD disk drive B: > > Then I proceeded as follows. > (Shame on me that I do not know how to do it better with purely Linux and freeDos basis > Is anybody out there who can educate me?) > > Unpack the zip archive. > This yields > > CB0061.BIO > CB0061.ITK > IFLASH.EXE > > Copy these files to a USB stick with FAT FS > > Reboot the host and enter BIOS > Set Advanced/Drives Disk mode from RAID to IDE > This allows for a proper Win98SE2 boot from CD > > Boot a Win98SE2 CD. > It will recognize the USB stick as drive b: > > b: > iflash /PF CB0061.BIO > > When prompted > - remove CD > - remove USB stick > > type return an wait until BIOS flash has finished > > It takes about 3-5 minutes > > > > _______________________________________________ > 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
James550
2008-Nov-12 21:17 UTC
Re: [Xen-users] Problem with VT-d on Mainboard Intel DQ45CB
I did the same thing as you in updating to the *61 bios. That also got me past the "PV guests disabled" freeze that I also was experiencing. Now, I am hitting a freeze after "(XEN) mtrr: your CPUs had inconsistent fixed MTRR settings" is displayed. From what I see, "(XEN) *** LOADING DOMAIN 0 ***" should be the next thing seen. When I did previous installations of XEN on CentOS 5.2 without using VT-d, I did not have to setup anything ahead of time. I wonder if I need to edit another config somewhere to make the boot process complete? Other than the changes/settings that you showed in your "solution" post, were there other settings (perhaps dom 0 related) that I am just missing or need to correct? Perhaps something during a compile or config?!? I would appreciate any help that you can offer. :) -- View this message in context: http://www.nabble.com/Problem-with-VT-d-on-Mainboard-Intel-DQ45CB-tp20125720p20469660.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Todd Deshane
2008-Nov-12 21:22 UTC
Re: [Xen-users] Problem with VT-d on Mainboard Intel DQ45CB
On Wed, Nov 12, 2008 at 4:17 PM, James550 <jrh4u@hotmail.com> wrote:> > I did the same thing as you in updating to the *61 bios. That also got me > past the "PV guests disabled" freeze that I also was experiencing. Now, I > am hitting a freeze after "(XEN) mtrr: your CPUs had inconsistent fixed MTRR > settings" is displayed. From what I see, "(XEN) *** LOADING DOMAIN 0 ***" > should be the next thing seen. When I did previous installations of XEN on > CentOS 5.2 without using VT-d, I did not have to setup anything ahead of > time. I wonder if I need to edit another config somewhere to make the boot > process complete? Other than the changes/settings that you showed in your > "solution" post, were there other settings (perhaps dom 0 related) that I am > just missing or need to correct? Perhaps something during a compile or > config?!? I would appreciate any help that you can offer. :)Could you try xen-unstable? there have been a lot of bug fixes since the 3.3.0 release. Cheers, Todd> -- > View this message in context: http://www.nabble.com/Problem-with-VT-d-on-Mainboard-Intel-DQ45CB-tp20125720p20469660.html > Sent from the Xen - User mailing list archive at Nabble.com. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Todd Deshane http://todddeshane.net http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James550
2008-Nov-12 21:58 UTC
Re: [Xen-users] Problem with VT-d on Mainboard Intel DQ45CB
I ran through the setup process for xen-unstable and I believe that everything is coming up as 3.4 for the xen-unstable rev. I can''t immediately confirm as I am not near the machine. But, in perusing the boot folder(s) I am pretty sure that I saw a few "xen-3.4" type files. I used xen-unstable on the previous attempt (the one that ended at the boot hang at "PV..." like yours did) and ran through the same setup steps this time. I got past that freeze (after the bios update) but am now stuck elsewhere. :( I wondered if I missed some config step in the compile/config steps or if there was some other setup step to allow it to boot into things normally. Up until this recent error, it really seemed as though we were suffering from the exact same issue(s). -- View this message in context: http://www.nabble.com/Problem-with-VT-d-on-Mainboard-Intel-DQ45CB-tp20125720p20469985.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Franz Regensburger
2008-Nov-13 13:45 UTC
Re: [Xen-users] Problem with VT-d on Mainboard Intel DQ45CB
Hello James,
please find my settings and some howtos about the Xen build and Win-guest
setup in the attachment. I also attached the xen kernel config file I used
for my build.
I am not sure where you are stuck at the moment.
Please contact me if you need more details about my settings or some
additional messages.
On my side the DQ45CB works quite well.
Especially VT-d with HVM guests like Win2003Server seem to work.
Only things I am missing with respect to the DQ45CB are:
- onboard NIC is not configurable. Probably a driver (e1000) problem
- onboard graphics card is not supported by the X-Server I am using
I use the
xserver-xorg 7.1.0-19 the X.Org X server
xserver-xorg-core 1.1.1-21etch5 X.Org X server -- core server
that comes with DebianEtch
Regards,
Franz
Am Mittwoch, 12. November 2008 22:58 schrieb James550:> I ran through the setup process for xen-unstable and I believe that
> everything is coming up as 3.4 for the xen-unstable rev. I can''t
> immediately confirm as I am not near the machine. But, in perusing the
> boot folder(s) I am pretty sure that I saw a few "xen-3.4" type
files. I
> used xen-unstable on the previous attempt (the one that ended at the boot
> hang at "PV..." like yours did) and ran through the same setup
steps this
> time. I got past that freeze (after the bios update) but am now stuck
> elsewhere. :( I wondered if I missed some config step in the compile/config
> steps or if there was some other setup step to allow it to boot into things
> normally. Up until this recent error, it really seemed as though we were
> suffering from the exact same issue(s).
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
James550
2008-Nov-13 18:04 UTC
Re: [Xen-users] Problem with VT-d on Mainboard Intel DQ45CB
Looks like you''re running your config off of a debian system and I am on an RH/CentOS OS. Should I start over using a deb/Ubuntu style OS? Would that give me more options/better compatibility for the Xen install? I can''t seem to accomplish some of the install steps that you listed in your reply as I just am not finding RH equivalent commands... -- View this message in context: http://www.nabble.com/Problem-with-VT-d-on-Mainboard-Intel-DQ45CB-tp20125720p20486209.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Franz Regensburger
2008-Nov-17 13:12 UTC
Re: [Xen-users] Problem with VT-d on Mainboard Intel DQ45CB
Hello James, Am Donnerstag, 13. November 2008 19:04 schrieb James550:> Should I start over using a deb/Ubuntu style OS? Would that > give me more options/better compatibility for the Xen install?I don''t think that you need to switch to Debian. The packets I install on my Debian machine just provide the basis for the build environment (compiler, libs etc.) All what comprises Xen is part of the stuff you download via mercurial using the commands hg clone http://xenbits.xensource.com/xen-unstable.hg hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg> I can''t > seem to accomplish some of the install steps that you listed in your reply > as I just am not finding RH equivalent commands...What exactly are these commands? If you refer to the preliminary dpkg -i ./mercurial-common_1.0.1-5.1~bpo40+1_all.deb dpkg -i ./mercurial_1.0.1-5.1~bpo40+1_amd64.deb and aptitude install iproute aptitude install bridge-utils ... this is no problem. You ''just'' need to find out the equivalent package manager commands for your distro. As an alternative you also may download the software as tar-balls and compile them yourself on your machine. The following info is from the /usr/src/xen-unstable.hg/README. It lists all the components you need for building Xen from the sources. ## START Quick-Start Guide - Source Release ================================= First, there are a number of prerequisites for building a Xen source release. Make sure you have all the following installed, either by visiting the project webpage or installing a pre-built package provided by your Linux distributor: * GCC v3.4 or later * GNU Make * GNU Binutils * Development install of zlib (e.g., zlib-dev) * Development install of Python v2.3 or later (e.g., python-dev) * Development install of curses (e.g., libncurses-dev) * Development install of openssl (e.g., openssl-dev) * Development install of x11 (e.g. xorg-x11-dev) * bridge-utils package (/sbin/brctl) * iproute package (/sbin/ip) * hotplug or udev ## END Regards, Franz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James550
2008-Nov-19 06:19 UTC
Re: [Xen-users] Problem with VT-d on Mainboard Intel DQ45CB
Still using Centos5.2, followed the steps mentioned here and elsewhere to see if it made a difference when compared to my original steps. Unfortunately I am still running into a boot freeze at the "MTRR" line that I mentioned earlier. If I change "iommu" to 0, then I can boot into the 2.6.18-xen kernel w/out the freeze. Is there a bios setting that I am missing? Is there a setting during the "make linux-2.6-xen-config CONFIGMODE=menuconfig" step that I missed or need to change? It looks like this is what is expected to follow this "(XEN) mtrr: your CPUs had inconsistent fixed MTRR settings": (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> 0xffffffff805c048c I''m stumped and would love to benefit from any of your knowledge and experience. :) -- View this message in context: http://www.nabble.com/Problem-with-VT-d-on-Mainboard-Intel-DQ45CB-tp20125720p20574334.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Franz Regensburger
2008-Nov-20 20:27 UTC
Re: [Xen-users] Problem with VT-d on Mainboard Intel DQ45CB
Hello James, did you do the following (it''s metioned in my howto file)?>make linux-2.6-xen-config CONFIGMODE=menuconfig > > change XEN->"PCI-device backend driver" from "M" to "*".This compiles the PCI-device backend driver fixed into the kernel. I tried to use the module but did not succeed in loading the module and activating the PCI backend hiding that way. However, compiling it fixed into the kernel works for me. Regards, Franz Am Mittwoch, 19. November 2008 07:19 schrieb James550:> Still using Centos5.2, followed the steps mentioned here and elsewhere to > see if it made a difference when compared to my original steps. > Unfortunately I am still running into a boot freeze at the "MTRR" line that > I mentioned earlier. If I change "iommu" to 0, then I can boot into the > 2.6.18-xen kernel w/out the freeze. Is there a bios setting that I am > missing? Is there a setting during the "make linux-2.6-xen-config > CONFIGMODE=menuconfig" step that I missed or need to change? > > > It looks like this is what is expected to follow this "(XEN) mtrr: your > CPUs had inconsistent fixed MTRR settings": > > (XEN) *** LOADING DOMAIN 0 *** > > (XEN) Xen kernel: 64-bit, lsb, compat32 > > (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> > 0xffffffff805c048c > > > I''m stumped and would love to benefit from any of your knowledge and > experience. :)_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James550
2008-Nov-21 01:57 UTC
Re: [Xen-users] Problem with VT-d on Mainboard Intel DQ45CB
Oh yes, I most certainly did do that (change "M" to "*"). I''ve done that each time that I''ve started from scratch. I''ve done my best to follow the "VT-d howto" on the Xen site. Would it be an issue w/just the "PCI-device backend driver" setting that would keep the system from fully booting w/iommu set to "1" in menu.lst? Since it seems to freeze before the section where it boots into dom0; might there be something else, with iommu=1, that keeps that linux/xen kernel from booting? Otherwise, I can try to go w/a Debian setup (and have no problem with the idea of doing so), I just want the CentOS one to work!! :) -- View this message in context: http://www.nabble.com/Problem-with-VT-d-on-Mainboard-Intel-DQ45CB-tp20125720p20613888.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Daniel Kao
2009-Jul-16 20:59 UTC
Re: [Xen-users] Problem with VT-d on Mainboard Intel DQ45CB
James550 wrote:> Oh yes, I most certainly did do that (change "M" to "*"). I''ve done that > each time that I''ve started from scratch. I''ve done my best to follow the > "VT-d howto" on the Xen site. Would it be an issue w/just the "PCI-device > backend driver" setting that would keep the system from fully booting > w/iommu set to "1" in menu.lst? Since it seems to freeze before the section > where it boots into dom0; might there be something else, with iommu=1, that > keeps that linux/xen kernel from booting? Otherwise, I can try to go w/a > Debian setup (and have no problem with the idea of doing so), I just want > the CentOS one to work!! :) > >Sorry to resurrect and old thread, but I was wondering how the Intel DQ45CB & VT-d is working on 3.4.0? Anyone using CentOS 5.3 x86_64 as the dom0 and 3.4.0 off the git repo? Cheers, Daniel -- Daniel Kao - Seattle, WA, U.S.A. Übermind, Inc. * http://ubermind.com/ * "Your Vision, Our Experience" WOlastic * http://wolastic.com/ * "WebObjects in the Cloud" _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users