* ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk
@ 2015-06-02 7:40 Sanjeev Pandita
2015-06-02 8:22 ` Stefan Bader
0 siblings, 1 reply; 14+ messages in thread
From: Sanjeev Pandita @ 2015-06-02 7:40 UTC (permalink / raw)
To: xen-devel; +Cc: Ian.Campbell, Pranavkumar Sawargaonkar, stefano.stabellini
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
All,
I am pretty new to xen . I am trying to boot DOMU with qemu qcow AARCH64
Ubuntu 15.04 disk on Xen but I am getting the errors which link to
"/usr/local/lib/xen/bin/qemu-system-i386".
Since I am working on aarch64 system the
/usr/local/lib/xen/bin/qemu-system-i386 bin might not be present or might
not work as expected.
Please let me know how to make the Qemu qcow image work on Xen.
Attached are the DomU boot log and config file.
Thanks,
San
--
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and contains information
that is confidential and proprietary to Applied Micro Circuits Corporation
or its subsidiaries.
It is to be used solely for the purpose of furthering the parties' business
relationship.
All unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by reply
e-mail
and destroy all copies of the original message.
[-- Attachment #2: config.log --]
[-- Type: application/octet-stream, Size: 214 bytes --]
linux:/mnt/xen # cat vm1
name = "vm1"
uuid = "3fb78ba6-8182-484c-acf7-8faba9773f68"
disk = ["phy:/dev/loop0,xvda,rw"]
memory = 512
kernel = "./Image"
extra = "root=/dev/xvda rw console=hvc0 earlyprintk=xen"
[-- Attachment #3: DomU_booting.log --]
[-- Type: application/octet-stream, Size: 34846 bytes --]
linux:/mnt/xen # xl -vvv create vm1
Parsing config from vm1
libxl: debug: libxl_create.c:1544:do_domain_create: ao 0x61615d0: create: how=(nil) callback=(nil) poller=0x6166dc0
libxl: debug: libxl_arm.c:58:libxl__arch_domain_prepare_config: Configure the domain
libxl: debug: libxl_arm.c:61:libxl__arch_domain_prepare_config: - Allocate 0 SPIs
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk vdev=xvdaspec.backend=unknown
libxl: debug: libxl_device.c:252:disk_try_backend: Disk vdev=xvda, backend phy unsuitable due to format qcow
libxl: debug: libxl_device.c:298:libxl__device_disk_set_backend: Disk vdev=xvda,using backend qdisk
libxl: debug: libxl_create.c:949:initiate_domain_create: running bootloader
libxl: debug: libxl_bootloader.c:329:libxl__bootloader_run: no bootloader configured, using user supplied kernel
libxl: debug: libxl_event.c:652:libxl__ev_xswatch_deregister: watch w=0x6167968:deregister unregistered
domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/xvda1 rw console=hvc0earlyprintk=xen", features="(null)"
libxl: debug: libxl_dom.c:630:libxl__build_pv: pv kernel mapped 0 path ./Image
domainbuilder: detail: xc_dom_kernel_file: filename="./Image"
domainbuilder: detail: xc_dom_malloc_filemap : 8891 kB
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.6, caps xen-3.0-aarch64 xen-3.0-armv7l
domainbuilder: detail: xc_dom_rambase_init: RAM starts at 40000
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 zImage (ARM64) loader ...
domainbuilder: detail: loader probe OK
domainbuilder: detail: xc_dom_parse_zimage64_kernel: called
domainbuilder: detail: xc_dom_parse_zimage64_kernel: xen-3.0-aarch64: 0x40080000-> 0x4092ec00
libxl: debug: libxl_arm.c:571:libxl__arch_domain_init_hw_description: constructing DTB for Xen version 4.6 guest
libxl: debug: libxl_arm.c:572:libxl__arch_domain_init_hw_description: - vGIC version: V2
libxl: debug: libxl_arm.c:333:make_memory_nodes: Creating placeholder node /memory@40000000
libxl: debug: libxl_arm.c:333:make_memory_nodes: Creating placeholder node /memory@200000000
libxl: debug: libxl_arm.c:647:libxl__arch_domain_init_hw_description: fdt totalsize 1270
domainbuilder: detail: xc_dom_devicetree_mem: called
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: set_mode: guest xen-3.0-aarch64, address size 64
domainbuilder: detail: xc_dom_malloc : 1024 kB
domainbuilder: detail: populate_guest_memory: populating RAM @ 0000000040000000-0000000060000000 (512MB)
domainbuilder: detail: populate_one_size: populated 0x100/0x100 entries with shift 9
domainbuilder: detail: arch_setup_meminit: placing boot modules at 0x48000000
domainbuilder: detail: arch_setup_meminit: devicetree: 0x48000000 -> 0x48001000
libxl: debug: libxl_arm.c:678:finalise_one_memory_node: Populating placeholder node /memory@40000000
libxl: debug: libxl_arm.c:672:finalise_one_memory_node: Nopping out placeholdernode /memory@200000000
domainbuilder: detail: xc_dom_build_image: called
domainbuilder: detail: xc_dom_alloc_segment: kernel : 0x40080000 -> 0x4092f000 (pfn 0x40080 + 0x8af pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x40080+0x8af at 0x7f8c7ee000
domainbuilder: detail: xc_dom_load_zimage_kernel: called
domainbuilder: detail: xc_dom_load_zimage_kernel: kernel seg 0x40080000-0x4092f000
domainbuilder: detail: xc_dom_load_zimage_kernel: copy 9104384 bytes from blob 0x7f8d19e000 to dst 0x7f8c7ee000
domainbuilder: detail: xc_dom_alloc_segment: devicetree : 0x48000000 -> 0x48001000 (pfn 0x48000 + 0x1 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x48000+0x1at 0x7f8ddfd000
domainbuilder: detail: alloc_magic_pages: called
domainbuilder: detail: count_pgtables_arm: called
domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0x48001000
domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0x0
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-aarch64 <= matches
domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-armv7l
domainbuilder: detail: setup_pgtables_arm: called
domainbuilder: detail: clear_page: pfn 0x39000, mfn 0x39000
domainbuilder: detail: clear_page: pfn 0x39001, mfn 0x39001
domainbuilder: detail: start_info_arm: called
domainbuilder: detail: domain builder memory footprint
domainbuilder: detail: allocated
domainbuilder: detail: malloc : 1078 kB
domainbuilder: detail: anon mmap : 0 bytes
domainbuilder: detail: mapped
domainbuilder: detail: file mmap : 8891 kB
domainbuilder: detail: domU mmap : 8896 kB
domainbuilder: detail: vcpu_arm64: called
domainbuilder: detail: DTB 48000000
domainbuilder: detail: Initial state CPSR 0x1c5 PC 0x40080000
domainbuilder: detail: launch_vm: called, ctxt=0x7f8ddff004
domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0x38000
domainbuilder: detail: xc_dom_release: called
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk vdev=xvdaspec.backend=qdisk
libxl: debug: libxl_event.c:652:libxl__ev_xswatch_deregister: watch w=0x615e290:deregister unregistered
libxl: debug: libxl_dm.c:1495:libxl__spawn_local_dm: Spawning device-model /usr/local/lib/xen/bin/qemu-system-i386 with arguments:
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: /usr/local/lib/xen/bin/qemu-system-i386
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -xen-domid
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: 1
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -chardev
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-1,server,nowait
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -no-shutdown
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -mon
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: chardev=libxl-cmd,mode=control
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -chardev
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: socket,id=libxenstat-cmd,path=/var/run/xen/qmp-libxenstat-1,server,nowait
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -mon
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: chardev=libxenstat-cmd,mode=control
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -nodefaults
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -xen-attach
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -name
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: vm1
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -vnc
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: none
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -display
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: none
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -nographic
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -machine
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: xenpv
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -m
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: 512
libxl: debug: libxl_event.c:600:libxl__ev_xswatch_register: watch w=0x6167be8 wpath=/local/domain/0/device-model/1/state token=3/0: register slotnum=3
libxl: debug: libxl_create.c:1560:do_domain_create: ao 0x61615d0: inprogress: poller=0x6166dc0, flags=i
libxl: debug: libxl_event.c:537:watchfd_callback: watch w=0x6167be8 wpath=/local/domain/0/device-model/1/state token=3/0: event epath=/local/domain/0/device-model/1/state
libxl: debug: libxl_event.c:537:watchfd_callback: watch w=0x6167be8 wpath=/local/domain/0/device-model/1/state token=3/0: event epath=/local/domain/0/device-model/1/state
libxl: debug: libxl_event.c:638:libxl__ev_xswatch_deregister: watch w=0x6167be8wpath=/local/domain/0/device-model/1/state token=3/0: deregister slotnum=3
libxl: debug: libxl_event.c:652:libxl__ev_xswatch_deregister: watch w=0x6167be8:deregister unregistered
libxl: debug: libxl_qmp.c:705:libxl__qmp_initialize: connected to /var/run/xen/qmp-libxl-1
libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: qmp
libxl: debug: libxl_qmp.c:555:qmp_send_prepare: next qmp command: '{
"execute": "qmp_capabilities",
"id": 1
}
'
libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: return
libxl: debug: libxl_qmp.c:555:qmp_send_prepare: next qmp command: '{
"execute": "query-chardev",
"id": 2
}
'
libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: return
libxl: debug: libxl_qmp.c:555:qmp_send_prepare: next qmp command: '{
"execute": "query-vnc",
"id": 3
}
'
libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: return
libxl: debug: libxl_event.c:1944:libxl__ao_progress_report: ao 0x61615d0: progress report: ignored
libxl: debug: libxl_event.c:1768:libxl__ao_complete: ao 0x61615d0: complete, rc=0
libxl: debug: libxl_event.c:1740:libxl__ao__destroy: ao 0x61615d0: destroy
xc: debug: hypercall buffer: total allocations:101 total releases:101
xc: debug: hypercall buffer: current allocations:0 maximum allocations:3
xc: debug: hypercall buffer: cache current size:3
xc: debug: hypercall buffer: cache hits:90 misses:3 toobig:8
linux:/mnt/xen #
linux:/mnt/xen # xl console vm1
Booting Linux on physical CPU 0x0
Initializing cgroup subsys cpu
Linux version 3.19.8 (san@san-Precision-WorkStation-T3400) (gcc version 4.9.3 20141031 (prerelease) (Linaro GCC 2014.11) ) #5 SMP PREEMPT Mon May 18 14:50:00 IST 2015
CPU: AArch64 Processor [500f0001] revision 1
Detected PIPT I-cache on CPU0
efi: Getting EFI parameters from FDT:
efi: UEFI not found.
cma: Reserved 16 MiB at 0x000000005f000000
psci: probing for conduit method from DT.
psci: PSCIv0.2 detected in firmware.
psci: Using standard PSCI v0.2 function IDs
PERCPU: Embedded 13 pages/cpu @ffffffc01efea000 s14080 r8192 d30976 u53248
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129024
Kernel command line: root=/dev/xvda1 rw console=hvc0 earlyprintk=xen
PID hash table entries: 2048 (order: 2, 16384 bytes)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Memory: 481528K/524288K available (6049K kernel code, 395K rwdata, 2124K rodata,272K init, 204K bss, 26376K reserved, 16384K cma-reserved)
Virtual kernel memory layout:
vmalloc : 0xffffff8000000000 - 0xffffffbdbfff0000 ( 246 GB)
vmemmap : 0xffffffbdc0000000 - 0xffffffbfc0000000 ( 8 GB maximum)
0xffffffbdc1000000 - 0xffffffbdc1800000 ( 8 MB actual)
PCI I/O : 0xffffffbffa000000 - 0xffffffbffb000000 ( 16 MB)
fixed : 0xffffffbffbdfd000 - 0xffffffbffbdff000 ( 8 KB)
modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB)
memory : 0xffffffc000000000 - 0xffffffc020000000 ( 512 MB)
.init : 0xffffffc00087e000 - 0xffffffc0008c2000 ( 272 KB)
.text : 0xffffffc000080000 - 0xffffffc00087d524 ( 8182 KB)
.data : 0xffffffc0008cc000 - 0xffffffc00092ec00 ( 395 KB)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptible hierarchical RCU implementation.
RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=1.
RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
NR_IRQS:64 nr_irqs:64 0
Architected cp15 timer(s) running at 50.00MHz (virt).
sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 2748779069440ns
Console: colour dummy device 80x25
Calibrating delay loop (skipped), value calculated using timer frequency.. 100.00 BogoMIPS (lpj=500000)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)
Mountpoint-cache hash table entries: 1024 (order: 1, 8192 bytes)
Initializing cgroup subsys memory
Initializing cgroup subsys hugetlb
hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 1 counters available
EFI services will not be available.
Xen 4.6 support found, events_irq=4 gnttab_frame=0x0000000038000000
xen:grant_table: Grant tables using version 1 layout
Grant table initialized
xen:events: Using FIFO-based ABI
Xen: initializing cpu0
Brought up 1 CPUs
SMP: Total of 1 processors activated.
devtmpfs: initialized
DMI not present or invalid.
atomic64_test: passed
NET: Registered protocol family 16
vdso: 2 pages (1 code @ ffffffc0008d1000, 1 data @ ffffffc0008d0000)
hw-breakpoint: found 4 breakpoint and 4 watchpoint registers.
software IO TLB [mem 0x5d000000-0x5d400000] (4MB) mapped at [ffffffc01d000000-ffffffc01d3fffff]
DMA: preallocated 256 KiB pool for atomic allocations
Serial: AMBA PL011 UART driver
xen:balloon: Initialising balloon driver
xen_balloon: Initialising balloon driver
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
Switched to clocksource arch_sys_counter
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP: reno registered
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
kvm [1]: HYP mode not available
futex hash table entries: 256 (order: 2, 16384 bytes)
audit: initializing netlink subsys (disabled)
audit: type=2000 audit(0.090:1): initialized
HugeTLB registered 2 MB page size, pre-allocated 0 pages
VFS: Disk quotas dquot_6.5.2
VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
fuse init (API version 7.23)
9p: Installing v9fs 9p2000 file system support
io scheduler noop registered
io scheduler cfq registered (default)
xen:xen_evtchn: Event-channel device installed
console [hvc0] enabled
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
brd: module loaded
loop: module loaded
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
e1000: Copyright (c) 1999-2006 Intel Corporation.
e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
igb: Intel(R) Gigabit Ethernet Network Driver - version 5.2.15-k
igb: Copyright (c) 2007-2014 Intel Corporation.
igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.0.2-k
igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 4.0.1-k
ixgbe: Copyright (c) 1999-2014 Intel Corporation.
ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver - version 2.12.1-k
ixgbevf: Copyright (c) 2009 - 2012 Intel Corporation.
i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 1.2.2-k
i40e: Copyright (c) 2013 - 2014 Intel Corporation.
ixgb: Intel(R) PRO/10GbE Network Driver - version 1.0.135-k2-NAPI
ixgb: Copyright (c) 1999-2008 Intel Corporation.
i40evf: Intel(R) XL710/X710 Virtual Function Network Driver - version 1.0.6
Copyright (c) 2013 - 2014 Intel Corporation.
Intel(R) Ethernet Switch Host Interface Driver - version 0.12.2-k
Copyright (c) 2013 Intel Corporation.
xen_netfront: Initialising Xen virtual ethernet driver
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ehci-platform: EHCI generic platform driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
ohci-platform: OHCI generic platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
Driver 'mmcblk' needs updating - please use bus_type methods
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP: cubic registered
NET: Registered protocol family 17
bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
8021q: 802.1Q VLAN Support v1.8
9pnet: Installing 9P2000 support
registered taskstats version 1
xenbus_probe_frontend: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s...
235s...230s...225s...220s...215s...210s...205s...linux:/mnt/xen # xl -vvv create vm1 ; xl console vm1
Parsing config from vm1
libxl: debug: libxl_create.c:1544:do_domain_create: ao 0x1c4a65d0: create: how=(nil) callback=(nil) poller=0x1c4abdc0
libxl: debug: libxl_arm.c:58:libxl__arch_domain_prepare_config: Configure the domain
libxl: debug: libxl_arm.c:61:libxl__arch_domain_prepare_config: - Allocate 0 SPIs
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk vdev=xvda spec.backend=unknown
libxl: debug: libxl_device.c:252:disk_try_backend: Disk vdev=xvda, backend phy unsuitable due to format qcow
libxl: debug: libxl_device.c:298:libxl__device_disk_set_backend: Disk vdev=xvda, using backend qdisk
libxl: debug: libxl_create.c:949:initiate_domain_create: running bootloader
libxl: debug: libxl_bootloader.c:329:libxl__bootloader_run: no bootloader configured, using user supplied kernel
libxl: debug: libxl_event.c:652:libxl__ev_xswatch_deregister: watch w=0x1c4ac968: deregister unregistered
domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/xvda1 rw console=hvc0 earlyprintk=xen", features="(null)"
libxl: debug: libxl_dom.c:630:libxl__build_pv: pv kernel mapped 0 path ./Image
domainbuilder: detail: xc_dom_kernel_file: filename="./Image"
domainbuilder: detail: xc_dom_malloc_filemap : 8891 kB
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.6, caps xen-3.0-aarch64 xen-3.0-armv7l
domainbuilder: detail: xc_dom_rambase_init: RAM starts at 40000
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 zImage (ARM64) loader ...
domainbuilder: detail: loader probe OK
domainbuilder: detail: xc_dom_parse_zimage64_kernel: called
domainbuilder: detail: xc_dom_parse_zimage64_kernel: xen-3.0-aarch64: 0x40080000 -> 0x4092ec00
libxl: debug: libxl_arm.c:571:libxl__arch_domain_init_hw_description: constructing DTB for Xen version 4.6 guest
libxl: debug: libxl_arm.c:572:libxl__arch_domain_init_hw_description: - vGIC version: V2
libxl: debug: libxl_arm.c:333:make_memory_nodes: Creating placeholder node /memory@40000000
libxl: debug: libxl_arm.c:333:make_memory_nodes: Creating placeholder node /memory@200000000
libxl: debug: libxl_arm.c:647:libxl__arch_domain_init_hw_description: fdt total size 1270
domainbuilder: detail: xc_dom_devicetree_mem: called
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: set_mode: guest xen-3.0-aarch64, address size 64
domainbuilder: detail: xc_dom_malloc : 1024 kB
domainbuilder: detail: populate_guest_memory: populating RAM @ 0000000040000000-0000000060000000 (512MB)
domainbuilder: detail: populate_one_size: populated 0x100/0x100 entries with shift 9
domainbuilder: detail: arch_setup_meminit: placing boot modules at 0x48000000
domainbuilder: detail: arch_setup_meminit: devicetree: 0x48000000 -> 0x48001000
libxl: debug: libxl_arm.c:678:finalise_one_memory_node: Populating placeholder node /memory@40000000
libxl: debug: libxl_arm.c:672:finalise_one_memory_node: Nopping out placeholder node /memory@200000000
domainbuilder: detail: xc_dom_build_image: called
domainbuilder: detail: xc_dom_alloc_segment: kernel : 0x40080000 -> 0x4092f000 (pfn 0x40080 + 0x8af pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x40080+0x8af at 0x7f96710000
domainbuilder: detail: xc_dom_load_zimage_kernel: called
domainbuilder: detail: xc_dom_load_zimage_kernel: kernel seg 0x40080000-0x4092f000
domainbuilder: detail: xc_dom_load_zimage_kernel: copy 9104384 bytes from blob 0x7f970c0000 to dst 0x7f96710000
domainbuilder: detail: xc_dom_alloc_segment: devicetree : 0x48000000 -> 0x48001000 (pfn 0x48000 + 0x1 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x48000+0x1 at 0x7f97d1f000
domainbuilder: detail: alloc_magic_pages: called
domainbuilder: detail: count_pgtables_arm: called
domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0x48001000
domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0x0
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-aarch64 <= matches
domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-armv7l
domainbuilder: detail: setup_pgtables_arm: called
domainbuilder: detail: clear_page: pfn 0x39000, mfn 0x39000
domainbuilder: detail: clear_page: pfn 0x39001, mfn 0x39001
domainbuilder: detail: start_info_arm: called
domainbuilder: detail: domain builder memory footprint
domainbuilder: detail: allocated
domainbuilder: detail: malloc : 1078 kB
domainbuilder: detail: anon mmap : 0 bytes
domainbuilder: detail: mapped
domainbuilder: detail: file mmap : 8891 kB
domainbuilder: detail: domU mmap : 8896 kB
domainbuilder: detail: vcpu_arm64: called
domainbuilder: detail: DTB 48000000
domainbuilder: detail: Initial state CPSR 0x1c5 PC 0x40080000
domainbuilder: detail: launch_vm: called, ctxt=0x7f97d21004
domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0x38000
domainbuilder: detail: xc_dom_release: called
libxl: debug: libxl_device.c:269:libxl__device_disk_set_backend: Disk vdev=xvda spec.backend=qdisk
libxl: debug: libxl_event.c:652:libxl__ev_xswatch_deregister: watch w=0x1c4a32b0: deregister unregistered
libxl: debug: libxl_dm.c:1495:libxl__spawn_local_dm: Spawning device-model /usr/local/lib/xen/bin/qemu-system-i386 with arguments:
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: /usr/local/lib/xen/bin/qemu-system-i386
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -xen-domid
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: 2
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -chardev
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-2,server,nowait
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -no-shutdown
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -mon
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: chardev=libxl-cmd,mode=control
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -chardev
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: socket,id=libxenstat-cmd,path=/var/run/xen/qmp-libxenstat-2,server,nowait
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -mon
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: chardev=libxenstat-cmd,mode=control
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -nodefaults
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -xen-attach
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -name
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: vm1
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -vnc
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: none
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -display
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: none
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -nographic
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -machine
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: xenpv
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: -m
libxl: debug: libxl_dm.c:1497:libxl__spawn_local_dm: 512
libxl: debug: libxl_event.c:600:libxl__ev_xswatch_register: watch w=0x1c4acbe8 wpath=/local/domain/0/device-model/2/state token=3/0: register slotnum=3
libxl: debug: libxl_create.c:1560:do_domain_create: ao 0x1c4a65d0: inprogress: poller=0x1c4abdc0, flags=i
libxl: debug: libxl_event.c:537:watchfd_callback: watch w=0x1c4acbe8 wpath=/local/domain/0/device-model/2/state token=3/0: event epath=/local/domain/0/device-model/2/state
libxl: debug: libxl_event.c:537:watchfd_callback: watch w=0x1c4acbe8 wpath=/local/domain/0/device-model/2/state token=3/0: event epath=/local/domain/0/device-model/2/state
libxl: debug: libxl_event.c:638:libxl__ev_xswatch_deregister: watch w=0x1c4acbe8 wpath=/local/domain/0/device-model/2/state token=3/0: deregister slotnum=3
libxl: debug: libxl_event.c:652:libxl__ev_xswatch_deregister: watch w=0x1c4acbe8: deregister unregistered
libxl: debug: libxl_qmp.c:705:libxl__qmp_initialize: connected to /var/run/xen/qmp-libxl-2
libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: qmp
libxl: debug: libxl_qmp.c:555:qmp_send_prepare: next qmp command: '{
"execute": "qmp_capabilities",
"id": 1
}
'
libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: return
libxl: debug: libxl_qmp.c:555:qmp_send_prepare: next qmp command: '{
"execute": "query-chardev",
"id": 2
}
'
libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: return
libxl: debug: libxl_qmp.c:555:qmp_send_prepare: next qmp command: '{
"execute": "query-vnc",
"id": 3
}
'
libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: return
libxl: debug: libxl_event.c:1944:libxl__ao_progress_report: ao 0x1c4a65d0: progress report: ignored
libxl: debug: libxl_event.c:1768:libxl__ao_complete: ao 0x1c4a65d0: complete, rc=0
libxl: debug: libxl_event.c:1740:libxl__ao__destroy: ao 0x1c4a65d0: destroy
xc: debug: hypercall buffer: total allocations:101 total releases:101
xc: debug: hypercall buffer: current allocations:0 maximum allocations:3
xc: debug: hypercall buffer: cache current size:3
xc: debug: hypercall buffer: cache hits:90 misses:3 toobig:8
Booting Linux on physical CPU 0x0
Initializing cgroup subsys cpu
Linux version 3.19.8 (san@san-Precision-WorkStation-T3400) (gcc version 4.9.3 20141031 (prerelease) (Linaro GCC 2014.11) ) #5 SMP PREEMPT Mon May 18 14:50:00 IST 2015
CPU: AArch64 Processor [500f0001] revision 1
Detected PIPT I-cache on CPU0
efi: Getting EFI parameters from FDT:
efi: UEFI not found.
cma: Reserved 16 MiB at 0x000000005f000000
psci: probing for conduit method from DT.
psci: PSCIv0.2 detected in firmware.
psci: Using standard PSCI v0.2 function IDs
PERCPU: Embedded 13 pages/cpu @ffffffc01efea000 s14080 r8192 d30976 u53248
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129024
Kernel command line: root=/dev/xvda1 rw console=hvc0 earlyprintk=xen
PID hash table entries: 2048 (order: 2, 16384 bytes)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Memory: 481528K/524288K available (6049K kernel code, 395K rwdata, 2124K rodata, 272K init, 204K bss, 26376K reserved, 16384K cma-reserved)
Virtual kernel memory layout:
vmalloc : 0xffffff8000000000 - 0xffffffbdbfff0000 ( 246 GB)
vmemmap : 0xffffffbdc0000000 - 0xffffffbfc0000000 ( 8 GB maximum)
0xffffffbdc1000000 - 0xffffffbdc1800000 ( 8 MB actual)
PCI I/O : 0xffffffbffa000000 - 0xffffffbffb000000 ( 16 MB)
fixed : 0xffffffbffbdfd000 - 0xffffffbffbdff000 ( 8 KB)
modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB)
memory : 0xffffffc000000000 - 0xffffffc020000000 ( 512 MB)
.init : 0xffffffc00087e000 - 0xffffffc0008c2000 ( 272 KB)
.text : 0xffffffc000080000 - 0xffffffc00087d524 ( 8182 KB)
.data : 0xffffffc0008cc000 - 0xffffffc00092ec00 ( 395 KB)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptible hierarchical RCU implementation.
RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=1.
RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
NR_IRQS:64 nr_irqs:64 0
Architected cp15 timer(s) running at 50.00MHz (virt).
sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 2748779069440ns
Console: colour dummy device 80x25
Calibrating delay loop (skipped), value calculated using timer frequency.. 100.00 BogoMIPS (lpj=500000)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)
Mountpoint-cache hash table entries: 1024 (order: 1, 8192 bytes)
Initializing cgroup subsys memory
Initializing cgroup subsys hugetlb
hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 1 counters available
EFI services will not be available.
Xen 4.6 support found, events_irq=4 gnttab_frame=0x0000000038000000
xen:grant_table: Grant tables using version 1 layout
Grant table initialized
xen:events: Using FIFO-based ABI
Xen: initializing cpu0
Brought up 1 CPUs
SMP: Total of 1 processors activated.
devtmpfs: initialized
DMI not present or invalid.
atomic64_test: passed
NET: Registered protocol family 16
vdso: 2 pages (1 code @ ffffffc0008d1000, 1 data @ ffffffc0008d0000)
hw-breakpoint: found 4 breakpoint and 4 watchpoint registers.
software IO TLB [mem 0x5d000000-0x5d400000] (4MB) mapped at [ffffffc01d000000-ffffffc01d3fffff]
DMA: preallocated 256 KiB pool for atomic allocations
Serial: AMBA PL011 UART driver
xen:balloon: Initialising balloon driver
xen_balloon: Initialising balloon driver
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
Switched to clocksource arch_sys_counter
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP: reno registered
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
kvm [1]: HYP mode not available
futex hash table entries: 256 (order: 2, 16384 bytes)
audit: initializing netlink subsys (disabled)
audit: type=2000 audit(0.090:1): initialized
HugeTLB registered 2 MB page size, pre-allocated 0 pages
VFS: Disk quotas dquot_6.5.2
VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
fuse init (API version 7.23)
9p: Installing v9fs 9p2000 file system support
io scheduler noop registered
io scheduler cfq registered (default)
xen:xen_evtchn: Event-channel device installed
console [hvc0] enabled
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
brd: module loaded
loop: module loaded
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
e1000: Copyright (c) 1999-2006 Intel Corporation.
e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
igb: Intel(R) Gigabit Ethernet Network Driver - version 5.2.15-k
igb: Copyright (c) 2007-2014 Intel Corporation.
igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.0.2-k
igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 4.0.1-k
ixgbe: Copyright (c) 1999-2014 Intel Corporation.
ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver - version 2.12.1-k
ixgbevf: Copyright (c) 2009 - 2012 Intel Corporation.
i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 1.2.2-k
i40e: Copyright (c) 2013 - 2014 Intel Corporation.
ixgb: Intel(R) PRO/10GbE Network Driver - version 1.0.135-k2-NAPI
ixgb: Copyright (c) 1999-2008 Intel Corporation.
i40evf: Intel(R) XL710/X710 Virtual Function Network Driver - version 1.0.6
Copyright (c) 2013 - 2014 Intel Corporation.
Intel(R) Ethernet Switch Host Interface Driver - version 0.12.2-k
Copyright (c) 2013 Intel Corporation.
xen_netfront: Initialising Xen virtual ethernet driver
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ehci-platform: EHCI generic platform driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
ohci-platform: OHCI generic platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
Driver 'mmcblk' needs updating - please use bus_type methods
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP: cubic registered
NET: Registered protocol family 17
bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
8021q: 802.1Q VLAN Support v1.8
9pnet: Installing 9P2000 support
registered taskstats version 1
xenbus_probe_frontend: Waiting for devices to initialise: 25s...20s...linux:/mnt/xen #
[-- 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] 14+ messages in thread
* Re: ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk
2015-06-02 7:40 ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk Sanjeev Pandita
@ 2015-06-02 8:22 ` Stefan Bader
2015-06-02 10:32 ` Stefano Stabellini
2015-06-02 12:09 ` Sanjeev Pandita
0 siblings, 2 replies; 14+ messages in thread
From: Stefan Bader @ 2015-06-02 8:22 UTC (permalink / raw)
To: Sanjeev Pandita, xen-devel
Cc: stefano.stabellini, Ian.Campbell, Pranavkumar Sawargaonkar
[-- Attachment #1.1: Type: text/plain, Size: 1041 bytes --]
On 02.06.2015 09:40, Sanjeev Pandita wrote:
> All,
>
> I am pretty new to xen . I am trying to boot DOMU with qemu qcow AARCH64
> Ubuntu 15.04 disk on Xen but I am getting the errors which link to
> "/usr/local/lib/xen/bin/qemu-system-i386".
> Since I am working on aarch64 system the
> /usr/local/lib/xen/bin/qemu-system-i386 bin might not be present or might
> not work as expected.
Because I am lacking hardware and feedback, the arm64 packaging is a rather
theoretical exercise. At least for armhf I thought qemu-system-x86 was a
dependency. That binary should provide x86 emulation on arm64, the same as one
could install qemu for other arches on x86.
Have you tried to install qemu-system-x86 manually?
-Stefan
>
> Please let me know how to make the Qemu qcow image work on Xen.
> Attached are the DomU boot log and config file.
>
> Thanks,
> San
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: 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] 14+ messages in thread
* Re: ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk
2015-06-02 8:22 ` Stefan Bader
@ 2015-06-02 10:32 ` Stefano Stabellini
2015-06-02 10:35 ` Stefano Stabellini
2015-06-02 12:09 ` Sanjeev Pandita
1 sibling, 1 reply; 14+ messages in thread
From: Stefano Stabellini @ 2015-06-02 10:32 UTC (permalink / raw)
To: Stefan Bader
Cc: Ian.Campbell, stefano.stabellini, Sanjeev Pandita,
Pranavkumar Sawargaonkar, xen-devel
On Tue, 2 Jun 2015, Stefan Bader wrote:
> On 02.06.2015 09:40, Sanjeev Pandita wrote:
> > All,
> >
> > I am pretty new to xen . I am trying to boot DOMU with qemu qcow AARCH64
> > Ubuntu 15.04 disk on Xen but I am getting the errors which link to
> > "/usr/local/lib/xen/bin/qemu-system-i386".
> > Since I am working on aarch64 system the
> > /usr/local/lib/xen/bin/qemu-system-i386 bin might not be present or might
> > not work as expected.
>
> Because I am lacking hardware and feedback, the arm64 packaging is a rather
> theoretical exercise. At least for armhf I thought qemu-system-x86 was a
> dependency. That binary should provide x86 emulation on arm64, the same as one
> could install qemu for other arches on x86.
> Have you tried to install qemu-system-x86 manually?
Hi Stefan,
On arm and arm64 Xen still needs a qemu-system-i386 binary, just to
provide the PV backends in userspace (disk, console, etc.).
Unfortunately the output binary is still named "qemu-system-i386". I
know that the name is misleading, but fixing it is not trivial: it
requires disentangling code in QEMU in non trivial ways.
Cheers,
Stefano
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk
2015-06-02 10:32 ` Stefano Stabellini
@ 2015-06-02 10:35 ` Stefano Stabellini
2015-06-02 10:58 ` Stefan Bader
0 siblings, 1 reply; 14+ messages in thread
From: Stefano Stabellini @ 2015-06-02 10:35 UTC (permalink / raw)
To: Stefano Stabellini
Cc: Ian.Campbell, Pranavkumar Sawargaonkar, Sanjeev Pandita,
Stefan Bader, xen-devel
On Tue, 2 Jun 2015, Stefano Stabellini wrote:
> On Tue, 2 Jun 2015, Stefan Bader wrote:
> > On 02.06.2015 09:40, Sanjeev Pandita wrote:
> > > All,
> > >
> > > I am pretty new to xen . I am trying to boot DOMU with qemu qcow AARCH64
> > > Ubuntu 15.04 disk on Xen but I am getting the errors which link to
> > > "/usr/local/lib/xen/bin/qemu-system-i386".
> > > Since I am working on aarch64 system the
> > > /usr/local/lib/xen/bin/qemu-system-i386 bin might not be present or might
> > > not work as expected.
> >
> > Because I am lacking hardware and feedback, the arm64 packaging is a rather
> > theoretical exercise. At least for armhf I thought qemu-system-x86 was a
> > dependency. That binary should provide x86 emulation on arm64, the same as one
> > could install qemu for other arches on x86.
> > Have you tried to install qemu-system-x86 manually?
>
> Hi Stefan,
>
> On arm and arm64 Xen still needs a qemu-system-i386 binary, just to
> provide the PV backends in userspace (disk, console, etc.).
> Unfortunately the output binary is still named "qemu-system-i386". I
> know that the name is misleading, but fixing it is not trivial: it
> requires disentangling code in QEMU in non trivial ways.
Just to be clear, qemu-system-i386 for ARM is the output of a QEMU build
on ARM with ./configure --enable-xen --target-list=i386-softmmu. It
could do x86 emulation, but it does not when used on Xen.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk
2015-06-02 10:35 ` Stefano Stabellini
@ 2015-06-02 10:58 ` Stefan Bader
2015-06-02 11:28 ` Stefano Stabellini
0 siblings, 1 reply; 14+ messages in thread
From: Stefan Bader @ 2015-06-02 10:58 UTC (permalink / raw)
To: Stefano Stabellini
Cc: Ian.Campbell, Sanjeev Pandita, Pranavkumar Sawargaonkar, xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 1721 bytes --]
On 02.06.2015 12:35, Stefano Stabellini wrote:
> On Tue, 2 Jun 2015, Stefano Stabellini wrote:
>> On Tue, 2 Jun 2015, Stefan Bader wrote:
>>> On 02.06.2015 09:40, Sanjeev Pandita wrote:
>>>> All,
>>>>
>>>> I am pretty new to xen . I am trying to boot DOMU with qemu qcow AARCH64
>>>> Ubuntu 15.04 disk on Xen but I am getting the errors which link to
>>>> "/usr/local/lib/xen/bin/qemu-system-i386".
>>>> Since I am working on aarch64 system the
>>>> /usr/local/lib/xen/bin/qemu-system-i386 bin might not be present or might
>>>> not work as expected.
>>>
>>> Because I am lacking hardware and feedback, the arm64 packaging is a rather
>>> theoretical exercise. At least for armhf I thought qemu-system-x86 was a
>>> dependency. That binary should provide x86 emulation on arm64, the same as one
>>> could install qemu for other arches on x86.
>>> Have you tried to install qemu-system-x86 manually?
>>
>> Hi Stefan,
>>
>> On arm and arm64 Xen still needs a qemu-system-i386 binary, just to
>> provide the PV backends in userspace (disk, console, etc.).
>> Unfortunately the output binary is still named "qemu-system-i386". I
>> know that the name is misleading, but fixing it is not trivial: it
>> requires disentangling code in QEMU in non trivial ways.
>
> Just to be clear, qemu-system-i386 for ARM is the output of a QEMU build
> on ARM with ./configure --enable-xen --target-list=i386-softmmu. It
> could do x86 emulation, but it does not when used on Xen.
>
Hi Stefano,
so for Debian and Ubuntu we moved to use the standard qemu binary which is build
with xen enabled. This works on x86, but I could not verify correctness for any
arm port (due to lack of hw).
-Stefan
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: 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] 14+ messages in thread
* Re: ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk
2015-06-02 10:58 ` Stefan Bader
@ 2015-06-02 11:28 ` Stefano Stabellini
0 siblings, 0 replies; 14+ messages in thread
From: Stefano Stabellini @ 2015-06-02 11:28 UTC (permalink / raw)
To: Stefan Bader
Cc: Ian.Campbell, xen-devel, Sanjeev Pandita,
Pranavkumar Sawargaonkar, Stefano Stabellini
On Tue, 2 Jun 2015, Stefan Bader wrote:
> On 02.06.2015 12:35, Stefano Stabellini wrote:
> > On Tue, 2 Jun 2015, Stefano Stabellini wrote:
> >> On Tue, 2 Jun 2015, Stefan Bader wrote:
> >>> On 02.06.2015 09:40, Sanjeev Pandita wrote:
> >>>> All,
> >>>>
> >>>> I am pretty new to xen . I am trying to boot DOMU with qemu qcow AARCH64
> >>>> Ubuntu 15.04 disk on Xen but I am getting the errors which link to
> >>>> "/usr/local/lib/xen/bin/qemu-system-i386".
> >>>> Since I am working on aarch64 system the
> >>>> /usr/local/lib/xen/bin/qemu-system-i386 bin might not be present or might
> >>>> not work as expected.
> >>>
> >>> Because I am lacking hardware and feedback, the arm64 packaging is a rather
> >>> theoretical exercise. At least for armhf I thought qemu-system-x86 was a
> >>> dependency. That binary should provide x86 emulation on arm64, the same as one
> >>> could install qemu for other arches on x86.
> >>> Have you tried to install qemu-system-x86 manually?
> >>
> >> Hi Stefan,
> >>
> >> On arm and arm64 Xen still needs a qemu-system-i386 binary, just to
> >> provide the PV backends in userspace (disk, console, etc.).
> >> Unfortunately the output binary is still named "qemu-system-i386". I
> >> know that the name is misleading, but fixing it is not trivial: it
> >> requires disentangling code in QEMU in non trivial ways.
> >
> > Just to be clear, qemu-system-i386 for ARM is the output of a QEMU build
> > on ARM with ./configure --enable-xen --target-list=i386-softmmu. It
> > could do x86 emulation, but it does not when used on Xen.
> >
>
> Hi Stefano,
>
> so for Debian and Ubuntu we moved to use the standard qemu binary which is build
> with xen enabled. This works on x86, but I could not verify correctness for any
> arm port (due to lack of hw).
OK, from what you say it should work
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk
2015-06-02 8:22 ` Stefan Bader
2015-06-02 10:32 ` Stefano Stabellini
@ 2015-06-02 12:09 ` Sanjeev Pandita
2015-06-02 12:41 ` Stefan Bader
2015-06-02 14:25 ` Stefano Stabellini
1 sibling, 2 replies; 14+ messages in thread
From: Sanjeev Pandita @ 2015-06-02 12:09 UTC (permalink / raw)
To: Stefan Bader, xen-devel
Cc: stefano.stabellini, Ian.Campbell, Pranavkumar Sawargaonkar
Hi,
-----Original Message-----
From: Stefan Bader [mailto:stefan.bader@canonical.com]
Sent: Tuesday, June 02, 2015 1:52 PM
To: Sanjeev Pandita; xen-devel@lists.xen.org
Cc: Ian.Campbell@citrix.com; Pranavkumar Sawargaonkar;
stefano.stabellini@eu.citrix.com
Subject: Re: [Xen-devel] ARM64: XEN Domu not booting with the qemu qcow
AARCH64 Ubuntu 15.04 disk
On 02.06.2015 09:40, Sanjeev Pandita wrote:
> All,
>
> I am pretty new to xen . I am trying to boot DOMU with qemu qcow
> AARCH64 Ubuntu 15.04 disk on Xen but I am getting the errors which
> link to "/usr/local/lib/xen/bin/qemu-system-i386".
> Since I am working on aarch64 system the
> /usr/local/lib/xen/bin/qemu-system-i386 bin might not be present or
> might not work as expected.
Because I am lacking hardware and feedback, the arm64 packaging is a
rather theoretical exercise. At least for armhf I thought qemu-system-x86
was a dependency. That binary should provide x86 emulation on arm64, the
same as one could install qemu for other arches on x86.
Have you tried to install qemu-system-x86 manually?
-Stefan
>
> Please let me know how to make the Qemu qcow image work on Xen.
> Attached are the DomU boot log and config file.
>
> Thanks,
> San
Thanks for your inputs, I have installed the qemu-system-i386 but my DomU
booting is still crashing with following short logs. Am I missing anything
?
Kernel Crash logs:
xenbus_probe_frontend: Waiting for devices to initialise:
25s...20s...15s...10s...5s...0s...
235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s
...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...1
30s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75
s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s.
..10s...5s...0s...
xenbus_probe_frontend: Timeout connecting to device: device/vbd/51712
(local state 3, remote state 2)
console [netcon0] enabled
netconsole: network logging started
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
VFS: Cannot open root device "xvda" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available
partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.8 #5
Hardware name: XENVM-4.6 (DT)
Call trace:
[<ffffffc00008a0dc>] dump_backtrace+0x0/0x124
[<ffffffc00008a210>] show_stack+0x10/0x1c
[<ffffffc000657d88>] dump_stack+0x80/0xc4
[<ffffffc000656f04>] panic+0xe0/0x220
[<ffffffc00087eea8>] mount_block_root+0x1a4/0x24c
[<ffffffc00087f19c>] mount_root+0x110/0x130
[<ffffffc00087f328>] prepare_namespace+0x16c/0x1b8
[<ffffffc00087eb44>] kernel_init_freeable+0x1c4/0x1ec
[<ffffffc00065481c>] kernel_init+0xc/0xd8
---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
My config file :
linux:/mnt/xen # cat vm1
name = "vm1"
uuid = "3fb78ba6-8182-484c-acf7-8faba9773f68"
disk = [ 'tap:qcow:/mnt/xen/vivid-server-cloudimg-arm64-disk1.img,xvda,w'
]
memory = 512
kernel = "./Image"
extra = "root=/dev/xvda rw console=hvc0 earlyprintk=xen"
Regards,
San
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
--
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and contains information
that is confidential and proprietary to Applied Micro Circuits Corporation
or its subsidiaries.
It is to be used solely for the purpose of furthering the parties' business
relationship.
All unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by reply
e-mail
and destroy all copies of the original message.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk
2015-06-02 12:09 ` Sanjeev Pandita
@ 2015-06-02 12:41 ` Stefan Bader
2015-06-02 14:25 ` Stefano Stabellini
1 sibling, 0 replies; 14+ messages in thread
From: Stefan Bader @ 2015-06-02 12:41 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 3668 bytes --]
On 02.06.2015 14:09, Sanjeev Pandita wrote:
> Hi,
>
> -----Original Message-----
> From: Stefan Bader [mailto:stefan.bader@canonical.com]
> Sent: Tuesday, June 02, 2015 1:52 PM
> To: Sanjeev Pandita; xen-devel@lists.xen.org
> Cc: Ian.Campbell@citrix.com; Pranavkumar Sawargaonkar;
> stefano.stabellini@eu.citrix.com
> Subject: Re: [Xen-devel] ARM64: XEN Domu not booting with the qemu qcow
> AARCH64 Ubuntu 15.04 disk
>
> On 02.06.2015 09:40, Sanjeev Pandita wrote:
>> All,
>>
>> I am pretty new to xen . I am trying to boot DOMU with qemu qcow
>> AARCH64 Ubuntu 15.04 disk on Xen but I am getting the errors which
>> link to "/usr/local/lib/xen/bin/qemu-system-i386".
>> Since I am working on aarch64 system the
>> /usr/local/lib/xen/bin/qemu-system-i386 bin might not be present or
>> might not work as expected.
>
> Because I am lacking hardware and feedback, the arm64 packaging is a
> rather theoretical exercise. At least for armhf I thought qemu-system-x86
> was a dependency. That binary should provide x86 emulation on arm64, the
> same as one could install qemu for other arches on x86.
> Have you tried to install qemu-system-x86 manually?
>
> -Stefan
>
>>
>> Please let me know how to make the Qemu qcow image work on Xen.
>> Attached are the DomU boot log and config file.
>>
>> Thanks,
>> San
>
> Thanks for your inputs, I have installed the qemu-system-i386 but my DomU
> booting is still crashing with following short logs. Am I missing anything
> ?
>
> Kernel Crash logs:
>
> xenbus_probe_frontend: Waiting for devices to initialise:
> 25s...20s...15s...10s...5s...0s...
> 235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s
> ...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...1
> 30s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75
> s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s.
> ..10s...5s...0s...
>
> xenbus_probe_frontend: Timeout connecting to device: device/vbd/51712
> (local state 3, remote state 2)
> console [netcon0] enabled
> netconsole: network logging started
> drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> VFS: Cannot open root device "xvda" or unknown-block(0,0): error -6
> Please append a correct "root=" boot option; here are the available
> partitions:
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
> CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.8 #5
> Hardware name: XENVM-4.6 (DT)
> Call trace:
> [<ffffffc00008a0dc>] dump_backtrace+0x0/0x124
> [<ffffffc00008a210>] show_stack+0x10/0x1c
> [<ffffffc000657d88>] dump_stack+0x80/0xc4
> [<ffffffc000656f04>] panic+0xe0/0x220
> [<ffffffc00087eea8>] mount_block_root+0x1a4/0x24c
> [<ffffffc00087f19c>] mount_root+0x110/0x130
> [<ffffffc00087f328>] prepare_namespace+0x16c/0x1b8
> [<ffffffc00087eb44>] kernel_init_freeable+0x1c4/0x1ec
> [<ffffffc00065481c>] kernel_init+0xc/0xd8
> ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
>
>
> My config file :
>
> linux:/mnt/xen # cat vm1
> name = "vm1"
> uuid = "3fb78ba6-8182-484c-acf7-8faba9773f68"
> disk = [ 'tap:qcow:/mnt/xen/vivid-server-cloudimg-arm64-disk1.img,xvda,w'
We do not have blktap support. Maybe dropping that prefix helps...
> ]
> memory = 512
> kernel = "./Image"
> extra = "root=/dev/xvda rw console=hvc0 earlyprintk=xen"
>
>
> Regards,
> San
>
>
>>
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>>
>
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: 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] 14+ messages in thread
* Re: ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk
2015-06-02 12:09 ` Sanjeev Pandita
2015-06-02 12:41 ` Stefan Bader
@ 2015-06-02 14:25 ` Stefano Stabellini
2015-06-03 8:31 ` Sanjeev Pandita
1 sibling, 1 reply; 14+ messages in thread
From: Stefano Stabellini @ 2015-06-02 14:25 UTC (permalink / raw)
To: Sanjeev Pandita
Cc: stefano.stabellini, Pranavkumar Sawargaonkar, Ian.Campbell,
Stefan Bader, xen-devel
On Tue, 2 Jun 2015, Sanjeev Pandita wrote:
> From: Stefan Bader [mailto:stefan.bader@canonical.com]
> Sent: Tuesday, June 02, 2015 1:52 PM
> To: Sanjeev Pandita; xen-devel@lists.xen.org
> Cc: Ian.Campbell@citrix.com; Pranavkumar Sawargaonkar;
> stefano.stabellini@eu.citrix.com
> Subject: Re: [Xen-devel] ARM64: XEN Domu not booting with the qemu qcow
> AARCH64 Ubuntu 15.04 disk
>
> On 02.06.2015 09:40, Sanjeev Pandita wrote:
> > All,
> >
> > I am pretty new to xen . I am trying to boot DOMU with qemu qcow
> > AARCH64 Ubuntu 15.04 disk on Xen but I am getting the errors which
> > link to "/usr/local/lib/xen/bin/qemu-system-i386".
> > Since I am working on aarch64 system the
> > /usr/local/lib/xen/bin/qemu-system-i386 bin might not be present or
> > might not work as expected.
>
> Because I am lacking hardware and feedback, the arm64 packaging is a
> rather theoretical exercise. At least for armhf I thought qemu-system-x86
> was a dependency. That binary should provide x86 emulation on arm64, the
> same as one could install qemu for other arches on x86.
> Have you tried to install qemu-system-x86 manually?
>
> -Stefan
>
> >
> > Please let me know how to make the Qemu qcow image work on Xen.
> > Attached are the DomU boot log and config file.
> >
> > Thanks,
> > San
>
> Thanks for your inputs, I have installed the qemu-system-i386 but my DomU
> booting is still crashing with following short logs. Am I missing anything
> ?
>
> Kernel Crash logs:
>
> xenbus_probe_frontend: Waiting for devices to initialise:
> 25s...20s...15s...10s...5s...0s...
> 235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s
> ...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...1
> 30s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75
> s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s.
> ..10s...5s...0s...
>
> xenbus_probe_frontend: Timeout connecting to device: device/vbd/51712
> (local state 3, remote state 2)
> console [netcon0] enabled
> netconsole: network logging started
> drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> VFS: Cannot open root device "xvda" or unknown-block(0,0): error -6
> Please append a correct "root=" boot option; here are the available
> partitions:
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
> CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.8 #5
> Hardware name: XENVM-4.6 (DT)
> Call trace:
> [<ffffffc00008a0dc>] dump_backtrace+0x0/0x124
> [<ffffffc00008a210>] show_stack+0x10/0x1c
> [<ffffffc000657d88>] dump_stack+0x80/0xc4
> [<ffffffc000656f04>] panic+0xe0/0x220
> [<ffffffc00087eea8>] mount_block_root+0x1a4/0x24c
> [<ffffffc00087f19c>] mount_root+0x110/0x130
> [<ffffffc00087f328>] prepare_namespace+0x16c/0x1b8
> [<ffffffc00087eb44>] kernel_init_freeable+0x1c4/0x1ec
> [<ffffffc00065481c>] kernel_init+0xc/0xd8
> ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
It looks like the backend (QEMU) hasn't been initialized properly.
Could you please post the output of xenstore-ls? Also could you run ps
aux|grep qemu to check whether QEMU was spawned correctly?
>
> My config file :
>
> linux:/mnt/xen # cat vm1
> name = "vm1"
> uuid = "3fb78ba6-8182-484c-acf7-8faba9773f68"
> disk = [ 'tap:qcow:/mnt/xen/vivid-server-cloudimg-arm64-disk1.img,xvda,w'
> ]
> memory = 512
> kernel = "./Image"
> extra = "root=/dev/xvda rw console=hvc0 earlyprintk=xen"
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk
2015-06-02 14:25 ` Stefano Stabellini
@ 2015-06-03 8:31 ` Sanjeev Pandita
2015-06-03 10:15 ` Stefano Stabellini
0 siblings, 1 reply; 14+ messages in thread
From: Sanjeev Pandita @ 2015-06-03 8:31 UTC (permalink / raw)
To: Stefano Stabellini
Cc: Pranavkumar Sawargaonkar, Ian Campbell, Stefan Bader, xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 4683 bytes --]
On Tue, Jun 2, 2015 at 7:55 PM, Stefano Stabellini <
stefano.stabellini@eu.citrix.com> wrote:
> On Tue, 2 Jun 2015, Sanjeev Pandita wrote:
> > From: Stefan Bader [mailto:stefan.bader@canonical.com]
> > Sent: Tuesday, June 02, 2015 1:52 PM
> > To: Sanjeev Pandita; xen-devel@lists.xen.org
> > Cc: Ian.Campbell@citrix.com; Pranavkumar Sawargaonkar;
> > stefano.stabellini@eu.citrix.com
> > Subject: Re: [Xen-devel] ARM64: XEN Domu not booting with the qemu qcow
> > AARCH64 Ubuntu 15.04 disk
> >
> > On 02.06.2015 09:40, Sanjeev Pandita wrote:
> > > All,
> > >
> > > I am pretty new to xen . I am trying to boot DOMU with qemu qcow
> > > AARCH64 Ubuntu 15.04 disk on Xen but I am getting the errors which
> > > link to "/usr/local/lib/xen/bin/qemu-system-i386".
> > > Since I am working on aarch64 system the
> > > /usr/local/lib/xen/bin/qemu-system-i386 bin might not be present or
> > > might not work as expected.
> >
> > Because I am lacking hardware and feedback, the arm64 packaging is a
> > rather theoretical exercise. At least for armhf I thought qemu-system-x86
> > was a dependency. That binary should provide x86 emulation on arm64, the
> > same as one could install qemu for other arches on x86.
> > Have you tried to install qemu-system-x86 manually?
> >
> > -Stefan
> >
> > >
> > > Please let me know how to make the Qemu qcow image work on Xen.
> > > Attached are the DomU boot log and config file.
> > >
> > > Thanks,
> > > San
> >
> > Thanks for your inputs, I have installed the qemu-system-i386 but my DomU
> > booting is still crashing with following short logs. Am I missing
> anything
> > ?
> >
> > Kernel Crash logs:
> >
> > xenbus_probe_frontend: Waiting for devices to initialise:
> > 25s...20s...15s...10s...5s...0s...
> >
> 235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s
> >
> ...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...1
> >
> 30s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75
> >
> s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s.
> > ..10s...5s...0s...
> >
> > xenbus_probe_frontend: Timeout connecting to device: device/vbd/51712
> > (local state 3, remote state 2)
> > console [netcon0] enabled
> > netconsole: network logging started
> > drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> > VFS: Cannot open root device "xvda" or unknown-block(0,0): error -6
> > Please append a correct "root=" boot option; here are the available
> > partitions:
> > Kernel panic - not syncing: VFS: Unable to mount root fs on
> > unknown-block(0,0)
> > CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.8 #5
> > Hardware name: XENVM-4.6 (DT)
> > Call trace:
> > [<ffffffc00008a0dc>] dump_backtrace+0x0/0x124
> > [<ffffffc00008a210>] show_stack+0x10/0x1c
> > [<ffffffc000657d88>] dump_stack+0x80/0xc4
> > [<ffffffc000656f04>] panic+0xe0/0x220
> > [<ffffffc00087eea8>] mount_block_root+0x1a4/0x24c
> > [<ffffffc00087f19c>] mount_root+0x110/0x130
> > [<ffffffc00087f328>] prepare_namespace+0x16c/0x1b8
> > [<ffffffc00087eb44>] kernel_init_freeable+0x1c4/0x1ec
> > [<ffffffc00065481c>] kernel_init+0xc/0xd8
> > ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on
> > unknown-block(0,0)
>
> It looks like the backend (QEMU) hasn't been initialized properly.
> Could you please post the output of xenstore-ls? Also could you run ps
> aux|grep qemu to check whether QEMU was spawned correctly?
>
>
Attaching output of xenstore-ls and grep qemu.
Looks like qemu process is getting spawned and running fine.
I have also modified the config file to remove tap from disk like:
disk = [ 'qcow:/mnt/xen/vivid-server-cloudimg-arm64-disk1.img,xvda,w' ]
But still my DOMU booting is stuck and getting crashed due to lack of
rootfs/disk.
I am running this on mustang board.
Thanks,
San
>
> >
> > My config file :
> >
> > linux:/mnt/xen # cat vm1
> > name = "vm1"
> > uuid = "3fb78ba6-8182-484c-acf7-8faba9773f68"
> > disk = [ 'tap:qcow:/mnt/xen/vivid-server-cloudimg-arm64-disk1.img,xvda,w'
> > ]
> > memory = 512
> > kernel = "./Image"
> > extra = "root=/dev/xvda rw console=hvc0 earlyprintk=xen"
>
--
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and contains information
that is confidential and proprietary to Applied Micro Circuits Corporation
or its subsidiaries.
It is to be used solely for the purpose of furthering the parties' business
relationship.
All unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by reply
e-mail
and destroy all copies of the original message.
[-- Attachment #1.2: Type: text/html, Size: 6445 bytes --]
[-- Attachment #2: xenstore-ls_qemu_log.txt --]
[-- Type: text/plain, Size: 6835 bytes --]
linux:~ # xenstore-ls
tool = ""
xenstored = ""
local = ""
domain = ""
0 = ""
domid = "0"
name = "Domain-0"
device-model = ""
0 = ""
state = "running"
1 = ""
state = "running"
libxl = ""
disable_udev = "1"
backend = ""
qdisk = ""
1 = ""
51712 = ""
frontend = "/local/domain/1/device/vbd/51712"
params = "qcow:/mnt/xen/vivid-server-cloudimg-arm64-disk1.img"
frontend-id = "1"
online = "1"
removable = "0"
bootable = "1"
state = "2"
dev = "xvda"
type = "qdisk"
mode = "w"
device-type = "disk"
discard-enable = "1"
feature-flush-cache = "1"
feature-persistent = "1"
info = "0"
feature-discard = "1"
hotplug-status = "connected"
console = ""
1 = ""
0 = ""
frontend = "/local/domain/1/console"
frontend-id = "1"
online = "1"
state = "1"
protocol = "vt100"
1 = ""
vm = "/vm/3fb78ba6-8182-484c-acf7-8faba9773f68"
name = "vm4"
cpu = ""
0 = ""
availability = "online"
memory = ""
static-max = "524288"
target = "524288"
videoram = "0"
device = ""
suspend = ""
event-channel = ""
vbd = ""
51712 = ""
backend = "/local/domain/0/backend/qdisk/1/51712"
backend-id = "0"
state = "3"
virtual-device = "51712"
device-type = "disk"
protocol = "arm-abi"
ring-ref = "8"
event-channel = "3"
feature-persistent = "1"
control = ""
shutdown = ""
platform-feature-multiprocessor-suspend = "1"
platform-feature-xs_reset_watches = "1"
data = ""
domid = "1"
store = ""
port = "1"
ring-ref = "233473"
console = ""
backend = "/local/domain/0/backend/console/1/0"
backend-id = "0"
limit = "1048576"
type = "xenconsoled"
output = "pty"
tty = "/dev/pts/1"
port = "2"
ring-ref = "233472"
image = ""
device-model-pid = "1872"
vm = ""
3fb78ba6-8182-484c-acf7-8faba9773f68 = ""
name = "vm4"
uuid = "3fb78ba6-8182-484c-acf7-8faba9773f68"
image = ""
ostype = "linux"
kernel = "./Image"
cmdline = "root=/dev/xvda rw console=hvc0 earlyprintk=xen"
start_time = "1433319561.58"
libxl = ""
1 = ""
dm-version = "qemu_xen"
linux:~ #
linux:~ #
linux:~ #
linux:~ # ps -aex | grep -i qemu
1863 ? Sl 0:00 /usr/local/lib/xen/bin/qemu-system-i386 -xen-domid 0 -xen-attach -name dom0 -nographic -M xenpv -daemonize -monitor /dev/null -serial /dev/null -parallel /dev/null -pidfile /var/run/qemu-dom0.pid LESSKEY=/etc/lesskey.bin MANPATH= NNTPSERVER=news XDG_SESSION_ID=c1 HOSTNAME=linux XKEYSYMDB=/usr/X11R6/lib/X11/XKeysymDB SHELL=/bin/bash TERM=xterm HOST=linux HISTSIZE=1000 PROFILEREAD=true SSH_CLIENT=10.48.12.106 50412 22 MORE=-sl SSH_TTY=/dev/pts/0 USER=root LS_COLORS=no=00:fi=00:di=01;34:ln=00;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=41;33;01:ex=00;32:*.cmd=00;32:*.exe=01;32:*.com=01;32:*.bat=01;32:*.btm=01;32:*.dll=01;32:*.tar=00;31:*.tbz=00;31:*.tgz=00;31:*.rpm=00;31:*.deb=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.lzma=00;31:*.zip=00;31:*.zoo=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:*.tb2=00;31:*.tz2=00;31:*.tbz2=00;31:*.xz=00;31:*.avi=01;35:*.bmp=01;35:*.fli=01;35:*.gif=01;35:*.jpg=01;35:*.jpeg=01;35:*.mng=01;35:*.mov=01;35:*.mpg=01;35:*.pcx=01;35:*.pbm=01;35:*.pgm=01;35:*.png=01;35:*.ppm=01;35:*.tga=01;35:*.tif=01;35:*.xbm=01;35:*.xpm=01;35:*.dl=01;35:*.gl=01;35:*.wmv=01;35:*.aiff=00;32:*.au=00;32:*.mid=00;32:*.mp3=00;32:*.ogg=00;32:*.voc=00;32:*.wav=00;32: XNLSPATH=/usr/X11R6/lib/X11/nls HOSTTYPE=aarch64 CONFIG_SITE=/usr/share/site/aarch64-suse-linux-gnu PAGER=less CSHEDIT=emacs XDG_CONFIG_DIRS=/etc/xdg MINICOM=-c on LIBGL_DEBUG=quiet PATH=/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/games MAIL=/var/mail/root CPU=aarch64 SSH_SENDS_LOCALE=yes PWD=/mnt/xen INPUTRC=/etc/inputrc LANG=en_IN PYTHONSTARTUP=/etc/pythonstart GPG_TTY=/dev/pts/0 HOME=/root SHLVL=2 OSTYPE=linux LESS_ADVANCED_PREPROCESSOR=no LS_OPTIONS=-A -N --color=tty -T 0 WINDOWMANAGER= LOGNAME=root MACHTYPE=aarch64-suse-linux LESS=-M -I -R CVS_RSH=ssh SSH_CONNECTION=10.48.12.106 50412 10.48.12.191 22 XDG_DATA_DIRS=/usr/share LESSOPEN=lessopen.sh %s XDG_RUNTIME_DIR=/run/user/0 LESSCLOSE=lessclose.sh %s %s NO_AT_BRIDGE=1 G_BROKEN_FILENAMES=1 COLORTERM=1 _=/usr/local/lib/xen/bin/qemu-system-i386
1872 ? Ssl 0:00 /usr/local/lib/xen/bin/qemu-system-i386 -xen-domid 1 -chardev socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-1,server,nowait -no-shutdown -mon chardev=libxl-cmd,mode=control -chardev socket,id=libxenstat-cmd,path=/var/run/xen/qmp-libxenstat-1,server,nowait -mon chardev=libxenstat-cmd,mode=control -nodefaults -xen-attach -name vm4 -vnc none -display none -nographic -machine xenpv -m 512 LESSKEY=/etc/lesskey.bin NNTPSERVER=news MANPATH= XDG_SESSION_ID=c1 HOSTNAME=linux XKEYSYMDB=/usr/X11R6/lib/X11/XKeysymDB HOST=linux TERM=xterm SHELL=/bin/bash PROFILEREAD=true HISTSIZE=1000 SSH_CLIENT=10.48.12.106 50412 22 MORE=-sl OLDPWD=/root LIBXL_DEBUG_DUMP_DTB=guest.dtb SSH_TTY=/dev/pts/0 USER=root LS_COLORS=no=00:fi=00:di=01;34:ln=00;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=41;33;01:ex=00;32:*.cmd=00;32:*.exe=01;32:*.com=01;32:*.bat=01;32:*.btm=01;32:*.dll=01;32:*.tar=00;31:*.tbz=00;31:*.tgz=00;31:*.rpm=00;31:*.deb=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.lzma=00;31:*.zip=00;31:*.zoo=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:*.tb2=00;31:*.tz2=00;31:*.tbz2=00;31:*.xz=00;31:*.avi=01;35:*.bmp=01;35:*.fli=01;35:*.gif=01;35:*.jpg=01;35:*.jpeg=01;35:*.mng=01;35:*.mov=01;35:*.mpg=01;35:*.pcx=01;35:*.pbm=01;35:*.pgm=01;35:*.png=01;35:*.ppm=01;35:*.tga=01;35:*.tif=01;35:*.xbm=01;35:*.xpm=01;35:*.dl=01;35:*.gl=01;35:*.wmv=01;35:*.aiff=00;32:*.au=00;32:*.mid=00;32:*.mp3=00;32:*.ogg=00;32:*.voc=00;32:*.wav=00;32: XNLSPATH=/usr/X11R6/lib/X11/nls HOSTTYPE=aarch64 CONFIG_SITE=/usr/share/site/aarch64-suse-linux-gnu PAGER=less CSHEDIT=emacs XDG_CONFIG_DIRS=/etc/xdg LIBGL_DEBUG=quiet MINICOM=-c on MAIL=/var/mail/root PATH=/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/games CPU=aarch64 SSH_SENDS_LOCALE=yes INPUTRC=/etc/inputrc PWD=/mnt/xen LANG=en_IN PYTHONSTARTUP=/etc/pythonstart GPG_TTY=/dev/pts/0 SHLVL=1 HOME=/root LESS_ADVANCED_PREPROCESSOR=no OSTYPE=linux LS_OPTIONS=-A -N --color=tty -T 0 WINDOWMANAGER= LESS=-M -I -R MACHTYPE=aarch64-suse-linux LOGNAME=root CVS_RSH=ssh XDG_DATA_DIRS=/usr/share SSH_CONNECTION=10.48.12.106 50412 10.48.12.191 22 LESSOPEN=lessopen.sh %s XDG_RUNTIME_DIR=/run/user/0 NO_AT_BRIDGE=1 LESSCLOSE=lessclose.sh %s %s G_BROKEN_FILENAMES=1 COLORTERM=1 _=/usr/local/sbin/xl
[-- Attachment #3: 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] 14+ messages in thread
* Re: ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk
2015-06-03 8:31 ` Sanjeev Pandita
@ 2015-06-03 10:15 ` Stefano Stabellini
2015-06-03 11:12 ` Sanjeev Pandita
0 siblings, 1 reply; 14+ messages in thread
From: Stefano Stabellini @ 2015-06-03 10:15 UTC (permalink / raw)
To: Sanjeev Pandita
Cc: xen-devel, Pranavkumar Sawargaonkar, Ian Campbell, Stefan Bader,
Stefano Stabellini
On Wed, 3 Jun 2015, Sanjeev Pandita wrote:
> On Tue, Jun 2, 2015 at 7:55 PM, Stefano Stabellini <stefano.stabellini@eu.citrix.com> wrote:
> On Tue, 2 Jun 2015, Sanjeev Pandita wrote:
> > From: Stefan Bader [mailto:stefan.bader@canonical.com]
> > Sent: Tuesday, June 02, 2015 1:52 PM
> > To: Sanjeev Pandita; xen-devel@lists.xen.org
> > Cc: Ian.Campbell@citrix.com; Pranavkumar Sawargaonkar;
> > stefano.stabellini@eu.citrix.com
> > Subject: Re: [Xen-devel] ARM64: XEN Domu not booting with the qemu qcow
> > AARCH64 Ubuntu 15.04 disk
> >
> > On 02.06.2015 09:40, Sanjeev Pandita wrote:
> > > All,
> > >
> > > I am pretty new to xen . I am trying to boot DOMU with qemu qcow
> > > AARCH64 Ubuntu 15.04 disk on Xen but I am getting the errors which
> > > link to "/usr/local/lib/xen/bin/qemu-system-i386".
> > > Since I am working on aarch64 system the
> > > /usr/local/lib/xen/bin/qemu-system-i386 bin might not be present or
> > > might not work as expected.
> >
> > Because I am lacking hardware and feedback, the arm64 packaging is a
> > rather theoretical exercise. At least for armhf I thought qemu-system-x86
> > was a dependency. That binary should provide x86 emulation on arm64, the
> > same as one could install qemu for other arches on x86.
> > Have you tried to install qemu-system-x86 manually?
> >
> > -Stefan
> >
> > >
> > > Please let me know how to make the Qemu qcow image work on Xen.
> > > Attached are the DomU boot log and config file.
> > >
> > > Thanks,
> > > San
> >
> > Thanks for your inputs, I have installed the qemu-system-i386 but my DomU
> > booting is still crashing with following short logs. Am I missing anything
> > ?
> >
> > Kernel Crash logs:
> >
> > xenbus_probe_frontend: Waiting for devices to initialise:
> > 25s...20s...15s...10s...5s...0s...
> > 235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s
> > ...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...1
> > 30s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75
> > s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s.
> > ..10s...5s...0s...
> >
> > xenbus_probe_frontend: Timeout connecting to device: device/vbd/51712
> > (local state 3, remote state 2)
> > console [netcon0] enabled
> > netconsole: network logging started
> > drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> > VFS: Cannot open root device "xvda" or unknown-block(0,0): error -6
> > Please append a correct "root=" boot option; here are the available
> > partitions:
> > Kernel panic - not syncing: VFS: Unable to mount root fs on
> > unknown-block(0,0)
> > CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.8 #5
> > Hardware name: XENVM-4.6 (DT)
> > Call trace:
> > [<ffffffc00008a0dc>] dump_backtrace+0x0/0x124
> > [<ffffffc00008a210>] show_stack+0x10/0x1c
> > [<ffffffc000657d88>] dump_stack+0x80/0xc4
> > [<ffffffc000656f04>] panic+0xe0/0x220
> > [<ffffffc00087eea8>] mount_block_root+0x1a4/0x24c
> > [<ffffffc00087f19c>] mount_root+0x110/0x130
> > [<ffffffc00087f328>] prepare_namespace+0x16c/0x1b8
> > [<ffffffc00087eb44>] kernel_init_freeable+0x1c4/0x1ec
> > [<ffffffc00065481c>] kernel_init+0xc/0xd8
> > ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on
> > unknown-block(0,0)
>
> It looks like the backend (QEMU) hasn't been initialized properly.
> Could you please post the output of xenstore-ls? Also could you run ps
> aux|grep qemu to check whether QEMU was spawned correctly?
>
>
> Attaching output of xenstore-ls and grep qemu.
> Looks like qemu process is getting spawned and running fine.
>
> I have also modified the config file to remove tap from disk like:
> disk = [ 'qcow:/mnt/xen/vivid-server-cloudimg-arm64-disk1.img,xvda,w' ]
> But still my DOMU booting is stuck and getting crashed due to lack of rootfs/disk.
>
> I am running this on mustang board.
QEMU has been spawn correctly, and I can see that it changed the
backend state to "2" (/local/domain/0/backend/qdisk/1/51712 in xenstore).
Similarly the frontend initialization has started as the frontend state
has been changed to "3".
However they should be both "4". So unless you manage to capture a
transient state, the communication between frontend and backend got
stuck. I don't know why.
Is there anything interesting in the QEMU logs (under /var/log/xen) ?
If not, I think you might have to build your own QEMU and add some
tracing, something like this:
diff --git a/hw/block/xen_disk.c b/hw/block/xen_disk.c
index 21842a0..e62c14d 100644
--- a/hw/block/xen_disk.c
+++ b/hw/block/xen_disk.c
@@ -755,6 +755,9 @@ static void blk_alloc(struct XenDevice *xendev)
{
struct XenBlkDev *blkdev = container_of(xendev, struct XenBlkDev, xendev);
+
+ printf("DEBUG %s %d\n",__func__,__LINE__);
+
QLIST_INIT(&blkdev->inflight);
QLIST_INIT(&blkdev->finished);
QLIST_INIT(&blkdev->freelist);
@@ -767,6 +770,9 @@ static void blk_alloc(struct XenDevice *xendev)
xen_be_printf(xendev, 0, "xc_gnttab_set_max_grants failed: %s\n",
strerror(errno));
}
+
+ printf("DEBUG %s %d\n",__func__,__LINE__);
+
}
static void blk_parse_discard(struct XenBlkDev *blkdev)
@@ -790,6 +796,7 @@ static int blk_init(struct XenDevice *xendev)
int info = 0;
char *directiosafe = NULL;
+ printf("DEBUG %s %d\n",__func__,__LINE__);
/* read xenstore entries */
if (blkdev->params == NULL) {
char *h = NULL;
@@ -853,6 +860,8 @@ static int blk_init(struct XenDevice *xendev)
blk_parse_discard(blkdev);
+ printf("DEBUG %s %d\n",__func__,__LINE__);
+
g_free(directiosafe);
return 0;
@@ -878,6 +887,8 @@ static int blk_connect(struct XenDevice *xendev)
int pers, index, qflags;
bool readonly = true;
+ printf("DEBUG %s %d\n",__func__,__LINE__);
+
/* read-only ? */
if (blkdev->directiosafe) {
qflags = BDRV_O_NOCACHE | BDRV_O_NATIVE_AIO;
@@ -1026,6 +1037,9 @@ static int blk_connect(struct XenDevice *xendev)
"remote port %d, local port %d\n",
blkdev->xendev.protocol, blkdev->ring_ref,
blkdev->xendev.remote_port, blkdev->xendev.local_port);
+
+ printf("DEBUG %s %d\n",__func__,__LINE__);
+
return 0;
}
@@ -1033,6 +1047,9 @@ static void blk_disconnect(struct XenDevice *xendev)
{
struct XenBlkDev *blkdev = container_of(xendev, struct XenBlkDev, xendev);
+
+ printf("DEBUG %s %d\n",__func__,__LINE__);
+
if (blkdev->blk) {
blk_detach_dev(blkdev->blk, blkdev);
blk_unref(blkdev->blk);
@@ -1083,6 +1100,9 @@ static int blk_free(struct XenDevice *xendev)
g_free(ioreq);
}
+
+ printf("DEBUG %s %d\n",__func__,__LINE__);
+
g_free(blkdev->params);
g_free(blkdev->mode);
g_free(blkdev->type);
^ permalink raw reply related [flat|nested] 14+ messages in thread
* Re: ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk
2015-06-03 10:15 ` Stefano Stabellini
@ 2015-06-03 11:12 ` Sanjeev Pandita
2015-06-03 11:50 ` Stefano Stabellini
0 siblings, 1 reply; 14+ messages in thread
From: Sanjeev Pandita @ 2015-06-03 11:12 UTC (permalink / raw)
To: Stefano Stabellini
Cc: Pranavkumar Sawargaonkar, Ian Campbell, Stefan Bader, xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 8549 bytes --]
Hi Stefano,
On Wed, Jun 3, 2015 at 3:45 PM, Stefano Stabellini <
stefano.stabellini@eu.citrix.com> wrote:
> On Wed, 3 Jun 2015, Sanjeev Pandita wrote:
> > On Tue, Jun 2, 2015 at 7:55 PM, Stefano Stabellini <
> stefano.stabellini@eu.citrix.com> wrote:
> > On Tue, 2 Jun 2015, Sanjeev Pandita wrote:
> > > From: Stefan Bader [mailto:stefan.bader@canonical.com]
> > > Sent: Tuesday, June 02, 2015 1:52 PM
> > > To: Sanjeev Pandita; xen-devel@lists.xen.org
> > > Cc: Ian.Campbell@citrix.com; Pranavkumar Sawargaonkar;
> > > stefano.stabellini@eu.citrix.com
> > > Subject: Re: [Xen-devel] ARM64: XEN Domu not booting with the
> qemu qcow
> > > AARCH64 Ubuntu 15.04 disk
> > >
> > > On 02.06.2015 09:40, Sanjeev Pandita wrote:
> > > > All,
> > > >
> > > > I am pretty new to xen . I am trying to boot DOMU with qemu
> qcow
> > > > AARCH64 Ubuntu 15.04 disk on Xen but I am getting the errors
> which
> > > > link to "/usr/local/lib/xen/bin/qemu-system-i386".
> > > > Since I am working on aarch64 system the
> > > > /usr/local/lib/xen/bin/qemu-system-i386 bin might not be
> present or
> > > > might not work as expected.
> > >
> > > Because I am lacking hardware and feedback, the arm64 packaging
> is a
> > > rather theoretical exercise. At least for armhf I thought
> qemu-system-x86
> > > was a dependency. That binary should provide x86 emulation on
> arm64, the
> > > same as one could install qemu for other arches on x86.
> > > Have you tried to install qemu-system-x86 manually?
> > >
> > > -Stefan
> > >
> > > >
> > > > Please let me know how to make the Qemu qcow image work on Xen.
> > > > Attached are the DomU boot log and config file.
> > > >
> > > > Thanks,
> > > > San
> > >
> > > Thanks for your inputs, I have installed the qemu-system-i386
> but my DomU
> > > booting is still crashing with following short logs. Am I
> missing anything
> > > ?
> > >
> > > Kernel Crash logs:
> > >
> > > xenbus_probe_frontend: Waiting for devices to initialise:
> > > 25s...20s...15s...10s...5s...0s...
> > >
> 235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s
> > >
> ...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...1
> > >
> 30s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75
> > >
> s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s.
> > > ..10s...5s...0s...
> > >
> > > xenbus_probe_frontend: Timeout connecting to device:
> device/vbd/51712
> > > (local state 3, remote state 2)
> > > console [netcon0] enabled
> > > netconsole: network logging started
> > > drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> > > VFS: Cannot open root device "xvda" or unknown-block(0,0): error
> -6
> > > Please append a correct "root=" boot option; here are the
> available
> > > partitions:
> > > Kernel panic - not syncing: VFS: Unable to mount root fs on
> > > unknown-block(0,0)
> > > CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.8 #5
> > > Hardware name: XENVM-4.6 (DT)
> > > Call trace:
> > > [<ffffffc00008a0dc>] dump_backtrace+0x0/0x124
> > > [<ffffffc00008a210>] show_stack+0x10/0x1c
> > > [<ffffffc000657d88>] dump_stack+0x80/0xc4
> > > [<ffffffc000656f04>] panic+0xe0/0x220
> > > [<ffffffc00087eea8>] mount_block_root+0x1a4/0x24c
> > > [<ffffffc00087f19c>] mount_root+0x110/0x130
> > > [<ffffffc00087f328>] prepare_namespace+0x16c/0x1b8
> > > [<ffffffc00087eb44>] kernel_init_freeable+0x1c4/0x1ec
> > > [<ffffffc00065481c>] kernel_init+0xc/0xd8
> > > ---[ end Kernel panic - not syncing: VFS: Unable to mount root
> fs on
> > > unknown-block(0,0)
> >
> > It looks like the backend (QEMU) hasn't been initialized properly.
> > Could you please post the output of xenstore-ls? Also could you run ps
> > aux|grep qemu to check whether QEMU was spawned correctly?
> >
> >
> > Attaching output of xenstore-ls and grep qemu.
> > Looks like qemu process is getting spawned and running fine.
> >
> > I have also modified the config file to remove tap from disk like:
> > disk = [ 'qcow:/mnt/xen/vivid-server-cloudimg-arm64-disk1.img,xvda,w' ]
> > But still my DOMU booting is stuck and getting crashed due to lack of
> rootfs/disk.
> >
> > I am running this on mustang board.
>
> QEMU has been spawn correctly, and I can see that it changed the
> backend state to "2" (/local/domain/0/backend/qdisk/1/51712 in xenstore).
>
> Similarly the frontend initialization has started as the frontend state
> has been changed to "3".
>
> However they should be both "4". So unless you manage to capture a
> transient state, the communication between frontend and backend got
> stuck. I don't know why.
>
> Is there anything interesting in the QEMU logs (under /var/log/xen) ?
>
>
I checked /var/log/xen. Here is the error message.
linux:/var/log/xen # cat qemu-dm-vm4.log
xen be: qdisk-51712: error: 'xvda' uses a qcow feature which is not
supported by this qemu version: QCOW version 2
xen be: qdisk-51712: initialise() failed
Thanks,
San
> If not, I think you might have to build your own QEMU and add some
> tracing, something like this:
>
>
> diff --git a/hw/block/xen_disk.c b/hw/block/xen_disk.c
> index 21842a0..e62c14d 100644
> --- a/hw/block/xen_disk.c
> +++ b/hw/block/xen_disk.c
> @@ -755,6 +755,9 @@ static void blk_alloc(struct XenDevice *xendev)
> {
> struct XenBlkDev *blkdev = container_of(xendev, struct XenBlkDev,
> xendev);
>
> +
> + printf("DEBUG %s %d\n",__func__,__LINE__);
> +
> QLIST_INIT(&blkdev->inflight);
> QLIST_INIT(&blkdev->finished);
> QLIST_INIT(&blkdev->freelist);
> @@ -767,6 +770,9 @@ static void blk_alloc(struct XenDevice *xendev)
> xen_be_printf(xendev, 0, "xc_gnttab_set_max_grants failed: %s\n",
> strerror(errno));
> }
> +
> + printf("DEBUG %s %d\n",__func__,__LINE__);
> +
> }
>
> static void blk_parse_discard(struct XenBlkDev *blkdev)
> @@ -790,6 +796,7 @@ static int blk_init(struct XenDevice *xendev)
> int info = 0;
> char *directiosafe = NULL;
>
> + printf("DEBUG %s %d\n",__func__,__LINE__);
> /* read xenstore entries */
> if (blkdev->params == NULL) {
> char *h = NULL;
> @@ -853,6 +860,8 @@ static int blk_init(struct XenDevice *xendev)
>
> blk_parse_discard(blkdev);
>
> + printf("DEBUG %s %d\n",__func__,__LINE__);
> +
> g_free(directiosafe);
> return 0;
>
> @@ -878,6 +887,8 @@ static int blk_connect(struct XenDevice *xendev)
> int pers, index, qflags;
> bool readonly = true;
>
> + printf("DEBUG %s %d\n",__func__,__LINE__);
> +
> /* read-only ? */
> if (blkdev->directiosafe) {
> qflags = BDRV_O_NOCACHE | BDRV_O_NATIVE_AIO;
> @@ -1026,6 +1037,9 @@ static int blk_connect(struct XenDevice *xendev)
> "remote port %d, local port %d\n",
> blkdev->xendev.protocol, blkdev->ring_ref,
> blkdev->xendev.remote_port, blkdev->xendev.local_port);
> +
> + printf("DEBUG %s %d\n",__func__,__LINE__);
> +
> return 0;
> }
>
> @@ -1033,6 +1047,9 @@ static void blk_disconnect(struct XenDevice *xendev)
> {
> struct XenBlkDev *blkdev = container_of(xendev, struct XenBlkDev,
> xendev);
>
> +
> + printf("DEBUG %s %d\n",__func__,__LINE__);
> +
> if (blkdev->blk) {
> blk_detach_dev(blkdev->blk, blkdev);
> blk_unref(blkdev->blk);
> @@ -1083,6 +1100,9 @@ static int blk_free(struct XenDevice *xendev)
> g_free(ioreq);
> }
>
> +
> + printf("DEBUG %s %d\n",__func__,__LINE__);
> +
> g_free(blkdev->params);
> g_free(blkdev->mode);
> g_free(blkdev->type);
>
--
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and contains information
that is confidential and proprietary to Applied Micro Circuits Corporation
or its subsidiaries.
It is to be used solely for the purpose of furthering the parties' business
relationship.
All unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by reply
e-mail
and destroy all copies of the original message.
[-- Attachment #1.2: Type: text/html, Size: 10856 bytes --]
[-- Attachment #2: 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] 14+ messages in thread
* Re: ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk
2015-06-03 11:12 ` Sanjeev Pandita
@ 2015-06-03 11:50 ` Stefano Stabellini
2015-06-09 6:39 ` Sanjeev Pandita
0 siblings, 1 reply; 14+ messages in thread
From: Stefano Stabellini @ 2015-06-03 11:50 UTC (permalink / raw)
To: Sanjeev Pandita
Cc: xen-devel, Pranavkumar Sawargaonkar, Ian Campbell, Stefan Bader,
Stefano Stabellini
[-- Attachment #1: Type: text/plain, Size: 6425 bytes --]
On Wed, 3 Jun 2015, Sanjeev Pandita wrote:
> Hi Stefano,
>
> On Wed, Jun 3, 2015 at 3:45 PM, Stefano Stabellini <stefano.stabellini@eu.citrix.com> wrote:
> On Wed, 3 Jun 2015, Sanjeev Pandita wrote:
> > On Tue, Jun 2, 2015 at 7:55 PM, Stefano Stabellini <stefano.stabellini@eu.citrix.com> wrote:
> > On Tue, 2 Jun 2015, Sanjeev Pandita wrote:
> > > From: Stefan Bader [mailto:stefan.bader@canonical.com]
> > > Sent: Tuesday, June 02, 2015 1:52 PM
> > > To: Sanjeev Pandita; xen-devel@lists.xen.org
> > > Cc: Ian.Campbell@citrix.com; Pranavkumar Sawargaonkar;
> > > stefano.stabellini@eu.citrix.com
> > > Subject: Re: [Xen-devel] ARM64: XEN Domu not booting with the qemu qcow
> > > AARCH64 Ubuntu 15.04 disk
> > >
> > > On 02.06.2015 09:40, Sanjeev Pandita wrote:
> > > > All,
> > > >
> > > > I am pretty new to xen . I am trying to boot DOMU with qemu qcow
> > > > AARCH64 Ubuntu 15.04 disk on Xen but I am getting the errors which
> > > > link to "/usr/local/lib/xen/bin/qemu-system-i386".
> > > > Since I am working on aarch64 system the
> > > > /usr/local/lib/xen/bin/qemu-system-i386 bin might not be present or
> > > > might not work as expected.
> > >
> > > Because I am lacking hardware and feedback, the arm64 packaging is a
> > > rather theoretical exercise. At least for armhf I thought qemu-system-x86
> > > was a dependency. That binary should provide x86 emulation on arm64, the
> > > same as one could install qemu for other arches on x86.
> > > Have you tried to install qemu-system-x86 manually?
> > >
> > > -Stefan
> > >
> > > >
> > > > Please let me know how to make the Qemu qcow image work on Xen.
> > > > Attached are the DomU boot log and config file.
> > > >
> > > > Thanks,
> > > > San
> > >
> > > Thanks for your inputs, I have installed the qemu-system-i386 but my DomU
> > > booting is still crashing with following short logs. Am I missing anything
> > > ?
> > >
> > > Kernel Crash logs:
> > >
> > > xenbus_probe_frontend: Waiting for devices to initialise:
> > > 25s...20s...15s...10s...5s...0s...
> > > 235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s
> > > ...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...1
> > > 30s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75
> > > s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s.
> > > ..10s...5s...0s...
> > >
> > > xenbus_probe_frontend: Timeout connecting to device: device/vbd/51712
> > > (local state 3, remote state 2)
> > > console [netcon0] enabled
> > > netconsole: network logging started
> > > drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> > > VFS: Cannot open root device "xvda" or unknown-block(0,0): error -6
> > > Please append a correct "root=" boot option; here are the available
> > > partitions:
> > > Kernel panic - not syncing: VFS: Unable to mount root fs on
> > > unknown-block(0,0)
> > > CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.8 #5
> > > Hardware name: XENVM-4.6 (DT)
> > > Call trace:
> > > [<ffffffc00008a0dc>] dump_backtrace+0x0/0x124
> > > [<ffffffc00008a210>] show_stack+0x10/0x1c
> > > [<ffffffc000657d88>] dump_stack+0x80/0xc4
> > > [<ffffffc000656f04>] panic+0xe0/0x220
> > > [<ffffffc00087eea8>] mount_block_root+0x1a4/0x24c
> > > [<ffffffc00087f19c>] mount_root+0x110/0x130
> > > [<ffffffc00087f328>] prepare_namespace+0x16c/0x1b8
> > > [<ffffffc00087eb44>] kernel_init_freeable+0x1c4/0x1ec
> > > [<ffffffc00065481c>] kernel_init+0xc/0xd8
> > > ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on
> > > unknown-block(0,0)
> >
> > It looks like the backend (QEMU) hasn't been initialized properly.
> > Could you please post the output of xenstore-ls? Also could you run ps
> > aux|grep qemu to check whether QEMU was spawned correctly?
> >
> >
> > Attaching output of xenstore-ls and grep qemu.
> > Looks like qemu process is getting spawned and running fine.
> >
> > I have also modified the config file to remove tap from disk like:
> > disk = [ 'qcow:/mnt/xen/vivid-server-cloudimg-arm64-disk1.img,xvda,w' ]
> > But still my DOMU booting is stuck and getting crashed due to lack of rootfs/disk.
> >
> > I am running this on mustang board.
>
> QEMU has been spawn correctly, and I can see that it changed the
> backend state to "2" (/local/domain/0/backend/qdisk/1/51712 in xenstore).
>
> Similarly the frontend initialization has started as the frontend state
> has been changed to "3".
>
> However they should be both "4". So unless you manage to capture a
> transient state, the communication between frontend and backend got
> stuck. I don't know why.
>
> Is there anything interesting in the QEMU logs (under /var/log/xen) ?
>
>
>
> I checked /var/log/xen. Here is the error message.
>
> linux:/var/log/xen # cat qemu-dm-vm4.log
> xen be: qdisk-51712: error: 'xvda' uses a qcow feature which is not supported by this qemu version: QCOW version 2
> xen be: qdisk-51712: initialise() failed
All right, maybe you just need to specify:
disk = ['tap:qcow2:/mnt/xen/vivid-server-cloudimg-arm64-disk1.img,xvda,w']
?
[-- Attachment #2: 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] 14+ messages in thread
* Re: ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk
2015-06-03 11:50 ` Stefano Stabellini
@ 2015-06-09 6:39 ` Sanjeev Pandita
0 siblings, 0 replies; 14+ messages in thread
From: Sanjeev Pandita @ 2015-06-09 6:39 UTC (permalink / raw)
To: Stefano Stabellini
Cc: Pranavkumar Sawargaonkar, Ian Campbell, Stefan Bader, xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 7072 bytes --]
Hi,
On Wed, Jun 3, 2015 at 5:20 PM, Stefano Stabellini <
stefano.stabellini@eu.citrix.com> wrote:
> On Wed, 3 Jun 2015, Sanjeev Pandita wrote:
> > Hi Stefano,
> >
> > On Wed, Jun 3, 2015 at 3:45 PM, Stefano Stabellini <
> stefano.stabellini@eu.citrix.com> wrote:
> > On Wed, 3 Jun 2015, Sanjeev Pandita wrote:
> > > On Tue, Jun 2, 2015 at 7:55 PM, Stefano Stabellini <
> stefano.stabellini@eu.citrix.com> wrote:
> > > On Tue, 2 Jun 2015, Sanjeev Pandita wrote:
> > > > From: Stefan Bader [mailto:stefan.bader@canonical.com]
> > > > Sent: Tuesday, June 02, 2015 1:52 PM
> > > > To: Sanjeev Pandita; xen-devel@lists.xen.org
> > > > Cc: Ian.Campbell@citrix.com; Pranavkumar Sawargaonkar;
> > > > stefano.stabellini@eu.citrix.com
> > > > Subject: Re: [Xen-devel] ARM64: XEN Domu not booting
> with the qemu qcow
> > > > AARCH64 Ubuntu 15.04 disk
> > > >
> > > > On 02.06.2015 09:40, Sanjeev Pandita wrote:
> > > > > All,
> > > > >
> > > > > I am pretty new to xen . I am trying to boot DOMU with
> qemu qcow
> > > > > AARCH64 Ubuntu 15.04 disk on Xen but I am getting the
> errors which
> > > > > link to "/usr/local/lib/xen/bin/qemu-system-i386".
> > > > > Since I am working on aarch64 system the
> > > > > /usr/local/lib/xen/bin/qemu-system-i386 bin might not
> be present or
> > > > > might not work as expected.
> > > >
> > > > Because I am lacking hardware and feedback, the arm64
> packaging is a
> > > > rather theoretical exercise. At least for armhf I
> thought qemu-system-x86
> > > > was a dependency. That binary should provide x86
> emulation on arm64, the
> > > > same as one could install qemu for other arches on x86.
> > > > Have you tried to install qemu-system-x86 manually?
> > > >
> > > > -Stefan
> > > >
> > > > >
> > > > > Please let me know how to make the Qemu qcow image
> work on Xen.
> > > > > Attached are the DomU boot log and config file.
> > > > >
> > > > > Thanks,
> > > > > San
> > > >
> > > > Thanks for your inputs, I have installed the
> qemu-system-i386 but my DomU
> > > > booting is still crashing with following short logs. Am
> I missing anything
> > > > ?
> > > >
> > > > Kernel Crash logs:
> > > >
> > > > xenbus_probe_frontend: Waiting for devices to initialise:
> > > > 25s...20s...15s...10s...5s...0s...
> > > >
> 235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s
> > > >
> ...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...1
> > > >
> 30s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75
> > > >
> s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s.
> > > > ..10s...5s...0s...
> > > >
> > > > xenbus_probe_frontend: Timeout connecting to device:
> device/vbd/51712
> > > > (local state 3, remote state 2)
> > > > console [netcon0] enabled
> > > > netconsole: network logging started
> > > > drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> > > > VFS: Cannot open root device "xvda" or
> unknown-block(0,0): error -6
> > > > Please append a correct "root=" boot option; here are
> the available
> > > > partitions:
> > > > Kernel panic - not syncing: VFS: Unable to mount root fs
> on
> > > > unknown-block(0,0)
> > > > CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.8 #5
> > > > Hardware name: XENVM-4.6 (DT)
> > > > Call trace:
> > > > [<ffffffc00008a0dc>] dump_backtrace+0x0/0x124
> > > > [<ffffffc00008a210>] show_stack+0x10/0x1c
> > > > [<ffffffc000657d88>] dump_stack+0x80/0xc4
> > > > [<ffffffc000656f04>] panic+0xe0/0x220
> > > > [<ffffffc00087eea8>] mount_block_root+0x1a4/0x24c
> > > > [<ffffffc00087f19c>] mount_root+0x110/0x130
> > > > [<ffffffc00087f328>] prepare_namespace+0x16c/0x1b8
> > > > [<ffffffc00087eb44>] kernel_init_freeable+0x1c4/0x1ec
> > > > [<ffffffc00065481c>] kernel_init+0xc/0xd8
> > > > ---[ end Kernel panic - not syncing: VFS: Unable to
> mount root fs on
> > > > unknown-block(0,0)
> > >
> > > It looks like the backend (QEMU) hasn't been initialized
> properly.
> > > Could you please post the output of xenstore-ls? Also could you
> run ps
> > > aux|grep qemu to check whether QEMU was spawned correctly?
> > >
> > >
> > > Attaching output of xenstore-ls and grep qemu.
> > > Looks like qemu process is getting spawned and running fine.
> > >
> > > I have also modified the config file to remove tap from disk
> like:
> > > disk = [
> 'qcow:/mnt/xen/vivid-server-cloudimg-arm64-disk1.img,xvda,w' ]
> > > But still my DOMU booting is stuck and getting crashed due to
> lack of rootfs/disk.
> > >
> > > I am running this on mustang board.
> >
> > QEMU has been spawn correctly, and I can see that it changed the
> > backend state to "2" (/local/domain/0/backend/qdisk/1/51712 in xenstore).
> >
> > Similarly the frontend initialization has started as the frontend state
> > has been changed to "3".
> >
> > However they should be both "4". So unless you manage to capture a
> > transient state, the communication between frontend and backend got
> > stuck. I don't know why.
> >
> > Is there anything interesting in the QEMU logs (under /var/log/xen) ?
> >
> >
> >
> > I checked /var/log/xen. Here is the error message.
> >
> > linux:/var/log/xen # cat qemu-dm-vm4.log
> > xen be: qdisk-51712: error: 'xvda' uses a qcow feature which is not
> supported by this qemu version: QCOW version 2
> > xen be: qdisk-51712: initialise() failed
>
> All right, maybe you just need to specify:
>
> disk = ['tap:qcow2:/mnt/xen/vivid-server-cloudimg-arm64-disk1.img,xvda,w']
>
> ?
qcow2 is working fine on Mustang :).
Sorry for the delayed reply .
Thanks for helping me out.
Regards,
Sanjeev
--
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and contains information
that is confidential and proprietary to Applied Micro Circuits Corporation
or its subsidiaries.
It is to be used solely for the purpose of furthering the parties' business
relationship.
All unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by reply
e-mail
and destroy all copies of the original message.
[-- Attachment #1.2: Type: text/html, Size: 9220 bytes --]
[-- Attachment #2: 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] 14+ messages in thread
end of thread, other threads:[~2015-06-09 6:39 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-06-02 7:40 ARM64: XEN Domu not booting with the qemu qcow AARCH64 Ubuntu 15.04 disk Sanjeev Pandita
2015-06-02 8:22 ` Stefan Bader
2015-06-02 10:32 ` Stefano Stabellini
2015-06-02 10:35 ` Stefano Stabellini
2015-06-02 10:58 ` Stefan Bader
2015-06-02 11:28 ` Stefano Stabellini
2015-06-02 12:09 ` Sanjeev Pandita
2015-06-02 12:41 ` Stefan Bader
2015-06-02 14:25 ` Stefano Stabellini
2015-06-03 8:31 ` Sanjeev Pandita
2015-06-03 10:15 ` Stefano Stabellini
2015-06-03 11:12 ` Sanjeev Pandita
2015-06-03 11:50 ` Stefano Stabellini
2015-06-09 6:39 ` Sanjeev Pandita
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.