similar to: PCI Passthrough not working

On Wed, Jun 22, 2016 at 11:49 AM, Francis Greaves <francis at choughs.net> wrote: > More information... > I have pcifront showing as a module in the DomU and the usb shows in dmesg > as: > [ 3.167543] usbcore: registered new interface driver usbfs > [ 3.167563] usbcore: registered new interface driver hub > [ 3.167585] usbcore: registered new device driver usb >

>On Mon, May 16, 2016 at 12:00 PM, Francis Greaves <francis at choughs.net> wrote: >> Dear George please find attached the three files as requested. >> I have used >> >> iommu=soft >> >> in the grub command line for the kernel in the domU as explained before. >> many thanks >The options are: >1. Figure out what the other device is and

Dear George please find attached the three files as requested. I have used iommu=soft in the grub command line for the kernel in the domU as explained before. many thanks Francis From: "George Dunlap" <dunlapg at umich.edu> To: "francis" <francis at choughs.net>, "centos-virt" <centos-virt at centos.org> Sent: Monday, 16 May, 2016 10:29:09

Further to my last post, I have removed the xen-pciback module from the Dom0 kernel, and reloaded it as modprobe xen-pciback passthrough=1 I now have the PCI device on the DomU matching the Dom0 Device usb usb1: SerialNumber: 0000:00:1a.0 instead of 0000:00:00.0 However I now have this error ehci_hcd 0000:00:1a.0: Unlink after no-IRQ? Controller is probably using the wrong IRQ. does

More information... I have pcifront showing as a module in the DomU and the usb shows in dmesg as: [ 3.167543] usbcore: registered new interface driver usbfs [ 3.167563] usbcore: registered new interface driver hub [ 3.167585] usbcore: registered new device driver usb [ 3.196056] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 3.196060] usb usb1: New USB device strings:

Hi All, We tested the xm block-attach/detach command. It repeats block-attach/detach command for DomU and pv-on-hvm on HVM Domain. (block-attach -> block-detach -> block-attach -> block-detach -> ...) The block-attach command failed when repeating 256 times. It is because the channel had not been freed in blkfront. Therefore, it remain using the event channel. This patch is

On 10/23/2021 11:11 AM, Hans van Kranenburg wrote: > Hi! > > On 10/19/21 5:44 AM, Chuck Zmudzinski wrote: >> On 5/10/2021 1:33 PM, Chuck Zmudzinski wrote: >>> [...] with buster and bullseye running as the Dom0, I can only get the VGA/Passthrough feature to work with Windows Xen HVMs. I would expect both Windows and Linux HVMs to work comparably well. > You don'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

Hello, I''m also seeing this exact same problem. I''ve posted on xen-users, but did not get an answer. Venkat seems to be experiencing the same problem as me. I have the latest BIOS for my motherboard DQ35JO. (BIOS ver 933) I''m running a Q6600 as well. It hangs at "Brought up 4 CPUs." I''ve tried all sorts of combinations of Xen versions and kernels to

Dear All I am using Centos 7 with Xen 4.6 on a Dell Poweredge T430 When the machine boots, after the 'Scrubbing Free RAM' message, I get a screen filled with little white squares until the login prompt, so I cannot see what is happening as the machine boots. Also there is nothing on the screen when I reboot. My /etc/default/grub is GRUB_DISTRIBUTOR="$(sed 's, release

This patch maps RMRR in intel_iommu_add_device() if the device has RMRR; move domain_context_mapping() to be in front of list_move() in reassign_device_ownership(). Currently, hypervisor sets up devices and RMRR for dom0, and dom0 also adds devices for itself via hypercall. This is obviously duplicate. In order to allow old dom0 kernels to work with iommu-capable platforms, maybe it cannot be

hi, I am trying the Xen unstable on X48 chipset these days but it failed due to an corrupted RMRR table in the ACPI. The following is the acpi dump of DMAR. DMAR @ 0x7fef1000 0000: 44 4d 41 52 20 01 00 00 01 d1 49 4e 54 45 4c 20 DMAR .....INTEL 0010: 44 58 34 38 42 54 32 20 12 06 00 00 4d 53 46 54 DX48BT2 ....MSFT 0020: 13 00 00 01 23 00 00 00 00 00 00 00 00 00 00 00 ....#...........

I am using Xen 4.6.0-8.el7 on CentOS 7 with 3 Linux DomUs. I did have Xen 4.? on CentOS 6.5 on my previous system. I installed using yum install centos-release-xen. On shutting down the Hypervisor it used to wait for the DomUs to shut down gracefully (one can take a minute or more), then on starting up again it would restart the DomUs, all nice and controlled. For some reason the DomUs (CentOS

Hello, I am desperately trying to get pci-passthrough to working. I want to pass a tg3 nic to domU. when booting domU I get a lot of messages: pcifront pci-0: pciback not responding!!! in domU, "ifconfig eth... adress up" hangs for 2 minutes, finally ifconfig -a shows a correct setting with no data transmitted rx/tx The IP Adress is being assigned, but there is no data transmission

Rather than requiring the scopes to be the first members of their respective structures (so that casts can be used to switch between the different views), properly use types and container_of(). Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/drivers/passthrough/vtd/dmar.c +++ b/xen/drivers/passthrough/vtd/dmar.c @@ -304,13 +304,15 @@ static int __init scope_device_count(con

This adds a boolean boot parameter to xen to allow reserved memory regions to be added to the iommu mappings for dom0. The parameter is "iommu_include_reserved" and is off by default. A warning is also traced when incorrect RMRR to system memory map values are detected. This is being added to address some incorrect BIOS''s that do not report correctly the requied reserved memory

https://bugs.freedesktop.org/show_bug.cgi?id=99913 Bug ID: 99913 Summary: [G96] Reclocking fails on voltage Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

Yes I usually work headless, but I have been setting it up from new, so need to see what is going on. Regards Francis From: "Scot P. Floess" <sfloess at nc.rr.com> To: "Francis Greaves" <francis at choughs.net> Cc: "centos-virt" <centos-virt at centos.org> Sent: Monday, 22 February, 2016 17:02:12 Subject: Re: [CentOS-virt] Garbled screen

Hi I have a couple of questions: 1. How do I exist from a domU console back to dom0 console (after issuing xm console [domU])? 2. How do I setup a dom0/domU in order to get a tty login? TIA Paolo _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users