Displaying 7 results from an estimated 7 matches for "domainbuilder".
2012 Nov 25
2
Cannot open root device xvda1 or unknown-block(0,0)
...and three DomU (all Gentoo) with kernel 3.5.7 and
Xen 4.1.1. Each Dom has it''s own md (md0 for Dom0, md1 for Dom1 etc). Dom0
works fine so far, however, I''m stuck trying to create DomUs. It appears the
xvda1 device on DomU is not created or accessible:
Parsing config file dom1
domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/xvda1 console=hvc0
root=/dev/xvda1 ro 3", features="(null)"
domainbuilder: detail: xc_dom_kernel_mem: called
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.1, caps xen-3.0-x86_64
xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-...
2012 Jun 08
3
cannot boot guest VM
...backend: Disk vdev=xvda, backend phy unsuitable as phys path not a block device
libxl: debug: libxl_device.c:144:disk_try_backend: Disk vdev=xvda, backend tap unsuitable because blktap not available
libxl: debug: libxl_device.c:219:libxl__device_disk_set_backend: Disk vdev=xvda, using backend qdisk
domainbuilder: detail: xc_dom_allocate: cmdline="debian-installer/exit/always_halt=true -- console=hvc0", features="(null)"
domainbuilder: detail: xc_dom_kernel_file: filename="vmlinuz-2.6.32-5-amd64"
domainbuilder: detail: xc_dom_malloc_filemap : 2367 kB
domainbuilder: detail: x...
2013 Oct 08
10
xl console regression on xen-unstable
I''m unable to start xl console on latest xen-unstable (build with commit
8e0da8c07f4f80e14314977a11f738bd74a5b62b).
> xl -vvv console sid
> xenconsole: Could not read tty from store: No such file or directory
I also tried "xl create -c", and it shows console from pygrub but when
the "xl create" reaches the end I got the same error:
> xenconsole: Could not
2012 Apr 24
21
no console when using xl toolstack xen 4.1.2
...pts/3
xs_read(): target get error. /local/domain/2/target.
Key lost : keysym=0xffe7(65511)
Key lost : keysym=0xffe7(65511)
__END__
Here''s running xl create on domutest with the -v option:
__START__
[root@xentest2012 noauto]# xl -v create -c domutest.cfg
Parsing config file domutest.cfg
domainbuilder: detail: xc_dom_allocate: cmdline="(hd0)/boot/grub/menu.lst", features="(null)"
domainbuilder: detail: xc_dom_kernel_file: filename="/usr/lib/xen/boot/pv-grub-x86_64.gz"
domainbuilder: detail: xc_dom_malloc_filemap : 1130 kB
domainbuilder: detail: xc_dom_malloc...
2013 Apr 24
15
Bare-metal Xen on ARM boot
Hi,
I was wondering if there is any documentation on how to write a bare metal
application for Xen. I don''t need to parse the device tree and such yet, a
simple booting "Hello World" would be fine :-)
We wrote one and when trying to boot we get ( this was an uncompressed
binary, no image):
libxl: notice: libxl_numa.c:451:libxl__get_numa_candidate: NUMA placement
failed,
2015 Oct 01
5
xen and spice problem
...0007f000000
xc: detail: ENTRY: 0000000000100610
xc: detail: PHYSICAL MEMORY ALLOCATION:
xc: detail: 4KB PAGES: 0x0000000000000200
xc: detail: 2MB PAGES: 0x00000000000003f7
xc: detail: 1GB PAGES: 0x0000000000000000
xc: detail: elf_load_binary: phdr 0 at 0x7fab7190a000 -> 0x7fab719bb151
domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0xff000
libxl: error: libxl_dm.c:1849:device_model_spawn_outcome: domain 29
device model: spawn failed (rc=-3)
libxl: error: libxl_create.c:1340:domcreate_devmodel_started: device
model did not start: -3
libxl: error: libxl_dm.c:1959:kill_device_model:...
2015 Oct 01
0
xen and spice problem
...Y: 0000000000100610
> xc: detail: PHYSICAL MEMORY ALLOCATION:
> xc: detail: 4KB PAGES: 0x0000000000000200
> xc: detail: 2MB PAGES: 0x00000000000003f7
> xc: detail: 1GB PAGES: 0x0000000000000000
> xc: detail: elf_load_binary: phdr 0 at 0x7fab7190a000 -> 0x7fab719bb151
> domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0xff000
> libxl: error: libxl_dm.c:1849:device_model_spawn_outcome: domain 29 device
> model: spawn failed (rc=-3)
> libxl: error: libxl_create.c:1340:domcreate_devmodel_started: device model
> did not start: -3
> libxl: error: libxl_dm.c:...