Re: [Xen-users] DomU sees only 512MB RAM with PCI-passthrough

All of lore.kernel.org
 help / color / mirror / Atom feed

* Re: [Xen-users] DomU sees only 512MB RAM with PCI-passthrough
       [not found]                 ` <519F89BB.3020709@holpert.de>
@ 2013-05-25 11:13                   ` Konrad Rzeszutek Wilk
  2013-05-25 15:18                     ` Christian Holpert
  0 siblings, 1 reply; 9+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-05-25 11:13 UTC (permalink / raw)
  To: Christian Holpert; +Cc: xen-devel

On Fri, May 24, 2013 at 05:39:39PM +0200, Christian Holpert wrote:
> Konrad,

Please don't drop the xen-devel from the email. I am putting it back.
> 
> as written before: your patch is not working for me.

I must have missed your previous email. When did you send it?
> 
> Even worse: when I create the domU it simply dies before running the kernel.

How so? Can you get the console output if you boot it with 'earlyprintk=xen"
> 
> Logs attached for
> memory=512
> and
> memory=1024

Right, with that option the E820 looks to have the right values:

libxl_x86.c:201:e820_sanitize: :	[0 -> 20000] RAM
libxl_x86.c:201:e820_sanitize: :	[20000 -> 20200] Reserved
libxl_x86.c:201:e820_sanitize: :	[20200 -> 40004] Unusable
libxl_x86.c:201:e820_sanitize: :	[40004 -> 40005] Reserved
libxl_x86.c:201:e820_sanitize: :	[40005 -> d9cbf] Unusable
libxl_x86.c:201:e820_sanitize: :	[d9cbf -> da286] Reserved
libxl_x86.c:201:e820_sanitize: :	[da286 -> da506] ACPI NVS
libxl_x86.c:201:e820_sanitize: :	[da506 -> da50b] ACPI
libxl_x86.c:201:e820_sanitize: :	[da50b -> da54e] ACPI NVS
libxl_x86.c:201:e820_sanitize: :	[da54e -> dad56] Unusable
libxl_x86.c:201:e820_sanitize: :	[dad56 -> daff2] Reserved
libxl_x86.c:201:e820_sanitize: :	[daff2 -> db000] Unusable
libxl_x86.c:201:e820_sanitize: :	[db800 -> dfa00] Reserved
libxl_x86.c:201:e820_sanitize: :	[f8000 -> fc000] Reserved
libxl_x86.c:201:e820_sanitize: :	[fec00 -> fec01] Reserved
libxl_x86.c:201:e820_sanitize: :	[fed00 -> fed04] Reserved
libxl_x86.c:201:e820_sanitize: :	[fed1c -> fed20] Reserved
libxl_x86.c:201:e820_sanitize: :	[fee00 -> fee01] Reserved
libxl_x86.c:201:e820_sanitize: :	[ff000 -> 100000] Reserved
----> libxl_x86.c:201:e820_sanitize: :	[100000 -> 120000] RAM <-----

(as the extra amount of memory is added).
> 
> maxmem is not used.
> 
> Reverting the patch at least makes the domU bootable again. With 512MB.

Hm, the E820 with 512MB looks to be the same as you posted earlier.
Are you sure you are using the same exact kernel you did last time?

> 
> Anything else I can test?

I am at loss here. The 512MB case has no E820 changes so I am not entirely
sure how it could be crashing. Try with 'earlyprintk=xen'
> 
> Regards,
> Christian
> 
> 
> ---- Original-Nachricht ----
>   Von: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>   Datum: Freitag, 24. Mai 2013 17:28:37
> >On Wed, May 22, 2013 at 05:17:52PM -0400, Konrad Rzeszutek Wilk wrote:
> >>On Wed, May 22, 2013 at 05:15:37PM -0400, Konrad Rzeszutek Wilk wrote:
> >>>On Wed, May 22, 2013 at 05:06:18PM -0400, Konrad Rzeszutek Wilk wrote:
> >>>>On Thu, Dec 20, 2012 at 01:40:38PM +0100, Christian Holpert wrote:
> >>>>>Hello,
> >>>>>
> >>>>>the output of xl -vvv create is attached for xen 4.2.1 with PCI and
> >>>>>without PCI.
> >>>>Could you also attach the host dmesg please?
> >>>Nevermind. I can reproduce it. The interesting thing is that initially I had
> >>>this in my guest config:
> >>>
> >>>maxmem=2048
> >>>memory=1024
> >>>
> >>>and the output of the tools told me:
> >>>Memory: 1048576kB End of RAM: 0x20000 (PFN) Delta: 524288kB, PCI start: 524288kB (0x20000 PFN), Balloon 1048576kB
> >>>
> >>>.. and then it added that 1G to the end:
> >>>
> >>>libxl_x86.c:201:e820_sanitize: :  [100000 -> 160000] RAM
> >>>
> >>>and the guest booted nicely.
> >>>
> >>>But if maxmem=memory I get:
> >>>
> >>>Memory: 2097152kB End of RAM: 0x20000 (PFN) Delta: 1572864kB, PCI start: 524288kB (0x20000 PFN), Balloon 0kB
> >>>
> >>>And of course no E820 entry at 4G and guest crashes.
> >>Pff, try this patch please:
> >>
> >>diff --git a/tools/libxl/libxl_x86.c b/tools/libxl/libxl_x86.c
> >>index a17f6ae..a78c91d 100644
> >>--- a/tools/libxl/libxl_x86.c
> >>+++ b/tools/libxl/libxl_x86.c
> >>@@ -182,7 +182,7 @@ static int e820_sanitize(libxl_ctx *ctx, struct e820entry src[],
> >>          idx++;
> >>      }
> >>      /* At this point we have the mapped RAM + E820 entries from src. */
> >>-    if (balloon_kb) {
> >>+    if (balloon_kb || delta_kb) {
> >>          /* and if we truncated the RAM region, then add it to the end. */
> >>          e820[idx].type = E820_RAM;
> >>          e820[idx].addr = (uint64_t)(1ULL << 32) > last ?
> >>
> >>(I am heading out for today and will retry it tomorrow, but I am 99%
> >>that is the culprit).
> >And it works. Will send out a patch shortly.
> 
> Mit freundlichen Grüßen,
> Christian Holpert
> 
> -- 
> Christian Holpert
> Im Markthof 5
> 63776 Mömbris
>   Tel.: 06029-1379 Fax: 9986589
> 

> libxl: debug: libxl_create.c:1192:do_domain_create: ao 0xf242c0: create: how=(nil) callback=(nil) poller=0xf246a0
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda1 spec.backend=unknown
> libxl: debug: libxl_device.c:175:disk_try_backend: Disk vdev=xvda1, backend phy unsuitable as phys path not a block device
> libxl: debug: libxl_device.c:184:disk_try_backend: Disk vdev=xvda1, backend tap unsuitable because blktap not available
> libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=xvda1, using backend qdisk
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda2 spec.backend=unknown
> libxl: debug: libxl_device.c:175:disk_try_backend: Disk vdev=xvda2, backend phy unsuitable as phys path not a block device
> libxl: debug: libxl_device.c:184:disk_try_backend: Disk vdev=xvda2, backend tap unsuitable because blktap not available
> libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=xvda2, using backend qdisk
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda3 spec.backend=unknown
> libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=xvda3, using backend phy
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda4 spec.backend=unknown
> libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=xvda4, using backend phy
> libxl: debug: libxl_create.c:694:initiate_domain_create: running bootloader
> libxl: debug: libxl_bootloader.c:327:libxl__bootloader_run: no bootloader configured, using user supplied kernel
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch w=0xf24e50: deregister unregistered
> libxl: debug: libxl_numa.c:435:libxl__get_numa_candidate: New best NUMA placement candidate found: nr_nodes=1, nr_cpus=4, nr_vcpus=8, free_memkb=7025
> libxl: detail: libxl_dom.c:193:numa_place_domain: NUMA placement candidate with 1 nodes, 4 cpus and 7025 KB free selected
> libxl: debug: libxl_x86.c:82:e820_sanitize: Memory: 1048576kB End of RAM: 0x20000 (PFN) Delta: 524288kB, PCI start: 524288kB (0x20000 PFN), Balloon 0kB
> 
> domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/xvda1 rootfstype=ext4 rootfsflags=barrier=0 console=hvc0 xencons=hvc xen-fbfront.video=6,1024,768 xenfb.video=6,1024,768 noirqdebug elevator=noop cifs.enable_oplocks=0 netconsole=6666@10.75.157.21/eth0,6666@10.75.157.46/BC:5F:F4:3B:63:9D", features="(null)"
> libxl: debug: libxl_dom.c:384:libxl__build_pv: pv kernel mapped 0 path /boot/kernel-3.7.3-xenU
> 
> domainbuilder: detail: xc_dom_kernel_file: filename="/boot/kernel-3.7.3-xenU"
> domainbuilder: detail: xc_dom_malloc_filemap    : 6233 kB
> domainbuilder: detail: xc_dom_boot_xen_init: ver 4.2, caps xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 
> domainbuilder: detail: xc_dom_parse_image: called
> domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary loader ... 
> domainbuilder: detail: loader probe failed
> domainbuilder: detail: xc_dom_find_loader: trying Linux bzImage loader ... 
> domainbuilder: detail: xc_dom_probe_bzimage_kernel: kernel is not a bzImage
> domainbuilder: detail: loader probe failed
> domainbuilder: detail: xc_dom_find_loader: trying ELF-generic loader ... 
> domainbuilder: detail: loader probe OK
> xc: detail: elf_parse_binary: phdr: paddr=0x1000000 memsz=0x40c000
> xc: detail: elf_parse_binary: phdr: paddr=0x140c000 memsz=0x353000
> xc: detail: elf_parse_binary: memory: 0x1000000 -> 0x175f000
> xc: detail: elf_xen_parse_note: GUEST_OS = "linux"
> xc: detail: elf_xen_parse_note: GUEST_VERSION = "2.6"
> xc: detail: elf_xen_parse_note: XEN_VERSION = "xen-3.0"
> xc: detail: elf_xen_parse_note: VIRT_BASE = 0xc0000000
> xc: detail: elf_xen_parse_note: ENTRY = 0xc143c24c
> xc: detail: elf_xen_parse_note: HYPERCALL_PAGE = 0xc1001000
> xc: detail: elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb"
> xc: detail: elf_xen_parse_note: PAE_MODE = "yes"
> xc: detail: elf_xen_parse_note: LOADER = "generic"
> xc: detail: elf_xen_parse_note: unknown xen elf note (0xd)
> xc: detail: elf_xen_parse_note: SUSPEND_CANCEL = 0x1
> xc: detail: elf_xen_parse_note: HV_START_LOW = 0xf5800000
> xc: detail: elf_xen_parse_note: PADDR_OFFSET = 0x0
> xc: detail: elf_xen_addr_calc_check: addresses:
> xc: detail:     virt_base        = 0xc0000000
> xc: detail:     elf_paddr_offset = 0x0
> xc: detail:     virt_offset      = 0xc0000000
> xc: detail:     virt_kstart      = 0xc1000000
> xc: detail:     virt_kend        = 0xc175f000
> xc: detail:     virt_entry       = 0xc143c24c
> xc: detail:     p2m_base         = 0xffffffffffffffff
> domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_32p: 0xc1000000 -> 0xc175f000
> domainbuilder: detail: xc_dom_mem_init: mem 1024 MB, pages 0x40000 pages, 4k each
> domainbuilder: detail: xc_dom_mem_init: 0x40000 pages
> domainbuilder: detail: xc_dom_boot_mem_init: called
> domainbuilder: detail: x86_compat: guest xen-3.0-x86_32p, address size 32
> domainbuilder: detail: xc_dom_malloc            : 2048 kB
> domainbuilder: detail: xc_dom_build_image: called
> domainbuilder: detail: xc_dom_alloc_segment:   kernel       : 0xc1000000 -> 0xc175f000  (pfn 0x1000 + 0x75f pages)
> domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x1000+0x75f at 0x7fa8fcc96000
> xc: detail: elf_load_binary: phdr 0 at 0x0x7fa8fcc96000 -> 0x0x7fa8fd0a2000
> xc: detail: elf_load_binary: phdr 1 at 0x0x7fa8fd0a2000 -> 0x0x7fa8fd131000
> domainbuilder: detail: xc_dom_alloc_segment:   phys2mach    : 0xc175f000 -> 0xc185f000  (pfn 0x175f + 0x100 pages)
> domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x175f+0x100 at 0x7fa900028000
> domainbuilder: detail: xc_dom_alloc_page   :   start info   : 0xc185f000 (pfn 0x185f)
> domainbuilder: detail: xc_dom_alloc_page   :   xenstore     : 0xc1860000 (pfn 0x1860)
> domainbuilder: detail: xc_dom_alloc_page   :   console      : 0xc1861000 (pfn 0x1861)
> domainbuilder: detail: nr_page_tables: 0x00000000ffffffff/32: 0x0000000000000000 -> 0x00000000ffffffff, 1 table(s)
> domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30: 0x00000000c0000000 -> 0x00000000ffffffff, 1 table(s)
> domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21: 0x00000000c0000000 -> 0x00000000c1bfffff, 14 table(s)
> domainbuilder: detail: xc_dom_alloc_segment:   page tables  : 0xc1862000 -> 0xc1872000  (pfn 0x1862 + 0x10 pages)
> domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x1862+0x10 at 0x7fa900018000
> domainbuilder: detail: xc_dom_alloc_page   :   boot stack   : 0xc1872000 (pfn 0x1872)
> domainbuilder: detail: xc_dom_build_image  : virt_alloc_end : 0xc1873000
> domainbuilder: detail: xc_dom_build_image  : virt_pgtab_end : 0xc1c00000
> domainbuilder: detail: xc_dom_boot_image: called
> domainbuilder: detail: arch_setup_bootearly: doing nothing
> domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_64
> domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_32p <= matches
> domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32
> domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32p
> domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_64
> domainbuilder: detail: xc_dom_update_guest_p2m: dst 32bit, pages 0x40000
> domainbuilder: detail: clear_page: pfn 0x1861, mfn 0x31ac5a
> domainbuilder: detail: clear_page: pfn 0x1860, mfn 0x31ac5b
> domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x185f+0x1 at 0x7fa900138000
> domainbuilder: detail: start_info_x86_32: called
> domainbuilder: detail: setup_hypercall_page: vaddr=0xc1001000 pfn=0x1001
> domainbuilder: detail: domain builder memory footprint
> domainbuilder: detail:    allocated
> domainbuilder: detail:       malloc             : 2101 kB
> domainbuilder: detail:       anon mmap          : 0 bytes
> domainbuilder: detail:    mapped
> domainbuilder: detail:       file mmap          : 6233 kB
> domainbuilder: detail:       domU mmap          : 8640 kB
> domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn 0xb8800
> domainbuilder: detail: shared_info_x86_32: called
> domainbuilder: detail: vcpu_x86_32: called
> domainbuilder: detail: vcpu_x86_32: cr3: pfn 0x1862 mfn 0x31ac59
> domainbuilder: detail: launch_vm: called, ctxt=0x7fffe3521820
> domainbuilder: detail: xc_dom_release: called
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda1 spec.backend=qdisk
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda1 spec.backend=qdisk
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda1 spec.backend=qdisk
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda1 spec.backend=qdisk
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda1 spec.backend=qdisk
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda1 spec.backend=qdisk
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda2 spec.backend=qdisk
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda3 spec.backend=phy
> libxl: debug: libxl_event.c:558:libxl__ev_xswatch_register: watch w=0xf292b8 wpath=/local/domain/0/backend/vbd/6/51715/state token=3/0: register slotnum=3
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda4 spec.backend=phy
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda4 spec.backend=phy
> libxl: debug: libxl_event.c:558:libxl__ev_xswatch_register: watch w=0xf29bb8 wpath=/local/domain/0/backend/vbd/6/51716/state token=2/1: register slotnum=2
> libxl: debug: libxl_create.c:1205:do_domain_create: ao 0xf242c0: inprogress: poller=0xf246a0, flags=i
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xf292b8 wpath=/local/domain/0/backend/vbd/6/51715/state token=3/0: event epath=/local/domain/0/backend/vbd/6/51715/state
> libxl: debug: libxl_event.c:642:devstate_watch_callback: backend /local/domain/0/backend/vbd/6/51715/state wanted state 2 ok
> libxl: debug: libxl_event.c:595:libxl__ev_xswatch_deregister: watch w=0xf292b8 wpath=/local/domain/0/backend/vbd/6/51715/state token=3/0: deregister slotnum=3
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch w=0xf292b8: deregister unregistered
> libxl: debug: libxl_device.c:917:device_hotplug: calling hotplug script: /etc/xen/scripts/block add
> libxl: debug: libxl_event.c:472:watchfd_callback: watch epath=/local/domain/0/backend/vbd/6/51715/state token=3/0: empty slot
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xf29bb8 wpath=/local/domain/0/backend/vbd/6/51716/state token=2/1: event epath=/local/domain/0/backend/vbd/6/51716/state
> libxl: debug: libxl_event.c:642:devstate_watch_callback: backend /local/domain/0/backend/vbd/6/51716/state wanted state 2 ok
> libxl: debug: libxl_event.c:595:libxl__ev_xswatch_deregister: watch w=0xf29bb8 wpath=/local/domain/0/backend/vbd/6/51716/state token=2/1: deregister slotnum=2
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch w=0xf29bb8: deregister unregistered
> libxl: debug: libxl_device.c:917:device_hotplug: calling hotplug script: /etc/xen/scripts/block add
> libxl: debug: libxl_event.c:472:watchfd_callback: watch epath=/local/domain/0/backend/vbd/6/51716/state token=2/1: empty slot
> libxl: debug: libxl_dm.c:1148:libxl__spawn_local_dm: Spawning device-model /usr/lib/xen/bin/qemu-system-i386 with arguments:
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   /usr/lib/xen/bin/qemu-system-i386
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   -xen-domid
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   6
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   -chardev
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-6,server,nowait
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   -mon
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   chardev=libxl-cmd,mode=control
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   -xen-attach
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   -name
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   nodi
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   -vnc
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   0.0.0.0:10,to=99
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   -k
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   de
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   -M
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   xenpv
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   -m
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   1025
> libxl: debug: libxl_event.c:558:libxl__ev_xswatch_register: watch w=0xf25088 wpath=/local/domain/0/device-model/6/state token=2/2: register slotnum=2
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xf25088 wpath=/local/domain/0/device-model/6/state token=2/2: event epath=/local/domain/0/device-model/6/state
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xf25088 wpath=/local/domain/0/device-model/6/state token=2/2: event epath=/local/domain/0/device-model/6/state
> libxl: debug: libxl_event.c:595:libxl__ev_xswatch_deregister: watch w=0xf25088 wpath=/local/domain/0/device-model/6/state token=2/2: deregister slotnum=2
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch w=0xf25088: deregister unregistered
> libxl: debug: libxl_qmp.c:696:libxl__qmp_initialize: connected to /var/run/xen/qmp-libxl-6
> libxl: debug: libxl_qmp.c:299:qmp_handle_response: message type: qmp
> libxl: debug: libxl_qmp.c:556:qmp_send_prepare: next qmp command: '{"execute":"qmp_capabilities","id":1}'
> libxl: debug: libxl_qmp.c:299:qmp_handle_response: message type: return
> libxl: debug: libxl_qmp.c:556:qmp_send_prepare: next qmp command: '{"execute":"query-chardev","id":2}'
> libxl: debug: libxl_qmp.c:299:qmp_handle_response: message type: return
> libxl: debug: libxl_qmp.c:556:qmp_send_prepare: next qmp command: '{"execute":"query-vnc","id":3}'
> libxl: debug: libxl_qmp.c:299:qmp_handle_response: message type: return
> libxl: debug: libxl_event.c:558:libxl__ev_xswatch_register: watch w=0xf2da08 wpath=/local/domain/0/backend/vif/6/0/state token=2/3: register slotnum=2
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xf2da08 wpath=/local/domain/0/backend/vif/6/0/state token=2/3: event epath=/local/domain/0/backend/vif/6/0/state
> libxl: debug: libxl_event.c:646:devstate_watch_callback: backend /local/domain/0/backend/vif/6/0/state wanted state 2 still waiting state 1
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0xf2da08 wpath=/local/domain/0/backend/vif/6/0/state token=2/3: event epath=/local/domain/0/backend/vif/6/0/state
> libxl: debug: libxl_event.c:642:devstate_watch_callback: backend /local/domain/0/backend/vif/6/0/state wanted state 2 ok
> libxl: debug: libxl_event.c:595:libxl__ev_xswatch_deregister: watch w=0xf2da08 wpath=/local/domain/0/backend/vif/6/0/state token=2/3: deregister slotnum=2
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch w=0xf2da08: deregister unregistered
> libxl: debug: libxl_device.c:917:device_hotplug: calling hotplug script: /etc/xen/scripts/vif-bridge online
> libxl: debug: libxl_pci.c:85:libxl__create_pci_backend: Creating pci backend
> libxl: debug: libxl_event.c:1736:libxl__ao_progress_report: ao 0xf242c0: progress report: ignored
> libxl: debug: libxl_event.c:1568:libxl__ao_complete: ao 0xf242c0: complete, rc=0
> libxl: debug: libxl_event.c:1540:libxl__ao__destroy: ao 0xf242c0: destroy
> xc: debug: hypercall buffer: total allocations:509 total releases:509
> xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
> xc: debug: hypercall buffer: cache current size:4
> xc: debug: hypercall buffer: cache hits:499 misses:4 toobig:6
> Parsing config from /opt/xen/nodi.cfg
> Daemon running with PID 9501

> libxl: debug: libxl_create.c:1192:do_domain_create: ao 0x1c4f2c0: create: how=(nil) callback=(nil) poller=0x1c4f6a0
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda1 spec.backend=unknown
> libxl: debug: libxl_device.c:175:disk_try_backend: Disk vdev=xvda1, backend phy unsuitable as phys path not a block device
> libxl: debug: libxl_device.c:184:disk_try_backend: Disk vdev=xvda1, backend tap unsuitable because blktap not available
> libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=xvda1, using backend qdisk
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda2 spec.backend=unknown
> libxl: debug: libxl_device.c:175:disk_try_backend: Disk vdev=xvda2, backend phy unsuitable as phys path not a block device
> libxl: debug: libxl_device.c:184:disk_try_backend: Disk vdev=xvda2, backend tap unsuitable because blktap not available
> libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=xvda2, using backend qdisk
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda3 spec.backend=unknown
> libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=xvda3, using backend phy
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda4 spec.backend=unknown
> libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=xvda4, using backend phy
> libxl: debug: libxl_create.c:694:initiate_domain_create: running bootloader
> libxl: debug: libxl_bootloader.c:327:libxl__bootloader_run: no bootloader configured, using user supplied kernel
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch w=0x1c4fe50: deregister unregistered
> libxl: debug: libxl_numa.c:435:libxl__get_numa_candidate: New best NUMA placement candidate found: nr_nodes=1, nr_cpus=4, nr_vcpus=8, free_memkb=7025
> libxl: detail: libxl_dom.c:193:numa_place_domain: NUMA placement candidate with 1 nodes, 4 cpus and 7025 KB free selected
> libxl: debug: libxl_x86.c:82:e820_sanitize: Memory: 524288kB End of RAM: 0x20000 (PFN) Delta: 0kB, PCI start: 524288kB (0x20000 PFN), Balloon 0kB
> 
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[0 -> 20000] RAM
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[20000 -> 20200] Reserved
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[20200 -> 40004] Unusable
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[40004 -> 40005] Reserved
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[40005 -> d9cbf] Unusable
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[d9cbf -> da286] Reserved
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[da286 -> da506] ACPI NVS
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[da506 -> da50b] ACPI
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[da50b -> da54e] ACPI NVS
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[da54e -> dad56] Unusable
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[dad56 -> daff2] Reserved
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[daff2 -> db000] Unusable
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[db800 -> dfa00] Reserved
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[f8000 -> fc000] Reserved
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[fec00 -> fec01] Reserved
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[fed00 -> fed04] Reserved
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[fed1c -> fed20] Reserved
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[fee00 -> fee01] Reserved
> libxl: debug: libxl_x86.c:201:e820_sanitize: :	[ff000 -> 100000] Reserved
> domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/xvda1 rootfstype=ext4 rootfsflags=barrier=0 console=hvc0 xencons=hvc xen-fbfront.video=6,1024,768 xenfb.video=6,1024,768 noirqdebug elevator=noop cifs.enable_oplocks=0 netconsole=6666@10.75.157.21/eth0,6666@10.75.157.46/BC:5F:F4:3B:63:9D", features="(null)"
> libxl: debug: libxl_dom.c:384:libxl__build_pv: pv kernel mapped 0 path /boot/kernel-3.7.3-xenU
> 
> domainbuilder: detail: xc_dom_kernel_file: filename="/boot/kernel-3.7.3-xenU"
> domainbuilder: detail: xc_dom_malloc_filemap    : 6233 kB
> domainbuilder: detail: xc_dom_boot_xen_init: ver 4.2, caps xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 
> domainbuilder: detail: xc_dom_parse_image: called
> domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary loader ... 
> domainbuilder: detail: loader probe failed
> domainbuilder: detail: xc_dom_find_loader: trying Linux bzImage loader ... 
> domainbuilder: detail: xc_dom_probe_bzimage_kernel: kernel is not a bzImage
> domainbuilder: detail: loader probe failed
> domainbuilder: detail: xc_dom_find_loader: trying ELF-generic loader ... 
> domainbuilder: detail: loader probe OK
> xc: detail: elf_parse_binary: phdr: paddr=0x1000000 memsz=0x40c000
> xc: detail: elf_parse_binary: phdr: paddr=0x140c000 memsz=0x353000
> xc: detail: elf_parse_binary: memory: 0x1000000 -> 0x175f000
> xc: detail: elf_xen_parse_note: GUEST_OS = "linux"
> xc: detail: elf_xen_parse_note: GUEST_VERSION = "2.6"
> xc: detail: elf_xen_parse_note: XEN_VERSION = "xen-3.0"
> xc: detail: elf_xen_parse_note: VIRT_BASE = 0xc0000000
> xc: detail: elf_xen_parse_note: ENTRY = 0xc143c24c
> xc: detail: elf_xen_parse_note: HYPERCALL_PAGE = 0xc1001000
> xc: detail: elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb"
> xc: detail: elf_xen_parse_note: PAE_MODE = "yes"
> xc: detail: elf_xen_parse_note: LOADER = "generic"
> xc: detail: elf_xen_parse_note: unknown xen elf note (0xd)
> xc: detail: elf_xen_parse_note: SUSPEND_CANCEL = 0x1
> xc: detail: elf_xen_parse_note: HV_START_LOW = 0xf5800000
> xc: detail: elf_xen_parse_note: PADDR_OFFSET = 0x0
> xc: detail: elf_xen_addr_calc_check: addresses:
> xc: detail:     virt_base        = 0xc0000000
> xc: detail:     elf_paddr_offset = 0x0
> xc: detail:     virt_offset      = 0xc0000000
> xc: detail:     virt_kstart      = 0xc1000000
> xc: detail:     virt_kend        = 0xc175f000
> xc: detail:     virt_entry       = 0xc143c24c
> xc: detail:     p2m_base         = 0xffffffffffffffff
> domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_32p: 0xc1000000 -> 0xc175f000
> domainbuilder: detail: xc_dom_mem_init: mem 512 MB, pages 0x20000 pages, 4k each
> domainbuilder: detail: xc_dom_mem_init: 0x20000 pages
> domainbuilder: detail: xc_dom_boot_mem_init: called
> domainbuilder: detail: x86_compat: guest xen-3.0-x86_32p, address size 32
> domainbuilder: detail: xc_dom_malloc            : 1024 kB
> domainbuilder: detail: xc_dom_build_image: called
> domainbuilder: detail: xc_dom_alloc_segment:   kernel       : 0xc1000000 -> 0xc175f000  (pfn 0x1000 + 0x75f pages)
> domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x1000+0x75f at 0x7f737cc49000
> xc: detail: elf_load_binary: phdr 0 at 0x0x7f737cc49000 -> 0x0x7f737d055000
> xc: detail: elf_load_binary: phdr 1 at 0x0x7f737d055000 -> 0x0x7f737d0e4000
> domainbuilder: detail: xc_dom_alloc_segment:   phys2mach    : 0xc175f000 -> 0xc17df000  (pfn 0x175f + 0x80 pages)
> domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x175f+0x80 at 0x7f737fd59000
> domainbuilder: detail: xc_dom_alloc_page   :   start info   : 0xc17df000 (pfn 0x17df)
> domainbuilder: detail: xc_dom_alloc_page   :   xenstore     : 0xc17e0000 (pfn 0x17e0)
> domainbuilder: detail: xc_dom_alloc_page   :   console      : 0xc17e1000 (pfn 0x17e1)
> domainbuilder: detail: nr_page_tables: 0x00000000ffffffff/32: 0x0000000000000000 -> 0x00000000ffffffff, 1 table(s)
> domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30: 0x00000000c0000000 -> 0x00000000ffffffff, 1 table(s)
> domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21: 0x00000000c0000000 -> 0x00000000c1bfffff, 14 table(s)
> domainbuilder: detail: xc_dom_alloc_segment:   page tables  : 0xc17e2000 -> 0xc17f2000  (pfn 0x17e2 + 0x10 pages)
> domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x17e2+0x10 at 0x7f737fd49000
> domainbuilder: detail: xc_dom_alloc_page   :   boot stack   : 0xc17f2000 (pfn 0x17f2)
> domainbuilder: detail: xc_dom_build_image  : virt_alloc_end : 0xc17f3000
> domainbuilder: detail: xc_dom_build_image  : virt_pgtab_end : 0xc1c00000
> domainbuilder: detail: xc_dom_boot_image: called
> domainbuilder: detail: arch_setup_bootearly: doing nothing
> domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_64
> domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_32p <= matches
> domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32
> domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32p
> domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_64
> domainbuilder: detail: xc_dom_update_guest_p2m: dst 32bit, pages 0x20000
> domainbuilder: detail: clear_page: pfn 0x17e1, mfn 0x338cda
> domainbuilder: detail: clear_page: pfn 0x17e0, mfn 0x338cdb
> domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x17df+0x1 at 0x7f737feea000
> domainbuilder: detail: start_info_x86_32: called
> domainbuilder: detail: setup_hypercall_page: vaddr=0xc1001000 pfn=0x1001
> domainbuilder: detail: domain builder memory footprint
> domainbuilder: detail:    allocated
> domainbuilder: detail:       malloc             : 1074 kB
> domainbuilder: detail:       anon mmap          : 0 bytes
> domainbuilder: detail:    mapped
> domainbuilder: detail:       file mmap          : 6233 kB
> domainbuilder: detail:       domU mmap          : 8128 kB
> domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn 0xb8819
> domainbuilder: detail: shared_info_x86_32: called
> domainbuilder: detail: vcpu_x86_32: called
> domainbuilder: detail: vcpu_x86_32: cr3: pfn 0x17e2 mfn 0x338cd9
> domainbuilder: detail: launch_vm: called, ctxt=0x7fff55001b50
> domainbuilder: detail: xc_dom_release: called
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda1 spec.backend=qdisk
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda1 spec.backend=qdisk
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda1 spec.backend=qdisk
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda1 spec.backend=qdisk
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda1 spec.backend=qdisk
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda1 spec.backend=qdisk
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda2 spec.backend=qdisk
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda3 spec.backend=phy
> libxl: debug: libxl_event.c:558:libxl__ev_xswatch_register: watch w=0x1c542b8 wpath=/local/domain/0/backend/vbd/5/51715/state token=3/0: register slotnum=3
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda4 spec.backend=phy
> libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda4 spec.backend=phy
> libxl: debug: libxl_event.c:558:libxl__ev_xswatch_register: watch w=0x1c54bb8 wpath=/local/domain/0/backend/vbd/5/51716/state token=2/1: register slotnum=2
> libxl: debug: libxl_create.c:1205:do_domain_create: ao 0x1c4f2c0: inprogress: poller=0x1c4f6a0, flags=i
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x1c542b8 wpath=/local/domain/0/backend/vbd/5/51715/state token=3/0: event epath=/local/domain/0/backend/vbd/5/51715/state
> libxl: debug: libxl_event.c:642:devstate_watch_callback: backend /local/domain/0/backend/vbd/5/51715/state wanted state 2 ok
> libxl: debug: libxl_event.c:595:libxl__ev_xswatch_deregister: watch w=0x1c542b8 wpath=/local/domain/0/backend/vbd/5/51715/state token=3/0: deregister slotnum=3
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch w=0x1c542b8: deregister unregistered
> libxl: debug: libxl_device.c:917:device_hotplug: calling hotplug script: /etc/xen/scripts/block add
> libxl: debug: libxl_event.c:472:watchfd_callback: watch epath=/local/domain/0/backend/vbd/5/51715/state token=3/0: empty slot
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x1c54bb8 wpath=/local/domain/0/backend/vbd/5/51716/state token=2/1: event epath=/local/domain/0/backend/vbd/5/51716/state
> libxl: debug: libxl_event.c:642:devstate_watch_callback: backend /local/domain/0/backend/vbd/5/51716/state wanted state 2 ok
> libxl: debug: libxl_event.c:595:libxl__ev_xswatch_deregister: watch w=0x1c54bb8 wpath=/local/domain/0/backend/vbd/5/51716/state token=2/1: deregister slotnum=2
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch w=0x1c54bb8: deregister unregistered
> libxl: debug: libxl_device.c:917:device_hotplug: calling hotplug script: /etc/xen/scripts/block add
> libxl: debug: libxl_event.c:472:watchfd_callback: watch epath=/local/domain/0/backend/vbd/5/51716/state token=2/1: empty slot
> libxl: debug: libxl_dm.c:1148:libxl__spawn_local_dm: Spawning device-model /usr/lib/xen/bin/qemu-system-i386 with arguments:
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   /usr/lib/xen/bin/qemu-system-i386
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   -xen-domid
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   5
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   -chardev
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-5,server,nowait
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   -mon
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   chardev=libxl-cmd,mode=control
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   -xen-attach
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   -name
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   nodi
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   -vnc
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   0.0.0.0:10,to=99
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   -k
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   de
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   -M
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   xenpv
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   -m
> libxl: debug: libxl_dm.c:1150:libxl__spawn_local_dm:   513
> libxl: debug: libxl_event.c:558:libxl__ev_xswatch_register: watch w=0x1c50088 wpath=/local/domain/0/device-model/5/state token=2/2: register slotnum=2
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x1c50088 wpath=/local/domain/0/device-model/5/state token=2/2: event epath=/local/domain/0/device-model/5/state
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x1c50088 wpath=/local/domain/0/device-model/5/state token=2/2: event epath=/local/domain/0/device-model/5/state
> libxl: debug: libxl_event.c:595:libxl__ev_xswatch_deregister: watch w=0x1c50088 wpath=/local/domain/0/device-model/5/state token=2/2: deregister slotnum=2
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch w=0x1c50088: deregister unregistered
> libxl: debug: libxl_qmp.c:696:libxl__qmp_initialize: connected to /var/run/xen/qmp-libxl-5
> libxl: debug: libxl_qmp.c:299:qmp_handle_response: message type: qmp
> libxl: debug: libxl_qmp.c:556:qmp_send_prepare: next qmp command: '{"execute":"qmp_capabilities","id":1}'
> libxl: debug: libxl_qmp.c:299:qmp_handle_response: message type: return
> libxl: debug: libxl_qmp.c:556:qmp_send_prepare: next qmp command: '{"execute":"query-chardev","id":2}'
> libxl: debug: libxl_qmp.c:299:qmp_handle_response: message type: return
> libxl: debug: libxl_qmp.c:556:qmp_send_prepare: next qmp command: '{"execute":"query-vnc","id":3}'
> libxl: debug: libxl_qmp.c:299:qmp_handle_response: message type: return
> libxl: debug: libxl_event.c:558:libxl__ev_xswatch_register: watch w=0x1c58a08 wpath=/local/domain/0/backend/vif/5/0/state token=2/3: register slotnum=2
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x1c58a08 wpath=/local/domain/0/backend/vif/5/0/state token=2/3: event epath=/local/domain/0/backend/vif/5/0/state
> libxl: debug: libxl_event.c:646:devstate_watch_callback: backend /local/domain/0/backend/vif/5/0/state wanted state 2 still waiting state 1
> libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x1c58a08 wpath=/local/domain/0/backend/vif/5/0/state token=2/3: event epath=/local/domain/0/backend/vif/5/0/state
> libxl: debug: libxl_event.c:642:devstate_watch_callback: backend /local/domain/0/backend/vif/5/0/state wanted state 2 ok
> libxl: debug: libxl_event.c:595:libxl__ev_xswatch_deregister: watch w=0x1c58a08 wpath=/local/domain/0/backend/vif/5/0/state token=2/3: deregister slotnum=2
> libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch w=0x1c58a08: deregister unregistered
> libxl: debug: libxl_device.c:917:device_hotplug: calling hotplug script: /etc/xen/scripts/vif-bridge online
> libxl: debug: libxl_pci.c:85:libxl__create_pci_backend: Creating pci backend
> libxl: debug: libxl_event.c:1736:libxl__ao_progress_report: ao 0x1c4f2c0: progress report: ignored
> libxl: debug: libxl_event.c:1568:libxl__ao_complete: ao 0x1c4f2c0: complete, rc=0
> libxl: debug: libxl_event.c:1540:libxl__ao__destroy: ao 0x1c4f2c0: destroy
> xc: debug: hypercall buffer: total allocations:509 total releases:509
> xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
> xc: debug: hypercall buffer: cache current size:4
> xc: debug: hypercall buffer: cache hits:499 misses:4 toobig:6
> Parsing config from /opt/xen/nodi.cfg
> Daemon running with PID 9309

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [Xen-users] DomU sees only 512MB RAM with PCI-passthrough
  2013-05-25 11:13                   ` [Xen-users] DomU sees only 512MB RAM with PCI-passthrough Konrad Rzeszutek Wilk
@ 2013-05-25 15:18                     ` Christian Holpert
  2013-05-25 18:31                       ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 9+ messages in thread
From: Christian Holpert @ 2013-05-25 15:18 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk; +Cc: xen-devel

At 13:13 25.05.2013, Konrad Rzeszutek Wilk wrote:
>Please don't drop the xen-devel from the email. I am putting it back.

OK.

> > as written before: your patch is not working for me.
>
>I must have missed your previous email. When did you send it?

http://www.gossamer-threads.com/lists/xen/users/283697#283697

> > Even worse: when I create the domU it simply dies before running 
> the kernel.
>
>How so? Can you get the console output if you boot it with 'earlyprintk=xen"

How do I do that exactly?

>Hm, the E820 with 512MB looks to be the same as you posted earlier.
>Are you sure you are using the same exact kernel you did last time?

I did some more tests:

With your patch I can boot a 32bit domU (dom0 is 64bit) with 512MB. 
Any more will silently crash as described.
xl dmesg shows (last lines):
(XEN) mm.c:864:d8 Non-privileged (8) attempt to map I/O space 00020000
(XEN) mm.c:5317:d8 ptwr_emulate: could not get_page_from_l1e()

I can boot a 64bit domU with 2GB of RAM without problems with your 
patch and PCI is working. Just tried that out. I might be going to 
64bit for my dom0 and have that solved for me.

Christian

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [Xen-users] DomU sees only 512MB RAM with PCI-passthrough
  2013-05-25 15:18                     ` Christian Holpert
@ 2013-05-25 18:31                       ` Konrad Rzeszutek Wilk
  2013-05-26 10:59                         ` Christian Holpert
  0 siblings, 1 reply; 9+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-05-25 18:31 UTC (permalink / raw)
  To: Christian Holpert; +Cc: xen-devel

Christian Holpert <christian@holpert.de> wrote:

>At 13:13 25.05.2013, Konrad Rzeszutek Wilk wrote:
>>Please don't drop the xen-devel from the email. I am putting it back.
>
>OK.
>
>> > as written before: your patch is not working for me.
>>
>>I must have missed your previous email. When did you send it?
>
>http://www.gossamer-threads.com/lists/xen/users/283697#283697
>
>> > Even worse: when I create the domU it simply dies before running 
>> the kernel.
>>
>>How so? Can you get the console output if you boot it with
>'earlyprintk=xen"
>
>How do I do that exactly?
>
>>Hm, the E820 with 512MB looks to be the same as you posted earlier.
>>Are you sure you are using the same exact kernel you did last time?
>
>I did some more tests:
>
>With your patch I can boot a 32bit domU (dom0 is 64bit) with 512MB. 
>Any more will silently crash as described.
>xl dmesg shows (last lines):
>(XEN) mm.c:864:d8 Non-privileged (8) attempt to map I/O space 00020000
>(XEN) mm.c:5317:d8 ptwr_emulate: could not get_page_from_l1e()
>
>I can boot a 64bit domU with 2GB of RAM without problems with your 
>patch and PCI is working. Just tried that out. I might be going to 
>64bit for my dom0 and have that solved for me.
>
>Christian

For the earlyprintk=xen just add it along with the xencons_...

I must admit I hadn't  tested the 32bit in a while so you might be hitting another bug. When I get back on Monday to the office  I will try it out.  Thanks! 
-- 
Sent from my Android phone. Please excuse my brevity.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [Xen-users] DomU sees only 512MB RAM with PCI-passthrough
  2013-05-25 18:31                       ` Konrad Rzeszutek Wilk
@ 2013-05-26 10:59                         ` Christian Holpert
  2013-05-28 19:38                           ` Konrad Rzeszutek Wilk
  2013-05-28 19:45                           ` Konrad Rzeszutek Wilk
  0 siblings, 2 replies; 9+ messages in thread
From: Christian Holpert @ 2013-05-26 10:59 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk; +Cc: xen-devel

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

At 20:31 25.05.2013, Konrad Rzeszutek Wilk wrote:
>For the earlyprintk=xen just add it along with the xencons_...

I needed to recompile xen first with debug flag set. Now I get 
results from earlyprintk.

Please find attached:
xl_dmesg_512:  domU (32bit) booting fine with memory = 512
xl_dmesg_2048: domU (32bit) silently crashing with memory = 2048
Both tests with your patch active and no other changes in between.

Log shows
BUG: unable to handle kernel NULL pointer dereference at   (null)
and oopses out.

xl list does not show the process. ps shows that the corresponding 
qemu-system-i386 process is still alive and has to be killed manually.

Thanks for working on this and enjoy your weekend,
Christian

-- 
Markt-Apotheke Christian Holpert e.K., Mömbris
   http://www.marktapotheke.org - info@marktapotheke.org
   http://www.blue-essentials-shop.de - info@blue-essentials-shop.de
   Apotheker Christian Holpert
Im Markthof 5
63776 Mömbris
   Tel.: 06029-1379 Fax: 9986589

Amtsgericht Aschaffenburg, HR.A, Registernummer 2165

[-- Attachment #2: xl_dmesg_512 --]
[-- Type: application/octet-stream, Size: 4003 bytes --]

mapping kernel into physical memory
about to get started...
Reserving virtual address space above 0xf5800000
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 3.8.13-gentoo (root@nodi) (gcc version 4.7.3 (Gentoo 4.7.3 p1.0, pie-0.5.5) ) #1 SMP Sat May 25 10:59:04 CEST 2013
ACPI in unprivileged domain disabled
Set 917504 page(s) to 1-1 mapping
e820: BIOS-provided physical RAM map:
Xen: [mem 0x0000000000000000-0x000000000009ffff] usable
Xen: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Xen: [mem 0x0000000000100000-0x000000001fffffff] usable
Xen: [mem 0x0000000020000000-0x00000000201fffff] reserved
Xen: [mem 0x0000000020200000-0x0000000040003fff] unusable
Xen: [mem 0x0000000040004000-0x0000000040004fff] reserved
Xen: [mem 0x0000000040005000-0x00000000d9cbefff] unusable
Xen: [mem 0x00000000d9cbf000-0x00000000da285fff] reserved
Xen: [mem 0x00000000da286000-0x00000000da505fff] ACPI NVS
Xen: [mem 0x00000000da506000-0x00000000da50afff] ACPI data
Xen: [mem 0x00000000da50b000-0x00000000da54dfff] ACPI NVS
Xen: [mem 0x00000000da54e000-0x00000000dad55fff] unusable
Xen: [mem 0x00000000dad56000-0x00000000daff1fff] reserved
Xen: [mem 0x00000000daff2000-0x00000000daffffff] unusable
Xen: [mem 0x00000000db800000-0x00000000df9fffff] reserved
Xen: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Xen: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Xen: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Xen: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Xen: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Xen: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
bootconsole [xenboot0] enabled
NX (Execute Disable) protection: active
DMI not present or invalid.
e820: last_pfn = 0x20000 max_arch_pfn = 0x1000000
init_memory_mapping: [mem 0x00000000-0x1fffffff]
0MB HIGHMEM available.
512MB LOWMEM available.
  mapped low ram: 0 - 20000000
  low ram: 0 - 20000000
Zone ranges:
  DMA      [mem 0x00010000-0x00ffffff]
  Normal   [mem 0x01000000-0x1fffffff]
  HighMem  empty
Movable zone start for each node
Early memory node ranges
  node   0: [mem 0x00010000-0x0009ffff]
  node   0: [mem 0x00100000-0x1fffffff]
Using APIC driver default
smpboot: Allowing 4 CPUs, 0 hotplug CPUs
Local APIC disabled by BIOS -- you can enable it with "lapic"
APIC: disable apic facility
APIC: switched to apic NOOP
e820: [mem 0xdfa00000-0xf7ffffff] available for PCI devices
Booting paravirtualized kernel on Xen
Xen version: 4.2.2 (preserve-AD)
setup_percpu: NR_CPUS:4 nr_cpumask_bits:4 nr_cpu_ids:4 nr_node_ids:1
PERCPU: Embedded 12 pages/cpu @dfbb4000 s27904 r0 d21248 u49152
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 129936
Kernel command line: root=/dev/xvda1 rootfstype=ext4 rootfsflags=barrier=0 console=hvc0 xencons=hvc xen-fbfront.video=6,1024,768 xenfb.video=6,1024,768 noirqdebug elevator=noop cifs.enable_oplocks=0 earlyprintk=xen
IRQ lockup detection disabled
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
__ex_table already sorted, skipping sort
Initializing CPU#0
xsave: enabled xstate_bv 0x7, cntxt size 0x340
Initializing HighMem for node 0 (00000000:00000000)
Memory: 510932k/524288k available (4323k kernel code, 12908k reserved, 1293k data, 412k init, 0k highmem)
virtual kernel memory layout:
    fixmap  : 0xf5765000 - 0xf57ff000   ( 616 kB)
    pkmap   : 0xf5400000 - 0xf5600000   (2048 kB)
    vmalloc : 0xe0800000 - 0xf53fe000   ( 331 MB)
    lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
      .init : 0xc157d000 - 0xc15e4000   ( 412 kB)
      .data : 0xc1438cdf - 0xc157c440   (1293 kB)
      .text : 0xc1000000 - 0xc1438cdf   (4323 kB)
SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:2304 nr_irqs:304 16
Console: colour dummy device 80x25
console [tty0] enabled
console [hvc0] enabled, bootconsole disabled

[-- Attachment #3: xl_dmesg_2048 --]
[-- Type: application/octet-stream, Size: 3796 bytes --]

mapping kernel into physical memory
about to get started...
Reserving virtual address space above 0xf5800000
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 3.8.13-gentoo (root@nodi) (gcc version 4.7.3 (Gentoo 4.7.3 p1.0, pie-0.5.5) ) #1 SMP Sat May 25 10:59:04 CEST 2013
ACPI in unprivileged domain disabled
Freeing 20000-80000 pfn range: 393216 pages freed
Released 393216 pages of unused memory
Set 917504 page(s) to 1-1 mapping
Populating 100000-160000 pfn range: 393216 pages added
e820: BIOS-provided physical RAM map:
Xen: [mem 0x0000000000000000-0x000000000009ffff] usable
Xen: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Xen: [mem 0x0000000000100000-0x000000001fffffff] usable
Xen: [mem 0x0000000020000000-0x00000000201fffff] reserved
Xen: [mem 0x0000000020200000-0x0000000040003fff] unusable
Xen: [mem 0x0000000040004000-0x0000000040004fff] reserved
Xen: [mem 0x0000000040005000-0x00000000d9cbefff] unusable
Xen: [mem 0x00000000d9cbf000-0x00000000da285fff] reserved
Xen: [mem 0x00000000da286000-0x00000000da505fff] ACPI NVS
Xen: [mem 0x00000000da506000-0x00000000da50afff] ACPI data
Xen: [mem 0x00000000da50b000-0x00000000da54dfff] ACPI NVS
Xen: [mem 0x00000000da54e000-0x00000000dad55fff] unusable
Xen: [mem 0x00000000dad56000-0x00000000daff1fff] reserved
Xen: [mem 0x00000000daff2000-0x00000000daffffff] unusable
Xen: [mem 0x00000000db800000-0x00000000df9fffff] reserved
Xen: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Xen: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Xen: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Xen: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Xen: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Xen: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Xen: [mem 0x0000000100000000-0x000000015fffffff] usable
bootconsole [xenboot0] enabled
NX (Execute Disable) protection: active
DMI not present or invalid.
e820: last_pfn = 0x160000 max_arch_pfn = 0x1000000
init_memory_mapping: [mem 0x00000000-0x2d3fdfff]
(XEN) mm.c:864:d6 Non-privileged (6) attempt to map I/O space 00020000
(XEN) mm.c:5317:d6 ptwr_emulate: could not get_page_from_l1e()
BUG: unable to handle kernel NULL pointer dereference at   (null)
IP: [<c157fe96>] xen_set_pte_init+0x3b/0x43
*pdpt = 0000000000000000 *pde = c2c2c2c2c2c2c2c2 
Oops: 0003 [#1] SMP 
Modules linked in:
Pid: 0, comm: swapper Not tainted 3.8.13-gentoo #1  
EIP: e019:[<c157fe96>] EFLAGS: 00010046 CPU: 0
EIP is at xen_set_pte_init+0x3b/0x43
EAX: c2380000 EBX: 00000000 ECX: 20000403 EDX: 20000403
ESI: 00020001 EDI: 00000000 EBP: 20000403 ESP: c1545e18
 DS: e021 ES: e021 FS: 00d8 GS: 00e0 SS: e021
CR0: 80050033 CR2: 00000000 CR3: 015ec000 CR4: 00002660
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
Process swapper (pid: 0, ti=c1544000 task=c1550120 task.ti=c1544000)
Stack:
 00000000 20000403 00000000 00020000 e0000000 c158f111 00000000 00000000
 c15ec018 00000003 c15ec018 00000003 20000000 00000000 0002d3fe c1668800
 00000100 c2380000 00000001 00000000 fffe0000 0016d000 00000001 c1545eb8
Call Trace:
 [<c158f111>] ? kernel_physical_mapping_init+0x1cc/0x2a5
 [<c14211d9>] ? init_memory_mapping+0x1f9/0x4f0
 [<c158204d>] ? setup_arch+0x764/0xa37
 [<c1431bd5>] ? printk+0x37/0x3b
 [<c157d6de>] ? start_kernel+0xbb/0x31b
 [<c157f269>] ? xen_start_kernel+0x650/0x65a
 [<c140905e>] ? sctp_assoc_rm_peer+0xde/0x200
Code: 81 e6 00 f0 ff ff 0f ac fe 0c 53 31 db 89 0c 24 31 c9 46 74 13 8b 08 f6 c1 01 74 07 89 ca 83 ca fd 21 ea 8b 1c 24 89 d1 89 58 04 <89> 08 58 5b 5e 5f 5d c3 50 e8 ba f6 00 00 e8 77 38 a8 ff a1 44
EIP: [<c157fe96>] xen_set_pte_init+0x3b/0x43 SS:ESP e021:c1545e18
CR2: 0000000000000000
---[ end trace a7919e7f17c0a725 ]---
Kernel panic - not syncing: Attempted to kill the idle task!

[-- Attachment #4: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [Xen-users] DomU sees only 512MB RAM with PCI-passthrough
  2013-05-26 10:59                         ` Christian Holpert
@ 2013-05-28 19:38                           ` Konrad Rzeszutek Wilk
  2013-05-29 12:08                             ` Christian Holpert
  2013-05-28 19:45                           ` Konrad Rzeszutek Wilk
  1 sibling, 1 reply; 9+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-05-28 19:38 UTC (permalink / raw)
  To: Christian Holpert; +Cc: xen-devel

On Sun, May 26, 2013 at 12:59:56PM +0200, Christian Holpert wrote:
> At 20:31 25.05.2013, Konrad Rzeszutek Wilk wrote:
> >For the earlyprintk=xen just add it along with the xencons_...
> 
> I needed to recompile xen first with debug flag set. Now I get
> results from earlyprintk.
> 
> Please find attached:
> xl_dmesg_512:  domU (32bit) booting fine with memory = 512
> xl_dmesg_2048: domU (32bit) silently crashing with memory = 2048
> Both tests with your patch active and no other changes in between.

Is your kernel compiled with CONFIG_NUMA ? can you try without it?

> 
> Log shows
> BUG: unable to handle kernel NULL pointer dereference at   (null)
> and oopses out.
> 
> xl list does not show the process. ps shows that the corresponding
> qemu-system-i386 process is still alive and has to be killed
> manually.
> 
> Thanks for working on this and enjoy your weekend,
> Christian
> 
> -- 
> Markt-Apotheke Christian Holpert e.K., Mömbris
>   http://www.marktapotheke.org - info@marktapotheke.org
>   http://www.blue-essentials-shop.de - info@blue-essentials-shop.de
>   Apotheker Christian Holpert
> Im Markthof 5
> 63776 Mömbris
>   Tel.: 06029-1379 Fax: 9986589
> 
> Amtsgericht Aschaffenburg, HR.A, Registernummer 2165

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [Xen-users] DomU sees only 512MB RAM with PCI-passthrough
  2013-05-28 19:38                           ` Konrad Rzeszutek Wilk
@ 2013-05-29 12:08                             ` Christian Holpert
  0 siblings, 0 replies; 9+ messages in thread
From: Christian Holpert @ 2013-05-29 12:08 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk; +Cc: xen-devel

At 21:38 28.05.2013, Konrad Rzeszutek Wilk wrote:
>On Sun, May 26, 2013 at 12:59:56PM +0200, Christian Holpert wrote:
> > Please find attached:
> > xl_dmesg_512:  domU (32bit) booting fine with memory = 512
> > xl_dmesg_2048: domU (32bit) silently crashing with memory = 2048
> > Both tests with your patch active and no other changes in between.
>
>Is your kernel compiled with CONFIG_NUMA ? can you try without it?

Dom0 is compiled with NUMA.
xen ~ # zgrep CONFIG_NUMA  /proc/config.gz
CONFIG_NUMA_BALANCING_DEFAULT_ENABLED=y
CONFIG_NUMA_BALANCING=y
CONFIG_NUMA=y
# CONFIG_NUMA_EMU is not set
xen ~ #

DomU is compiled without NUMA.
nodi ~ # zgrep CONFIG_NUMA  /proc/config.gz
nodi ~ #

Will try 3.10 as soon as possible.

Regards,
Christian

-- 
Markt-Apotheke Christian Holpert e.K., Mömbris
   http://www.marktapotheke.org - info@marktapotheke.org
   http://www.blue-essentials-shop.de - info@blue-essentials-shop.de
   Apotheker Christian Holpert
Im Markthof 5
63776 Mömbris
   Tel.: 06029-1379 Fax: 9986589

Amtsgericht Aschaffenburg, HR.A, Registernummer 2165

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [Xen-users] DomU sees only 512MB RAM with PCI-passthrough
  2013-05-26 10:59                         ` Christian Holpert
  2013-05-28 19:38                           ` Konrad Rzeszutek Wilk
@ 2013-05-28 19:45                           ` Konrad Rzeszutek Wilk
  2013-05-29 15:23                             ` Christian Holpert
  1 sibling, 1 reply; 9+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-05-28 19:45 UTC (permalink / raw)
  To: Christian Holpert; +Cc: xen-devel

On Sun, May 26, 2013 at 12:59:56PM +0200, Christian Holpert wrote:
> At 20:31 25.05.2013, Konrad Rzeszutek Wilk wrote:
> >For the earlyprintk=xen just add it along with the xencons_...
> 
> I needed to recompile xen first with debug flag set. Now I get
> results from earlyprintk.
> 
> Please find attached:
> xl_dmesg_512:  domU (32bit) booting fine with memory = 512
> xl_dmesg_2048: domU (32bit) silently crashing with memory = 2048
> Both tests with your patch active and no other changes in between.

So with a 2048 guest it boots for me. Here is the diff between your
kernel and mine:


Reserving virtual address space above 0xf5800000		Reserving virtual address space above 0xf5800000
Initializing cgroup subsys cpuset				Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu					Initializing cgroup subsys cpu
Linux version 3.8.13-gentoo (root@nodi) (gcc version 4.7.3 (G |	Initializing cgroup subsys cpuacct
							      >	Linux version 3.10.0-rc3upstream-00894-g597e694 (konrad@build
ACPI in unprivileged domain disabled				ACPI in unprivileged domain disabled
Freeing 20000-80000 pfn range: 393216 pages freed		Freeing 20000-80000 pfn range: 393216 pages freed
Released 393216 pages of unused memory				Released 393216 pages of unused memory
Set 917504 page(s) to 1-1 mapping				Set 917504 page(s) to 1-1 mapping
Populating 100000-160000 pfn range: 393216 pages added		Populating 100000-160000 pfn range: 393216 pages added
e820: BIOS-provided physical RAM map:				e820: BIOS-provided physical RAM map:
Xen: [mem 0x0000000000000000-0x000000000009ffff] usable		Xen: [mem 0x0000000000000000-0x000000000009ffff] usable
Xen: [mem 0x00000000000a0000-0x00000000000fffff] reserved	Xen: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Xen: [mem 0x0000000000100000-0x000000001fffffff] usable		Xen: [mem 0x0000000000100000-0x000000001fffffff] usable
Xen: [mem 0x0000000020000000-0x00000000201fffff] reserved	Xen: [mem 0x0000000020000000-0x00000000201fffff] reserved
Xen: [mem 0x0000000020200000-0x0000000040003fff] unusable     |	Xen: [mem 0x0000000020200000-0x000000003fffffff] unusable
Xen: [mem 0x0000000040004000-0x0000000040004fff] reserved     |	Xen: [mem 0x0000000040000000-0x00000000401fffff] reserved
Xen: [mem 0x0000000040005000-0x00000000d9cbefff] unusable     |	Xen: [mem 0x0000000040200000-0x00000000c6cd3fff] unusable
Xen: [mem 0x00000000d9cbf000-0x00000000da285fff] reserved     |	Xen: [mem 0x00000000c6cd4000-0x00000000c6d1cfff] ACPI NVS
Xen: [mem 0x00000000da286000-0x00000000da505fff] ACPI NVS     |	Xen: [mem 0x00000000c6d1d000-0x00000000c6d27fff] ACPI data
Xen: [mem 0x00000000da506000-0x00000000da50afff] ACPI data    |	Xen: [mem 0x00000000c6d28000-0x00000000c6d28fff] ACPI NVS
Xen: [mem 0x00000000da50b000-0x00000000da54dfff] ACPI NVS     |	Xen: [mem 0x00000000c6d29000-0x00000000c6d49fff] reserved
Xen: [mem 0x00000000da54e000-0x00000000dad55fff] unusable     |	Xen: [mem 0x00000000c6d4a000-0x00000000c6d4bfff] unusable
Xen: [mem 0x00000000dad56000-0x00000000daff1fff] reserved     |	Xen: [mem 0x00000000c6d4c000-0x00000000c6d6cfff] ACPI NVS
Xen: [mem 0x00000000daff2000-0x00000000daffffff] unusable     |	Xen: [mem 0x00000000c6d6d000-0x00000000c6d8ffff] reserved
Xen: [mem 0x00000000db800000-0x00000000df9fffff] reserved     |	Xen: [mem 0x00000000c6d90000-0x00000000c6d9cfff] ACPI NVS
Xen: [mem 0x00000000f8000000-0x00000000fbffffff] reserved     |	Xen: [mem 0x00000000c6d9d000-0x00000000c6d9ffff] reserved
Xen: [mem 0x00000000fec00000-0x00000000fec00fff] reserved     |	Xen: [mem 0x00000000c6da0000-0x00000000c6db0fff] ACPI NVS
Xen: [mem 0x00000000fed00000-0x00000000fed03fff] reserved     |	Xen: [mem 0x00000000c6db1000-0x00000000c6ddcfff] reserved
Xen: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved     |	Xen: [mem 0x00000000c6ddd000-0x00000000c6e1ffff] ACPI NVS
							      >	Xen: [mem 0x00000000c6e20000-0x00000000c6ffffff] unusable
							      >	Xen: [mem 0x00000000c7800000-0x00000000cf9fffff] reserved
							      >	Xen: [mem 0x00000000fed1c000-0x00000000fed3ffff] reserved
Xen: [mem 0x00000000fee00000-0x00000000fee00fff] reserved	Xen: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Xen: [mem 0x00000000ff000000-0x00000000ffffffff] reserved	Xen: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Xen: [mem 0x0000000100000000-0x000000015fffffff] usable		Xen: [mem 0x0000000100000000-0x000000015fffffff] usable
bootconsole [xenboot0] enabled				      <
NX (Execute Disable) protection: active				NX (Execute Disable) protection: active
DMI not present or invalid.					DMI not present or invalid.
e820: last_pfn = 0x160000 max_arch_pfn = 0x1000000		e820: last_pfn = 0x160000 max_arch_pfn = 0x1000000
init_memory_mapping: [mem 0x00000000-0x2d3fdfff]	      |	Scanning 1 areas for low memory corruption
(XEN) mm.c:864:d6 Non-privileged (6) attempt to map I/O space |	init_memory_mapping: [mem 0x00000000-0x000fffff]
(XEN) mm.c:5317:d6 ptwr_emulate: could not get_page_from_l1e( |	init_memory_mapping: [mem 0x1fe00000-0x1fffffff]
BUG: unable to handle kernel NULL pointer dereference at   (n |	init_memory_mapping: [mem 0x1c000000-0x1fdfffff]
IP: [<c157fe96>] xen_set_pte_init+0x3b/0x43		      |	init_memory_mapping: [mem 0x00100000-0x1bffffff]
*pdpt = 0000000000000000 *pde = c2c2c2c2c2c2c2c2 	      |	RAMDISK: [mem 0x01b51000-0x107b0fff]
Oops: 0003 [#1] SMP 					      |	4908MB HIGHMEM available.
Modules linked in:					      |	723MB LOWMEM available.
Pid: 0, comm: swapper Not tainted 3.8.13-gentoo #1  	      |	  mapped low ram: 0 - 20000000
EIP: e019:[<c157fe96>] EFLAGS: 00010046 CPU: 0		      |	  low ram: 0 - 2d3fe000
EIP is at xen_set_pte_init+0x3b/0x43			      |	Zone ranges:
EAX: c2380000 EBX: 00000000 ECX: 20000403 EDX: 20000403	      |	  DMA      [mem 0x00001000-0x00ffffff]
ESI: 00020001 EDI: 00000000 EBP: 20000403 ESP: c1545e18	      |	  Normal   [mem 0x01000000-0x2d3fdfff]
 DS: e021 ES: e021 FS: 00d8 GS: 00e0 SS: e021		      |	  HighMem  [mem 0x2d3fe000-0x5fffffff]
CR0: 80050033 CR2: 00000000 CR3: 015ec000 CR4: 00002660	      |	Movable zone start for each node
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000	      |	Early memory node ranges
DR6: ffff0ff0 DR7: 00000400				      |	  node   0: [mem 0x00001000-0x0009ffff]
Process swapper (pid: 0, ti=c1544000 task=c1550120 task.ti=c1 |	  node   0: [mem 0x00100000-0x1fffffff]
Stack:							      |	  node   0: [mem 0x00000000-0x5fffffff]
 00000000 20000403 00000000 00020000 e0000000 c158f111 000000 |	Using APIC driver default
 c15ec018 00000003 c15ec018 00000003 20000000 00000000 0002d3 |	smpboot: Allowing 4 CPUs, 0 hotplug CPUs
 00000100 c2380000 00000001 00000000 fffe0000 0016d000 000000 |	Local APIC disabled by BIOS -- you can enable it with "lapic"
Call Trace:						      |	APIC: disable apic facility
 [<c158f111>] ? kernel_physical_mapping_init+0x1cc/0x2a5      |	APIC: switched to apic NOOP
 [<c14211d9>] ? init_memory_mapping+0x1f9/0x4f0		      |	PM: Registered nosave memory: 00000000000a0000 - 000000000010
 [<c158204d>] ? setup_arch+0x764/0xa37			      |	PM: Registered nosave memory: 0000000020000000 - 000000002020
 [<c1431bd5>] ? printk+0x37/0x3b			      |	PM: Registered nosave memory: 0000000020200000 - 000000004000
 [<c157d6de>] ? start_kernel+0xbb/0x31b			      |	e820: [mem 0xcfa00000-0xfed1bfff] available for PCI devices
 [<c157f269>] ? xen_start_kernel+0x650/0x65a		      |	Booting paravirtualized kernel on Xen
 [<c140905e>] ? sctp_assoc_rm_peer+0xde/0x200		      |	Xen version: 4.3-unstable (preserve-AD)
Code: 81 e6 00 f0 ff ff 0f ac fe 0c 53 31 db 89 0c 24 31 c9 4 |	setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:4 nr_nod
EIP: [<c157fe96>] xen_set_pte_init+0x3b/0x43 SS:ESP e021:c154 |	PERCPU: Embedded 14 pages/cpu @dd343000 s35520 r0 d21824 u573
CR2: 0000000000000000					      |	Built 1 zonelists in Zone order, mobility grouping on.  Total
---[ end trace a7919e7f17c0a725 ]---			      |	Kernel command line: console=hvc0
Kernel panic - not syncing: Attempted to kill the idle task!  |	PID hash table entries: 2048 (order: 1, 8192 bytes)
							      >	Dentry cache hash table entries: 65536 (order: 6, 262144 byte
							      >	Inode-cache hash table entries: 32768 (order: 5, 131072 bytes
							      >	Initializing CPU#0
							      >	xsave: enabled xstate_bv 0x7, cntxt size 0x340
							      >	Initializing HighMem for node 0 (0002d3fe:00160000)
							      >	Memory: 1796596k/5767168k available (5818k kernel code, 30016
							      >	virtual kernel memory layout:


Can you try the v3.10 or v3.9 and see how it works for you?

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [Xen-users] DomU sees only 512MB RAM with PCI-passthrough
  2013-05-28 19:45                           ` Konrad Rzeszutek Wilk
@ 2013-05-29 15:23                             ` Christian Holpert
  2013-05-29 17:05                               ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 9+ messages in thread
From: Christian Holpert @ 2013-05-29 15:23 UTC (permalink / raw)
  To: Konrad Rzeszutek Wilk; +Cc: xen-devel

---- Original-Nachricht ----
   Von: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
   Datum: Mittwoch, 29. Mai 2013 17:02:32
> So with a 2048 guest it boots for me. Here is the diff between your 
> kernel and mine:
>
> Can you try the v3.10 or v3.9 and see how it works for you?
Tried out v3.10-rc3 and can confirm that your patch works.

DomU boots up fine with 2048MB.

I did 'make oldconfig' with the old .config. Answered all those 
questions about new options and built the kernel. So there shouldn't be 
too many questions between the configs.

Thanks a lot,
Christian Holpert

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [Xen-users] DomU sees only 512MB RAM with PCI-passthrough
  2013-05-29 15:23                             ` Christian Holpert
@ 2013-05-29 17:05                               ` Konrad Rzeszutek Wilk
  0 siblings, 0 replies; 9+ messages in thread
From: Konrad Rzeszutek Wilk @ 2013-05-29 17:05 UTC (permalink / raw)
  To: Christian Holpert; +Cc: xen-devel

On Wed, May 29, 2013 at 05:23:42PM +0200, Christian Holpert wrote:
> ---- Original-Nachricht ----
>   Von: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>   Datum: Mittwoch, 29. Mai 2013 17:02:32
> >So with a 2048 guest it boots for me. Here is the diff between
> >your kernel and mine:
> >
> >Can you try the v3.10 or v3.9 and see how it works for you?
> Tried out v3.10-rc3 and can confirm that your patch works.

Great! So something is off with v3.8 kernel. The hint seems
to be:

Populating 100000-160000 pfn range: 393216 pages added		Populating 100000-160000 pfn range: 393216 pages added
..
Xen: [mem 0x0000000100000000-0x000000015fffffff] usable		Xen: [mem 0x0000000100000000-0x000000015fffffff] usable
bootconsole [xenboot0] enabled				      <
NX (Execute Disable) protection: active				NX (Execute Disable) protection: active
DMI not present or invalid.					DMI not present or invalid.
e820: last_pfn = 0x160000 max_arch_pfn = 0x1000000		e820: last_pfn = 0x160000 max_arch_pfn = 0x1000000
init_memory_mapping: [mem 0x00000000-0x2d3fdfff]	      |	Scanning 1 areas for low memory corruption
(XEN) mm.c:864:d6 Non-privileged (6) attempt to map I/O space |	init_memory_mapping: [mem 0x00000000-0x000fffff]
(XEN) mm.c:5317:d6 ptwr_emulate: could not get_page_from_l1e( |	init_memory_mapping: [mem 0x1fe00000-0x1fffffff]
BUG: unable to handle kernel NULL pointer dereference at   (n |	init_memory_mapping: [mem 0x1c000000-0x1fdfffff]
IP: [<c157fe96>] xen_set_pte_init+0x3b/0x43		      |	init_memory_mapping: [mem 0x00100000-0x1bffffff]
*pdpt = 0000000000000000 *pde = c2c2c2c2c2c2c2c2 	      |	RAMDISK: [mem 0x01b51000-0x107b0fff]

That v3.8 is trying to allocate pages up to 2d3fdfff. Which we don't in v3.10.

But we do seem to use said area for HighMem (0x2d3fe000-0x5fffffff) which
works in v3.10.

Oops: 0003 [#1] SMP 					      |	4908MB HIGHMEM available.
Modules linked in:					      |	723MB LOWMEM available.
Pid: 0, comm: swapper Not tainted 3.8.13-gentoo #1  	      |	  mapped low ram: 0 - 20000000
EIP: e019:[<c157fe96>] EFLAGS: 00010046 CPU: 0		      |	  low ram: 0 - 2d3fe000
EIP is at xen_set_pte_init+0x3b/0x43			      |	Zone ranges:
EAX: c2380000 EBX: 00000000 ECX: 20000403 EDX: 20000403	      |	  DMA      [mem 0x00001000-0x00ffffff]
ESI: 00020001 EDI: 00000000 EBP: 20000403 ESP: c1545e18	      |	  Normal   [mem 0x01000000-0x2d3fdfff]
 DS: e021 ES: e021 FS: 00d8 GS: 00e0 SS: e021		      |	  HighMem  [mem 0x2d3fe000-0x5fffffff]
CR0: 80050033 CR2: 00000000 CR3: 015ec000 CR4: 00002660	      |	Movable zone start for each node
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000	      |	Early memory node ranges
DR6: ffff0ff0 DR7: 00000400				      |	  node   0: [mem 0x00001000-0x0009ffff]
Process swapper (pid: 0, ti=c1544000 task=c1550120 task.ti=c1 |	  node   0: [mem 0x00100000-0x1fffffff]
Stack:							      |	  node   0: [mem 0x00000000-0x5fffffff]
 00000000 20000403 00000000 00020000 e0000000 c158f111 000000 |	Using APIC driver default
 c15ec018 00000003 c15ec018 00000003 20000000 00000000 0002d3 |	smpboot: Allowing 4 CPUs, 0 hotplug CPUs
 00000100 c2380000 00000001 00000000 fffe0000 0016d000 000000 |	Local APIC disabled by BIOS -- you can enable it with "lapic"
Call Trace:						      |	APIC: disable apic facility

Would need to dig in this deeper, but that looks to be
an issue with the kernel, not with the toolstack.

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2013-05-29 17:05 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <50C9C725.9060809@citrix.com>
     [not found] ` <20121219173838.GC25471@phenom.dumpdata.com>
     [not found]   ` <E1TlR48-0008MI-N7@smtprelay05.ispgateway.de>
     [not found]     ` <20121219222624.GA12842@phenom.dumpdata.com>
     [not found]       ` <E1TlfQZ-0004aC-6k@smtprelay03.ispgateway.de>
     [not found]         ` <20130522210618.GA13319@phenom.dumpdata.com>
     [not found]           ` <20130522211537.GA13471@phenom.dumpdata.com>
     [not found]             ` <20130522211752.GB13471@phenom.dumpdata.com>
     [not found]               ` <20130524133859.GA3665@phenom.dumpdata.com>
     [not found]                 ` <519F89BB.3020709@holpert.de>
2013-05-25 11:13                   ` [Xen-users] DomU sees only 512MB RAM with PCI-passthrough Konrad Rzeszutek Wilk
2013-05-25 15:18                     ` Christian Holpert
2013-05-25 18:31                       ` Konrad Rzeszutek Wilk
2013-05-26 10:59                         ` Christian Holpert
2013-05-28 19:38                           ` Konrad Rzeszutek Wilk
2013-05-29 12:08                             ` Christian Holpert
2013-05-28 19:45                           ` Konrad Rzeszutek Wilk
2013-05-29 15:23                             ` Christian Holpert
2013-05-29 17:05                               ` Konrad Rzeszutek Wilk

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.