[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Xen 4.3 PCI passthrough possible bug
Ok. I started ran the initscripts and now xl works. However, I still see the same behavior as before: root@fiat:~# xl create /etc/xen/ubuntu-hvm-0.cfg
Parsing config from /etc/xen/ubuntu-hvm-0.cfg libxl: error: libxl_qmp.c:448:qmp_next: Socket read error: Connection reset by peer libxl: error: libxl_qmp.c:691:libxl__qmp_initialize: Connection error: Connection refused
libxl: error: libxl_qmp.c:691:libxl__qmp_initialize: Connection error: Connection refused libxl: error: libxl_qmp.c:691:libxl__qmp_initialize: Connection error: Connection refused root@fiat:~# xl list
Name ID Mem VCPUs State Time(s) Domain-0 0 1024 1 r----- 15.2
ubuntu-hvm-0 1 1025 1 ------ 0.0 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x23f3000 (XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000134000000->0000000138000000 (233690 pages to be allocated) (XEN) Init. ramdisk: 000000013d0da000->000000013ffffe00 (XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff823f3000
(XEN) Init. ramdisk: ffffffff823f3000->ffffffff85318e00 (XEN) Phys-Mach map: ffffffff85319000->ffffffff85519000 (XEN) Start info: ffffffff85519000->ffffffff855194b4 (XEN) Page tables: ffffffff8551a000->ffffffff85549000
(XEN) Boot stack: ffffffff85549000->ffffffff8554a000 (XEN) TOTAL: ffffffff80000000->ffffffff85800000 (XEN) ENTRY ADDRESS: ffffffff81d261e0 (XEN) Dom0 has maximum 1 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81b2f000 (XEN) elf_load_binary: phdr 1 at 0xffffffff81c00000 -> 0xffffffff81d0f0f0 (XEN) elf_load_binary: phdr 2 at 0xffffffff81d10000 -> 0xffffffff81d252c0
(XEN) elf_load_binary: phdr 3 at 0xffffffff81d26000 -> 0xffffffff81e6d000 (XEN) Scrubbing Free RAM: .............................done. (XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All (XEN) Guest Loglevel: All (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 260kB init memory. (XEN) PCI add device 0000:00:00.0 (XEN) PCI add device 0000:00:01.0 (XEN) PCI add device 0000:00:1a.0 (XEN) PCI add device 0000:00:1c.0
(XEN) PCI add device 0000:00:1d.0 (XEN) PCI add device 0000:00:1e.0 (XEN) PCI add device 0000:00:1f.0 (XEN) PCI add device 0000:00:1f.2 (XEN) PCI add device 0000:00:1f.3
(XEN) PCI add device 0000:01:00.0
(XEN) PCI add device 0000:02:02.0 (XEN) PCI add device 0000:02:04.0 (XEN) PCI add device 0000:03:00.0 (XEN) PCI add device 0000:03:00.1 (XEN) PCI add device 0000:04:00.0
(XEN) PCI add device 0000:04:00.1 (XEN) PCI add device 0000:05:00.0 (XEN) PCI add device 0000:05:00.1 (XEN) PCI add device 0000:06:03.0 (XEN) page_alloc.c:1460:d0 Over-allocation for domain 1: 262401 > 262400
(XEN) memory.c:158:d0 Could not allocate order=0 extent: id=1 memflags=0 (200 of 1024) (d1) HVM Loader (d1) Detected Xen v4.4-rc2 (d1) Xenbus rings @0xfeffc000, event channel 4
(d1) System requested SeaBIOS (d1) CPU speed is 3093 MHz (d1) Relocating guest memory for lowmem MMIO space disabled Excerpt from /var/log/xen/*
qemu: hardware error: xen: failed to populate ram at 40050000 On Fri, Feb 7, 2014 at 3:39 PM, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:
_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |