Xen project Mailing List

On Sat, Jan 18, 2014 at 12:28 AM, Richard Mortier <Richard.Mortier@xxxxxxxxxxxxxxxx> wrote:

having fixed the previous problem (with some assistance from dave :) i can now build a xen image but not successfully start it. this is true of my website and of mirage/lib_test/basic. i get the output appended below (trying to start the combinator example in mirage/mirage).

i'm not very familiar with interpreting these logs -- anyone any suggestions?

root@greyjay-xen:~/mirage/mirage/lib_test/combinator# xl -v create mux.xl -cd
Parsing config from mux.xl
{"domid":null,"config":{"c_info":{"type":"pv","hap":"<default>","oos":"<default>","ssidref":0,"name":"mux","uuid":"dd23d957-6739-4215-bba8-313c99f204b5","xsdata":{},"platformdata":{},"poolid":0,"run_hotplug_scripts":"True"},"b_info":{"max_vcpus":0,"avail_vcpus":[],"cpumap":[],"numa_placement":"<default>","tsc_mode":"default","max_memkb":262144,"target_memkb":262144,"video_memkb":-1,"shadow_memkb":2048,"rtc_timeoffset":0,"localtime":"<default>","disable_migrate":"<default>","cpuid":[],"blkdev_start":null,"device_model_version":null,"device_model_stubdomain":"<default>","device_model":null,"device_model_ssidref":0,"extra":[],"extra_pv":[],"extra_hvm":[],"sched_params":{"sched":"unknown","weight":-1,"cap":-1,"period":-1,"slice":-1,"latency":-1,"extratime":-1},"ioports":[],"irqs":[],"u":{"kernel":"/home/mort/mirage/mirage/lib_test/combinator/mir-mux.xen","slack_memkb":-1,"bootloader":null,"bootloader_args":[],"cmdline":"","ramdisk":null,"e820_host":"<default>"}},"disks":[],"nics":[],"pcidevs":[],"vfbs":[],"vkbs":[],"on_poweroff":"destroy","on_reboot":"restart","on_watchdog":"destroy","on_crash":"destroy"}}
libxl: detail: libxl_dom.c:193:numa_place_domain: NUMA placement candidate with 1 nodes, 1 cpus and 438 KB free selected

I notice "disks:[]" and "nics:[]" -- are you expecting a disk or network interface?

[ snipped domain building spam ]

domainbuilder: detail: launch_vm: called, ctxt=0x7fffa8c65820

It went up ...

domainbuilder: detail: xc_dom_release: called

... and down again

Daemon running with PID 16748
libxl: error: libxl_dom.c:35:libxl__domain_type: unable to get domain type for domid=10
Unable to attach console

When the VM dies early on, xenconsoled cleans up the console before 'xl' can attach to it. There might be some interesting text on there. You can see it by starting the VM paused:

xl create -c -p mux.xl

and, in another terminal, unpausing it

xl unpause mux

Cheers,

Dave

Re: [MirageOS-devel] xen issues