similar to: Which QEMU device-model to use for Windows HVM guests???

This bug, at its core, is that currently there is no supported solution for VGA passthrough on Xen for stable version Jessie from Debian. After browsing Xen's repositories, I found out that Xen did not claim to support VGA passthrough with the upstream qemu-xen device model until Sep 25, 2015, the date the xl.cfg man page was updated to indicate support for VGA passthrough with upstream

Hi, I''m doing VGA passthrough for an ATI (HD 6770) graphics card to a DomU Windows. The passthrough itself is working. However, everytime when I reboot the DomU Windows, the whole machine freezes. I see no error messages from Dom0 kernel or the xen qemu log (or perhaps I haven''t got the most verbose debugging turned on?). Though from what I can tell, the the freeze happens

Hi- I am trying to pass an LSI SAS2008-based HBA (IBM M1015) through to an HVM Solaris VM, using Xen 4.2 unstable and the qemu-traditional device model. On boot I see the following error: MPT BIOS Fault 09h encountered at adapter PCI(00h,05h,00h) A list search yielded (http://comments.gmane.org/gmane.comp.emulators.xen.devel/128172), however there was no solution for an HVM VM. I''ve

On Wed, 2014-01-01 at 09:52 -0600, Marc F. Clemente wrote: > I have seen posts mentioning "traditional" and "upstream" qemu-dm. > But it is not clear to me what the difference is between "traditional" > and "upstream", or how to select either one. This is explained in the xl.cfg(5) man page. http://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-3515 / XSA-17 version 2 Qemu VT100 emulation vulnerability UPDATES IN VERSION 2 ==================== Public release. ISSUE DESCRIPTION ================= The device model used by fully virtualised (HVM) domains, qemu, does not properly handle escape VT100

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-3515 / XSA-17 version 2 Qemu VT100 emulation vulnerability UPDATES IN VERSION 2 ==================== Public release. ISSUE DESCRIPTION ================= The device model used by fully virtualised (HVM) domains, qemu, does not properly handle escape VT100

On 01/02/2014 11:56 AM, Ian Campbell wrote: > You can select a non-default model use by using the > "device_model_version" directive in your config. From what I gather, for now, you MUST select a non-default model, using something like: device_model_version="qemu-xen" device_model_override="/usr/bin/qemu-system-x86_64" > In the context of Debian the

Hi, everyone! I am working on xen-4.2.0 with spice remote connect. My host is Fedora 14 and guest is win7. I have installed spice package and now I can connect to guest by spice client. For better graphics experience, I want to try the VGA passthrough. With spice tool, I have to create a VM by xl command, and now I am wondering if it supports VGA passghrouth? If so, how should I test it ?

Package: xen-utils-4.3 Version: 4.3.0-3+b1 Severity: normal When I try to create an HVW withDevian/xen, I run into trouble. It used to work, maybe with xen 4.1, but it has never worked since. Bug 688311 was filed, with the same exact problem. That bug was somehow closed and no resolution or explanation was provided. I have seen posts mentioning "traditional" and "upstream"

Hi, I have just applied IGD VGA Passthrough patches to Xen 4.4-unstable changeset 27238. Please refer to the 2 attached patches. 1. [Xen-devel] [PATCH 2/3] V4 qemu-xen-trad: Correctly expose PCH ISA bridge for IGD passthrough Link: http://lists.xenproject.org/archives/html/xen-devel/2013-06/msg01720.html 2. [Xen-devel] [PATCH 3/3] qemu-xen-trad: IGD passthrough: Expose vendor specific pci

Hi, I have just applied IGD VGA Passthrough patches to Xen 4.4-unstable changeset 27238. Please refer to the 2 attached patches. 1. [Xen-devel] [PATCH 2/3] V4 qemu-xen-trad: Correctly expose PCH ISA bridge for IGD passthrough Link: http://lists.xenproject.org/archives/html/xen-devel/2013-06/msg01720.html 2. [Xen-devel] [PATCH 3/3] qemu-xen-trad: IGD passthrough: Expose vendor specific pci

So, I made a mistake a bought four systems with the Intel Core i3 processors, without doing my homework to make sure that these systems actually supported VTd. Turns out there''s plenty of information out there indicating that the Core i3 processors do *not* support VTd. I was counting on VTd for two applications: Graphics Passthrough and passing through a PCIe 4-port serial card. Of

Hello everyone! With the completion of our first few release candidates for 4.2, it''s time to look forward and start planning for the 4.3 release. I''ve volunteered to step up and help coordinate the release for this cycle. The 4.2 release cycle this time has been nearly a year and a half. One of the problems with having such a long release is that people who get in features

Hi all I''m trying to enable VGA passthrough in linux domU without success. I want to pass through AMD Radeon HD 4850 - 03:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD 4850] as a _primary_ VGA for the VM. Nothing is showing up on the monitor that I have connected to graphics card''s HDMI port. I have IOMMU enabled. I searched mailing lists

Dom0 is Wheezy 64 bit with kernel 3.2.0-1-amd64 version 3.2.4-1, xen from xen-unstable.hg changeset 24858:a88ba599add1 plus these patch for not fail build: http://xen.1045712.n5.nabble.com/PATCH-0-of-2-rename-libxl-yajl-gen-alloc-td5469362.html And also this change for lib patch modified with multiarch support: vi config/StdGNU.mk LIBLEAFDIR_x86_64 ?= lib DomUs PV working, domUs with

Just out of annoyance more than curiosity, but ever since I started using Xen 4.2-unstable rev-25467, every time I try to run "sudo xl create <domu_config_file>", or "sudo xl reboot", or "sudo xl destroy", it always gives me this message: "*xend is running, which prevents xl from working correctly. If you still want to force the execution of xl please

Hello, I recently swapped some components, and rebuilt my system. Changes to the configuration: - Wheezy Beta 1 > Wheezy Beta 2 - Kernel 3.4.9 > Kernel 3.4.11 I have tested the new Xen 4.2 stable, and Xen unstable revision 25777, both are giving me the same error so I do not believe it is related to a change in Xen. The first attempt to pass a PCI device after booting the system

Package: xen-utils-4.1 Version: 4.1.3-2 Severity: important Dear Maintainer, Creating a new HVM domU fails with the following error: map shared IO page returned error 22 I've narrowed it down to qemu-dm which fails to start: # /usr/lib/xen-4.1/bin/qemu-dm [...] qemu_map_cache_init nr_buckets = 10000 size 4194304 errno0 = 2 domid = -1 shared page at pfn 0 errno1 = 3 errno2 = 22 map shared IO

Processing commands for xen@bugs.xenproject.org: > create ^ Created new bug #20 rooted at `<1571692646.20131009000945@eikelenboom.it>'' Title: `Re: [HVM} xen_platform_pci=0 doesn''t prevent platform device creation and disk and nic take over by PV drivers.'' > title it xen_platform_pci=0 doesn''t work with qemu-xen Set title for #20 to