|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] no console when using xl toolstack xen 4.1.2
Hello!
I was asking for help on the Freenode channel, and I was pointed here.
I have a situation where, using xl, I can create a functional PV domU, with or
without pv-grub, but I cannot access the console. Firing up xend and using xm
works without trouble. Since xend and company is being deprecated, I would
like to transition to using the xl toolstack.
The system is an Arch Linux system running under VMWare Fusion-- I normally
build and test packages this way before I test them on my dev hardware as my
dev hardware is a rather loud HP server. I'm compiling Xen in a package,
based off of the one in AUR but with some changes (the AUR package doesn't
compile pv-grub, for instance). It's Xen 4.1.2, and my linux kernel is the
standard Arch Linux kernel version 3.3.2, and it is very near the stock
kernel. Clearly, I have done no HVM testing yet.
Here's what it looks like when I try xl:
__START__
[root@xentest2012 noauto]# xl create -c finnix.cfg
Parsing config file finnix.cfg
Unable to attach console
Daemon running with PID 851
[root@xentest2012 noauto]# xl console finnix
Unable to attach console
[root@xentest2012 noauto]# ls
domutest.cfg finnix.cfg
[root@xentest2012 noauto]# xl create -c domutest.cfg
Parsing config file domutest.cfg
xc: error: panic: xc_dom_bzimageloader.c:556: xc_dom_probe_bzimage_kernel:
kernel is not a bzImage: Invalid kernel
Unable to attach console
Daemon running with PID 916
[root@xentest2012 noauto]# xl console domutest
Unable to attach console
[root@xentest2012 noauto]#
__END__
Firing up xend, it works just as you would expect.
Here are the configuration files:
finnix.cfg:
__START__
kernel = "/var/finnix/linux64"
ramdisk = "/var/finnix/initrd.xz"
name = "finnix"
memory = "128"
disk = [ 'file:/var/finnix/finnix-104.iso,xvda,r', ]
vif = [ 'bridge=outer0', ]
__END__
domutest.cfg:
__START__
kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
extra = "(hd0)/boot/grub/menu.lst"
memory = 512
vcpus = 4
name = "domutest"
disk = [ "phy:/dev/xtG0/domutest-root,xvda1,w",
"phy:/dev/xtG0/domutest-swap,xvda2,w" ]
vif = [ "bridge=outer0" ]
vfb = [ "type=vnc,vnclisten=0.0.0.0,vncdisplay=5,vncpasswd=smeghead" ]
__END__
I can see finnix ask for a DHCP address, and I can connect to domutest using
the VNC vfb and use it as normal, so I've concluded that the domUs are running.
And now for some other information:
xen-hotplug.log
__START__
RTNETLINK answers: Operation not supported
RTNETLINK answers: Operation not supported
__END__
qemu-dm-finnix.log
__START__
domid: 1
Warning: vlan 0 is not connected to host network
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
/home/sam/build/xen/src/xen-4.1.2/tools/ioemu-qemu-xen/hw/xen_blktap.c:628:
Init blktap pipes
/home/sam/build/xen/src/xen-4.1.2/tools/ioemu-qemu-xen/hw/xen_blktap.c:603:
Created /var/run/tap directory
Could not open /var/run/tap/qemu-read-1
char device redirected to /dev/pts/2
xs_read(): target get error. /local/domain/1/target.
(qemu) (qemu)
__END__
qemu-dm-domutest.log
__START__
domid: 2
Warning: vlan 0 is not connected to host network
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
/home/sam/build/xen/src/xen-4.1.2/tools/ioemu-qemu-xen/hw/xen_blktap.c:628:
Init blktap pipes
Could not open /var/run/tap/qemu-read-2
char device redirected to /dev/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 : 14779 kB
domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x11a833 -> 0xe6effa
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.1, caps xen-3.0-x86_64
xen-3.0-x86_32p
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 ...
xc: error: panic: xc_dom_bzimageloader.c:556: xc_dom_probe_bzimage_kernel:
kernel is not a bzImage: Invalid kerne
l
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=0x0 memsz=0x99ff60
xc: detail: elf_parse_binary: memory: 0x0 -> 0x99ff60
xc: detail: elf_xen_parse: __xen_guest:
"GUEST_OS=Mini-OS,XEN_VER=xen-3.0,VIRT_BASE=0x0,ELF_PADDR_OFFSET=0x0,HYPE
RCALL_PAGE=0x2,LOADER=generic"
xc: detail: elf_xen_parse_guest_info: GUEST_OS="Mini-OS"
xc: detail: elf_xen_parse_guest_info: XEN_VER="xen-3.0"
xc: detail: elf_xen_parse_guest_info: VIRT_BASE="0x0"
xc: detail: elf_xen_parse_guest_info: ELF_PADDR_OFFSET="0x0"
xc: detail: elf_xen_parse_guest_info: HYPERCALL_PAGE="0x2"
xc: detail: elf_xen_parse_guest_info: LOADER="generic"
xc: detail: elf_xen_addr_calc_check: addresses:
xc: detail: virt_base = 0x0
xc: detail: elf_paddr_offset = 0x0
xc: detail: virt_offset = 0x0
xc: detail: virt_kstart = 0x0
xc: detail: virt_kend = 0x99ff60
xc: detail: virt_entry = 0x0
xc: detail: p2m_base = 0xffffffffffffffff
domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64: 0x0 -> 0x99ff60
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_64, address size 64
domainbuilder: detail: xc_dom_malloc : 1024 kB
domainbuilder: detail: xc_dom_build_image: called
domainbuilder: detail: xc_dom_alloc_segment: kernel : 0x0 -> 0x9a0000
(pfn 0x0 + 0x9a0 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x0+0x9a0 at
0x7f18be2e9000
xc: detail: elf_load_binary: phdr 0 at 0x0x7f18be2e9000 -> 0x0x7f18bec88f60
domainbuilder: detail: xc_dom_alloc_segment: phys2mach : 0x9a0000 ->
0xaa0000 (pfn 0x9a0 + 0x100 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x9a0+0x100 at
0x7f18be1e9000
domainbuilder: detail: xc_dom_alloc_page : start info : 0xaa0000 (pfn
0xaa0)
domainbuilder: detail: xc_dom_alloc_page : xenstore : 0xaa1000 (pfn
0xaa1)
domainbuilder: detail: xc_dom_alloc_page : console : 0xaa2000 (pfn
0xaa2)
domainbuilder: detail: nr_page_tables: 0x0000ffffffffffff/48:
0x0000000000000000 -> 0x0000ffffffffffff, 1 table(s
)
domainbuilder: detail: nr_page_tables: 0x0000007fffffffff/39:
0x0000000000000000 -> 0x0000007fffffffff, 1 table(s
)
domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30:
0x0000000000000000 -> 0x000000003fffffff, 1 table(s
)
domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21:
0x0000000000000000 -> 0x0000000000bfffff, 6 table(s
)
domainbuilder: detail: xc_dom_alloc_segment: page tables : 0xaa3000 ->
0xaac000 (pfn 0xaa3 + 0x9 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0xaa3+0x9 at
0x7f18be1e0000
domainbuilder: detail: xc_dom_alloc_page : boot stack : 0xaac000 (pfn
0xaac)
domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0xaad000
domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0xc00000
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 <= matches
domainbuilder: detail: xc_dom_compat_check: supported guest type:
xen-3.0-x86_32p
domainbuilder: detail: xc_dom_update_guest_p2m: dst 64bit, pages 0x20000
domainbuilder: detail: clear_page: pfn 0xaa2, mfn 0x5dd0c
domainbuilder: detail: clear_page: pfn 0xaa1, mfn 0x5dd0d
domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0xaa0+0x1 at
0x7f18be1df000
domainbuilder: detail: start_info_x86_64: called
domainbuilder: detail: setup_hypercall_page: vaddr=0x2000 pfn=0x2
domainbuilder: detail: domain builder memory footprint
domainbuilder: detail: allocated
domainbuilder: detail: malloc : 15870 kB
domainbuilder: detail: anon mmap : 0 bytes
domainbuilder: detail: mapped
domainbuilder: detail: file mmap : 1130 kB
domainbuilder: detail: domU mmap : 10920 kB
domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn 0x587bb
domainbuilder: detail: shared_info_x86_64: called
domainbuilder: detail: vcpu_x86_64: called
domainbuilder: detail: vcpu_x86_64: cr3: pfn 0xaa3 mfn 0x5dd0b
domainbuilder: detail: launch_vm: called, ctxt=0x7fffa9ec8e90
domainbuilder: detail: xc_dom_release: called
Unable to attach console
Daemon running with PID 1395
__END__
And the output of xl info:
__START__
host : xentest2012
release : 3.3.2-1-ARCH
version : #1 SMP PREEMPT Sat Apr 14 09:48:37 CEST 2012
machine : x86_64
nr_cpus : 4
nr_nodes : 1
cores_per_socket : 1
threads_per_core : 1
cpu_mhz : 2403
hw_caps :
0febfbff:20100800:00000000:00000940:80002201:00000000:00000001:00000000
virt_caps :
total_memory : 2047
free_memory : 870
free_cpus : 0
xen_major : 4
xen_minor : 1
xen_extra : .2
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
xen_commandline : dom0_mem=512M loglvl=all guest_loglvl=all
com1=115200,8n1 console=com1
cc_compiler : gcc version 4.7.0 20120414 (prerelease) (GCC)
cc_compile_by : sam
cc_compile_domain : (none)
cc_compile_date : Sun Apr 22 19:02:17 PDT 2012
xend_config_format : 4
__END__
The xl logs have a single line in them:
xl-domutest.log:
Waiting for domain domutest (domid 6) to die [pid 1696]
xl-finnix.log :
Waiting for domain finnix (domid 7) to die [pid 1763]
That's what I've got. Any pointers would help. Thanks!
-Sam
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |