Re: [Xen-users] Xen-3.2.1 VT-d supportLink to this message

["Bryan York" <bryan.york@xxxxxxxxx>]

Hello again,

I just tried again with the SPRMS. It still hangs with pci=nommconf. Also, do I put pci=nommconf in the kernel or module line?

My current grub list:

title CentOS (2.6.18-92.1.6.el5xen)
        root (hd0,0)
#       kernel /xen.gz-2.6.18-92.1.6.el5
        kernel /xen.gz-3.2 vtd=1 pci=nommconf
        module /vmlinuz-2.6.18-92.1.6.el5xen pci=nommconf ro root=/dev/VolGroup00/LogVol00 rhgb
        module /initrd-2.6.18-92.1.6.el5xen.img

Thanks for any help...

-Bryan

On Mon, Aug 4, 2008 at 4:53 PM, Bryan York <bryan.york@xxxxxxxxx> wrote:

1) CentOS 5.2 (Tried with mercurial with 3.2, testing and 3.2 CentOS SRPMS)
2) Tried vmlinuz-2.6.18-92.1.6.el5xen per SPRMS (thanks to your message on the list) and mercurial 3.2 and unstable 2.6.18.8-xen kernel.
3) title CentOS (2.6.18.8-xen)
        root (hd0,0)
        kernel /xen.gz vtd=1 msi_irq_enable=1 com1=115200,8n1 console=com1
        module /vmlinuz-2.6.18.8-xen ro root=/dev/VolGroup00/LogVol00 rhgb xencons=ttyS console=tty0 console=ttyS0, pciback.hide=(02:00.0)
        module /initrd-2.6.18-xen.img
4) VT-d is enabled in the bios.

I just tried pci=nommconf and it boots now, however now I get:

(XEN) [VT-D]dmar.c:441: RMRR is incorrect.
(XEN) Failed to parse ACPI DMAR.  Disabling VT-d.
(XEN) [VT-D]ACPI DMAR:No DMAR devices found

This is with mercurial Xen 3.2 testing. Please let me know if the CentOS SRPMS might work in this case.

Thanks!

-Bryan

On Mon, Aug 4, 2008 at 4:21 PM, Daniel Kao <dkao@xxxxxxxxxxxx> wrote:

Bryan,

#1. Which distro are you using under Xen (i.e. RHEL/Cent5, SUSE 10, etc.)
#2. Which Xen kernel are you using? (e.g. module /vmlinuz-2.6.18-92.1.6.el5xen)
#3. Please copy/paste us your kernel & module line in your grub.conf (i.e. kernel /xen.gz-3.2 vtd=1) etc.

** Please note that on my DQ35JO with stock RHEL5/CentOS5 kernels, I had to disable mmconf to even boot the system on a DQ35JO. (pci=nommconf)  Otherwise, the system hangs.

#4. Check to make sure "VT-d" is enabled in the DQ35JO BIOS along with the Vanderpool BIOS settings.  (VT-d is disabled by default on the DQ35JO).

Cheers,
Daniel

Bryan York wrote:

Hello,

I'm also seeing this. I have DQ35JO motherboard and a Q6600 processor. I have the latest 933 bios for my motherboard. It hangs for me at "Brought up 4 CPUs." I've gone through many many different distros and can't find a solution. I've also tried xen-unstable, but then vt-d does not get enabled. I get "I/O Virtualisation disabled."

Any ideas?

Thanks,

-Bryan

-- 
Daniel Kao
Übermind, Inc.
Seattle, WA, U.S.A.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx

http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users