[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] [Xen-devel] Cannot Start Linux Paravirtualized (PV) Guests with Xen 4.2-unstable



On 20/03/2012 15:12, Ian Campbell wrote:
On Tue, 2012-03-20 at 01:11 +0000, Teo En Ming (Zhang Enming) wrote:
[...]
Please can you provide a single guest configuration file which
demonstrates the issue which you are seeing and the output of running
"xl -vvv create -c<cfg>" for that precisely that<cfg>   file. Please
also attach exactly the /var/log/xen/qemu-dm-<name>.log
and /var/log/xen/xl-<name>.log produced by exactly that invocation of
xl.
[...]
I will be attaching my How To / tutorial / documentation shortly.
Please provide exactly and only the information I asked for in my
previous mail (quoted above). Otherwise I cannot help you. I am not
going to try and infer the answers to those questions from a How To.

Ian.



Dear Ian,

As I told you before, I cannot start Linux PV guests in Xen 4.2-unstable. There is a bug with xl in Xen 4.2-unstable. However, I am able to start Fedora 16 amd64 PV domU in Xen 4.1.3-rc1-pre.

My F16 Linux PV guest configuration file is as follows:

=======================================================================================================================

# NOTE: Paravirtualized guests will only work with Xen 4.1.3-rc1-pre
# and NOT Xen 4.2-unstable changeset 25070.
#
# XL domain configuration file for Fedora 16 x86_64 PV domU
# Please refer to "man xl.cfg" for further explanations.
# See also docs/misc/xl-network-configuration.markdown and
# docs/misc/xl-disk-configuration.txt
# Written by Teo En Ming (Zhang Enming)
# Email #1: teo.en.ming@xxxxxxxxx
# Email #2: teo-en-ming@xxxxxxxxxxxxxxx
# Mobile Phone: +65-8369-2618
# Country: Singapore
# Date: 19 Mar 2012 Mon
name="Fedora16x86_64"
builder="generic"
vcpus=2
# Minimum memory of 768 MB is required to install Fedora 16 x86_64
#memory=768
memory=512
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
# Format compatible with Xen 4.2-unstable
#disk=[ 'format=raw, vdev=hda, access=rw, target=/etc/xen/images/fedora16x86_64.img' ]
# Format compatible with Xen 4.1.3-rc1-pre
disk=[ 'file:/etc/xen/images/fedora16x86_64.img,hda,w' ]
# Keywords type and model are reserved for HVM guests and NOT valid for PV guests
vif=[ 'bridge=virbr0' ]
# Virtual frame buffer parameter is for paravirtualized guests only.
vfb=[ 'vnc=1,vnclisten=localhost,vncdisplay=2,vncunused=1,vncpasswd=,sdl=0' ]
gfx_passthru=0
# Step 1
# To install Fedora 16 x86_64 PV domU, configure the kernel, ramdisk, and extra keys below and
comment out bootloader.
# Kernel image to boot
#kernel = "/home/teo-en-ming/vms/f16/vmlinuz"
# Ramdisk (optional)
#ramdisk = "/home/teo-en-ming/vms/f16/initrd.img"
# Kernel command line options
#extra = "root=/dev/xvda1"
# Step 2
# To boot the already installed Fedora 16 x86_64 PV domU, comment out the parameters in Step 1
and uncomment bootloader below.
bootloader="pygrub"

=============================================================================

The output of "sudo xl -vvv create -c Fedora16x86_64" is as follows:

=============================================================================

pyGRUB version 0.6
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
â Fedora Linux, with Linux 3.2.10-3.fc16.x86_64 â
â Fedora Linux, with Linux 3.2.10-3.fc16.x86_64 (recovery mode) â
â â
â â
â â
â â
â â
â â
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, 'e' to edit the
commands before booting, 'a' to modify the kernel arguments
before booting, or 'c' for a command line.




Will boot selected entry in 1 seconds


domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/mapper/vg_fedora16x8664-lv_root ro rd.lvm.lv=vg_fedora16x8664/lv_swap rd.dm=0 rd.lvm.lv=vg_fedora16x8664/lv_root KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.md=0 rd.luks=0 LANG=en_US.UTF-8 ", features="(null)"
domainbuilder: detail: xc_dom_kernel_mem: called
domainbuilder: detail: xc_dom_ramdisk_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-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_malloc : 16818 kB
domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x45dc95 -> 0x106c970
domainbuilder: detail: loader probe OK
xc: detail: elf_parse_binary: phdr: paddr=0x1000000 memsz=0x87e000
xc: detail: elf_parse_binary: phdr: paddr=0x1a00000 memsz=0xd50e0
xc: detail: elf_parse_binary: phdr: paddr=0x1ad6000 memsz=0x14480
xc: detail: elf_parse_binary: phdr: paddr=0x1aeb000 memsz=0x40b000
xc: detail: elf_parse_binary: memory: 0x1000000 -> 0x1ef6000
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 = 0xffffffff80000000
xc: detail: elf_xen_parse_note: ENTRY = 0xffffffff81aeb200
xc: detail: elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000
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 = 0xffff800000000000
xc: detail: elf_xen_parse_note: PADDR_OFFSET = 0x0
xc: detail: elf_xen_addr_calc_check: addresses:
xc: detail: virt_base = 0xffffffff80000000
xc: detail: elf_paddr_offset = 0x0
xc: detail: virt_offset = 0xffffffff80000000
xc: detail: virt_kstart = 0xffffffff81000000
xc: detail: virt_kend = 0xffffffff81ef6000
xc: detail: virt_entry = 0xffffffff81aeb200
xc: detail: p2m_base = 0xffffffffffffffff
domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64: 0xffffffff81000000 -> 0xffffffff81ef6000 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 : 0xffffffff81000000 -> 0xffffffff81ef6000 (pfn 0x1000 + 0xef6 pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x1000+0xef6 at 0x7f0808ebc000
xc: detail: elf_load_binary: phdr 0 at 0x0x7f0808ebc000 -> 0x0x7f080973a000
xc: detail: elf_load_binary: phdr 1 at 0x0x7f08098bc000 -> 0x0x7f08099910e0
xc: detail: elf_load_binary: phdr 2 at 0x0x7f0809992000 -> 0x0x7f08099a6480
xc: detail: elf_load_binary: phdr 3 at 0x0x7f08099a7000 -> 0x0x7f0809b28000
domainbuilder: detail: xc_dom_alloc_segment: ramdisk : 0xffffffff81ef6000 -> 0xffffffff84bef000 (pfn 0x1ef6 + 0x2cf9 pages)
domainbuilder: detail: xc_dom_malloc : 269 kB
domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x1ef6+0x2cf9 at 0x7f08061c3000
domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x1089152 -> 0x2cf8810
domainbuilder: detail: xc_dom_alloc_segment: phys2mach : 0xffffffff84bef000 -> 0xffffffff84cef000 (pfn 0x4bef + 0x100 pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x4bef+0x100 at 0x7f08060c3000 domainbuilder: detail: xc_dom_alloc_page : start info : 0xffffffff84cef000 (pfn 0x4cef) domainbuilder: detail: xc_dom_alloc_page : xenstore : 0xffffffff84cf0000 (pfn 0x4cf0) domainbuilder: detail: xc_dom_alloc_page : console : 0xffffffff84cf1000 (pfn 0x4cf1) domainbuilder: detail: nr_page_tables: 0x0000ffffffffffff/48: 0xffff000000000000 -> 0xffffffffffffffff, 1 table(s) domainbuilder: detail: nr_page_tables: 0x0000007fffffffff/39: 0xffffff8000000000 -> 0xffffffffffffffff, 1 table(s) domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30: 0xffffffff80000000 -> 0xffffffffbfffffff, 1 table(s) domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21: 0xffffffff80000000 -> 0xffffffff84ffffff, 40 table(s) domainbuilder: detail: xc_dom_alloc_segment: page tables : 0xffffffff84cf2000 -> 0xffffffff84d1d000 (pfn 0x4cf2 + 0x2b pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x4cf2+0x2b at 0x7f080e89f000 domainbuilder: detail: xc_dom_alloc_page : boot stack : 0xffffffff84d1d000 (pfn 0x4d1d) domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0xffffffff84d1e000 domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0xffffffff85000000
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_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 64bit, pages 0x20000
domainbuilder: detail: clear_page: pfn 0x4cf1, mfn 0x18bd93
domainbuilder: detail: clear_page: pfn 0x4cf0, mfn 0x18bd94
domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x4cef+0x1 at 0x7f080e89e000
domainbuilder: detail: start_info_x86_64: called
domainbuilder: detail: setup_hypercall_page: vaddr=0xffffffff81001000 pfn=0x1001

Fedora release 16 (Verne)
Kernel 3.2.10-3.fc16.x86_64 on an x86_64 (hvc0)

fedora16-x86-64 login:

==============================================================================================================

Please look at the screenshot of Fedora 16 x86-64 PV domU as follows:

http://i.imgur.com/a2FVr.png

Thank you very much.

Yours sincerely,

Teo En Ming (Zhang Enming)




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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.