search for: dom6

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

...################################################### # net rpc trustdom list -Uuser%passwd Trusted domains list: DOM1 S-1-5-21-790525478-1844823847-725345543 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...

...More Error messages: ==================== domU, dmesg shows: : pcifront pci-0: pciback not responding!!! pcifront pci-0: pciback not responding!!! NET: Registered protocol family 10 lo: Disabled Privacy Extensions ADDRCONF(NETDEV_UP): eth0: link is not ready in dom0, xm dmesg shows: (XEN) DOM6: (file=mm.c, line=486) Non-privileged attempt to map I/O space 00000000 (XEN) DOM6: (file=mm.c, line=486) Non-privileged attempt to map I/O space 000000c0 (XEN) DOM6: (file=mm.c, line=486) Non-privileged attempt to map I/O space 0000009f pciback runs with trace, so dom0 dmesg shows: : pciback:...

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

...---------------------------------------------------------------------- (d6) HVM Loader (d6) Detected Xen v4.4-unstable (d6) Xenbus rings @0xfeffc000, event channel 4 (d6) System requested SeaBIOS (d6) CPU speed is 2661 MHz (d6) Relocating guest memory for lowmem MMIO space disabled (XEN) irq.c:270: Dom6 PCI link 0 changed 0 -> 5 (d6) PCI-ISA link 0 routed to IRQ5 (XEN) irq.c:270: Dom6 PCI link 1 changed 0 -> 10 (d6) PCI-ISA link 1 routed to IRQ10 (XEN) irq.c:270: Dom6 PCI link 2 changed 0 -> 11 (d6) PCI-ISA link 2 routed to IRQ11 (XEN) irq.c:270: Dom6 PCI link 3 changed 0 -> 5 (d6) PCI...

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

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

...usb 1-1: new high-speed USB device number 5 using ehci_hcd [ 55.824112] usb 1-1: device not accepting address 5, error -110 I am looking at xl dmesg in Dom0 where there are some messages relating to the PCI usb: [VT-D] It's disallowed to assign 0000: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...

...spci in your domU to xen-users? There will be a lot more eyeballs there to help you get things sorted out. > I am looking at xl dmesg in Dom0 where there are some messages relating to > the PCI usb: > [VT-D] It's disallowed to assign 0000: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&...

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

This is more or less simplified series of patches that bring power usage on my NV86 close to that of binary blob. Best regards, Maxim Levitsky