similar to: VT-d Problem with Xen

Hi all, I''m having difficulty getting VT-d to work correctly with a new Supermicro MBD-X10SAE-O in QubesOS <http://qubes-os.org/trac>, and I''m hoping someone here might be able to help me (or at least shed some light on my situation). A Qubes developer suggested I contact this list. Here''s my HCL post from the qubes-users group

Hi Fr?d?ric, It appears Ben made his own version of this patch (probably based on the one you added to the kernel bz), and it's already upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.6-rc2&id=0e6176c6d286316e9431b4f695940cfac4ffe6c2 Cheers, -ilia On Thu, Feb 20, 2020 at 12:19 PM Fr?d?ric Pierret <frederic.pierret at qubes-os.org>

Pointer to structure array is assumed not NULL by default. It has the consequence to raise a kernel panic when it's not the case. Basically, running at least a RTX2080TI on Xen makes a bad mmio error which causes having 'mthd' pointer to be NULL in 'channv50.c'. From the code, it's assumed to be not NULL by accessing directly 'mthd->data[0]' which is the reason

The iommu is enabled by default when xen is booting and later disabled in iommu_setup() when no iommu is present. But under some circumstances iommu-code can be called before iommu_setup() is processed. If there is no iommu available xen crashes. This can happen for example when panic(...) is called that got introduced with patch "x86-64: detect processors subject to AMD erratum #121 and

Hi, I installed wine on my Debian system, but if i try to start wine or wine config my screen get screwed up. After I try it, everthing on screen is scattert to little qubes or/and lines, I can't select or indentify anything on it. Thanks

Hello, I''m facing a rather strange problem with the netback interface. My setup involves a netvm, which has some physical network interfaces assigned, and a client VM where a net front is running (exposed as eth0) and which is connected to that netvm (via vif42.0 interface, as seen in the netvm on the dumps below). Now, the netvm has two physical network interfaces assigned: 1) A

Hello, I am looking into building a workstation using Xen to host several operating systems. Looking at the pci passthrough requirements of Xen4.1 on the VTdHowTo<http://wiki.xensource.com/xenwiki/VTdHowTo>page, I am a little puzzled with the fact that only Intel Core2Duo (with VT-x), Core2Quad, i7 and Core i5 (vPro Brand) CPU''s are supported while motherboards with the i55x0

The iommu is enabled by default when xen is booting and later disabled in iommu_setup() when no iommu is present. But under some circumstances iommu code can be called before iommu_setup() is processed. If there is no iommu available xen crashes. This can happen for example when panic(...) is called as introduced with the patch "x86-64: detect processors subject to AMD erratum #121 and

https://bugs.freedesktop.org/show_bug.cgi?id=95193 Bug ID: 95193 Summary: Nouveau not working with Quadro K2200 (NV117) and Debian Wheezy Product: xorg Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component:

I had an off-list discussion with George Dunlap yesterday, who suggested that it might be helpful to have an ability to test the S3 functionality in a bit more of an end-to-end fashion, and possibly introduce an ability to do all of the S3 related things without actually putting the machine to sleep. Attached is a very simple patch to xen that introduces a command line argument

Hi, I''ve still have problems with ACPI(?) on Xen. After some system startup or resume CPU temperature goes high although all domUs (and dom0) are idle. On "good" system startup it is about 50-55C, on "bad" - above 67C (most time above 70C). I''ve noticed difference in C-states repored by Xen (attached files). On "bad" startups in addition suspend

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

Hi, I have just upgraded my computer to Intel Core i5-4430 Quad Core @ 3.0 GHz (supports VT-d), ASRock B85M Pro4 micro-ATX LGA1150 motherboard (supports VT-d), 8 GB Kingston DDR3-1600 memory and Cooler Master Elite 311 ATX casing (all for SGD$501). I made my computer upgrade on Independence Day 4th July 2013. I have also flashed the UEFI BIOS of ASRock B85M Pro4 motherboard to version 1.50.

On Mon, Feb 01, 2016 at 09:50:53AM -0500, Konrad Rzeszutek Wilk wrote: > > The second bullet looks at first pretty interesting from this PoV, > > see?http://xenbits.xen.org/xsa/advisory-157.html?for info on the XSA and > > the various patches. Konrad is on the CC already so hopefully he has some > > ideas. > > Thanks. I will try to reproduce this with the upstream

On Wed, Jan 29, 2020 at 05:22:13PM +0100, Fr?d?ric Pierret wrote: > Dear Ben Skeggs, > > Please find attached a patch solving a blocking issue I encountered: > https://bugzilla.kernel.org/show_bug.cgi?id=206299 > > Basically, running at least a RTX2080TI on Xen makes a bad mmio error > which causes having 'mthd' pointer to be NULL in 'channv50.c'. From the

Hello, I thinking about using PCI passthrough to dedicated a domU as firewall. I understand PCI passthrough concept. When done, my domU will see network card and the dom0 won''t any more. So I''ll be able to filter all trafic from outside, since it will go through network domU. Then, how will I be able to connect other domU (and maybe dom0) to the network domU ? In a normal way,

Dear Ben Skeggs, Please find attached a patch solving a blocking issue I encountered: https://bugzilla.kernel.org/show_bug.cgi?id=206299 Basically, running at least a RTX2080TI on Xen makes a bad mmio error which causes having 'mthd' pointer to be NULL in 'channv50.c'. From the code, it's assumed to be not NULL by accessing directly 'mthd->data[0]' which is the

Moat of the advanced persistent threats (APT) are initiated via e-mail. Opening an attachment or clicking on a web link starts the process. Why isn't Firefox and Evolution confined with SELinux policy in a way that APT can't damage the rest of the system? Why are we not sandboxing these two apps with SELinux? I've discovered some guidance for sandboxing Firefox using the

When a domain''s VT-d table is changed, only the iommus under which the domain has assigned devices need to be flushed. Signed-off-by: Yang, Xiaowei <xiaowei.yang@intel.com> Thanks, Xiaowei _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

This a step forward to fix the security hole introduced by dom0''s 1:1 mapping VT-d table: remove the critical code and data from it. The more flexible solution is to update dom0''s VT-d table on demand as what will be done for other PV domains. However, there could bring a performance issue even with software optimization. Iotlb flush of some hardware is time-consuming.