search for: dom8

...345543 DOM2 S-1-5-21-776971034-1374619893-1389755056 DOM5 S-1-5-21-1979410263-576795079-1250845650 DOM6 S-1-5-21-2091962305-833907787-4047963448 DOM3 S-1-5-21-144846545-115680220-1939559906 DOM4 S-1-5-21-151263845-1299922530-322568963 DOM8 S-1-5-21-607462080-1190682306-324685044 DOM7 S-1-5-21-2068281220-2021992396-681445708 DOM10 S-1-5-21-2856294414-1944682179-2323182264 DOM11 S-1-5-21-606747145-1801674531-839522115 DOM9 S-1-5-21-770417570-4267868530-655758658 DO...

...us mode xenbr0: port 3(vif7.0) entering disabled state device vif8.0 entered promiscuous mode (XEN) DOM0: (file=mm.c, line=1688) Bad type (saw 28000001 != exp e0000000) for mfn 96efe (pfn 573) (XEN) DOM0: (file=mm.c, line=606) Error getting mfn 96efe (pfn 573) from L1 entry 0000000096efe027 for dom8 (XEN) DOM0: (file=mm.c, line=1266) Bad get_page_from_l1e(): pl1e = fefa6a30, nl1e = 96efe027, ol1e = 0, gl1mfn = d8538 (XEN) DOM0: (file=mm.c, line=2283) Could not modify L1 entry: va == fefa6a30, l1e == 96efe027, mfn == d8538 (I''ve added the two MEM_LOG() calls at line 1266 and 2283....

Further to my messages back in May I have at last got round to trying to get my DomU to recognise USB devices. I am using Xen 4.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

...5e c067f6c4 c067f6e3 c067f800 (XEN) c067f8ad c067f90f c067f948 c067f94e c067fd3d c067fd4e c067fd58 c067ff7e (XEN) mm.c:1887:d8 Bad type (saw 0000000028000001 != exp 00000000e0000000) for mfn 4dff84 (pfn f0) (XEN) mm.c:665:d8 Error getting mfn 4dff84 (pfn f0) from L1 entry 00000004dff84063 for dom8 (XEN) mm.c:1887:d8 Bad type (saw 0000000028000001 != exp 00000000e0000000) for mfn 4dff84 (pfn f0) (XEN) mm.c:665:d8 Error getting mfn 4dff84 (pfn f0) from L1 entry 00000004dff84063 for dom8 (XEN) mm.c:3498:d8 ptwr_emulate: could not get_page_from_l1e() (XEN) Unhandled page fault in domain 8 on V...

...000:00:1a.0 with shared RMRR at 7b800000 for Dom6. (XEN) XEN_DOMCTL_assign_device: assign 0000:00:1a.0 to dom6 failed (-1) (XEN) [VT-D] It's risky to assign 0000:00:1a.0 with shared RMRR at 7b800000 for Dom7. (XEN) [VT-D] It's risky to assign 0000:00:1a.0 with shared 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. In the as an aside... I just get blocks on the screen after the scrubbing message, and no text. I see there is a...

...R at 7b800000 > for Dom6. > (XEN) XEN_DOMCTL_assign_device: assign 0000:00:1a.0 to dom6 failed (-1) > (XEN) [VT-D] It's risky to assign 0000:00:1a.0 with shared RMRR at 7b800000 > for Dom7. > (XEN) [VT-D] It's risky to assign 0000:00:1a.0 with shared 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...