similar to: VT-d with P6T Deluxe

tmoore wrote: > > > I`ve raised a support case with ASUS to try to get them to fix the BIOS on > P6T Deluxe ... I`ll keep this thread updated. > > The IOMMU is seriously broken on this board, I have tried many workarounds > and it always results in failure. > > > Hello, did you get a reply? Somebody else has something new about the Asus P6T and this problem? How

reaver wrote: > > On Tue, Feb 24, 2009 at 12:36 AM, Dustin Henning > <Dustin.Henning@prd-inc.com> wrote: >> Christian, >>        I am not sure what lead me to believe you had an AMD system.  To >> summarize what I was trying to say, ASUS is claiming that this issue is >> unsupported because you use Linux, but at the end of the day, the issue >> has

Trying to set up PCI pass through with xen 3.2.1 on Debian Lenny, with xen Kernel 2.6.26... having no luck. I have the following configured... i) Virtualization and vt-d are both enabled in the bios, I have power cycled after making these changes. ii) I have these option in grub menu; iommu=1 pciback.permissive pciback.hide=(07:01.0)(01:00.0) vtd=1 iii) I have this in my cfg file

I''m using (XEN) Xen version 4.1.2 (Debian 4.1.2-2) (waldi at debian dot org) (gcc version 4.6.2 (Debian 4.6.2-6) ) Sat Dec 10 19:58:21 UTC 2011 With VT-d enabled in BIOS the ACPI Direct Memory Access remapping (DMAR) in the P6T Deluxe V2 (BIOS 1202, 2011/10/10) reports RMRR (Reserved Memory Region Reporting Structure) is bf7dc000 - bf7dbfff e820 table:

Hi, I''ve successfully used VT-d on an ASUS P6T mainboard which is known to have really buggy RMRR tables. I tested passtrough with: - the onboard (fake-)raid-controller (no problems) - a pci card (no problems) - VGA cards (worked only partly - I''ll investigate that) I wrote a little patch to the code parsing the RMRR tables and enabled the following command line options:

I have a chipset which supports VT-d (Intel X58) and, according to my motherboard manufacturers, VT-d is enabled in the BIOS and listed as "Intel VT." The problem is that xm dmesg shows "I/O virtualisation disabled" and I get this error message when I try to create a domU with a pci device assigned: ''Error: failed to assign device: maybe the platform doesn''t

I try pci pci passthrough with xen 3.3.1 and CentOS 5.2(64bit) on a SUPERMICRO C7X58 board I see the following the error in my boot log. (XEN) [VT-D]dmar.c:372: RMRR is incorrect. This problem is caused by this condition in dmr.c:372. if ( rmrr->base_address >= rmrr->end_address ) { dprintk(XENLOG_ERR VTDPREFIX, "RMRR is incorrect.\n"); return -EFAULT; } As an

I try pci pci passthrough with xen 3.3.1 and CentOS 5.2(64bit) on a SUPERMICRO C7X58 board I see the following the error in my boot log. (XEN) [VT-D]dmar.c:372: RMRR is incorrect. This problem is caused by this condition in dmr.c:372. if ( rmrr->base_address >= rmrr->end_address ) { dprintk(XENLOG_ERR VTDPREFIX, "RMRR is incorrect.\n"); return -EFAULT; } As an

Source: xen Version: 4.6.0-1 Severity: important Dear Maintainer, I attempted to create a HVM domU - using a config that previously worked on xen 4.4 (on Jessie). When I execute "xl create <vm config>", I get: Parsing config from router.internal.tomjepp.uk xc: error: Could not open kernel image '/usr/lib/xen/boot/hvmloader' (2 = No such file or directory): Internal

I'm looking at setting up a new machine to run CentOS 5 and a few VMWare machines to test Windows XP, Vista, and 7. I'm working with a custom PC shop and they've recommended I use either the ASUS PT6 or Intel DX58SO. Any feedback good or bad on either of these? Thanks! --Chris

Hello to you guys, yeah Im also one of the people who seem to have a corrupted BIOS. I read already stuff about the issue''s with certain vendors - and I guess in one particular area it was made clear that even you cant do a lot about it you still collect details. CPU Intel Core i7 X980 Mainboard Asus P6T WS Professional (X58/LGA1333)(bios 1207) rev. 1.01G I also have two other

Hi All, Thought I would let those that are interested know that I had success in running 24G on an Asus P6T with 24G kit of Kingston DDR3. While I was putting this together I saw lots of forum posts asking if anyone had tried it. Well we did here at our work and all looks great including running "memtest86" overnight. I have a fluid dynamics simulation running on it with 90% memory

Control: reassign -1 src:xen On Sb, 23 aug 14, 18:18:51, Thomas Jepp wrote: > After doing a xen upgrade this morning to 4.4 I hit this same issue. > > I?ve compiled a set of test packages from this commit: http://anonscm.debian.org/cgit/pkg-xen/xen.git/commit/?h=feature/seabios&id=44daa679dc80f2df734e5471476df159bc0ad38d > > My HVM domUs now start as expected so this seems to

Hi! I''m developing an localization plugin (just for my own purposes) and I wanted to extend the to_s method for the Time class. What I want to do: when someone does date.to_s(:short) that a localized version of the :short date is displayed. But I don''t know how to accomplish this. I know have this: class Time def to_s(option) print option.to_yaml

Has anyone been able to get domU NFS boots working with any version of Xen 4.x? If so, can you please post your config? Both the dom0 Xen version & kernel, as well as the domU config file. I''ve spent a lot of time running through all the docs, HOWTO''s and published configs and assorted patches for Ubuntu 9x-10x and Xen 4x trying NFS booting with each. I''m not going

Hello Debian Xen team, I have two questions regarding Xen vulnerability CVE-2015-3456 / XSA-133 / "Venom" in Debian [1]: * I noticed that [1] says 4.4.1-9 not to be vulnerable ("fixed") but according to the Debian Changelog [2] 4.4.1-9 appeared in Debian before XSA-133 was published and xen_4.4.1-9.debian.tar.xz [3] does not seem to contain any XSA-133 patch.

On 15/05/2015 09:41, Sebastian Pipping wrote: > * I noticed that [1] says 4.4.1-9 not to be vulnerable ("fixed") > but according to the Debian Changelog [2] 4.4.1-9 appeared > in Debian before XSA-133 was published and > xen_4.4.1-9.debian.tar.xz [3] does not seem to contain > any XSA-133 patch. Could you elaborate why 4.4.1-9 is not affected? This would

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 13 Feb 2004, Dave St John wrote: > I think that would be a good feature to add in icecast2, dont get me wrong, > im just saying with QoS > you have far much more flexibility in handling bandwidth. > tcp/ip packets can be marked with iptables and then ran threw tc which you > could then prioritize your packets You mean by using

On 19.11.2015 11:00, Ian Campbell wrote: > On Wed, 2015-11-18 at 23:07 +0000, Thomas Jepp wrote: >> >> [...] >> xc: error: Could not open kernel image '/usr/lib/xen/boot/hvmloader' (2 = No such file or directory): Internal error > > This is the wrong path, in the Debian packages it should be /usr/lib/xen- > 4.6/boot/hvmloader (and this should be arranged by

Dear Xen-Team, after an debian-update (jessie) the hvm do not start: I'm not sure it's a bug or a support-question? If it's a bug I don't know which packet is affected. <http://www.dict.cc/englisch-deutsch/affected.html> I get now response on mailing lists so it look looks like bug fore me. The hvm works fine until I did 'apt-get upgrade' ( I think on Aug 9).