Hi, I have a couple of basic questions regarding the Xen on ARM (with virtualization extensions). It probably falls under WIP but i thought i''ll ask anyway. 1. Using the current unstable Xen on ARM code is it possible to virtualize network, usb, sata and things like that? I looked at the wiki pages for Arndale, VExpress but could not figure out whether this is supported right now. If not, are there any patches that i can try out? After going through the recent talk from Stefano [1] i got the impression getting network and SATA requires SWIOTLB support. Is that correct? 2. For domU to see the network and SATA interfaces is the DTB supposed to be updated? Is there some guideline on how to do this? Do i just add in the nodes similar to dom0? Right now i have an OMAP5 dom0 with network+usb support and i am trying to figure out how to get these things in domU and hence the questions. If these things are already answered somewhere and i missed it please point me to it :) Regards, Vaibhav [1] http://www.youtube.com/watch?v=Xa33qR0Zopo
On Mon, 2013-11-18 at 13:57 -0500, Vaibhav Bedia wrote:> Hi, > > I have a couple of basic questions regarding the Xen on ARM (with > virtualization extensions). It probably falls under WIP but i thought > i''ll ask anyway. > > 1. Using the current unstable Xen on ARM code is it possible to > virtualize network, usb, sata and things like that? I looked at the > wiki pages for Arndale, VExpress but could not figure out whether this > is supported right now. If not, are there any patches that i can > try out?Xen on ARM does not expose real USB/SATA/network etc to the guests/domU. All of the physical devices are exposed only to dom0 which in turn provides "paravirtualised" virtual devices for disk, network and console which are exposed to the guest. There is currently no PV usb for Xen on ARM, although there is some work ongoing on x86 which may be reuseable. Eventually we will also support physical device passthrough which would allow you to dedicate each device (USB controller, SATA controller, NIC etc) to a single guest.> After going through the recent talk from Stefano [1] i got > the impression getting network and SATA requires SWIOTLB support. Is > that correct?The SWIOTLB or an IOMMU/SMMU is necessary for dom0 to drive the physical devices and provide the virtual interfaces to the guests. Device passthrough will only be supported with an IOMMU/SMMU.> 2. For domU to see the network and SATA interfaces is the DTB supposed > to be updated? Is there some guideline on how to do this? Do i just > add in the nodes similar to dom0?Hopefully the above has made this question moot.> Right now i have an OMAP5 dom0 with network+usb support and i am > trying to figure out how to get these things in domU and hence the > questions.You need blkback and netback in dom0 and blkfront and netfront in domU (all in mainline Linux). Then you need to add vif and disk options to your guest configuration. Ian.
Hi Ian, Sorry for the delayed response. I was struggling with some dom0 crashes when i migrated to v3.12 based kernel. On Tue, Nov 19, 2013 at 6:20 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:> On Mon, 2013-11-18 at 13:57 -0500, Vaibhav Bedia wrote: >> Hi, >> >> I have a couple of basic questions regarding the Xen on ARM (with >> virtualization extensions). It probably falls under WIP but i thought >> i''ll ask anyway. >> >> 1. Using the current unstable Xen on ARM code is it possible to >> virtualize network, usb, sata and things like that? I looked at the >> wiki pages for Arndale, VExpress but could not figure out whether this >> is supported right now. If not, are there any patches that i can >> try out? > > Xen on ARM does not expose real USB/SATA/network etc to the guests/domU. > > All of the physical devices are exposed only to dom0 which in turn > provides "paravirtualised" virtual devices for disk, network and console > which are exposed to the guest. > > There is currently no PV usb for Xen on ARM, although there is some work > ongoing on x86 which may be reuseable. > > Eventually we will also support physical device passthrough which would > allow you to dedicate each device (USB controller, SATA controller, NIC > etc) to a single guest. >Ok. Thanks for the clarification.>> After going through the recent talk from Stefano [1] i got >> the impression getting network and SATA requires SWIOTLB support. Is >> that correct? > > The SWIOTLB or an IOMMU/SMMU is necessary for dom0 to drive the physical > devices and provide the virtual interfaces to the guests. > > Device passthrough will only be supported with an IOMMU/SMMU. >So on SoCs like OMAP5 which don''t have an IOMMU device passthrough won''t be supported? Or it can be done via SWIOTLB if someone works on it?>> 2. For domU to see the network and SATA interfaces is the DTB supposed >> to be updated? Is there some guideline on how to do this? Do i just >> add in the nodes similar to dom0? > > Hopefully the above has made this question moot. >Yes.>> Right now i have an OMAP5 dom0 with network+usb support and i am >> trying to figure out how to get these things in domU and hence the >> questions. > > You need blkback and netback in dom0 and blkfront and netfront in domU > (all in mainline Linux). Then you need to add vif and disk options to > your guest configuration. >I enabled both of the options and can get a ramdisk based domU running fine. I tried a Ubuntu based fs for domU but can''t get to the login prompt for some reason. I tried out the various options mentioned @ http://wiki.xen.org/wiki/Xen_Common_Problems#Console and some other things mentioned on various forums but nothing seems to work :( Any hints on where things could be going wrong? I have hvc0.conf under /etc/init/ On the networking front, i setup the brigde in dom0 and verified that i can ping external hosts. However there''s some issue with the whole thing since domU can get an ip address but still can''t ping the outside world. Switching back to dom0 the network seems to eventually die and at times dom0 becomes totally unresponsive :( Regards, Vaibhav
On Fri, 2013-11-22 at 10:05 -0500, Vaibhav Bedia wrote:> >> After going through the recent talk from Stefano [1] i got > >> the impression getting network and SATA requires SWIOTLB support. Is > >> that correct? > > > > The SWIOTLB or an IOMMU/SMMU is necessary for dom0 to drive the physical > > devices and provide the virtual interfaces to the guests. > > > > Device passthrough will only be supported with an IOMMU/SMMU. > > > > So on SoCs like OMAP5 which don''t have an IOMMU device passthrough won''t be > supported? Or it can be done via SWIOTLB if someone works on it?I''m not in favour of supporting this. It''s a big can of worms wrt security.> >> Right now i have an OMAP5 dom0 with network+usb support and i am > >> trying to figure out how to get these things in domU and hence the > >> questions. > > > > You need blkback and netback in dom0 and blkfront and netfront in domU > > (all in mainline Linux). Then you need to add vif and disk options to > > your guest configuration. > > > > I enabled both of the options and can get a ramdisk based domU running fine. > I tried a Ubuntu based fs for domU but can''t get to the login prompt > for some reason. > I tried out the various options mentioned @ > http://wiki.xen.org/wiki/Xen_Common_Problems#Console > and some other things mentioned on various forums but nothing seems to work :( > Any hints on where things could be going wrong? I have hvc0.conf under > /etc/init/Do you have CONFIG_HVC_XEN enabled in the guest kernel config? Is the guest detecting that it is running under Xen? Can you post a guest dmesg please.> On the networking front, i setup the brigde in dom0 and verified that i can ping > external hosts. However there''s some issue with the whole thing since domU > can get an ip address but still can''t ping the outside world. Switching back to > dom0 the network seems to eventually die and at times dom0 becomes totally > unresponsive :(Is the domU getting an IP address via DHCP or some other method? Have you confirmed that the vif is added to the bridge? Do you have any firewalls setup in dom0? What do you mean by "switching back to dom0"? Ian.
Hi Ian, On Fri, Nov 22, 2013 at 10:22 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:> On Fri, 2013-11-22 at 10:05 -0500, Vaibhav Bedia wrote: >> >> After going through the recent talk from Stefano [1] i got >> >> the impression getting network and SATA requires SWIOTLB support. Is >> >> that correct? >> > >> > The SWIOTLB or an IOMMU/SMMU is necessary for dom0 to drive the physical >> > devices and provide the virtual interfaces to the guests. >> > >> > Device passthrough will only be supported with an IOMMU/SMMU. >> > >> >> So on SoCs like OMAP5 which don''t have an IOMMU device passthrough won''t be >> supported? Or it can be done via SWIOTLB if someone works on it? > > I''m not in favour of supporting this. It''s a big can of worms wrt > security. >Ok. I''ll leave it to the experts then :)>> >> Right now i have an OMAP5 dom0 with network+usb support and i am >> >> trying to figure out how to get these things in domU and hence the >> >> questions. >> > >> > You need blkback and netback in dom0 and blkfront and netfront in domU >> > (all in mainline Linux). Then you need to add vif and disk options to >> > your guest configuration. >> > >> >> I enabled both of the options and can get a ramdisk based domU running fine. >> I tried a Ubuntu based fs for domU but can''t get to the login prompt >> for some reason. >> I tried out the various options mentioned @ >> http://wiki.xen.org/wiki/Xen_Common_Problems#Console >> and some other things mentioned on various forums but nothing seems to work :( >> Any hints on where things could be going wrong? I have hvc0.conf under >> /etc/init/ > > Do you have CONFIG_HVC_XEN enabled in the guest kernel config? Is the > guest detecting that it is running under Xen? Can you post a guest dmesg > please. >Yes. It''s enabled. I can get the same image to the login prompt using a minimal ramdisk so it should be something to do with the Ubuntu filesystem, right? Guest bootlog in both the cases at the end.>> On the networking front, i setup the brigde in dom0 and verified that i can ping >> external hosts. However there''s some issue with the whole thing since domU >> can get an ip address but still can''t ping the outside world. Switching back to >> dom0 the network seems to eventually die and at times dom0 becomes totally >> unresponsive :( > > Is the domU getting an IP address via DHCP or some other method? Have > you confirmed that the vif is added to the bridge? Do you have any > firewalls setup in dom0? >The IP address is via DHCP. Once i get the login prompt using the minimal ramdisk i run $ ifconfig eth0 up <eth0 mac address is what i assign in the config file> $ udhcpc Guest gets an IP address now. The above sequence doesn''t work always but when it does get an IP address i can''t ping domU or have it ping some other host. I didn''t setup any firewall explicitly - just using plain ubuntu 13.04. I do see that the vif is added to the bridge. I also noticed that the errrors under eth0 starts going up when i create a guest and eventually the network in dom0 becomes completely unresponsive. root@arm:~# ifconfig eth0 Link encap:Ethernet HWaddr c6:e9:ba:c5:73:fe UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:637 errors:0 dropped:0 overruns:0 frame:0 TX packets:434 errors:180 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:56685 (56.6 KB) TX bytes:68582 (68.5 KB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:15 errors:0 dropped:0 overruns:0 frame:0 TX packets:15 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1924 (1.9 KB) TX bytes:1924 (1.9 KB) vif4.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) vif4.1 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) xenbr0 Link encap:Ethernet HWaddr c6:e9:ba:c5:73:fe inet addr:192.168.1.159 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:716 errors:0 dropped:0 overruns:0 frame:0 TX packets:535 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:83341 (83.3 KB) TX bytes:69860 (69.8 KB) root@arm:~#> What do you mean by "switching back to dom0"?Using "Ctrl + ]" to get back to the dom0 console. Regards, Vaibhav P.S. Apologies for the flood of seemingly random datapoints. As you can see i am right now a total newbie to xen and trying to find my way around :) ================ Guest bootlog with Ubuntu fs: == root@arm:~# xl console domU-xen [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 3.12.0-01110-g0c72f67-dirty (vaibhav@vaibhav-VirtualBox) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #13 [ 0.000000] CPU: ARMv7 Processor [412fc0f2] revision 2 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache [ 0.000000] Machine: Dummy Virtual Machine, model: XENVM-4.2 [ 0.000000] cma: CMA: reserved 16 MiB at 87000000 [ 0.000000] Memory policy: ECC disabled, Data cache writealloc [ 0.000000] PERCPU: Embedded 9 pages/cpu @c0ff4000 s15232 r8192 d13440 u36864 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 [ 0.000000] Kernel command line: console=hvc0 root=/dev/xvda mem=128M xencons=tty [ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes) [ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [ 0.000000] Memory: 98176K/131072K available (6191K kernel code, 653K rwdata, 2444K rodata, 414K init, 5549K bss, 32896K reserved, 0K hig) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) [ 0.000000] vmalloc : 0xc8800000 - 0xff000000 ( 872 MB) [ 0.000000] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) [ 0.000000] .text : 0xc0008000 - 0xc0876ec8 (8636 kB) [ 0.000000] .init : 0xc0877000 - 0xc08deb80 ( 415 kB) [ 0.000000] .data : 0xc08e0000 - 0xc09837b0 ( 654 kB) [ 0.000000] .bss : 0xc09837b0 - 0xc0eeefa0 (5550 kB) [ 0.000000] Hierarchical RCU implementation. [ 0.000000] RCU restricting CPUs from NR_CPUS=2 to nr_cpu_ids=1. [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] Architected cp15 timer(s) running at 6.14MHz (virt). [ 0.000000] Switching to timer-based delay loop [ 0.000000] sched_clock: ARM arch timer >56 bits at 6144kHz, resolution 162ns [ 0.000000] sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms [ 0.000000] Console: colour dummy device 80x30 [ 0.000000] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar [ 0.000000] ... MAX_LOCKDEP_SUBCLASSES: 8 [ 0.000000] ... MAX_LOCK_DEPTH: 48 [ 0.000000] ... MAX_LOCKDEP_KEYS: 8191 [ 0.000000] ... CLASSHASH_SIZE: 4096 [ 0.000000] ... MAX_LOCKDEP_ENTRIES: 16384 [ 0.000000] ... MAX_LOCKDEP_CHAINS: 32768 [ 0.000000] ... CHAINHASH_SIZE: 16384 [ 0.000000] memory used by lock dependency info: 3695 kB [ 0.000000] per task-struct memory footprint: 1152 bytes [ 2.851292] Calibrating delay loop (skipped), value calculated using timer frequency.. 12.28 BogoMIPS (lpj=61440) [ 2.864518] pid_max: default: 32768 minimum: 301 [ 2.867933] Security Framework initialized [ 2.901598] Mount-cache hash table entries: 512 [ 2.903860] CPU: Testing write buffer coherency: ok [ 2.912816] /cpus/cpu@0 missing clock-frequency property [ 2.917659] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 2.923399] Setting up static identity map for 0xc05dd0c8 - 0xc05dd120 [ 2.926913] Brought up 1 CPUs [ 2.930817] SMP: Total of 1 processors activated. [ 2.964571] CPU: All CPU(s) started in SVC mode. [ 2.968430] devtmpfs: initialized [ 2.969744] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0 [ 2.982276] Xen 4.2 support found, events_irq=31 gnttab_frame_pfn=b0000 [ 2.987497] xen:grant_table: Grant tables using version 1 layout [ 2.990086] Grant table initialized [ 2.997091] pinctrl core: initialized pinctrl subsystem [ 3.002420] regulator-dummy: no parameters [ 3.007333] NET: Registered protocol family 16 [ 3.010174] Xen: initializing cpu0 [ 3.019925] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 3.087320] xenbus: xs_reset_watches failed: -38 [ 3.091308] No ATAGs? [ 3.099246] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 3.104285] hw-breakpoint: maximum watchpoint size is 8 bytes. [ 3.205923] bio: create slab <bio-0> at 0 [ 3.215442] edma-dma-engine edma-dma-engine.0: Can''t allocate PaRAM dummy slot [ 3.221698] edma-dma-engine: probe of edma-dma-engine.0 failed with error -5 [ 3.226268] xen:balloon: Initialising balloon driver [ 3.294102] vgaarb: loaded [ 3.298552] SCSI subsystem initialized [ 3.307918] usbcore: registered new interface driver usbfs [ 3.312552] usbcore: registered new interface driver hub [ 3.317062] usbcore: registered new device driver usb [ 3.326151] Switched to clocksource arch_sys_counter [ 3.504507] NET: Registered protocol family 2 [ 3.511688] TCP established hash table entries: 1024 (order: 1, 8192 bytes) [ 3.517328] TCP bind hash table entries: 1024 (order: 3, 36864 bytes) [ 3.523017] TCP: Hash tables configured (established 1024 bind 1024) [ 3.525434] TCP: reno registered [ 3.560495] UDP hash table entries: 256 (order: 2, 20480 bytes) [ 3.566147] UDP-Lite hash table entries: 256 (order: 2, 20480 bytes) [ 3.570428] NET: Registered protocol family 1 [ 3.576396] RPC: Registered named UNIX socket transport module. [ 3.580287] RPC: Registered udp transport module. [ 3.584195] RPC: Registered tcp transport module. [ 3.589843] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 3.629628] NetWinder Floating Point Emulator V0.97 (double precision) [ 3.831976] VFS: Disk quotas dquot_6.5.2 [ 3.867554] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 3.873091] NFS: Registering the id_resolver key type [ 3.876576] Key type id_resolver registered [ 3.879788] Key type id_legacy registered [ 3.886048] jffs2: version 2.2. (NAND) (SUMMARY) ?© 2001-2006 Red Hat, Inc. [ 3.889148] msgmni has been set to 223 [ 3.894965] io scheduler noop registered [ 3.928370] io scheduler deadline registered [ 3.932241] io scheduler cfq registered (default) [ 3.945075] xen:xen_evtchn: Event-channel device installed [ 4.074520] console [hvc0] enabled [ 4.080780] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 4.101525] brd: module loaded [ 4.112806] loop: module loaded [ 4.149901] mtdoops: mtd device (mtddev=name/number) must be supplied [ 4.159703] xen_netfront: Initialising Xen virtual ethernet driver [ 4.244282] usbcore: registered new interface driver asix [ 4.249711] usbcore: registered new interface driver ax88179_178a [ 4.254883] usbcore: registered new interface driver cdc_ether [ 4.259682] usbcore: registered new interface driver r815x [ 4.264812] usbcore: registered new interface driver smsc95xx [ 4.269799] usbcore: registered new interface driver net1080 [ 4.275078] usbcore: registered new interface driver cdc_subset [ 4.279963] usbcore: registered new interface driver zaurus [ 4.285125] usbcore: registered new interface driver cdc_ncm [ 4.292446] ehci_hcd: USB 2.0 ''Enhanced'' Host Controller (EHCI) Driver [ 4.296077] ehci-pci: EHCI PCI platform driver [ 4.330628] ehci-omap: OMAP-EHCI Host Controller driver [ 4.336684] usbcore: registered new interface driver cdc_wdm [ 4.342022] usbcore: registered new interface driver usb-storage [ 4.347093] usbcore: registered new interface driver usbtest [ 4.353470] mousedev: PS/2 mouse device common for all mice [ 4.359595] i2c /dev entries driver [ 4.424040] Driver for 1-wire Dallas network protocol. [ 4.433012] ledtrig-cpu: registered to indicate activity on CPUs [ 4.439117] usbcore: registered new interface driver usbhid [ 4.442151] usbhid: USB HID core driver [ 4.447549] oprofile: no performance counters [ 4.452162] oprofile: using timer interrupt. [ 4.484857] TCP: cubic registered [ 4.488328] Initializing XFRM netlink socket [ 4.491980] NET: Registered protocol family 17 [ 4.495635] NET: Registered protocol family 15 [ 4.498936] Bridge firewalling registered [ 4.502394] 8021q: 802.1Q VLAN Support v1.8 [ 4.505874] Key type dns_resolver registered [ 4.509339] ThumbEE CPU extension supported. [ 4.513329] Registering SWP/SWPB emulation handler [ 4.587776] blkfront: xvda: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled; [ 4.600643] xvda: unknown partition table [ 4.742512] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 4.754670] EXT3-fs (xvda): error: couldn''t mount because of unsupported optional features (240) [ 4.764590] EXT2-fs (xvda): error: couldn''t mount because of unsupported optional features (244) [ 4.775433] EXT4-fs (xvda): INFO: recovery required on readonly filesystem [ 4.781320] EXT4-fs (xvda): write access will be enabled during recovery [ 4.850791] EXT4-fs (xvda): recovery complete [ 4.859316] EXT4-fs (xvda): mounted filesystem with ordered data mode. Opts: (null) [ 4.865305] VFS: Mounted root (ext4 filesystem) readonly on device 202:0. [ 4.869323] devtmpfs: mounted [ 4.875165] Freeing unused kernel memory: 412K (c0877000 - c08de000) <no login prompt> Guest bootlog with ramdisk == root@arm:~# xl console domU-xen [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 3.12.0-01110-g0c72f67-dirty (vaibhav@vaibhav-VirtualBox) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #13 [ 0.000000] CPU: ARMv7 Processor [412fc0f2] revision 2 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache [ 0.000000] Machine: Dummy Virtual Machine, model: XENVM-4.2 [ 0.000000] cma: CMA: reserved 16 MiB at 87000000 [ 0.000000] Memory policy: ECC disabled, Data cache writealloc [ 0.000000] PERCPU: Embedded 9 pages/cpu @c0ff4000 s15232 r8192 d13440 u36864 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 [ 0.000000] Kernel command line: console=hvc0 root=/dev/xvda mem=128M xencons=tty [ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes) [ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [ 0.000000] Memory: 98176K/131072K available (6191K kernel code, 653K rwdata, 2444K rodata, 414K init, 5549K bss, 32896K reserved, 0K hig) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) [ 0.000000] vmalloc : 0xc8800000 - 0xff000000 ( 872 MB) [ 0.000000] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) [ 0.000000] .text : 0xc0008000 - 0xc0876ec8 (8636 kB) [ 0.000000] .init : 0xc0877000 - 0xc08deb80 ( 415 kB) [ 0.000000] .data : 0xc08e0000 - 0xc09837b0 ( 654 kB) [ 0.000000] .bss : 0xc09837b0 - 0xc0eeefa0 (5550 kB) [ 0.000000] Hierarchical RCU implementation. [ 0.000000] RCU restricting CPUs from NR_CPUS=2 to nr_cpu_ids=1. [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] Architected cp15 timer(s) running at 6.14MHz (virt). [ 0.000000] Switching to timer-based delay loop [ 0.000000] sched_clock: ARM arch timer >56 bits at 6144kHz, resolution 162ns [ 0.000000] sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms [ 0.000000] Console: colour dummy device 80x30 [ 0.000000] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar [ 0.000000] ... MAX_LOCKDEP_SUBCLASSES: 8 [ 0.000000] ... MAX_LOCK_DEPTH: 48 [ 0.000000] ... MAX_LOCKDEP_KEYS: 8191 [ 0.000000] ... CLASSHASH_SIZE: 4096 [ 0.000000] ... MAX_LOCKDEP_ENTRIES: 16384 [ 0.000000] ... MAX_LOCKDEP_CHAINS: 32768 [ 0.000000] ... CHAINHASH_SIZE: 16384 [ 0.000000] memory used by lock dependency info: 3695 kB [ 0.000000] per task-struct memory footprint: 1152 bytes [ 2.772924] Calibrating delay loop (skipped), value calculated using timer frequency.. 12.28 BogoMIPS (lpj=61440) [ 2.786161] pid_max: default: 32768 minimum: 301 [ 2.789567] Security Framework initialized [ 2.823231] Mount-cache hash table entries: 512 [ 2.825465] CPU: Testing write buffer coherency: ok [ 2.834418] /cpus/cpu@0 missing clock-frequency property [ 2.839263] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 2.845006] Setting up static identity map for 0xc05dd0c8 - 0xc05dd120 [ 2.848509] Brought up 1 CPUs [ 2.852413] SMP: Total of 1 processors activated. [ 2.886170] CPU: All CPU(s) started in SVC mode. [ 2.890057] devtmpfs: initialized [ 2.891376] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0 [ 2.903907] Xen 4.2 support found, events_irq=31 gnttab_frame_pfn=b0000 [ 2.909130] xen:grant_table: Grant tables using version 1 layout [ 2.911718] Grant table initialized [ 2.978564] pinctrl core: initialized pinctrl subsystem [ 2.983916] regulator-dummy: no parameters [ 2.988835] NET: Registered protocol family 16 [ 2.991672] Xen: initializing cpu0 [ 3.001380] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 3.010183] xenbus: xs_reset_watches failed: -38 [ 3.014319] No ATAGs? [ 3.022269] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 3.027286] hw-breakpoint: maximum watchpoint size is 8 bytes. [ 3.098612] bio: create slab <bio-0> at 0 [ 3.107967] edma-dma-engine edma-dma-engine.0: Can''t allocate PaRAM dummy slot [ 3.114205] edma-dma-engine: probe of edma-dma-engine.0 failed with error -5 [ 3.119051] xen:balloon: Initialising balloon driver [ 3.246743] vgaarb: loaded [ 3.251208] SCSI subsystem initialized [ 3.260543] usbcore: registered new interface driver usbfs [ 3.265171] usbcore: registered new interface driver hub [ 3.269676] usbcore: registered new device driver usb [ 3.278695] Switched to clocksource arch_sys_counter [ 3.457030] NET: Registered protocol family 2 [ 3.464196] TCP established hash table entries: 1024 (order: 1, 8192 bytes) [ 3.469839] TCP bind hash table entries: 1024 (order: 3, 36864 bytes) [ 3.475526] TCP: Hash tables configured (established 1024 bind 1024) [ 3.477945] TCP: reno registered [ 3.512993] UDP hash table entries: 256 (order: 2, 20480 bytes) [ 3.518605] UDP-Lite hash table entries: 256 (order: 2, 20480 bytes) [ 3.522843] NET: Registered protocol family 1 [ 3.528797] RPC: Registered named UNIX socket transport module. [ 3.532690] RPC: Registered udp transport module. [ 3.536598] RPC: Registered tcp transport module. [ 3.542246] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 3.582009] NetWinder Floating Point Emulator V0.97 (double precision) [ 3.784448] VFS: Disk quotas dquot_6.5.2 [ 3.820035] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 3.825571] NFS: Registering the id_resolver key type [ 3.829056] Key type id_resolver registered [ 3.832269] Key type id_legacy registered [ 3.838528] jffs2: version 2.2. (NAND) (SUMMARY) ?© 2001-2006 Red Hat, Inc. [ 3.841628] msgmni has been set to 223 [ 3.847448] io scheduler noop registered [ 3.880850] io scheduler deadline registered [ 3.884712] io scheduler cfq registered (default) [ 3.897533] xen:xen_evtchn: Event-channel device installed [ 4.026898] console [hvc0] enabled [ 4.032559] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 4.054178] brd: module loaded [ 4.065334] loop: module loaded [ 4.102555] mtdoops: mtd device (mtddev=name/number) must be supplied [ 4.112350] xen_netfront: Initialising Xen virtual ethernet driver [ 4.195690] usbcore: registered new interface driver asix [ 4.201116] usbcore: registered new interface driver ax88179_178a [ 4.206278] usbcore: registered new interface driver cdc_ether [ 4.211073] usbcore: registered new interface driver r815x [ 4.216199] usbcore: registered new interface driver smsc95xx [ 4.251106] usbcore: registered new interface driver net1080 [ 4.256549] usbcore: registered new interface driver cdc_subset [ 4.261445] usbcore: registered new interface driver zaurus [ 4.266609] usbcore: registered new interface driver cdc_ncm [ 4.273937] ehci_hcd: USB 2.0 ''Enhanced'' Host Controller (EHCI) Driver [ 4.277576] ehci-pci: EHCI PCI platform driver [ 4.312124] ehci-omap: OMAP-EHCI Host Controller driver [ 4.318716] usbcore: registered new interface driver cdc_wdm [ 4.324072] usbcore: registered new interface driver usb-storage [ 4.329135] usbcore: registered new interface driver usbtest [ 4.335529] mousedev: PS/2 mouse device common for all mice [ 4.341636] i2c /dev entries driver [ 4.376309] Driver for 1-wire Dallas network protocol. [ 4.384436] ledtrig-cpu: registered to indicate activity on CPUs [ 4.390607] usbcore: registered new interface driver usbhid [ 4.393631] usbhid: USB HID core driver [ 4.399038] oprofile: no performance counters [ 4.433586] oprofile: using timer interrupt. [ 4.436566] TCP: cubic registered [ 4.440038] Initializing XFRM netlink socket [ 4.443697] NET: Registered protocol family 17 [ 4.447326] NET: Registered protocol family 15 [ 4.450591] Bridge firewalling registered [ 4.454056] 8021q: 802.1Q VLAN Support v1.8 [ 4.457518] Key type dns_resolver registered [ 4.461000] ThumbEE CPU extension supported. [ 4.494918] Registering SWP/SWPB emulation handler [ 4.538656] blkfront: xvda: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled; [ 4.550651] xvda: unknown partition table [ 4.695122] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 4.711795] VFS: Mounted root (ext2 filesystem) readonly on device 202:0. [ 4.717178] devtmpfs: mounted [ 4.723007] Freeing unused kernel memory: 412K (c0877000 - c08de000) mount: mounting none on /var/shm failed: No such file or directory :: :: Enabling hot-plug : [SUCCESS] :: :: : Populating /dev : [SUCCESS] [SUCCESS] :: :: :: Setting PATH :: : syslogd : [SUCCESS] : telnetd : [SUCCESS] Jan 1 00:00:02 arago syslog.info syslogd started: BusyBox v1.15.0.svn Please press Enter to activate this console. Jan 1 00:00:12 arago daemon.info init: starting pid 638, tty '''': ''-/bin/sh'' :: :: Setting shell environment ... :: : Path : Aliases : Touch Screen :: :: Done :: [root@arago /]# ===
Attaching my config file also... kernel = "/root/zImage-domU-debug" memory = "256" name = "domU-xen" bootargs = "mem=128M vram=16M xencons=hvc" vcpus = 1 vif = [ ''bridge=xenbr0'',''mac=00:16:3e:23:24:32''] extra ="console=hvc0 xencons=hvc" disk = [ ''phy:/dev/loop0,xvda,w'' ]
On Fri, 2013-11-22 at 14:20 -0500, Vaibhav Bedia wrote:> >> >> Right now i have an OMAP5 dom0 with network+usb support and i am > >> >> trying to figure out how to get these things in domU and hence the > >> >> questions. > >> > > >> > You need blkback and netback in dom0 and blkfront and netfront in domU > >> > (all in mainline Linux). Then you need to add vif and disk options to > >> > your guest configuration. > >> > > >> > >> I enabled both of the options and can get a ramdisk based domU running fine. > >> I tried a Ubuntu based fs for domU but can''t get to the login prompt > >> for some reason. > >> I tried out the various options mentioned @ > >> http://wiki.xen.org/wiki/Xen_Common_Problems#Console > >> and some other things mentioned on various forums but nothing seems to work :( > >> Any hints on where things could be going wrong? I have hvc0.conf under > >> /etc/init/ > > > > Do you have CONFIG_HVC_XEN enabled in the guest kernel config? Is the > > guest detecting that it is running under Xen? Can you post a guest dmesg > > please. > > > > Yes. It''s enabled. I can get the same image to the login prompt using a minimal > ramdisk so it should be something to do with the Ubuntu filesystem, right?You may need to configure Ubuntu to start a getty on hvc0 (the console device). This involves adding an upstart configuration file, copying an existing tty one and changing the device I guess? I don''t know the details. Hopefully there''s enough keywords there to let you do a search. Oh, I see further back in the thread that you have this. I''m afraid I don''t know enough about Ubuntu to diagnose what may be going wrong. Perhaps post your hvc.conf and maybe someone can spot what is going wrong.> The IP address is via DHCP. Once i get the login prompt using the > minimal ramdisk i run > $ ifconfig eth0 up > <eth0 mac address is what i assign in the config file> > $ udhcpc > Guest gets an IP address now.Do you know where the DHCP server is? It is worth checking the logs in case udhcpc has actually failed and used a previously successful lease which it has cached. I don''t know about udhcpc but other DHCP clients tend to log when they do this.> The above sequence doesn''t work always but when it does get an IP > address i can''t > ping domU or have it ping some other host. I didn''t setup any firewall > explicitly - just > using plain ubuntu 13.04.I don''t know if Ubuntu ships with a firewall enabled or not -- you should certainly confirm!> I do see that the vif is added to the bridge.In "brctl show" I suppose?> I also noticed that the > errrors under eth0 > starts going up when i create a guest and eventually the network in dom0 becomes > completely unresponsive.That''s quite, er, interesting. I''ve never heard of that before. I see you have two vifs, are they on the same bridge? Do they have different mac addresses? Can you post your guest cfg file please. I''d suggest taking the second vif out and working to get a single one working, just to eliminate variables etc.> P.S. Apologies for the flood of seemingly random datapoints. > As you can see i am right now a total newbie to xen and trying to find > my way around :)That''s ok. I''m a bit perplexed to be honest...> > ================> > Guest bootlog with Ubuntu fs: > ==> > root@arm:~# xl console domU-xen > [ 0.000000] Booting Linux on physical CPU 0x0 > [ 0.000000] Linux version 3.12.0-01110-g0c72f67-dirty > (vaibhav@vaibhav-VirtualBox) (gcc version 4.7.3 (Ubuntu/Linaro > 4.7.3-1ubuntu1) ) #13 > [ 0.000000] CPU: ARMv7 Processor [412fc0f2] revision 2 (ARMv7), cr=10c5387d > [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache > [ 0.000000] Machine: Dummy Virtual Machine, model: XENVM-4.2 > [ 0.000000] cma: CMA: reserved 16 MiB at 87000000 > [ 0.000000] Memory policy: ECC disabled, Data cache writealloc > [ 0.000000] PERCPU: Embedded 9 pages/cpu @c0ff4000 s15232 r8192 d13440 u36864 > [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. > Total pages: 32512 > [ 0.000000] Kernel command line: console=hvc0 root=/dev/xvda > mem=128M xencons=ttyHow much mem did you give the guest in its configuration file? What about in the DTB? I''d recommend leaving off this instance of mem= for now.> [ 4.074520] console [hvc0] enabledGood! [...]> [ 4.587776] blkfront: xvda: flush diskcache: enabled; persistent > grants: enabled; indirect descriptors: enabled; > [ 4.600643] xvda: unknown partition table > [ 4.742512] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) > [ 4.754670] EXT3-fs (xvda): error: couldn''t mount because of > unsupported optional features (240) > [ 4.764590] EXT2-fs (xvda): error: couldn''t mount because of > unsupported optional features (244) > [ 4.775433] EXT4-fs (xvda): INFO: recovery required on readonly filesystem > [ 4.781320] EXT4-fs (xvda): write access will be enabled during recovery > [ 4.850791] EXT4-fs (xvda): recovery complete > [ 4.859316] EXT4-fs (xvda): mounted filesystem with ordered data > mode. Opts: (null) > [ 4.865305] VFS: Mounted root (ext4 filesystem) readonly on device 202:0.Good.> [ 4.869323] devtmpfs: mounted > [ 4.875165] Freeing unused kernel memory: 412K (c0877000 - c08de000)This is the point at which I would expect to start seeing userspace/init system (e.g. upstart) output. You have a correct console= line so I can''t think where this might be going. Perhaps try booting with init=/bin/sh? Ian.
On Fri, 2013-11-22 at 14:22 -0500, Vaibhav Bedia wrote:> Attaching my config file also... > > kernel = "/root/zImage-domU-debug" > memory = "256" > name = "domU-xen" > bootargs = "mem=128M vram=16M xencons=hvc"Drop the mem=128M here, it will be confusing things. I suppose you are using a version of xen from a little ago and are therefore appending a DTB to your kernel? In which case the bootargs from there is what will matter. Actually -- xl doesn''t speak "bootargs", it uses "extra". SO this line isn''t actually doing anything. The "extra" line below is what xl understands (but if you are using appended DTB then it is ignored). You may find it simpler to upgrade to the current master at which point the DTB will be autogenerated and you can use the settings in this file (specifically the "extra" below) instead of in the DTB.> vcpus = 1 > vif = [ ''bridge=xenbr0'',''mac=00:16:3e:23:24:32'']This is actually creating two vifs. One one xenbr0 with a random mac and one with the given mac address on the default bridge (probably xenbr0!) You probably wanted: vif = [ ''bridge=xenbr0,mac=00:16:3e:23:24:32''] Or just: vif = [ ''mac=00:16:3e:23:24:32''] which works because xenbr0 is the default bridge.> extra ="console=hvc0 xencons=hvc" > disk = [ ''phy:/dev/loop0,xvda,w'' ]
On Fri, 22 Nov 2013, Vaibhav Bedia wrote:> Hi Ian, > > On Fri, Nov 22, 2013 at 10:22 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote: > > On Fri, 2013-11-22 at 10:05 -0500, Vaibhav Bedia wrote: > >> >> After going through the recent talk from Stefano [1] i got > >> >> the impression getting network and SATA requires SWIOTLB support. Is > >> >> that correct? > >> > > >> > The SWIOTLB or an IOMMU/SMMU is necessary for dom0 to drive the physical > >> > devices and provide the virtual interfaces to the guests. > >> > > >> > Device passthrough will only be supported with an IOMMU/SMMU. > >> > > >> > >> So on SoCs like OMAP5 which don''t have an IOMMU device passthrough won''t be > >> supported? Or it can be done via SWIOTLB if someone works on it? > > > > I''m not in favour of supporting this. It''s a big can of worms wrt > > security. > > > > Ok. I''ll leave it to the experts then :)Just for clarity: the big can of worms is allowing device passthrough without an IOMMU. (Except maybe for some ad-hoc static configurations that might be desirable on embedded platform.) Using the swiotlb for dom0 is OK.
On Thu, 2013-11-28 at 12:44 +0000, Stefano Stabellini wrote:> On Fri, 22 Nov 2013, Vaibhav Bedia wrote: > > Hi Ian, > > > > On Fri, Nov 22, 2013 at 10:22 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote: > > > On Fri, 2013-11-22 at 10:05 -0500, Vaibhav Bedia wrote: > > >> >> After going through the recent talk from Stefano [1] i got > > >> >> the impression getting network and SATA requires SWIOTLB support. Is > > >> >> that correct? > > >> > > > >> > The SWIOTLB or an IOMMU/SMMU is necessary for dom0 to drive the physical > > >> > devices and provide the virtual interfaces to the guests. > > >> > > > >> > Device passthrough will only be supported with an IOMMU/SMMU. > > >> > > > >> > > >> So on SoCs like OMAP5 which don''t have an IOMMU device passthrough won''t be > > >> supported? Or it can be done via SWIOTLB if someone works on it? > > > > > > I''m not in favour of supporting this. It''s a big can of worms wrt > > > security. > > > > > > > Ok. I''ll leave it to the experts then :) > > Just for clarity: the big can of worms is allowing device passthrough > without an IOMMU. (Except maybe for some ad-hoc static configurations > that might be desirable on embedded platform.) > Using the swiotlb for dom0 is OK.Yes, sorry, I latched onto the "device passthrough" bit of the question as being a question about giving devices to domU. swiotlb is fine for dom0 and OMAP5 is a platform which could be supportable, if you don''t care about giving physical devices to guests. In fact, we have omap5 platform code already from Chen Baozi. I don''t know which platform he actually has though. Ian.
Hi Ian, Sorry for the delayed response. Juggling between different thing in grad school. On Tue, Nov 26, 2013 at 4:34 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:> On Fri, 2013-11-22 at 14:20 -0500, Vaibhav Bedia wrote: >> >> >> Right now i have an OMAP5 dom0 with network+usb support and i am >> >> >> trying to figure out how to get these things in domU and hence the >> >> >> questions. >> >> > >> >> > You need blkback and netback in dom0 and blkfront and netfront in domU >> >> > (all in mainline Linux). Then you need to add vif and disk options to >> >> > your guest configuration. >> >> > >> >> >> >> I enabled both of the options and can get a ramdisk based domU running fine. >> >> I tried a Ubuntu based fs for domU but can''t get to the login prompt >> >> for some reason. >> >> I tried out the various options mentioned @ >> >> http://wiki.xen.org/wiki/Xen_Common_Problems#Console >> >> and some other things mentioned on various forums but nothing seems to work :( >> >> Any hints on where things could be going wrong? I have hvc0.conf under >> >> /etc/init/ >> > >> > Do you have CONFIG_HVC_XEN enabled in the guest kernel config? Is the >> > guest detecting that it is running under Xen? Can you post a guest dmesg >> > please. >> > >> >> Yes. It''s enabled. I can get the same image to the login prompt using a minimal >> ramdisk so it should be something to do with the Ubuntu filesystem, right? > > You may need to configure Ubuntu to start a getty on hvc0 (the console > device). This involves adding an upstart configuration file, copying an > existing tty one and changing the device I guess? I don''t know the > details. Hopefully there''s enough keywords there to let you do a search. >Thanks. I got this sorted out now (more below).> Oh, I see further back in the thread that you have this. I''m afraid I > don''t know enough about Ubuntu to diagnose what may be going wrong. > Perhaps post your hvc.conf and maybe someone can spot what is going > wrong. > >> The IP address is via DHCP. Once i get the login prompt using the >> minimal ramdisk i run >> $ ifconfig eth0 up >> <eth0 mac address is what i assign in the config file> >> $ udhcpc >> Guest gets an IP address now. > > Do you know where the DHCP server is? It is worth checking the logs in > case udhcpc has actually failed and used a previously successful lease > which it has cached. I don''t know about udhcpc but other DHCP clients > tend to log when they do this. >I doubt i''ll get anywhere the campus server :) I had to go through a few hoops just to get the ssh port enabled.>> The above sequence doesn''t work always but when it does get an IP >> address i can''t >> ping domU or have it ping some other host. I didn''t setup any firewall >> explicitly - just >> using plain ubuntu 13.04. > > I don''t know if Ubuntu ships with a firewall enabled or not -- you > should certainly confirm! >I learnt a bit about iptables and tcpdump and can now confirm that there''s no firewall enabled.>> I do see that the vif is added to the bridge. > > In "brctl show" I suppose? >Yes.>> I also noticed that the >> errrors under eth0 >> starts going up when i create a guest and eventually the network in dom0 becomes >> completely unresponsive. > > That''s quite, er, interesting. I''ve never heard of that before. > > I see you have two vifs, are they on the same bridge? Do they have > different mac addresses? > > Can you post your guest cfg file please. > > I''d suggest taking the second vif out and working to get a single one > working, just to eliminate variables etc. > >> P.S. Apologies for the flood of seemingly random datapoints. >> As you can see i am right now a total newbie to xen and trying to find >> my way around :) > > That''s ok. I''m a bit perplexed to be honest... > >> >> ================>> >> Guest bootlog with Ubuntu fs: >> ==>> >> root@arm:~# xl console domU-xen >> [ 0.000000] Booting Linux on physical CPU 0x0 >> [ 0.000000] Linux version 3.12.0-01110-g0c72f67-dirty >> (vaibhav@vaibhav-VirtualBox) (gcc version 4.7.3 (Ubuntu/Linaro >> 4.7.3-1ubuntu1) ) #13 >> [ 0.000000] CPU: ARMv7 Processor [412fc0f2] revision 2 (ARMv7), cr=10c5387d >> [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache >> [ 0.000000] Machine: Dummy Virtual Machine, model: XENVM-4.2 >> [ 0.000000] cma: CMA: reserved 16 MiB at 87000000 >> [ 0.000000] Memory policy: ECC disabled, Data cache writealloc >> [ 0.000000] PERCPU: Embedded 9 pages/cpu @c0ff4000 s15232 r8192 d13440 u36864 >> [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. >> Total pages: 32512 >> [ 0.000000] Kernel command line: console=hvc0 root=/dev/xvda >> mem=128M xencons=tty > > How much mem did you give the guest in its configuration file? What > about in the DTB? I''d recommend leaving off this instance of mem= for > now. > >> > This is the point at which I would expect to start seeing userspace/init > system (e.g. upstart) output. You have a correct console= line so I > can''t think where this might be going. > > Perhaps try booting with init=/bin/sh? > > Ian. >I seem to have the console mystery sorted out. I was using a standard ubuntu filesystem and after reading some more blogs related to xen usage realized that i had not never updated the /etc/fstab file to point it to /dev/xvda1! Once i did that i got the console fine. Thanks, Vaibhav
On Tue, Nov 26, 2013 at 4:38 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:> On Fri, 2013-11-22 at 14:22 -0500, Vaibhav Bedia wrote: >> Attaching my config file also... >> >> kernel = "/root/zImage-domU-debug" >> memory = "256" >> name = "domU-xen" >> bootargs = "mem=128M vram=16M xencons=hvc" > > Drop the mem=128M here, it will be confusing things. I suppose you are > using a version of xen from a little ago and are therefore appending a > DTB to your kernel? In which case the bootargs from there is what will > matter. >Yeah i was trying to stick to a known xen setup. Actually in the version that i could allocate more memory using the mem parameter.> Actually -- xl doesn''t speak "bootargs", it uses "extra". SO this line > isn''t actually doing anything. The "extra" line below is what xl > understands (but if you are using appended DTB then it is ignored). > > You may find it simpler to upgrade to the current master at which point > the DTB will be autogenerated and you can use the settings in this file > (specifically the "extra" below) instead of in the DTB. >So i gave this a shot. I am doing all the compilation natively and that''s causing more pains :( The latest xen-code expects libfdt to be present (noticed a patch from you in git logs). I installed that on my OMAP5 board but libfdt-dev package seems to be broken on ubuntu right now... I currently get /usr/include/libfdt.h:54:24: fatal error: libfdt_env.h: No such file or directory Google tells me this was bug in the library build [1]... trying to figure out how to get this sorted out. While i do this i seem to have a bigger reliability problem right now (details below)>> vcpus = 1 >> vif = [ ''bridge=xenbr0'',''mac=00:16:3e:23:24:32''] > > This is actually creating two vifs. One one xenbr0 with a random mac and > one with the given mac address on the default bridge (probably xenbr0!) > > You probably wanted: > vif = [ ''bridge=xenbr0,mac=00:16:3e:23:24:32''] > Or just: > vif = [ ''mac=00:16:3e:23:24:32''] > which works because xenbr0 is the default bridge. >Ok. I wanted only one vif. Didn''t realize this was creating two of those. Now that i get the console in the ubuntu filesystem for domU i was hoping to dig deeper into the "unable to ping" domU problem. My fresh builds of the kernels for dom0 and domU seems to have uncovered some other issue since i just can''t get a reliable domU boot now. Right now most of the domU creation hangs and it also kills off dom0. I have a heartbeat led in dom0 and that just stops - i can switch to xen using ctrl-a keystrokes and back but the dom0 seems to have crashed. Any suggestions on how to debug this? There are few "failed to unmap" messages when creating domUs but i don''t know how to debug this :( Pasting the log for xl create and xen-debug info post a crash below... ... Ok as i was trying this out to get a crash log i was able to bring up two instances for domU but when i switched to the second instance after adding the vif line (not sure this part is relevant - the observation has been really random so far) dom0 seems to have crashed root@OMAP5:~# xl -vvv create xen-domU.conf -d Parsing config from xen-domU.conf unable to format domain config as JSON (YAJL:1) libxl: debug: libxl_create.c:1237:do_domain_create: ao 0x3be70: create: how=(nil) callback=(nil) poller=0x3c4f0 libxl: verbose: libxl_create.c:130:libxl__domain_build_info_setdefault: qemu-xen is unavailable, use qemu-xen-traditional instead: No such fy libxl: debug: libxl_device.c:257:libxl__device_disk_set_backend: Disk vdev=xvda spec.backend=unknown libxl: debug: libxl_device.c:296:libxl__device_disk_set_backend: Disk vdev=xvda, using backend phy libxl: debug: libxl_create.c:681:initiate_domain_create: running bootloader libxl: debug: libxl_bootloader.c:327:libxl__bootloader_run: no bootloader configured, using user supplied kernel libxl: debug: libxl_event.c:608:libxl__ev_xswatch_deregister: watch w=0x3c72c: deregister unregistered libxl: debug: libxl_numa.c:475:libxl__get_numa_candidate: New best NUMA placement candidate found: nr_nodes=1, nr_cpus=1, nr_vcpus=3, free_m8 libxl: detail: libxl_dom.c:195:numa_place_domain: NUMA placement candidate with 1 nodes, 1 cpus and 1228 KB free selected domainbuilder: detail: xc_dom_allocate: cmdline="", features="(null)" libxl: debug: libxl_dom.c:348:libxl__build_pv: pv kernel mapped 0 path /root/zImage-domU-final domainbuilder: detail: xc_dom_kernel_file: filename="/root/zImage-domU-final" domainbuilder: detail: xc_dom_malloc_filemap : 4668 kB domainbuilder: detail: xc_dom_boot_xen_init: ver 4.4, caps xen-3.0-armv7l 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 (ARM) loader ... domainbuilder: detail: xc_dom_probe_zimage_kernel: found an appended DTB domainbuilder: detail: loader probe OK domainbuilder: detail: xc_dom_parse_zimage_kernel: called domainbuilder: detail: xc_dom_parse_zimage_kernel: xen-3.0-armv7l: RAM starts at 80000 domainbuilder: detail: xc_dom_parse_zimage_kernel: xen-3.0-armv7l: 0x80008000 -> 0x804972fd domainbuilder: detail: xc_dom_mem_init: mem 256 MB, pages 0x10000 pages, 4k each domainbuilder: detail: xc_dom_mem_init: 0x10000 pages domainbuilder: detail: xc_dom_boot_mem_init: called domainbuilder: detail: xc_dom_malloc : 512 kB domainbuilder: detail: xc_dom_build_image: called domainbuilder: detail: xc_dom_alloc_segment: kernel : 0x80008000 -> 0x80498000 (pfn 0x80008 + 0x490 pages) domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x80008+0x490 at 0xb634c000 domainbuilder: detail: xc_dom_load_zimage_kernel: called domainbuilder: detail: xc_dom_load_zimage_kernel: kernel sed 0x80008000-0x80498000 domainbuilder: detail: xc_dom_load_zimage_kernel: copy 4780797 bytes from blob 0xb685d000 to dst 0xb634c000 domainbuilder: detail: alloc_magic_pages: called 4Failed to unmap pfn:9d0c7 rc:-2 4Failed to unmap pfn:9d12a rc:-2 domainbuilder: detail: count_pgtables_arm: called domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0x80498000 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-armv7l <= matches domainbuilder: detail: setup_pgtables_arm: called domainbuilder: detail: clear_page: pfn 0x90000, mfn 0x90000 4Failed to unmap pfn:8e095 rc:-2 domainbuilder: detail: clear_page: pfn 0x90001, mfn 0x90001 4Failed to unmap pfn:8e096 rc:-2 domainbuilder: detail: start_info_arm: called domainbuilder: detail: domain builder memory footprint domainbuilder: detail: allocated domainbuilder: detail: malloc : 541 kB domainbuilder: detail: anon mmap : 0 bytes domainbuilder: detail: mapped domainbuilder: detail: file mmap : 4668 kB domainbuilder: detail: domU mmap : 4672 kB domainbuilder: detail: vcpu_arm: called domainbuilder: detail: Initial state CPSR 0x1d3 PC 0x80008000 4Failed to unmap pfn:9d7e5 rc:-2 domainbuilder: detail: launch_vm: called, ctxt=0xb6f33004 4Failed to unmap pfn:9d7e4 rc:-2 domainbuilder: detail: xc_dom_release: called libxl: debug: libxl_device.c:257:libxl__device_disk_set_backend: Disk vdev=xvda spec.backend=phy libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch w=0x3ccf0 wpath=/local/domain/0/backend/vbd/2/51712/state token=3/0: regis3 libxl: debug: libxl_create.c:1251:do_domain_create: ao 0x3be70: inprogress: poller=0x3c4f0, flags=i libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x3ccf0 wpath=/local/domain/0/backend/vbd/2/51712/state token=3/0: event epath=/loe libxl: debug: libxl_event.c:643:devstate_watch_callback: backend /local/domain/0/backend/vbd/2/51712/state wanted state 2 ok libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch w=0x3ccf0 wpath=/local/domain/0/backend/vbd/2/51712/state token=3/0: der3 libxl: debug: libxl_event.c:608:libxl__ev_xswatch_deregister: watch w=0x3ccf0: deregister unregistered libxl: debug: libxl_device.c:959:device_hotplug: calling hotplug script: /etc/xen/scripts/block add libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch w=0x385f8 wpath=/local/domain/0/backend/vif/2/0/state token=3/1: register 3 libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x385f8 wpath=/local/domain/0/backend/vif/2/0/state token=3/1: event epath=/local/e libxl: debug: libxl_event.c:643:devstate_watch_callback: backend /local/domain/0/backend/vif/2/0/state wanted state 2 ok libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch w=0x385f8 wpath=/local/domain/0/backend/vif/2/0/state token=3/1: deregis3 libxl: debug: libxl_event.c:608:libxl__ev_xswatch_deregister: watch w=0x385f8: deregister unregistered libxl: debug: libxl_device.c:959:device_hotplug: calling hotplug script: /etc/xen/scripts/vif-bridge online 6device vif2.0 entered promiscuous mode libxl: debug: libxl_event.c:1738:libxl__ao_progress_report: ao 0x3be70: progress report: ignored libxl: debug: libxl_event.c:1570:libxl__ao_complete: ao 0x3be70: complete, rc=0 libxl: debug: libxl_event.c:1542:libxl__ao__destroy: ao 0x3be70: destroy Daemon running with PID 11824 xc: debug: hypercall buffer: total allocations:112 total releases:112 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:104 misses:4 toobig:4 root@OMAP5:~# (d2) 6Booting Linux on physical CPU 0x0 (d2) 5Linux version 3.12.0-01112-gb85294d (vaibhav@vaibhav-VirtualBox) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #3 SMP M (d2) on Dec 2 06:56:44 EST 2013 (d2) CPU: ARMv7 Processor [412fc0f2] revision 2 (ARMv7), cr=10c5387d (d2) CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache (d2) 6Machine: Dummy Virtual Machine, model: XENVM-4.2 (d2) 6cma: CMA: reserved 16 MiB at 8f000000 (d2) Memory policy: ECC disabled, Data cache writealloc (d2) 7On node 0 totalpages: 65536 (d2) 7free_area_init_node: node 0, pgdat c0979a80, node_mem_map c0eec000 (d2) 7 Normal zone: 512 pages used for memmap (d2) 7 Normal zone: 0 pages reserved (d2) 7 Normal zone: 65536 pages, LIFO batch:15 (d2) 6PERCPU: Embedded 9 pages/cpu @c10f1000 s15232 r8192 d13440 u36864 (d2) 7pcpu-alloc: s15232 r8192 d13440 u36864 alloc=9*4096 (d2) 7pcpu-alloc: (d2) Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 (d2) 5Kernel command line: console=hvc0 root=/dev/xvda mem=256M (d2) 6PID hash table entries: 1024 (order: 0, 4096 bytes) (d2) 6Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) (d2) 6Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) (d2) Memory: 228136K/262144K available (6183K kernel code, 653K rwdata, 2440K rodata, 414K init, 5549K bss, 34008K reserved, 0K high (d2) mem) (d2) 5Virtual kernel memory layout: (d2) vector : 0xffff0000 - 0xffff1000 ( 4 kB) (d2) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) (d2) vmalloc : 0xd0800000 - 0xff000000 ( 744 MB) (d2) lowmem : 0xc0000000 - 0xd0000000 ( 256 MB) (d2) pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) (d2) modules : 0xbf000000 - 0xbfe00000 ( 14 MB) (d2) .text : 0xc0008000 - 0xc0873dd4 (8624 kB) (d2) .init : 0xc0874000 - 0xc08dbb80 ( 415 kB) (d2) .data : 0xc08dc000 - 0xc097f670 ( 654 kB) (d2) .bss : 0xc097f670 - 0xc0eeae60 (5550 kB) (d2) 6Hierarchical RCU implementation. (d2) 6 RCU restricting CPUs from NR_CPUS=2 to nr_cpu_ids=1. (d2) 6NR_IRQS:16 nr_irqs:16 16 (d2) 6Architected cp15 timer(s) running at 6.14MHz (virt). (d2) 6Switching to timer-based delay loop (d2) 6sched_clock: ARM arch timer >56 bits at 6144kHz, resolution 162ns (d2) 6sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms (d2) 6Console: colour dummy device 80x30 (d2) Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar (d2) ... MAX_LOCKDEP_SUBCLASSES: 8 (d2) ... MAX_LOCK_DEPTH: 48 (d2) ... MAX_LOCKDEP_KEYS: 8191 (d2) ... CLASSHASH_SIZE: 4096 (d2) ... MAX_LOCKDEP_ENTRIES: 16384 (d2) ... MAX_LOCKDEP_CHAINS: 32768 (d2) ... CHAINHASH_SIZE: 16384 (d2) memory used by lock dependency info: 3695 kB (d2) per task-struct memory footprint: 1152 bytes (d2) 6Calibrating delay loop (skipped), value calculated using timer frequency.. 12.28 BogoMIPS (lpj=61440) (d2) 6pid_max: default: 32768 minimum: 301 (d2) 6Security Framework initialized (d2) 6Mount-cache hash table entries: 512 (d2) 6CPU: Testing write buffer coherency: ok (d2) 3/cpus/cpu@0 missing clock-frequency property (d2) 6CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 (d2) 6Setting up static identity map for 0xc05da548 - 0xc05da5a0 (d2) 6Brought up 1 CPUs (d2) 6SMP: Total of 1 processors activated. (d2) 6CPU: All CPU(s) started in SVC mode. (d2) 6devtmpfs: initialized (d2) 6VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0 (d2) 6Xen 4.2 support found, events_irq=31 gnttab_frame_pfn=b0000 (d2) 6xen:grant_table: Grant tables using version 1 layout (d2) Grant table initialized (d2) 6pinctrl core: initialized pinctrl subsystem (d2) 6regulator-dummy: no parameters (d2) 6NET: Registered protocol family 16 (d2) 6Xen: initializing cpu0 (d2) 6DMA: preallocated 256 KiB pool for atomic coherent allocations (d2) 4xenbus: xs_reset_watches failed: -38 (d2) 6No ATAGs?6hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. (d2) 6hw-breakpoint: maximum watchpoint size is 8 bytes. (d2) 6bio: create slab <bio-0> at 0 (d2) edma-dma-engine edma-dma-engine.0: Can''t allocate PaRAM dummy slot (d2) 4edma-dma-engine: probe of edma-dma-engine.0 failed with error -5 (d2) 6xen:balloon: Initialising balloon driver (d2) 6vgaarb: loaded (d2) 5SCSI subsystem initialized (d2) 7libata version 3.00 loaded. (d2) 6usbcore: registered new interface driver usbfs (d2) 6usbcore: registered new interface driver hub (d2) 6usbcore: registered new device driver usb (d2) 6Switched to clocksource arch_sys_counter (d2) 6NET: Registered protocol family 2 (d2) 6TCP established hash table entries: 2048 (order: 2, 16384 bytes) (d2) 6TCP bind hash table entries: 2048 (order: 4, 73728 bytes) (d2) 6TCP: Hash tables configured (established 2048 bind 2048) (d2) 6TCP: reno registered (d2) 6UDP hash table entries: 256 (order: 2, 20480 bytes) (d2) 6UDP-Lite hash table entries: 256 (order: 2, 20480 bytes) (d2) 6NET: Registered protocol family 1 (d2) 6RPC: Registered named UNIX socket transport module. (d2) 6RPC: Registered udp transport module. (d2) 6RPC: Registered tcp transport module. (d2) 6RPC: Registered tcp NFSv4.1 backchannel transport module. (d2) 7PCI: CLS 0 bytes, default 64 (d2) 4NetWinder Floating Point Emulator V0.97 (double precision) (d2) 5VFS: Disk quotas dquot_6.5.2 (d2) Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) (d2) 5NFS: Registering the id_resolver key type (d2) 5Key type id_resolver registered (d2) 5Key type id_legacy registered (d2) 6jffs2: version 2.2. (NAND) (SUMMARY) ?© 2001-2006 Red Hat, Inc. (d2) 6msgmni has been set to 477 (d2) 6io scheduler noop registered (d2) 6io scheduler deadline registered (d2) 6io scheduler cfq registered (default) (d2) 6xen:xen_evtchn: Event-channel device installed (d2) 6console [hvc0] enabled (d2) 6Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled (d2) 6brd: module loaded (d2) 6loop: module loaded (d2) 3mtdoops: mtd device (mtddev=name/number) must be supplied (d2) 6xen_netfront: Initialising Xen virtual ethernet driver 6xen-blkback:ring-ref 8, event-channel 3, protocol 1 (arm-abi) persistent grants (XEN) grant_table.c:1249:d2 Expanding dom (2) grant table from (1) to (2) frames. (d2) 6usbcore: registered new interface driver asix (d2) 6usbcore: registered new interface driver ax88179_178a (d2) 6usbcore: registered new interface driver cdc_ether (d2) 6usbcore: registered new interface driver r815x (d2) 6usbcore: registered new interface driver smsc95xx (d2) 6usbcore: registered new interface driver net1080 (d2) 6usbcore: registered new interface driver cdc_subset (d2) 6usbcore: registered new interface driver zaurus (d2) 6usbcore: registered new interface driver cdc_ncm (d2) 6ehci_hcd: USB 2.0 ''Enhanced'' Host Controller (EHCI) Driver (d2) 6ehci-pci: EHCI PCI platform driver (d2) 6ehci-omap: OMAP-EHCI Host Controller driver (d2) 6usbcore: registered new interface driver cdc_wdm (d2) 6usbcore: registered new interface driver usb-storage (d2) 6usbcore: registered new interface driver usbtest (d2) 6mousedev: PS/2 mouse device common for all mice (d2) 6i2c /dev entries driver (d2) 6Driver for 1-wire Dallas network protocol. (d2) 6ledtrig-cpu: registered to indicate activity on CPUs (d2) 6usbcore: registered new interface driver usbhid (d2) 6usbhid: USB HID core driver (d2) 6oprofile: no performance counters (d2) 6oprofile: using timer interrupt. (d2) 6TCP: cubic registered (d2) 6Initializing XFRM netlink socket (d2) 6NET: Registered protocol family 17 (d2) 6NET: Registered protocol family 15 (d2) 5Bridge firewalling registered (d2) 68021q: 802.1Q VLAN Support v1.8 (d2) 5Key type dns_resolver registered (d2) 6ThumbEE CPU extension supported. (d2) 5Registering SWP/SWPB emulation handler (d2) 6blkfront: xvda: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled; (d2) 6 xvda: unknown partition table 6xenbr0: port 2(vif2.0) entered forwarding state 6xenbr0: port 2(vif2.0) entered forwarding state (d2) 3drivers/rtc/hctosys.c: unable to open rtc device (rtc0) (d2) 3EXT3-fs (xvda): error: couldn''t mount because of unsupported optional features (240) (d2) 3EXT2-fs (xvda): error: couldn''t mount because of unsupported optional features (244) (d2) 6EXT4-fs (xvda): INFO: recovery required on readonly filesystem (d2) 6EXT4-fs (xvda): write access will be enabled during recovery (d2) 6EXT4-fs (xvda): recovery complete (d2) 6EXT4-fs (xvda): mounted filesystem with ordered data mode. Opts: (null) (d2) 6VFS: Mounted root (ext4 filesystem) readonly on device 202:0. (d2) 6devtmpfs: mounted (d2) 6Freeing unused kernel memory: 412K (c0874000 - c08db000) (d2) udevd[704]: starting version 175 (XEN) mm.c:1250:d0 gnttab_mark_dirty not implemented yet (d2) init: udev-fallback-graphics main process (1035) terminated with status 1 (d2) init: plymouth main process (631) killed by ABRT signal (d2) init: plymouth-splash main process (1045) terminated with status 2 (d2) 6EXT4-fs (xvda): re-mounted. Opts: errors=remount-ro (d2) init: plymouth-log main process (1075) terminated with status 1 root@OMAP5:~# (d2) init: plymouth-stop pre-start process (1332) terminated with status 1 [...] switch to domU console via xl console command... i see the bootlog (skipped since it''s the same as above and then i lose control over dom0) *** Serial input -> Xen (type ''CTRL-a'' three times to switch input to DOM0) (XEN) ''h'' pressed -> showing installed handlers (XEN) key ''%'' (ascii ''25'') => trap to xendbg (XEN) key ''*'' (ascii ''2a'') => print all diagnostics (XEN) key ''0'' (ascii ''30'') => dump Dom0 registers (XEN) key ''A'' (ascii ''41'') => toggle alternative key handling (XEN) key ''H'' (ascii ''48'') => dump heap info (XEN) key ''R'' (ascii ''52'') => reboot machine (XEN) key ''a'' (ascii ''61'') => dump timer queues (XEN) key ''d'' (ascii ''64'') => dump registers (XEN) key ''e'' (ascii ''65'') => dump evtchn info (XEN) key ''g'' (ascii ''67'') => print grant table usage (XEN) key ''h'' (ascii ''68'') => show this message (XEN) key ''m'' (ascii ''6d'') => memory info (XEN) key ''q'' (ascii ''71'') => dump domain (and guest debug) info (XEN) key ''r'' (ascii ''72'') => dump run queues (XEN) key ''t'' (ascii ''74'') => display multi-cpu clock info (XEN) key ''w'' (ascii ''77'') => synchronously dump console ring buffer (dmesg) (XEN) ''*'' pressed -> firing all diagnostic keyhandlers (XEN) [d: dump registers] (XEN) ''d'' pressed -> dumping registers (XEN) (XEN) *** Dumping CPU0 guest state (d0:v0): *** (XEN) ----[ Xen-4.4-unstable arm32 debug=y Not tainted ]---- (XEN) CPU: 0 (XEN) PC: c0097518 (XEN) CPSR: 60000193 MODE:32-bit Guest SVC (XEN) R0: 00000018 R1: 00000478 R2: 00000000 R3: c09008e8 (XEN) R4: c09008e8 R5: c08f2000 R6: c1322a04 R7: c04f784c (XEN) R8: 60000193 R9: c099c4c4 R10:00000001 R11:c08f3e64 R12:60000193 (XEN) USR: SP: be9724f8 LR: b6f01234 (XEN) SVC: SP: c08f3de8 LR: c05e7120 SPSR:60000113 (XEN) ABT: SP: c0997a0c LR: c05e7a80 SPSR:80000193 (XEN) UND: SP: c0997a18 LR: c05e78e0 SPSR:80070093 (XEN) IRQ: SP: c0997a00 LR: c05e76c0 SPSR:60000193 (XEN) FIQ: SP: 00000000 LR: 00000000 SPSR:00000000 (XEN) FIQ: R8: 00000000 R9: 00000000 R10:00000000 R11:00000000 R12:00000000 (XEN) (XEN) SCTLR: 10c5387d (XEN) TCR: 00000000 (XEN) TTBR0: 000000009d27406a (XEN) TTBR1: 000000008000406a (XEN) IFAR: b6eb1aa0, IFSR: 00000007 (XEN) DFAR: b6c00008, DFSR: 00000817 (XEN) (XEN) VTCR_EL2: 80002558 (XEN) VTTBR_EL2: 00010000a200e000 (XEN) (XEN) SCTLR_EL2: 30cd187f (XEN) HCR_EL2: 0000000000282835 (XEN) TTBR0_EL2: 00000000feedf000 (XEN) (XEN) ESR_EL2: 07e00000 (XEN) HPFAR_EL2: 0000000000482110 (XEN) HDFAR: d0800100 (XEN) HIFAR: 00000000 (XEN) (XEN) No stack trace for 32-bit guest kernel-mode (XEN) (XEN) [0: dump Dom0 registers] (XEN) ''0'' pressed -> dumping Dom0''s registers (XEN) *** Dumping Dom0 vcpu#0 state: *** (XEN) ----[ Xen-4.4-unstable arm32 debug=y Not tainted ]---- (XEN) CPU: 0 (XEN) PC: c0097518 (XEN) CPSR: 60000193 MODE:32-bit Guest SVC (XEN) R0: 00000018 R1: 00000478 R2: 00000000 R3: c09008e8 (XEN) R4: c09008e8 R5: c08f2000 R6: c1322a04 R7: c04f784c (XEN) R8: 60000193 R9: c099c4c4 R10:00000001 R11:c08f3e64 R12:60000193 (XEN) USR: SP: be9724f8 LR: b6f01234 (XEN) SVC: SP: c08f3de8 LR: c05e7120 SPSR:60000113 (XEN) ABT: SP: c0997a0c LR: c05e7a80 SPSR:80000193 (XEN) UND: SP: c0997a18 LR: c05e78e0 SPSR:80070093 (XEN) IRQ: SP: c0997a00 LR: c05e76c0 SPSR:60000193 (XEN) FIQ: SP: 00000000 LR: 00000000 SPSR:00000000 (XEN) FIQ: R8: 00000000 R9: 00000000 R10:00000000 R11:00000000 R12:00000000 (XEN) (XEN) SCTLR: 10c5387d (XEN) TCR: 00000000 (XEN) TTBR0: 000000009d27406a (XEN) TTBR1: 000000008000406a (XEN) IFAR: b6eb1aa0, IFSR: 00000007 (XEN) DFAR: b6c00008, DFSR: 00000817 (XEN) (XEN) VTCR_EL2: 80002558 (XEN) VTTBR_EL2: 00010000a200e000 (XEN) (XEN) SCTLR_EL2: 30cd187f (XEN) HCR_EL2: 0000000000282835 (XEN) TTBR0_EL2: 00000000feedf000 (XEN) (XEN) ESR_EL2: 07e00000 (XEN) HPFAR_EL2: 0000000000482110 (XEN) HDFAR: d0800100 (XEN) HIFAR: 00000000 (XEN) (XEN) No stack trace for 32-bit guest kernel-mode (XEN) [H: dump heap info] (XEN) ''H'' pressed -> dumping heap info (now-0x2BD:5EA969FA) (XEN) heap[node=0][zone=0] -> 65416 pages (XEN) heap[node=0][zone=1] -> 0 pages (XEN) heap[node=0][zone=2] -> 0 pages (XEN) heap[node=0][zone=3] -> 0 pages (XEN) heap[node=0][zone=4] -> 0 pages (XEN) heap[node=0][zone=5] -> 0 pages (XEN) heap[node=0][zone=6] -> 0 pages (XEN) heap[node=0][zone=7] -> 0 pages (XEN) heap[node=0][zone=8] -> 0 pages (XEN) heap[node=0][zone=9] -> 0 pages (XEN) heap[node=0][zone=10] -> 0 pages (XEN) heap[node=0][zone=11] -> 0 pages (XEN) heap[node=0][zone=12] -> 0 pages (XEN) heap[node=0][zone=13] -> 0 pages (XEN) heap[node=0][zone=14] -> 0 pages (XEN) heap[node=0][zone=15] -> 0 pages (XEN) heap[node=0][zone=16] -> 0 pages (XEN) heap[node=0][zone=17] -> 0 pages (XEN) heap[node=0][zone=18] -> 0 pages (XEN) heap[node=0][zone=19] -> 0 pages (XEN) heap[node=0][zone=20] -> 183571 pages (XEN) heap[node=0][zone=21] -> 0 pages (XEN) heap[node=0][zone=22] -> 0 pages (XEN) heap[node=0][zone=23] -> 0 pages (XEN) heap[node=0][zone=24] -> 0 pages (XEN) heap[node=0][zone=25] -> 0 pages (XEN) heap[node=0][zone=26] -> 0 pages (XEN) heap[node=0][zone=27] -> 0 pages (XEN) heap[node=0][zone=28] -> 0 pages (XEN) [a: dump timer queues] (XEN) Dumping timer queues: (XEN) CPU00: (XEN) ex= 7386us timer=400325b0 cb=0021a848(00000000) csched_tick+0/0x45c (XEN) ex= 27389us timer=400322c0 cb=00218ba4(400322a8) csched_acct+0/0x5fc (XEN) [e: dump evtchn info] (XEN) ''e'' pressed -> dumping event-channel info (XEN) Event channel information for domain 0: (XEN) Polling vCPUs: {} (XEN) port [p/m/s] (XEN) 1 [0/0/0]: s=3 n=0 x=0 d=0 p=3 (XEN) 2 [0/0/0]: s=5 n=0 x=0 v=2 (XEN) 3 [0/0/0]: s=3 n=0 x=0 d=0 p=1 (XEN) 4 [0/0/0]: s=5 n=0 x=0 v=3 (XEN) 5 [0/0/0]: s=3 n=0 x=0 d=1 p=1 (XEN) 6 [0/0/0]: s=3 n=0 x=0 d=1 p=2 (XEN) 7 [0/0/0]: s=3 n=0 x=0 d=1 p=3 (XEN) 8 [0/0/0]: s=3 n=0 x=0 d=2 p=1 (XEN) 9 [0/0/0]: s=3 n=0 x=0 d=2 p=2 (XEN) 10 [0/0/0]: s=3 n=0 x=0 d=2 p=3 (XEN) 11 [0/0/0]: s=3 n=0 x=0 d=2 p=4 (XEN) 12 [0/0/0]: s=3 n=0 x=0 d=2 p=5 (XEN) Event channel information for domain 1: (XEN) Polling vCPUs: {} (XEN) port [p/m/s] (XEN) 1 [0/0/0]: s=3 n=0 x=0 d=0 p=5 (XEN) 2 [0/0/0]: s=3 n=0 x=0 d=0 p=6 (XEN) 3 [0/0/0]: s=3 n=0 x=0 d=0 p=7 (XEN) Event channel information for domain 2: (XEN) Polling vCPUs: {} (XEN) port [p/m/s] (XEN) 1 [0/0/0]: s=3 n=0 x=0 d=0 p=8 (XEN) 2 [0/0/0]: s=3 n=0 x=0 d=0 p=9 (XEN) 3 [0/0/0]: s=3 n=0 x=0 d=0 p=10 (XEN) 4 [0/0/0]: s=3 n=0 x=0 d=0 p=11 (XEN) 5 [0/0/0]: s=3 n=0 x=0 d=0 p=12 (XEN) [g: print grant table usage] (XEN) gnttab_usage_print_all [ key ''g'' pressed (XEN) -------- active -------- -------- shared -------- (XEN) [ref] localdom mfn pin localdom gmfn flags (XEN) grant-table for remote domain: 0 ... no active grant table entries (XEN) -------- active -------- -------- shared -------- (XEN) [ref] localdom mfn pin localdom gmfn flags (XEN) grant-table for remote domain: 1 (v1) (XEN) [ 0] 0 0x09d27f 0x00000001 0 0x090000 0x19 (XEN) [ 8] 0 0x0ae9de 0x00000001 0 0x08e2c9 0x19 (XEN) [ 9] 0 0x0ae566 0x00000001 0 0x08e73f 0x19 (XEN) [ 10] 0 0x0ae567 0x00000001 0 0x08e73e 0x19 (XEN) [ 11] 0 0x0ae568 0x00000001 0 0x08e73d 0x19 (XEN) [ 12] 0 0x0ae569 0x00000001 0 0x08e73c 0x19 (XEN) [ 13] 0 0x0ae56a 0x00000001 0 0x08e73b 0x19 (XEN) [ 14] 0 0x0ae56b 0x00000001 0 0x08e73a 0x19 (XEN) [ 15] 0 0x0ae56c 0x00000001 0 0x08e739 0x19 (XEN) [ 16] 0 0x0ae56d 0x00000001 0 0x08e738 0x19 (XEN) [ 17] 0 0x0ae56e 0x00000001 0 0x08e737 0x19 (XEN) [ 18] 0 0x0ae56f 0x00000001 0 0x08e736 0x19 (XEN) [ 19] 0 0x0ae570 0x00000001 0 0x08e735 0x19 (XEN) [ 20] 0 0x0ae571 0x00000001 0 0x08e734 0x19 (XEN) [ 21] 0 0x0ae572 0x00000001 0 0x08e733 0x19 (XEN) [ 22] 0 0x0ae573 0x00000001 0 0x08e732 0x19 (XEN) [ 23] 0 0x0ae574 0x00000001 0 0x08e731 0x19 (XEN) [ 24] 0 0x0ae575 0x00000001 0 0x08e730 0x19 (XEN) [ 25] 0 0x0ae576 0x00000001 0 0x08e72f 0x19 (XEN) [ 26] 0 0x0ae577 0x00000001 0 0x08e72e 0x19 (XEN) [ 27] 0 0x0ae578 0x00000001 0 0x08e72d 0x19 (XEN) [ 28] 0 0x0ae579 0x00000001 0 0x08e72c 0x19 (XEN) [ 29] 0 0x0ae57a 0x00000001 0 0x08e72b 0x19 (XEN) [ 30] 0 0x0ae57b 0x00000001 0 0x08e72a 0x19 (XEN) [ 31] 0 0x0ae57c 0x00000001 0 0x08e729 0x19 (XEN) [ 32] 0 0x0ae57d 0x00000001 0 0x08e728 0x19 (XEN) [ 33] 0 0x0ae57e 0x00000001 0 0x08e727 0x19 (XEN) [ 34] 0 0x0ae57f 0x00000001 0 0x08e726 0x19 (XEN) [ 35] 0 0x0ae580 0x00000001 0 0x08e725 0x19 (XEN) [ 36] 0 0x0ae581 0x00000001 0 0x08e724 0x19 (XEN) [ 37] 0 0x0ae582 0x00000001 0 0x08e723 0x19 (XEN) [ 38] 0 0x0ae583 0x00000001 0 0x08e722 0x19 (XEN) [ 39] 0 0x0ae585 0x00000001 0 0x08e720 0x19 (XEN) [ 40] 0 0x0ae586 0x00000001 0 0x08e71f 0x19 (XEN) [ 41] 0 0x0ae587 0x00000001 0 0x08e71e 0x19 (XEN) [ 42] 0 0x0ae588 0x00000001 0 0x08e71d 0x19 (XEN) [ 43] 0 0x0ae589 0x00000001 0 0x08e71c 0x19 (XEN) [ 44] 0 0x0ae58a 0x00000001 0 0x08e71b 0x19 (XEN) [ 45] 0 0x0ae58b 0x00000001 0 0x08e71a 0x19 (XEN) [ 46] 0 0x0ae58c 0x00000001 0 0x08e719 0x19 (XEN) [ 47] 0 0x0ae58d 0x00000001 0 0x08e718 0x19 (XEN) [ 48] 0 0x0ae58e 0x00000001 0 0x08e717 0x19 (XEN) [ 49] 0 0x0ae58f 0x00000001 0 0x08e716 0x19 (XEN) [ 50] 0 0x0ae590 0x00000001 0 0x08e715 0x19 (XEN) [ 51] 0 0x0ae591 0x00000001 0 0x08e714 0x19 (XEN) [ 52] 0 0x0ae592 0x00000001 0 0x08e713 0x19 (XEN) [ 53] 0 0x0ae593 0x00000001 0 0x08e712 0x19 (XEN) [ 54] 0 0x0ae594 0x00000001 0 0x08e711 0x19 (XEN) [ 55] 0 0x0ae595 0x00000001 0 0x08e710 0x19 (XEN) [ 56] 0 0x0ae596 0x00000001 0 0x08e70f 0x19 (XEN) [ 57] 0 0x0ae597 0x00000001 0 0x08e70e 0x19 (XEN) [ 58] 0 0x0ae598 0x00000001 0 0x08e70d 0x19 (XEN) [ 59] 0 0x0ae599 0x00000001 0 0x08e70c 0x19 (XEN) [ 60] 0 0x0ae59a 0x00000001 0 0x08e70b 0x19 (XEN) [ 61] 0 0x0ae59b 0x00000001 0 0x08e70a 0x19 (XEN) [ 62] 0 0x0ae59c 0x00000001 0 0x08e709 0x19 (XEN) [ 63] 0 0x0ae59d 0x00000001 0 0x08e708 0x19 (XEN) [ 64] 0 0x0ae59e 0x00000001 0 0x08e707 0x19 (XEN) [ 65] 0 0x0ae59f 0x00000001 0 0x08e706 0x19 (XEN) [ 66] 0 0x0ae5a0 0x00000001 0 0x08e705 0x19 (XEN) [ 67] 0 0x0ae5a1 0x00000001 0 0x08e704 0x19 (XEN) [ 68] 0 0x0ae5a2 0x00000001 0 0x08e703 0x19 (XEN) [ 69] 0 0x0ae5a3 0x00000001 0 0x08e702 0x19 (XEN) [ 70] 0 0x0ae5a4 0x00000001 0 0x08e701 0x19 (XEN) [ 71] 0 0x0ae5a5 0x00000001 0 0x08e700 0x19 (XEN) [ 72] 0 0x0ae5a6 0x00000001 0 0x08e6ff 0x19 (XEN) [ 73] 0 0x0ae5a7 0x00000001 0 0x08e6fe 0x19 (XEN) [ 74] 0 0x0ae5a8 0x00000001 0 0x08e6fd 0x19 (XEN) [ 75] 0 0x0ae5a9 0x00000001 0 0x08e6fc 0x19 (XEN) [ 76] 0 0x0ae5aa 0x00000001 0 0x08e6fb 0x19 (XEN) [ 77] 0 0x0ae5ab 0x00000001 0 0x08e6fa 0x19 (XEN) [ 78] 0 0x0ae5ac 0x00000001 0 0x08e6f9 0x19 (XEN) [ 79] 0 0x0ae5ad 0x00000001 0 0x08e6f8 0x19 (XEN) [ 80] 0 0x0ae5ae 0x00000001 0 0x08e6f7 0x19 (XEN) [ 81] 0 0x0ae5af 0x00000001 0 0x08e6f6 0x19 (XEN) [ 82] 0 0x0ae5b0 0x00000001 0 0x08e6f5 0x19 (XEN) [ 83] 0 0x0ae5b1 0x00000001 0 0x08e6f4 0x19 (XEN) [ 84] 0 0x0ae5b2 0x00000001 0 0x08e6f3 0x19 (XEN) [ 85] 0 0x0ae5b3 0x00000001 0 0x08e6f2 0x19 (XEN) [ 86] 0 0x0ae5b4 0x00000001 0 0x08e6f1 0x19 (XEN) [ 87] 0 0x0ae5b5 0x00000001 0 0x08e6f0 0x19 (XEN) [ 88] 0 0x0ae5b6 0x00000001 0 0x08e6ef 0x19 (XEN) [ 89] 0 0x0ae5b7 0x00000001 0 0x08e6ee 0x19 (XEN) [ 90] 0 0x0ae5b8 0x00000001 0 0x08e6ed 0x19 (XEN) [ 91] 0 0x0ae5b9 0x00000001 0 0x08e6ec 0x19 (XEN) [ 92] 0 0x0ae5ba 0x00000001 0 0x08e6eb 0x19 (XEN) [ 93] 0 0x0ae5bb 0x00000001 0 0x08e6ea 0x19 (XEN) [ 94] 0 0x0ae5bc 0x00000001 0 0x08e6e9 0x19 (XEN) [ 95] 0 0x0ae5bd 0x00000001 0 0x08e6e8 0x19 (XEN) [ 96] 0 0x0ae5be 0x00000001 0 0x08e6e7 0x19 (XEN) [ 97] 0 0x0ae5bf 0x00000001 0 0x08e6e6 0x19 (XEN) [ 98] 0 0x0ae5c1 0x00000001 0 0x08e6e4 0x19 (XEN) [ 99] 0 0x0ae5c2 0x00000001 0 0x08e6e3 0x19 (XEN) [100] 0 0x0ae5c3 0x00000001 0 0x08e6e2 0x19 (XEN) [101] 0 0x0ae5c4 0x00000001 0 0x08e6e1 0x19 (XEN) [102] 0 0x0ae5c5 0x00000001 0 0x08e6e0 0x19 (XEN) [103] 0 0x0ae5c6 0x00000001 0 0x08e6df 0x19 (XEN) [104] 0 0x0ae5c7 0x00000001 0 0x08e6de 0x19 (XEN) [105] 0 0x0ae5c8 0x00000001 0 0x08e6dd 0x19 (XEN) [106] 0 0x0ae5c9 0x00000001 0 0x08e6dc 0x19 (XEN) [107] 0 0x0ae5ca 0x00000001 0 0x08e6db 0x19 (XEN) [108] 0 0x0ae5cb 0x00000001 0 0x08e6da 0x19 (XEN) [109] 0 0x0ae5cc 0x00000001 0 0x08e6d9 0x19 (XEN) [110] 0 0x0ae5cd 0x00000001 0 0x08e6d8 0x19 (XEN) [111] 0 0x0ae5ce 0x00000001 0 0x08e6d7 0x19 (XEN) [112] 0 0x0ae5cf 0x00000001 0 0x08e6d6 0x19 (XEN) [113] 0 0x0ae5d0 0x00000001 0 0x08e6d5 0x19 (XEN) [114] 0 0x0ae5d1 0x00000001 0 0x08e6d4 0x19 (XEN) [115] 0 0x0ae5d2 0x00000001 0 0x08e6d3 0x19 (XEN) [116] 0 0x0ae5d3 0x00000001 0 0x08e6d2 0x19 (XEN) [117] 0 0x0ae5d4 0x00000001 0 0x08e6d1 0x19 (XEN) [118] 0 0x0ae5d5 0x00000001 0 0x08e6d0 0x19 (XEN) [119] 0 0x0ae5d6 0x00000001 0 0x08e6cf 0x19 (XEN) [120] 0 0x0ae5d7 0x00000001 0 0x08e6ce 0x19 (XEN) [121] 0 0x0ae5d8 0x00000001 0 0x08e6cd 0x19 (XEN) [122] 0 0x0ae5d9 0x00000001 0 0x08e6cc 0x19 (XEN) [123] 0 0x0ae5da 0x00000001 0 0x08e6cb 0x19 (XEN) [124] 0 0x0ae5db 0x00000001 0 0x08e6ca 0x19 (XEN) [125] 0 0x0ae5dc 0x00000001 0 0x08e6c9 0x19 (XEN) [126] 0 0x0ae5dd 0x00000001 0 0x08e6c8 0x19 (XEN) [127] 0 0x0ae5de 0x00000001 0 0x08e6c7 0x19 (XEN) [128] 0 0x0ae5df 0x00000001 0 0x08e6c6 0x19 (XEN) [129] 0 0x0ae5e0 0x00000001 0 0x08e6c5 0x19 (XEN) [130] 0 0x0ae5e1 0x00000001 0 0x08e6c4 0x19 (XEN) [131] 0 0x0ae5e2 0x00000001 0 0x08e6c3 0x19 (XEN) [132] 0 0x0ae5e3 0x00000001 0 0x08e6c2 0x19 (XEN) [133] 0 0x0ae5e4 0x00000001 0 0x08e6c1 0x19 (XEN) [134] 0 0x0ae5e5 0x00000001 0 0x08e6c0 0x19 (XEN) [135] 0 0x0ae5e6 0x00000001 0 0x08e6bf 0x19 (XEN) [136] 0 0x0ae5e7 0x00000001 0 0x08e6be 0x19 (XEN) [137] 0 0x0ae5e8 0x00000001 0 0x08e6bd 0x19 (XEN) [138] 0 0x0ae5e9 0x00000001 0 0x08e6bc 0x19 (XEN) -------- active -------- -------- shared -------- (XEN) [ref] localdom mfn pin localdom gmfn flags (XEN) grant-table for remote domain: 2 (v1) (XEN) [ 0] 0 0x0bcc92 0x00000001 0 0x090000 0x19 (XEN) [ 8] 0 0x0be979 0x00000001 0 0x08e327 0x19 (XEN) [768] 0 0x0be551 0x00000001 0 0x08e74d 0x19 (XEN) [769] 0 0x0be53e 0x00000001 0 0x08e760 0x19 (XEN) [770] 0 0x0be545 0x00000001 0 0x08e759 0x19 (XEN) [771] 0 0x0be553 0x00000001 0 0x08e74b 0x19 (XEN) [772] 0 0x0be554 0x00000001 0 0x08e74a 0x19 (XEN) [773] 0 0x0be555 0x00000001 0 0x08e749 0x19 (XEN) [774] 0 0x0be556 0x00000001 0 0x08e748 0x19 (XEN) [775] 0 0x0be557 0x00000001 0 0x08e747 0x19 (XEN) [776] 0 0x0be558 0x00000001 0 0x08e746 0x19 (XEN) [777] 0 0x0be559 0x00000001 0 0x08e745 0x19 (XEN) [778] 0 0x0be55a 0x00000001 0 0x08e744 0x19 (XEN) [779] 0 0x0be55b 0x00000001 0 0x08e743 0x19 (XEN) [780] 0 0x0be55c 0x00000001 0 0x08e742 0x19 (XEN) [781] 0 0x0be55d 0x00000001 0 0x08e741 0x19 (XEN) [782] 0 0x0be55e 0x00000001 0 0x08e740 0x19 (XEN) [783] 0 0x0be55f 0x00000001 0 0x08e73f 0x19 (XEN) [784] 0 0x0be560 0x00000001 0 0x08e73e 0x19 (XEN) [785] 0 0x0be561 0x00000001 0 0x08e73d 0x19 (XEN) [786] 0 0x0be562 0x00000001 0 0x08e73c 0x19 (XEN) [787] 0 0x0be563 0x00000001 0 0x08e73b 0x19 (XEN) [788] 0 0x0be564 0x00000001 0 0x08e73a 0x19 (XEN) [789] 0 0x0be565 0x00000001 0 0x08e739 0x19 (XEN) [790] 0 0x0be566 0x00000001 0 0x08e738 0x19 (XEN) [791] 0 0x0be567 0x00000001 0 0x08e737 0x19 (XEN) [792] 0 0x0be568 0x00000001 0 0x08e736 0x19 (XEN) [793] 0 0x0be569 0x00000001 0 0x08e735 0x19 (XEN) [794] 0 0x0be56a 0x00000001 0 0x08e734 0x19 (XEN) [795] 0 0x0be56b 0x00000001 0 0x08e733 0x19 (XEN) [796] 0 0x0be56c 0x00000001 0 0x08e732 0x19 (XEN) [797] 0 0x0be56d 0x00000001 0 0x08e731 0x19 (XEN) [798] 0 0x0be56e 0x00000001 0 0x08e730 0x19 (XEN) [799] 0 0x0be56f 0x00000001 0 0x08e72f 0x19 (XEN) [800] 0 0x0be570 0x00000001 0 0x08e72e 0x19 (XEN) [801] 0 0x0be571 0x00000001 0 0x08e72d 0x19 (XEN) [802] 0 0x0be572 0x00000001 0 0x08e72c 0x19 (XEN) [803] 0 0x0be573 0x00000001 0 0x08e72b 0x19 (XEN) [804] 0 0x0be574 0x00000001 0 0x08e72a 0x19 (XEN) [805] 0 0x0be575 0x00000001 0 0x08e729 0x19 (XEN) [806] 0 0x0be576 0x00000001 0 0x08e728 0x19 (XEN) [807] 0 0x0be577 0x00000001 0 0x08e727 0x19 (XEN) [808] 0 0x0be578 0x00000001 0 0x08e726 0x19 (XEN) [809] 0 0x0be579 0x00000001 0 0x08e725 0x19 (XEN) [810] 0 0x0be57a 0x00000001 0 0x08e724 0x19 (XEN) [811] 0 0x0be57b 0x00000001 0 0x08e723 0x19 (XEN) [812] 0 0x0be57c 0x00000001 0 0x08e722 0x19 (XEN) [813] 0 0x0be57d 0x00000001 0 0x08e721 0x19 (XEN) [814] 0 0x0be57e 0x00000001 0 0x08e720 0x19 (XEN) [815] 0 0x0be57f 0x00000001 0 0x08e71f 0x19 (XEN) [816] 0 0x0be580 0x00000001 0 0x08e71e 0x19 (XEN) [817] 0 0x0be581 0x00000001 0 0x08e71d 0x19 (XEN) [818] 0 0x0be582 0x00000001 0 0x08e71c 0x19 (XEN) [819] 0 0x0be583 0x00000001 0 0x08e71b 0x19 (XEN) [820] 0 0x0be584 0x00000001 0 0x08e71a 0x19 (XEN) [821] 0 0x0be585 0x00000001 0 0x08e719 0x19 (XEN) [822] 0 0x0be586 0x00000001 0 0x08e718 0x19 (XEN) [823] 0 0x0be587 0x00000001 0 0x08e717 0x19 (XEN) [824] 0 0x0be588 0x00000001 0 0x08e716 0x19 (XEN) [825] 0 0x0be589 0x00000001 0 0x08e715 0x19 (XEN) [826] 0 0x0be58a 0x00000001 0 0x08e714 0x19 (XEN) [827] 0 0x0be58b 0x00000001 0 0x08e713 0x19 (XEN) [828] 0 0x0be58c 0x00000001 0 0x08e712 0x19 (XEN) [829] 0 0x0be58d 0x00000001 0 0x08e711 0x19 (XEN) [830] 0 0x0be58f 0x00000001 0 0x08e70f 0x19 (XEN) [831] 0 0x0be590 0x00000001 0 0x08e70e 0x19 (XEN) [832] 0 0x0be591 0x00000001 0 0x08e70d 0x19 (XEN) [833] 0 0x0be592 0x00000001 0 0x08e70c 0x19 (XEN) [834] 0 0x0be593 0x00000001 0 0x08e70b 0x19 (XEN) [835] 0 0x0be594 0x00000001 0 0x08e70a 0x19 (XEN) [836] 0 0x0be595 0x00000001 0 0x08e709 0x19 (XEN) [837] 0 0x0be596 0x00000001 0 0x08e708 0x19 (XEN) [838] 0 0x0be597 0x00000001 0 0x08e707 0x19 (XEN) [839] 0 0x0be598 0x00000001 0 0x08e706 0x19 (XEN) [840] 0 0x0be599 0x00000001 0 0x08e705 0x19 (XEN) [841] 0 0x0be59a 0x00000001 0 0x08e704 0x19 (XEN) [842] 0 0x0be59b 0x00000001 0 0x08e703 0x19 (XEN) [843] 0 0x0be59c 0x00000001 0 0x08e702 0x19 (XEN) [844] 0 0x0be59d 0x00000001 0 0x08e701 0x19 (XEN) [845] 0 0x0be59e 0x00000001 0 0x08e700 0x19 (XEN) [846] 0 0x0be59f 0x00000001 0 0x08e6ff 0x19 (XEN) [847] 0 0x0be5a0 0x00000001 0 0x08e6fe 0x19 (XEN) [848] 0 0x0be5a1 0x00000001 0 0x08e6fd 0x19 (XEN) [849] 0 0x0be5a2 0x00000001 0 0x08e6fc 0x19 (XEN) [850] 0 0x0be5a3 0x00000001 0 0x08e6fb 0x19 (XEN) [851] 0 0x0be5a4 0x00000001 0 0x08e6fa 0x19 (XEN) [852] 0 0x0be5a5 0x00000001 0 0x08e6f9 0x19 (XEN) [853] 0 0x0be5a6 0x00000001 0 0x08e6f8 0x19 (XEN) [854] 0 0x0be5a7 0x00000001 0 0x08e6f7 0x19 (XEN) [855] 0 0x0be5a8 0x00000001 0 0x08e6f6 0x19 (XEN) [856] 0 0x0be5a9 0x00000001 0 0x08e6f5 0x19 (XEN) [857] 0 0x0be5aa 0x00000001 0 0x08e6f4 0x19 (XEN) [858] 0 0x0be5ab 0x00000001 0 0x08e6f3 0x19 (XEN) [859] 0 0x0be5ac 0x00000001 0 0x08e6f2 0x19 (XEN) [860] 0 0x0be5ad 0x00000001 0 0x08e6f1 0x19 (XEN) [861] 0 0x0be5ae 0x00000001 0 0x08e6f0 0x19 (XEN) [862] 0 0x0be5af 0x00000001 0 0x08e6ef 0x19 (XEN) [863] 0 0x0be5b0 0x00000001 0 0x08e6ee 0x19 (XEN) [864] 0 0x0be5b1 0x00000001 0 0x08e6ed 0x19 (XEN) [865] 0 0x0be5b2 0x00000001 0 0x08e6ec 0x19 (XEN) [866] 0 0x0be5b3 0x00000001 0 0x08e6eb 0x19 (XEN) [867] 0 0x0be5b4 0x00000001 0 0x08e6ea 0x19 (XEN) [868] 0 0x0be5b5 0x00000001 0 0x08e6e9 0x19 (XEN) [869] 0 0x0be5b6 0x00000001 0 0x08e6e8 0x19 (XEN) [870] 0 0x0be5b7 0x00000001 0 0x08e6e7 0x19 (XEN) [871] 0 0x0be5b8 0x00000001 0 0x08e6e6 0x19 (XEN) [872] 0 0x0be5b9 0x00000001 0 0x08e6e5 0x19 (XEN) [873] 0 0x0be5ba 0x00000001 0 0x08e6e4 0x19 (XEN) [874] 0 0x0be5bb 0x00000001 0 0x08e6e3 0x19 (XEN) [875] 0 0x0be5bc 0x00000001 0 0x08e6e2 0x19 (XEN) [876] 0 0x0be5bd 0x00000001 0 0x08e6e1 0x19 (XEN) [877] 0 0x0be5be 0x00000001 0 0x08e6e0 0x19 (XEN) [878] 0 0x0be5bf 0x00000001 0 0x08e6df 0x19 (XEN) [879] 0 0x0be5c0 0x00000001 0 0x08e6de 0x19 (XEN) [880] 0 0x0be5c1 0x00000001 0 0x08e6dd 0x19 (XEN) [881] 0 0x0be5c2 0x00000001 0 0x08e6dc 0x19 (XEN) [882] 0 0x0be5c3 0x00000001 0 0x08e6db 0x19 (XEN) [883] 0 0x0be5c4 0x00000001 0 0x08e6da 0x19 (XEN) [884] 0 0x0be5c5 0x00000001 0 0x08e6d9 0x19 (XEN) [885] 0 0x0be5c6 0x00000001 0 0x08e6d8 0x19 (XEN) [886] 0 0x0be5c7 0x00000001 0 0x08e6d7 0x19 (XEN) [887] 0 0x0be5c8 0x00000001 0 0x08e6d6 0x19 (XEN) [888] 0 0x0be5c9 0x00000001 0 0x08e6d5 0x19 (XEN) [889] 0 0x0be5cb 0x00000001 0 0x08e6d3 0x19 (XEN) [890] 0 0x0be5cc 0x00000001 0 0x08e6d2 0x19 (XEN) [891] 0 0x0be5cd 0x00000001 0 0x08e6d1 0x19 (XEN) [892] 0 0x0be5ce 0x00000001 0 0x08e6d0 0x19 (XEN) [893] 0 0x0be5cf 0x00000001 0 0x08e6cf 0x19 (XEN) [894] 0 0x0be5d0 0x00000001 0 0x08e6ce 0x19 (XEN) [895] 0 0x0be5d1 0x00000001 0 0x08e6cd 0x19 (XEN) [896] 0 0x0be5d2 0x00000001 0 0x08e6cc 0x19 (XEN) [897] 0 0x0be5d3 0x00000001 0 0x08e6cb 0x19 (XEN) [898] 0 0x0be5d4 0x00000001 0 0x08e6ca 0x19 (XEN) [899] 0 0x0be5d5 0x00000001 0 0x08e6c9 0x19 (XEN) gnttab_usage_print_all ] done (XEN) [m: memory info] (XEN) Physical memory information: (XEN) Xen heap: 261664kB free (XEN) heap[20]: 734284kB free (XEN) Dom heap: 734284kB free (XEN) [q: dump domain (and guest debug) info] (XEN) ''q'' pressed -> dumping domain info (now=0x2BD:CE2B1C8B) (XEN) General information for domain 0: (XEN) refcnt=3 dying=0 pause_count=0 (XEN) nr_pages=130804 xenheap_pages=2 shared_pages=0 paged_pages=0 dirty_cpus={} max_pages=4294967295 (XEN) handle=00000000-0000-0000-0000-000000000000 vm_assist=00000000 (XEN) GICH_LRs (vcpu 0) mask=1 (XEN) VCPU_LR[0]=1a080045 (XEN) VCPU_LR[1]=0 (XEN) VCPU_LR[2]=0 (XEN) VCPU_LR[3]=0 (XEN) Inflight irq=69 (XEN) Inflight irq=109 (XEN) Pending irq=109 (XEN) Rangesets belonging to domain 0: (XEN) Interrupts { } (XEN) I/O Memory { } (XEN) NODE affinity for domain 0: [0] (XEN) VCPU information and callbacks for domain 0: (XEN) VCPU0: CPU0 [has=F] poll=0 upcall_pend = 00, upcall_mask 01 dirty_cpus={} cpu_affinity={0-127} (XEN) pause_count=0 pause_flags=0 (XEN) No periodic timer (XEN) General information for domain 1: (XEN) refcnt=3 dying=0 pause_count=0 (XEN) nr_pages=65538 xenheap_pages=2 shared_pages=0 paged_pages=0 dirty_cpus={} max_pages=65792 (XEN) handle=6ee0884c-6779-45c6-bfc7-a259e61bea21 vm_assist=00000000 (XEN) GICH_LRs (vcpu 0) mask=0 (XEN) VCPU_LR[0]=0 (XEN) VCPU_LR[1]=0 (XEN) VCPU_LR[2]=0 (XEN) VCPU_LR[3]=0 (XEN) Inflight irq=27 (XEN) Pending irq=27 (XEN) Rangesets belonging to domain 1: (XEN) Interrupts { } (XEN) I/O Memory { } (XEN) NODE affinity for domain 1: [0] (XEN) VCPU information and callbacks for domain 1: (XEN) VCPU0: CPU0 [has=F] poll=0 upcall_pend = 00, upcall_mask 01 dirty_cpus={} cpu_affinity={0-127} (XEN) pause_count=0 pause_flags=0 (XEN) No periodic timer (XEN) General information for domain 2: (XEN) refcnt=3 dying=0 pause_count=0 (XEN) nr_pages=65538 xenheap_pages=3 shared_pages=0 paged_pages=0 dirty_cpus={} max_pages=65792 (XEN) handle=f4657601-cf72-481e-9607-259ebde6949d vm_assist=00000000 (XEN) GICH_LRs (vcpu 0) mask=0 (XEN) VCPU_LR[0]=0 (XEN) VCPU_LR[1]=0 (XEN) VCPU_LR[2]=0 (XEN) VCPU_LR[3]=0 (XEN) Inflight irq=27 (XEN) Pending irq=27 (XEN) Rangesets belonging to domain 2: (XEN) Interrupts { } (XEN) I/O Memory { } (XEN) NODE affinity for domain 2: [0] (XEN) VCPU information and callbacks for domain 2: (XEN) VCPU0: CPU0 [has=F] poll=0 upcall_pend = 00, upcall_mask 01 dirty_cpus={} cpu_affinity={0-127} (XEN) pause_count=0 pause_flags=0 (XEN) No periodic timer (XEN) Notifying guest 0:0 (virq 1, port 0) (XEN) Notifying guest 1:0 (virq 1, port 0) (XEN) Notifying guest 2:0 (virq 1, port 0) (XEN) [r: dump run queues] (XEN) sched_smt_power_savings: disabled (XEN) NOW=0x000002BDDBC7FF14 (XEN) Idle cpupool: (XEN) Scheduler: SMP Credit Scheduler (credit) (XEN) info: (XEN) ncpus = 1 (XEN) master = 0 (XEN) credit = 300 (XEN) credit balance = 0 (XEN) weight = 0 (XEN) runq_sort = 100108 (XEN) default-weight = 256 (XEN) tslice = 30ms (XEN) ratelimit = 1000us (XEN) credits per msec = 10 (XEN) ticks per tslice = 3 (XEN) migration delay = 0us (XEN) idlers: 00000000,00000000,00000000,00000000 (XEN) active vcpus: (XEN) Cpupool 0: (XEN) Scheduler: SMP Credit Scheduler (credit) (XEN) info: (XEN) ncpus = 1 (XEN) master = 0 (XEN) credit = 300 (XEN) credit balance = 0 (XEN) weight = 0 (XEN) runq_sort = 100108 (XEN) default-weight = 256 (XEN) tslice = 30ms (XEN) ratelimit = 1000us (XEN) credits per msec = 10 (XEN) ticks per tslice = 3 (XEN) migration delay = 0us (XEN) idlers: 00000000,00000000,00000000,00000000 (XEN) active vcpus: (XEN) CPU[00] sort=100108, sibling=00000000,00000000,00000000,00000001, core=00000000,00000000,00000000,00000001 (XEN) run: [32767.0] pri=0 flags=0 cpu=0 (XEN) 1: [2.0] pri=0 flags=0 cpu=0 credit=-1454 [w=256] (XEN) 2: [1.0] pri=0 flags=0 cpu=0 credit=109 [w=256] (XEN) 3: [0.0] pri=-1 flags=0 cpu=0 credit=299 [w=256] (XEN) [t: display multi-cpu clock info] (XEN) Synced stime skew: max=0ns avg=0ns samples=1 current=0ns (XEN) Synced cycles skew: max=0 avg=0 samples=1 current=0 Regards, Vaibhav [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706137
On Mon, 2013-12-02 at 08:02 -0500, Vaibhav Bedia wrote:> I currently get > /usr/include/libfdt.h:54:24: fatal error: libfdt_env.h: No such file > or directory > > Google tells me this was bug in the library build [1]... trying to figure > out how to get this sorted out.I keep hitting this, I just grabbed the source and copied libfdt_env.h to /usr/include. Works for me ;-)> >> vcpus = 1 > >> vif = [ ''bridge=xenbr0'',''mac=00:16:3e:23:24:32''] > > > > This is actually creating two vifs. One one xenbr0 with a random mac and > > one with the given mac address on the default bridge (probably xenbr0!) > > > > You probably wanted: > > vif = [ ''bridge=xenbr0,mac=00:16:3e:23:24:32''] > > Or just: > > vif = [ ''mac=00:16:3e:23:24:32''] > > which works because xenbr0 is the default bridge. > > > > Ok. I wanted only one vif. Didn''t realize this was creating two of those. > > Now that i get the console in the ubuntu filesystem for domU i was > hoping to dig deeper into the "unable to ping" domU problem. > > My fresh builds of the kernels for dom0 and domU seems to have > uncovered some other issue since i just can''t get a reliable domU > boot now. Right now most of the domU creation hangs and it also > kills off dom0. I have a heartbeat led in dom0 and that just stops - > i can switch to xen using ctrl-a keystrokes and back but the dom0 > seems to have crashed. > > Any suggestions on how to debug this? There are few "failed to unmap" > messages when creating domUs but i don''t know how to debug this :(Yes, these are annoying. In the absence of a proper fix I''ve been: diff --git a/drivers/xen/privcmd.c b/drivers/xen/privcmd.c index 8e74590..7b383bf 100644 --- a/drivers/xen/privcmd.c +++ b/drivers/xen/privcmd.c @@ -533,11 +533,16 @@ static void privcmd_close(struct vm_area_struct *vma) { struct page **pages = vma->vm_private_data; int numpgs = (vma->vm_end - vma->vm_start) >> PAGE_SHIFT; + int rc; if (!xen_feature(XENFEAT_auto_translated_physmap) || !numpgs || !pages) return; - xen_unmap_domain_mfn_range(vma, numpgs, pages); + rc = xen_unmap_domain_mfn_range(vma, numpgs, pages); + if (rc < 0) { + pr_crit("PRIVCMD: leaking %d pages\n", numpgs); + return; + } free_xenballooned_pages(numpgs, pages); kfree(pages); }> [...]> (XEN) *** Dumping CPU0 guest state (d0:v0): *** > (XEN) ----[ Xen-4.4-unstable arm32 debug=y Not tainted ]---- > (XEN) CPU: 0 > (XEN) PC: c0097518Does this address correspond to anything interesting in the dom0 kernel? That might give some hint where it has gotten stuck.> (XEN) CPSR: 60000193 MODE:32-bit Guest SVC > (XEN) R0: 00000018 R1: 00000478 R2: 00000000 R3: c09008e8 > (XEN) R4: c09008e8 R5: c08f2000 R6: c1322a04 R7: c04f784c > (XEN) R8: 60000193 R9: c099c4c4 R10:00000001 R11:c08f3e64 R12:60000193 > (XEN) USR: SP: be9724f8 LR: b6f01234 > (XEN) SVC: SP: c08f3de8 LR: c05e7120 SPSR:60000113 > (XEN) ABT: SP: c0997a0c LR: c05e7a80 SPSR:80000193 > (XEN) UND: SP: c0997a18 LR: c05e78e0 SPSR:80070093 > (XEN) IRQ: SP: c0997a00 LR: c05e76c0 SPSR:60000193 > (XEN) FIQ: SP: 00000000 LR: 00000000 SPSR:00000000 > (XEN) FIQ: R8: 00000000 R9: 00000000 R10:00000000 R11:00000000 R12:00000000 > (XEN) > (XEN) SCTLR: 10c5387d > (XEN) TCR: 00000000 > (XEN) TTBR0: 000000009d27406a > (XEN) TTBR1: 000000008000406a > (XEN) IFAR: b6eb1aa0, IFSR: 00000007 > (XEN) DFAR: b6c00008, DFSR: 00000817 > (XEN) > (XEN) VTCR_EL2: 80002558 > (XEN) VTTBR_EL2: 00010000a200e000 > (XEN) > (XEN) SCTLR_EL2: 30cd187f > (XEN) HCR_EL2: 0000000000282835 > (XEN) TTBR0_EL2: 00000000feedf000 > (XEN) > (XEN) ESR_EL2: 07e00000 > (XEN) HPFAR_EL2: 0000000000482110 > (XEN) HDFAR: d0800100 > (XEN) HIFAR: 00000000 > (XEN) > (XEN) No stack trace for 32-bit guest kernel-mode > (XEN)
On Mon, Dec 2, 2013 at 8:13 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:> On Mon, 2013-12-02 at 08:02 -0500, Vaibhav Bedia wrote: > >> I currently get >> /usr/include/libfdt.h:54:24: fatal error: libfdt_env.h: No such file >> or directory >> >> Google tells me this was bug in the library build [1]... trying to figure >> out how to get this sorted out. > > I keep hitting this, I just grabbed the source and copied libfdt_env.h > to /usr/include. Works for me ;-)Heh i was wondering whether i should just give that a shot. This has apparently been fixed in 13.10 release. I''ll go with the quick hack for now ;)>> >> vcpus = 1 >> >> vif = [ ''bridge=xenbr0'',''mac=00:16:3e:23:24:32''] >> > >> > This is actually creating two vifs. One one xenbr0 with a random mac and >> > one with the given mac address on the default bridge (probably xenbr0!) >> > >> > You probably wanted: >> > vif = [ ''bridge=xenbr0,mac=00:16:3e:23:24:32''] >> > Or just: >> > vif = [ ''mac=00:16:3e:23:24:32''] >> > which works because xenbr0 is the default bridge. >> > >> >> Ok. I wanted only one vif. Didn''t realize this was creating two of those. >> >> Now that i get the console in the ubuntu filesystem for domU i was >> hoping to dig deeper into the "unable to ping" domU problem. >> >> My fresh builds of the kernels for dom0 and domU seems to have >> uncovered some other issue since i just can''t get a reliable domU >> boot now. Right now most of the domU creation hangs and it also >> kills off dom0. I have a heartbeat led in dom0 and that just stops - >> i can switch to xen using ctrl-a keystrokes and back but the dom0 >> seems to have crashed. >> >> Any suggestions on how to debug this? There are few "failed to unmap" >> messages when creating domUs but i don''t know how to debug this :( > > Yes, these are annoying. In the absence of a proper fix I''ve been: > diff --git a/drivers/xen/privcmd.c b/drivers/xen/privcmd.c > index 8e74590..7b383bf 100644 > --- a/drivers/xen/privcmd.c > +++ b/drivers/xen/privcmd.c > @@ -533,11 +533,16 @@ static void privcmd_close(struct vm_area_struct *vma) > { > struct page **pages = vma->vm_private_data; > int numpgs = (vma->vm_end - vma->vm_start) >> PAGE_SHIFT; > + int rc; > > if (!xen_feature(XENFEAT_auto_translated_physmap) || !numpgs || !pages) > return; > > - xen_unmap_domain_mfn_range(vma, numpgs, pages); > + rc = xen_unmap_domain_mfn_range(vma, numpgs, pages); > + if (rc < 0) { > + pr_crit("PRIVCMD: leaking %d pages\n", numpgs); > + return; > + } > free_xenballooned_pages(numpgs, pages); > kfree(pages); > } >Ok i''ll add in this diff.> >> [...] > >> (XEN) *** Dumping CPU0 guest state (d0:v0): *** >> (XEN) ----[ Xen-4.4-unstable arm32 debug=y Not tainted ]---- >> (XEN) CPU: 0 >> (XEN) PC: c0097518 > > Does this address correspond to anything interesting in the dom0 kernel? > That might give some hint where it has gotten stuck. >I''ll check once my dom0 rebuild completes. I really should keep the system map around a bit longer. Regards, Vaibhav
On Mon, 2013-12-02 at 08:26 -0500, Vaibhav Bedia wrote:> I really should keep the system map around a bit longer.FWIW I strongly recommend: CONFIG_DEBUG_INFO=y CONFIG_DEBUG_INFO_REDUCED=y and either addr2line or gdb "list *0xABCDEF". System.map will just tell you which function, after inlining and all that jazz has hidden a bunch of stuff from you, and not a source line number. Ian.
On Mon, Dec 2, 2013 at 8:32 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:> On Mon, 2013-12-02 at 08:26 -0500, Vaibhav Bedia wrote: >> I really should keep the system map around a bit longer. > > FWIW I strongly recommend: > CONFIG_DEBUG_INFO=y > CONFIG_DEBUG_INFO_REDUCED=y > and either addr2line or gdb "list *0xABCDEF". System.map will just tell > you which function, after inlining and all that jazz has hidden a bunch > of stuff from you, and not a source line number. >Ok i''ll keep this in mind :) addr2line points me to irq_restore so that''s definitely interesting. vaibhav@vaibhav-VirtualBox:~/src/linux$ arm-linux-gnueabi-addr2line -f -e vmlinux c0097518 arch_local_irq_restore /home/vaibhav/src/linux/arch/arm/include/asm/irqflags.h:152 My kernel is based off v3.12 and the topmost commit in xen sources is: commit 720f45ad01b6a3af2d77fb8fe122d934bbadba47 Author: Julien Grall <julien.grall@linaro.org> Date: Mon Oct 14 23:19:37 2013 +0100 xen/evtchn: Fix build on ARM The recent event channel changes introduced by commit a77eb86 and before... break the compilation on Xen ARM. This commit adds missing includes in common/event_fifo.c and include/xen/sched.h. Signed-off-by: Julien Grall <julien.grall@linaro.org> Acked-by: Ian Campbell <ian.campbell@citrix.com> I got the xen tools updated. Will update the xen image also and check if it makes a difference. Regards, Vaibhav
On Mon, 2013-12-02 at 09:13 -0500, Vaibhav Bedia wrote:> On Mon, Dec 2, 2013 at 8:32 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote: > > On Mon, 2013-12-02 at 08:26 -0500, Vaibhav Bedia wrote: > >> I really should keep the system map around a bit longer. > > > > FWIW I strongly recommend: > > CONFIG_DEBUG_INFO=y > > CONFIG_DEBUG_INFO_REDUCED=y > > and either addr2line or gdb "list *0xABCDEF". System.map will just tell > > you which function, after inlining and all that jazz has hidden a bunch > > of stuff from you, and not a source line number. > > > Ok i''ll keep this in mind :) > > addr2line points me to irq_restore so that''s definitely interesting. > > vaibhav@vaibhav-VirtualBox:~/src/linux$ arm-linux-gnueabi-addr2line -f > -e vmlinux c0097518 > arch_local_irq_restore > /home/vaibhav/src/linux/arch/arm/include/asm/irqflags.h:152Assuming your file has the same content as mine that would point to arch_local_irq_restore, which is, erm, interesting... I''m not sure what to make of that, if reenabling interrupts were a problem I''d expect the PC to be pointing to some interrupt handler not at the instructing which enabled them. Does your version of the file line up with mine? IOW what do you have at line 152? Ian.> > My kernel is based off v3.12 and the topmost commit in xen sources is: > > commit 720f45ad01b6a3af2d77fb8fe122d934bbadba47 > Author: Julien Grall <julien.grall@linaro.org> > Date: Mon Oct 14 23:19:37 2013 +0100 > > xen/evtchn: Fix build on ARM > > The recent event channel changes introduced by commit a77eb86 and before... > break the compilation on Xen ARM. This commit adds missing includes in > common/event_fifo.c and include/xen/sched.h. > > Signed-off-by: Julien Grall <julien.grall@linaro.org> > Acked-by: Ian Campbell <ian.campbell@citrix.com> > > I got the xen tools updated. Will update the xen image also and check > if it makes > a difference. > > Regards, > Vaibhav
On Mon, Dec 2, 2013 at 9:17 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:> On Mon, 2013-12-02 at 09:13 -0500, Vaibhav Bedia wrote: >> >> addr2line points me to irq_restore so that''s definitely interesting. >> >> vaibhav@vaibhav-VirtualBox:~/src/linux$ arm-linux-gnueabi-addr2line -f >> -e vmlinux c0097518 >> arch_local_irq_restore >> /home/vaibhav/src/linux/arch/arm/include/asm/irqflags.h:152 > > Assuming your file has the same content as mine that would point to > arch_local_irq_restore, which is, erm, interesting... > > I''m not sure what to make of that, if reenabling interrupts were a > problem I''d expect the PC to be pointing to some interrupt handler not > at the instructing which enabled them. > > Does your version of the file line up with mine? IOW what do you have at > line 152? >Yes, that''s the same for me. /* * restore saved IRQ & FIQ state */ static inline void arch_local_irq_restore(unsigned long flags) { asm volatile( " msr " IRQMASK_REG_NAME_W ", %0 @ local_irq_restore" : : "r" (flags) : "memory", "cc"); }
On Mon, Dec 2, 2013 at 9:21 AM, Vaibhav Bedia <vaibhav.bedia@gmail.com> wrote:> On Mon, Dec 2, 2013 at 9:17 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote: >> On Mon, 2013-12-02 at 09:13 -0500, Vaibhav Bedia wrote: >>> >>> addr2line points me to irq_restore so that''s definitely interesting. >>> >>> vaibhav@vaibhav-VirtualBox:~/src/linux$ arm-linux-gnueabi-addr2line -f >>> -e vmlinux c0097518 >>> arch_local_irq_restore >>> /home/vaibhav/src/linux/arch/arm/include/asm/irqflags.h:152 >> >> Assuming your file has the same content as mine that would point to >> arch_local_irq_restore, which is, erm, interesting... >> >> I''m not sure what to make of that, if reenabling interrupts were a >> problem I''d expect the PC to be pointing to some interrupt handler not >> at the instructing which enabled them. >> >> Does your version of the file line up with mine? IOW what do you have at >> line 152? >> > > Yes, that''s the same for me. > > /* > * restore saved IRQ & FIQ state > */ > static inline void arch_local_irq_restore(unsigned long flags) > { > asm volatile( > " msr " IRQMASK_REG_NAME_W ", %0 @ > local_irq_restore" > : > : "r" (flags) > : "memory", "cc"); > }I updated the xen image to the current master and looks like i have some debugging to do... could be some hack that i put in xen src. Right now the last print after a bunch of "fixed name abc" and adding DT aliases is "No console". I''ll get back to this later today and report how it goes. Thanks for all the help so far :) Regards, Vaibhav