search for: rdm_policy

...vice is and assign them both to the guest >2. Tell Xen that you don't mind the sharing. > >You should only do #2 if you're not using Xen for isolation -- i.e., >if you trust the software in that VM not to attack dom0. > >I *think* you should be able to do #2 by adding 'rdm_policy=relaxed' >to your pci stanza; i.e., it should look like this: > >pci=['00:1a.0,rdm_policy=relaxed'] Dear George That worked, do I still need to add this to the cfg file? usb=1 usbdevice=['host:0529:0514'] or how do I assign the device without the 'rdm_policy=rela...

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

...restart' on_crash = 'restart' boot = 'c' acpi = '1' apic = '1' viridian = '1' xen_platform_pci = '1' serial = 'pty' vga = 'none' sdl = '0' vnc = '0' gfx_passthru = '1' pci = [ '00:1b.0', '00:14.0,rdm_policy=relaxed', '00:02.0' ] > > And, other configs you need to have in place to exclude the devices from > being seen as normal devices directly in dom0? (I haven't used > passthrough myself yet, but I read that this is needed.) I run this script in Dom0 before starting the...

....6 with CentOS kernel 3.18.34-20.el7.x86_64. I have to manually make the port available before creating the DomU by issuing the command: xl pci-assignable-add 00:1a.0 otherwise nothing shows in: xl pci-assignable-list I have added this to my .cfg file as per the May Emails: pci=['00:1a.0,rdm_policy=relaxed'] and in the DomU, which starts fine, I get the following information: lspci 00:00.0 USB controller: Intel Corporation Wellsburg USB Enhanced Host Controller #2 (rev 05) lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub However when I plug in a device to this...

...re out what the other device is and assign them both to the guest 2. Tell Xen that you don't mind the sharing. You should only do #2 if you're not using Xen for isolation -- i.e., if you trust the software in that VM not to attack dom0. I *think* you should be able to do #2 by adding 'rdm_policy=relaxed' to your pci stanza; i.e., it should look like this: pci=['00:1a.0,rdm_policy=relaxed'] Let me know if that works for you. -George

...RMRR at 7b800000 > for Dom8. > (XEN) [VT-D] It's risky to assign 0000:00:1a.0 with shared RMRR at 7b800000 > for Dom9. > (XEN) [VT-D] It's risky to assign 0000:00:1a.0 with shared RMRR at 7b800000 > for Dom10. This looks like you tried once to start your guest without "rdm_policy=relaxed" (which failed), and then tried it four times with "rdm_policy=relaxed" (which succeeded). Other than warning that there's a shared RMRR (which could potentially be a security risk), everything here looks normal. There's a possibility that the shared RMRR is what...

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 mention the used Xen version (Debian package version) for buster and bullseye

....6 with CentOS kernel 3.18.34-20.el7.x86_64. I have to manually make the port available before creating the DomU by issuing the command: xl pci-assignable-add 00:1a.0 otherwise nothing shows in: xl pci-assignable-list I have added this to my .cfg file as per the May Emails: pci=['00:1a.0,rdm_policy=relaxed'] and in the DomU, which starts fine, I get the following information: lspci 00:00.0 USB controller: Intel Corporation Wellsburg USB Enhanced Host Controller #2 (rev 05) lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub However when I plug in a device to this...

...c=00:16:3E:00:00:35, bridge=xenbr5', 'mac=00:16:3E:00:00:36, bridge=xenbr6'] # Disk Devices disk = ['phy:/dev/xen_vg/metsat_disk,xvda,w', 'phy:/dev/xen_vg/metsat_swap,xvdb,w', 'phy:/dev/xen_vg/metsat_receive,xvdc,w'] # for Eumetcast Dongle pci=['00:1a.0,rdm_policy=relaxed,permissive=1'] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' # Run section ============================================================== bootloader = "/usr/lib/xen/bin/pygrub" ===============================================...

...memory = 2048 vcpus = 2 vif = ['mac=00:16:3E:00:00:35, bridge=xenbr5', 'mac=00:16:3E:00:00:36, bridge=xenbr6'] disk = ['phy:/dev/xen_vg/metsat_disk,xvda,w', 'phy:/dev/xen_vg/metsat_swap,xvdb,w', 'phy:/dev/xen_vg/metsat_receive,xvdc,w'] pci=['00:1a.0,rdm_policy=relaxed,permissive=1,seize=1'] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' # Run section ============================================================== bootloader = "/usr/lib/xen/bin/pygrub" =========================================...