Hello there, I am using a Gigabyte H55M-UD2H (Intel H55-Chipset) together with a Core-i5-650. According to Gigabyte Support the Mainboard does support VT-d. Well, actually support says, that VT-d does work on Windows-7 in XP-Mode. They do not test and support Linux though. Did anybody here have success using VT-d on any H55-Board? Perhaps it is some misconfiguration on my side. I tried a hundred things, but with no effect. I am using Gentoo 32bit PAE as Dom0 with Xen 3.4.2. sys-kernel/xen-sources-2.6.31-r10 app-emulation/xen-3.4.2-r1 USE="pae -acm -custom-cflags -debug -flask -xsm" app-emulation/xen-tools-3.4.2 USE="hvm -acm -api -custom-cflags -debug -doc -flask -pygrub -screen" Grub: kernel /boot/xen.gz vtd=1 iommu=1 vga=gfx-1024x768x16 msi=1 ------------------------- xm info host : xen release : 2.6.31-xen-r10 version : #18 SMP Sun Feb 14 23:06:16 CET 2010 machine : i686 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 2 cpu_mhz : 3197 hw_caps : bfebfbff:28100000:00000000:00000740:0298e3ff:00000000:00000001:00000000 virt_caps : hvm total_memory : 3835 free_memory : 2 node_to_cpu : node0:0-3 node_to_memory : node0:2 xen_major : 3 xen_minor : 4 xen_extra : .2 xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xf5800000 xen_changeset : unavailable cc_compiler : gcc version 4.3.4 (Gentoo 4.3.4 p1.0, pie-10.1.5) cc_compile_by : root cc_compile_domain : holpert.de cc_compile_date : Wed Feb 17 15:01:17 CET 2010 xend_config_format : 4 ------------------------- xm dmesg __ __ _____ _ _ ____ \ \/ /___ _ __ |___ /| || | |___ \ \ // _ \ ''_ \ |_ \| || |_ __) | / \ __/ | | | ___) |__ _| / __/ /_/\_\___|_| |_| |____(_) |_|(_)_____| (XEN) Xen version 3.4.2 (root@holpert.de) (gcc version 4.3.4 (Gentoo 4.3.4 p1.0, pie-10.1.5) ) Wed Feb 17 15:01:17 CET 2010 (XEN) Latest ChangeSet: unavailable (XEN) Command line: vtd=1 iommu=1 vga=gfx-1024x768x16 msi=1 (XEN) Video information: (XEN) VGA is graphics mode 1024x768, 16 bpp (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009dc00 (usable) (XEN) 000000000009f800 - 00000000000a0000 (reserved) (XEN) 00000000000f0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 00000000d7be0000 (usable) (XEN) 00000000d7be0000 - 00000000d7be3000 (ACPI NVS) (XEN) 00000000d7be3000 - 00000000d7bf0000 (ACPI data) (XEN) 00000000d7bf0000 - 00000000d7c00000 (reserved) (XEN) 00000000f4000000 - 00000000f8000000 (reserved) (XEN) 00000000fec00000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000118000000 (usable) (XEN) System RAM: 3835MB (3927540kB) (XEN) ACPI: RSDP 000F7080, 0014 (r0 GBT ) (XEN) ACPI: RSDT D7BE3040, 0040 (r1 GBT GBTUACPI 42302E31 GBTU 1010101) (XEN) ACPI: FACP D7BE30C0, 0074 (r1 GBT GBTUACPI 42302E31 GBTU 1010101) (XEN) ACPI: DSDT D7BE3180, 54D2 (r1 GBT GBTUACPI 1000 MSFT 100000C) (XEN) ACPI: FACS D7BE0000, 0040 (XEN) ACPI: HPET D7BE87C0, 0038 (r1 GBT GBTUACPI 42302E31 GBTU 98) (XEN) ACPI: MCFG D7BE8840, 003C (r1 GBT GBTUACPI 42302E31 GBTU 1010101) (XEN) ACPI: EUDS D7BE8880, 04D0 (r1 GBT 0 0) (XEN) ACPI: TAMG D7BE8D50, 0A4A (r1 GBT GBT B0 5455312E BG^A^A 53450101) (XEN) ACPI: APIC D7BE86C0, 00BC (r1 GBT GBTUACPI 42302E31 GBTU 1010101) (XEN) ACPI: SSDT D7BE97A0, 1BA0 (r1 INTEL PPM RCM 80000001 INTL 20061109) (XEN) Xen heap: 9MB (9688kB) (XEN) Domain heap initialised (XEN) Processor #0 6:5 APIC version 21 (XEN) Processor #4 6:5 APIC version 21 (XEN) Processor #1 6:5 APIC version 21 (XEN) Processor #5 6:5 APIC version 21 (XEN) IOAPIC[0]: apic_id 2, 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 3197.832 MHz processor. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) VMX: EPT is available. (XEN) VMX: VPID is available. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging detected. (XEN) CPU0: Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz stepping 02 (XEN) Booting processor 1/4 eip 8c000 (XEN) CPU1: Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz stepping 02 (XEN) Booting processor 2/1 eip 8c000 (XEN) CPU2: Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz stepping 02 (XEN) Booting processor 3/5 eip 8c000 (XEN) CPU3: Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz stepping 02 (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 14.318MHz HPET (XEN) Brought up 4 CPUs (XEN) I/O virtualisation disabled (XEN) xenoprof: Initialization failed. Intel processor model 37 for P6 class family is not supported (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 32-bit, PAE, lsb (XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0x1000000 -> 0x1599000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000003c000000->000000003e000000 (929696 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c1000000->c1599000 (XEN) Init. ramdisk: c1599000->c1599000 (XEN) Phys-Mach map: c1599000->c192ce80 (XEN) Start info: c192d000->c192d47c (XEN) Page tables: c192e000->c1941000 (XEN) Boot stack: c1941000->c1942000 (XEN) TOTAL: c0000000->c1c00000 (XEN) ENTRY ADDRESS: c1000000 (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) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen) (XEN) Freed 124kB init memory. (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space (XEN) CPU 0 initialization completed (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space (XEN) CPU 1 initialization completed (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space (XEN) CPU 2 initialization completed (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space (XEN) CPU 3 initialization completed (XEN) no cpu_id for acpi_id 4 (XEN) no cpu_id for acpi_id 5 (XEN) no cpu_id for acpi_id 6 (XEN) no cpu_id for acpi_id 7 (XEN) mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining (XEN) mm.c:739:d2 Non-privileged (2) attempt to map I/O space 000000f8 (XEN) mm.c:739:d4 Non-privileged (4) attempt to map I/O space 000000f8 (XEN) Xen trace buffers: initialized (XEN) mm.c:739:d4 Non-privileged (4) attempt to map I/O space 000000f8 (XEN) mm.c:739:d4 Non-privileged (4) attempt to map I/O space 000000f8 (XEN) mm.c:739:d4 Non-privileged (4) attempt to map I/O space 000000f8 (XEN) mm.c:739:d4 Non-privileged (4) attempt to map I/O space 000000f8 ------------------------- Thanks, Christian -- Markt-Apotheke Christian Holpert e.K., Mömbris http://www.marktapotheke.org - info@marktapotheke.org http://www.blue-essentials-shop.de - info@blue-essentials-shop.de Apotheker Christian Holpert Im Markthof 5 63776 Mömbris Tel.: 06029-1379 Fax: 9986589 Amtsgericht Aschaffenburg, HR.A, Registernummer 2165 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Your xen_caps shows its not enabled or not detected. When it is working you will see a capability called hvm-directio. You will need set something in bios to enable this and vendors like gigabyte, msi, etc are known to have iffy support for vt-d if at any. Best boards in my experience for vt-d have been intel and a couple asus boards have worked as well. You should also check ark.intel.com to verify your cpu does in fact support vt-d, there needs to be support in both the motherboard and cpu. - chris On Fri, Feb 19, 2010 at 11:41 AM, Christian Holpert <christian@holpert.de>wrote:> Hello there, > > I am using a Gigabyte H55M-UD2H (Intel H55-Chipset) together with a > Core-i5-650. > According to Gigabyte Support the Mainboard does support VT-d. Well, > actually support says, that VT-d does work on Windows-7 in XP-Mode. They do > not test and support Linux though. > > Did anybody here have success using VT-d on any H55-Board? > > Perhaps it is some misconfiguration on my side. I tried a hundred things, > but with no effect. > > I am using Gentoo 32bit PAE as Dom0 with Xen 3.4.2. > sys-kernel/xen-sources-2.6.31-r10 > app-emulation/xen-3.4.2-r1 USE="pae -acm -custom-cflags -debug -flask > -xsm" > app-emulation/xen-tools-3.4.2 USE="hvm -acm -api -custom-cflags -debug > -doc -flask -pygrub -screen" > > > Grub: kernel /boot/xen.gz vtd=1 iommu=1 vga=gfx-1024x768x16 msi=1 > > ------------------------- > xm info > host : xen > release : 2.6.31-xen-r10 > version : #18 SMP Sun Feb 14 23:06:16 CET 2010 > machine : i686 > nr_cpus : 4 > nr_nodes : 1 > cores_per_socket : 2 > threads_per_core : 2 > cpu_mhz : 3197 > hw_caps : > bfebfbff:28100000:00000000:00000740:0298e3ff:00000000:00000001:00000000 > virt_caps : hvm > total_memory : 3835 > free_memory : 2 > node_to_cpu : node0:0-3 > node_to_memory : node0:2 > xen_major : 3 > xen_minor : 4 > xen_extra : .2 > xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xf5800000 > xen_changeset : unavailable > cc_compiler : gcc version 4.3.4 (Gentoo 4.3.4 p1.0, pie-10.1.5) > cc_compile_by : root > cc_compile_domain : holpert.de > cc_compile_date : Wed Feb 17 15:01:17 CET 2010 > xend_config_format : 4 > > ------------------------- > xm dmesg > > __ __ _____ _ _ ____ > \ \/ /___ _ __ |___ /| || | |___ \ > \ // _ \ ''_ \ |_ \| || |_ __) | > / \ __/ | | | ___) |__ _| / __/ > /_/\_\___|_| |_| |____(_) |_|(_)_____| > > (XEN) Xen version 3.4.2 (root@holpert.de) (gcc version 4.3.4 (Gentoo 4.3.4 > p1.0, pie-10.1.5) ) Wed Feb 17 15:01:17 CET 2010 > (XEN) Latest ChangeSet: unavailable > (XEN) Command line: vtd=1 iommu=1 vga=gfx-1024x768x16 msi=1 > (XEN) Video information: > (XEN) VGA is graphics mode 1024x768, 16 bpp > (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds > (XEN) Disc information: > (XEN) Found 1 MBR signatures > (XEN) Found 1 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 000000000009dc00 (usable) > (XEN) 000000000009f800 - 00000000000a0000 (reserved) > (XEN) 00000000000f0000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 00000000d7be0000 (usable) > (XEN) 00000000d7be0000 - 00000000d7be3000 (ACPI NVS) > (XEN) 00000000d7be3000 - 00000000d7bf0000 (ACPI data) > (XEN) 00000000d7bf0000 - 00000000d7c00000 (reserved) > (XEN) 00000000f4000000 - 00000000f8000000 (reserved) > (XEN) 00000000fec00000 - 0000000100000000 (reserved) > (XEN) 0000000100000000 - 0000000118000000 (usable) > (XEN) System RAM: 3835MB (3927540kB) > (XEN) ACPI: RSDP 000F7080, 0014 (r0 GBT ) > (XEN) ACPI: RSDT D7BE3040, 0040 (r1 GBT GBTUACPI 42302E31 GBTU 1010101) > (XEN) ACPI: FACP D7BE30C0, 0074 (r1 GBT GBTUACPI 42302E31 GBTU 1010101) > (XEN) ACPI: DSDT D7BE3180, 54D2 (r1 GBT GBTUACPI 1000 MSFT 100000C) > (XEN) ACPI: FACS D7BE0000, 0040 > (XEN) ACPI: HPET D7BE87C0, 0038 (r1 GBT GBTUACPI 42302E31 GBTU 98) > (XEN) ACPI: MCFG D7BE8840, 003C (r1 GBT GBTUACPI 42302E31 GBTU 1010101) > (XEN) ACPI: EUDS D7BE8880, 04D0 (r1 GBT 0 0) > (XEN) ACPI: TAMG D7BE8D50, 0A4A (r1 GBT GBT B0 5455312E BG^A^A > 53450101) > (XEN) ACPI: APIC D7BE86C0, 00BC (r1 GBT GBTUACPI 42302E31 GBTU 1010101) > (XEN) ACPI: SSDT D7BE97A0, 1BA0 (r1 INTEL PPM RCM 80000001 INTL 20061109) > (XEN) Xen heap: 9MB (9688kB) > (XEN) Domain heap initialised > (XEN) Processor #0 6:5 APIC version 21 > (XEN) Processor #4 6:5 APIC version 21 > (XEN) Processor #1 6:5 APIC version 21 > (XEN) Processor #5 6:5 APIC version 21 > (XEN) IOAPIC[0]: apic_id 2, 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 3197.832 MHz processor. > (XEN) VMX: Supported advanced features: > (XEN) - APIC MMIO access virtualisation > (XEN) - APIC TPR shadow > (XEN) - Extended Page Tables (EPT) > (XEN) - Virtual-Processor Identifiers (VPID) > (XEN) - Virtual NMI > (XEN) - MSR direct-access bitmap > (XEN) VMX: EPT is available. > (XEN) VMX: VPID is available. > (XEN) HVM: VMX enabled > (XEN) HVM: Hardware Assisted Paging detected. > (XEN) CPU0: Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz stepping 02 > (XEN) Booting processor 1/4 eip 8c000 > (XEN) CPU1: Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz stepping 02 > (XEN) Booting processor 2/1 eip 8c000 > (XEN) CPU2: Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz stepping 02 > (XEN) Booting processor 3/5 eip 8c000 > (XEN) CPU3: Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz stepping 02 > (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 14.318MHz HPET > (XEN) Brought up 4 CPUs > (XEN) I/O virtualisation disabled > (XEN) xenoprof: Initialization failed. Intel processor model 37 for P6 > class family is not supported > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 32-bit, PAE, lsb > (XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0x1000000 -> 0x1599000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 000000003c000000->000000003e000000 (929696 pages to > be allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: c1000000->c1599000 > (XEN) Init. ramdisk: c1599000->c1599000 > (XEN) Phys-Mach map: c1599000->c192ce80 > (XEN) Start info: c192d000->c192d47c > (XEN) Page tables: c192e000->c1941000 > (XEN) Boot stack: c1941000->c1942000 > (XEN) TOTAL: c0000000->c1c00000 > (XEN) ENTRY ADDRESS: c1000000 > (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) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input > to Xen) > (XEN) Freed 124kB init memory. > (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space > (XEN) CPU 0 initialization completed > (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space > (XEN) CPU 1 initialization completed > (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space > (XEN) CPU 2 initialization completed > (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space > (XEN) CPU 3 initialization completed > (XEN) no cpu_id for acpi_id 4 > (XEN) no cpu_id for acpi_id 5 > (XEN) no cpu_id for acpi_id 6 > (XEN) no cpu_id for acpi_id 7 > (XEN) mtrr: type mismatch for e0000000,10000000 old: write-back new: > write-combining > (XEN) mm.c:739:d2 Non-privileged (2) attempt to map I/O space 000000f8 > (XEN) mm.c:739:d4 Non-privileged (4) attempt to map I/O space 000000f8 > (XEN) Xen trace buffers: initialized > (XEN) mm.c:739:d4 Non-privileged (4) attempt to map I/O space 000000f8 > (XEN) mm.c:739:d4 Non-privileged (4) attempt to map I/O space 000000f8 > (XEN) mm.c:739:d4 Non-privileged (4) attempt to map I/O space 000000f8 > (XEN) mm.c:739:d4 Non-privileged (4) attempt to map I/O space 000000f8 > ------------------------- > > > Thanks, > Christian > > > -- > Markt-Apotheke Christian Holpert e.K., Mömbris > http://www.marktapotheke.org - info@marktapotheke.org > http://www.blue-essentials-shop.de - info@blue-essentials-shop.de > Apotheker Christian Holpert > Im Markthof 5 > 63776 Mömbris > Tel.: 06029-1379 Fax: 9986589 > > Amtsgericht Aschaffenburg, HR.A, Registernummer 2165 > > > _______________________________________________ > 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
Hi, thanks for your Reply. The CPU does support VT-d. In Bios VT is enabled: Miscellaneous Settings -> Virtualization Technology -> Enabled Actually the reason I am asking here is the missing hvm-directio in xm info. Christian At 19:51 19.02.2010, you wrote:>Your xen_caps shows its not enabled or not detected. When it is >working you will see a capability called hvm-directio. You will need >set something in bios to enable this and vendors like gigabyte, msi, >etc are known to have iffy support for vt-d if at any. Best boards >in my experience for vt-d have been intel and a couple asus boards >have worked as well. You should also check ><http://ark.intel.com>ark.intel.com to verify your cpu does in fact >support vt-d, there needs to be support in both the motherboard and cpu. > >- chris-- Markt-Apotheke Christian Holpert e.K., Mömbris http://www.marktapotheke.org - info@marktapotheke.org http://www.blue-essentials-shop.de - info@blue-essentials-shop.de Apotheker Christian Holpert Im Markthof 5 63776 Mömbris Tel.: 06029-1379 Fax: 9986589 Amtsgericht Aschaffenburg, HR.A, Registernummer 2165 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Vt-d is different than vt, there should be a bios option similar to "directed io for vt" or something like that. Sent from my iPhone On Feb 19, 2010, at 3:00 PM, Christian Holpert <christian@holpert.de> wrote:> Hi, > > thanks for your Reply. > > The CPU does support VT-d. > > In Bios VT is enabled: Miscellaneous Settings -> Virtualization > Technology -> Enabled > > Actually the reason I am asking here is the missing hvm-directio in > xm info. > > Christian > > > At 19:51 19.02.2010, you wrote: >> Your xen_caps shows its not enabled or not detected. When it is >> working you will see a capability called hvm-directio. You will >> need set something in bios to enable this and vendors like >> gigabyte, msi, etc are known to have iffy support for vt-d if at >> any. Best boards in my experience for vt-d have been intel and a >> couple asus boards have worked as well. You should also check <http://ark.intel.com >> >ark.intel.com to verify your cpu does in fact support vt-d, there >> needs to be support in both the motherboard and cpu. >> >> - chris > > -- > Markt-Apotheke Christian Holpert e.K., Mömbris > http://www.marktapotheke.org - info@marktapotheke.org > http://www.blue-essentials-shop.de - info@blue-essentials-shop.de > Apotheker Christian Holpert > Im Markthof 5 > 63776 Mömbris > Tel.: 06029-1379 Fax: 9986589 > > Amtsgericht Aschaffenburg, HR.A, Registernummer 2165 > > > _______________________________________________ > 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
On 2/19/2010 12:00 PM, Christian Holpert wrote:> Hi, > > thanks for your Reply. > > The CPU does support VT-d. > > In Bios VT is enabled: Miscellaneous Settings -> Virtualization > Technology -> Enabled > > Actually the reason I am asking here is the missing hvm-directio in xm > info. > > Christian >Christian, Any particular reason you need VT-d? Which hardware are you going to pass-through to your VM''s? VT-d is only needed if you''re doing directed IO to VM''s. 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
Hi, At 21:48 19.02.2010, you wrote:>Any particular reason you need VT-d?I''d like to pass a pci-device to a winXP-domU. AFAIK VT-d is necessary for that.>Which hardware are you going to pass-through to your VM''s?I did have a lot of IRQ-problems passing a Fritz!Card PCI for vbox3 and isdnlog to a domU running xen-sources-2.6.31-r10. Downgrading to 2.6.18-r12 I finally got it working with fcpci yesterday.>VT-d is only needed if you''re doing directed IO to VM''s.If I cant''t get the pci-card to work with the winXP-domU I''ll try the USB-Version of that card. If I understood that correctly, USB passthrough should work without VT-d. Thanks for your answer, Christian -- Markt-Apotheke Christian Holpert e.K., Mömbris http://www.marktapotheke.org - info@marktapotheke.org http://www.blue-essentials-shop.de - info@blue-essentials-shop.de Apotheker Christian Holpert Im Markthof 5 63776 Mömbris Tel.: 06029-1379 Fax: 9986589 Amtsgericht Aschaffenburg, HR.A, Registernummer 2165 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>From what you described, you do not have the proper bios option toenable vt-d. You can try checking for a bios update that may have the ability, but vendors like those are usually not a good bet. - chris On Sun, Feb 21, 2010 at 4:26 AM, Christian Holpert <christian@holpert.de> wrote:> Hi, > > At 21:48 19.02.2010, you wrote: >> >> Any particular reason you need VT-d? > > I''d like to pass a pci-device to a winXP-domU. AFAIK VT-d is necessary for > that. > >> Which hardware are you going to pass-through to your VM''s? > > I did have a lot of IRQ-problems passing a Fritz!Card PCI for vbox3 and > isdnlog to a domU running xen-sources-2.6.31-r10. Downgrading to 2.6.18-r12 > I finally got it working with fcpci yesterday. > >> VT-d is only needed if you''re doing directed IO to VM''s. > > If I cant''t get the pci-card to work with the winXP-domU I''ll try the > USB-Version of that card. If I understood that correctly, USB passthrough > should work without VT-d. > > Thanks for your answer, > Christian > > -- > Markt-Apotheke Christian Holpert e.K., Mömbris > http://www.marktapotheke.org - info@marktapotheke.org > http://www.blue-essentials-shop.de - info@blue-essentials-shop.de > Apotheker Christian Holpert > Im Markthof 5 > 63776 Mömbris > Tel.: 06029-1379 Fax: 9986589 > > Amtsgericht Aschaffenburg, HR.A, Registernummer 2165 > > > _______________________________________________ > 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
Just happened to come across a pic I took of the BIOS option for VT-d. The option would look similar to this if your motherboard supports VT-d. http://i42.tinypic.com/1zm2sz8.jpg - chris On Sun, Feb 21, 2010 at 4:31 AM, chris <tknchris@gmail.com> wrote:> From what you described, you do not have the proper bios option to > enable vt-d. You can try checking for a bios update that may have the > ability, but vendors like those are usually not a good bet. > > - chris > > On Sun, Feb 21, 2010 at 4:26 AM, Christian Holpert <christian@holpert.de> wrote: >> Hi, >> >> At 21:48 19.02.2010, you wrote: >>> >>> Any particular reason you need VT-d? >> >> I''d like to pass a pci-device to a winXP-domU. AFAIK VT-d is necessary for >> that. >> >>> Which hardware are you going to pass-through to your VM''s? >> >> I did have a lot of IRQ-problems passing a Fritz!Card PCI for vbox3 and >> isdnlog to a domU running xen-sources-2.6.31-r10. Downgrading to 2.6.18-r12 >> I finally got it working with fcpci yesterday. >> >>> VT-d is only needed if you''re doing directed IO to VM''s. >> >> If I cant''t get the pci-card to work with the winXP-domU I''ll try the >> USB-Version of that card. If I understood that correctly, USB passthrough >> should work without VT-d. >> >> Thanks for your answer, >> Christian >> >> -- >> Markt-Apotheke Christian Holpert e.K., Mömbris >> http://www.marktapotheke.org - info@marktapotheke.org >> http://www.blue-essentials-shop.de - info@blue-essentials-shop.de >> Apotheker Christian Holpert >> Im Markthof 5 >> 63776 Mömbris >> Tel.: 06029-1379 Fax: 9986589 >> >> Amtsgericht Aschaffenburg, HR.A, Registernummer 2165 >> >> >> _______________________________________________ >> 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