search for: dom10

...79-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 DOM12 S-1-5-21-448539723-725345543-1417001333 DOM13 S-1-5-21-3732380198-1900445356-114840463...

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

...hared 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 message: (XEN) Xen is relinquishing VGA console. How can I prevent this? Is there something wrong with my /etc/default/grub ... GRUB_CMDLINE_LINUX="crashkernel=auto intrema...

Goodmorning, I''m currently playing with XEN/arm on my Allwinner A20 (cubieboard2) I would like to get the XENFB driver working on domU. But currently in xen/arm there''s no support for VFB, atleast qemu is not supported. But this video http://www.youtube.com/watch?v=po1IeElg8tg and this one http://www.youtube.com/watch?v=Km6gBnIqaWo is showing a working framebuffer. So there are

...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 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...