Hi, I just upgraded to Xen 4.2.0 and after some problems I got everything working except my older legacy domU''s. I still have some old domU''s ported from Xen 3.0.4 which are running Debian etch and kernel 2.6.16.33-xen. When I try to launch them with xl create I get the following error messages: root@xen-2:/# xl create /etc/xen/lightning.cfg -c Daemon running with PID 5453 libxl: error: libxl_dom.c:34:libxl__domain_type: unable to get domain type for domid=10 Unable to attach console libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited with error status 1 If I try to launch it without the -c parameter it seems to start but it actually goes into some kind of bootloop. /var/log/xen/xl-lightning.log is looping these error messages: root@xen-2:/var/log/xen# cat xl-lightning.log Waiting for domain lightning (domid 132) to die [pid 24083] Domain 132 has shut down, reason code 3 0x3 Action for shutdown reason code 3 is restart Domain 132 needs to be cleaned up: destroying the domain Done. Rebooting now Waiting for domain lightning (domid 134) to die [pid 24083] Domain 134 has shut down, reason code 3 0x3 Action for shutdown reason code 3 is restart Domain 134 needs to be cleaned up: destroying the domain Done. Rebooting now If I start xend and use xm create the domU will start up just fine with no problems. - Valtteri _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Wed, 2012-10-03 at 11:09 +0100, Valtteri Kiviniemi wrote:> root@xen-2:/var/log/xen# cat xl-lightning.log > Waiting for domain lightning (domid 132) to die [pid 24083] > Domain 132 has shut down, reason code 3 0x3Reason code 3 is SHUTDOWN_crash. Please can you try to enable guest console logging as described at http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Guest_console_logs and see if the kernel prints anything at all. I''m not sure if such an old kernel has this option but you could also add "earlyprintk=xen" to the guest command line. Do you get any output in the hypervisor dmesg? Ian.
Valtteri Kiviniemi
2012-Oct-03 10:38 UTC
Re: Xen 4.2.0, xl toolstack cant launch older domUs
Hi, I enabled debugging and console logging. This is where it crashes: Parsing config from /etc/xen/lightning.cfg Daemon running with PID 4952 Linux version 2.6.16.33-xen-domU-oldgame (root@lightning) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Fri Sep 28 14:56:14 EEST 2012 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000080000000 (usable) 1320MB HIGHMEM available. 727MB LOWMEM available. NX (Execute Disable) protection: active early console enabled Built 1 zonelists Kernel command line: root=/dev/xvda1 ro console=xvc0 earlyprintk=xen Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 65536 bytes) Xen reported: 3392.374 MHz processor. disabling early console Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB disabled vmalloc area: ee000000-f51fe000, maxmem 2d7fe000 Memory: 2072132k/2097152k available (1917k kernel code, 23952k reserved, 537k data, 148k init, 1351688k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 6819.95 BogoMIPS (lpj=3409975) Mount-cache hash table entries: 512 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 256K CPU: L3 cache: 8192K Checking ''hlt'' instruction... OK. Initializing CPU#1 Initializing CPU#2 Initializing CPU#3 Initializing CPU#4 Initializing CPU#5 Initializing CPU#6 Brought up 8 CPUs Initializing CPU#7 migration_cost=3 Grant table initialized NET: Registered protocol family 16 xen_mem: Initialising balloon driver. SCSI subsystem initialized highmem bounce pool size: 64 pages Installing knfsd (copyright (C) 1996 okir@monad.swb.de). Initializing Cryptographic API io scheduler noop registered io scheduler cfq registered (default) rtc: IRQ 8 is not free. i8042.c: No controller found. loop: loaded (max 8 devices) Xen virtual console successfully installed as tty1 Event-channel device installed. netfront: Initialising virtual ethernet driver. mice: PS/2 mouse device common for all mice Netfilter messages via NETLINK v0.30. NET: Registered protocol family 2 Registering block device major 202 blkfront: xvda1: barriers enabled netfront: device eth0 has copying receive path. IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 8, 1048576 bytes) TCP bind hash table entries: 65536 (order: 7, 524288 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered ip_conntrack version 2.4 (8192 buckets, 65536 max) - 232 bytes per conntrack ip_conntrack_pptp version 3.1 loaded ip_nat_pptp version 3.0 loaded ip_tables: (C) 2000-2006 Netfilter Core Team ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>. http://snowman.net/projects/ipt_recent/ TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 NET: Registered protocol family 15 Bridge firewalling registered 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com> All bugs added by David S. Miller <davem@redhat.com> Using IPI Shortcut mode end_request: I/O error, dev xvda1, sector 2 EXT3-fs: unable to read superblock Unable to handle kernel paging request at virtual address 05de1ce8 printing eip: c0231fdc 005c4000 -> *pde = 00000000:00000000 Oops: 0000 [#1] SMP CPU: 0 EIP: 0061:[<c0231fdc>] Not tainted VLI EFLAGS: 00010007 (2.6.16.33-xen-domU-oldgame #1) EIP is at blkif_int+0x7f/0x228 eax: 189c9c00 ebx: c04df900 ecx: ed418000 edx: 05de1c00 esi: 00000000 edi: ca010100 ebp: c043d0ac esp: c0367ec0 ds: 007b es: 007b ss: e021 Process swapper (pid: 0, threadinfo=c0366000 task=c030d7c0) Stack: <0>c200ce24 20539c5e 00000000 00000001 00000001 00000002 00000000 00000001 c04df900 00000000 00000000 c0367f6c c0133197 0000011a ed418000 c0367f6c 0000011a 00008d00 c035c100 0000011a c04df900 c013328f 0000011a 0000000a Call Trace: [<c0133197>] handle_IRQ_event+0x38/0xa9 [<c013328f>] __do_IRQ+0x87/0xf8 [<c0106782>] do_IRQ+0x1a/0x25 [<c0228d85>] evtchn_do_upcall+0x95/0xa9 [<c010504d>] hypervisor_callback+0x3d/0x48 [<c0107ecf>] safe_halt+0x7a/0xb2 [<c0102efd>] xen_idle+0x2b/0x4e [<c0103014>] cpu_idle+0x52/0x67 [<c036871c>] start_kernel+0x2b8/0x33c [<c03681ea>] unknown_bootoption+0x0/0x27a Code: 83 ea 01 23 54 24 1c 8d 04 12 01 d0 8d 04 c0 8d 2c 85 40 00 00 00 03 69 28 8b 7d 00 8d 14 bf 89 d0 c1 e0 05 29 d0 01 f8 8d 14 08 <8b> 92 e8 00 00 00 89 54 24 0c 8d 74 08 7c 80 7e 01 00 74 29 31 <0>Kernel panic - not syncing: Fatal exception in interrupt Badness in smp_call_function at arch/i386/kernel/smp-xen.c:520 [<c010c8fe>] smp_call_function+0x146/0x14b [<c011ac6e>] printk+0x1b/0x1f [<c021a120>] do_unblank_screen+0xe/0x129 [<c010c9a9>] smp_send_stop+0x27/0x60 [<c010c943>] stop_this_cpu+0x0/0x3f [<c011a149>] panic+0x5e/0x155 [<c0105948>] die+0x231/0x23b [<c0110348>] do_page_fault+0x396/0xd30 [<c011eb6b>] getnstimeofday+0x14/0x37 [<c010ffb2>] do_page_fault+0x0/0xd30 [<c010500b>] error_code+0x2b/0x30 [<c0231fdc>] blkif_int+0x7f/0x228 [<c0133197>] handle_IRQ_event+0x38/0xa9 [<c013328f>] __do_IRQ+0x87/0xf8 [<c0106782>] do_IRQ+0x1a/0x25 [ - Valtteri 2012/10/3 Ian Campbell <Ian.Campbell@citrix.com>> On Wed, 2012-10-03 at 11:09 +0100, Valtteri Kiviniemi wrote: > > root@xen-2:/var/log/xen# cat xl-lightning.log > > Waiting for domain lightning (domid 132) to die [pid 24083] > > Domain 132 has shut down, reason code 3 0x3 > > Reason code 3 is SHUTDOWN_crash. > > Please can you try to enable guest console logging as described at > http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Guest_console_logs > and see if the kernel prints anything at all. > > I''m not sure if such an old kernel has this option but you could also > add "earlyprintk=xen" to the guest command line. > > Do you get any output in the hypervisor dmesg? > > Ian. > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Valtteri Kiviniemi
2012-Oct-03 10:42 UTC
Re: Xen 4.2.0, xl toolstack cant launch older domUs
Hi, I tried to lower vcpus to 1, and now it produces a different crash: Unable to handle kernel NULL pointer dereference at virtual address 00000024 printing eip: c0232139 005c4000 -> *pde = 00000000:00000000 Oops: 0000 [#1] SMP CPU: 0 EIP: 0061:[<c0232139>] Not tainted VLI EFLAGS: 00010097 (2.6.16.33-xen-domU-oldgame #1) EIP is at blkif_int+0x1dc/0x228 eax: 00000000 ebx: 00000001 ecx: c090e000 edx: 00000000 esi: d92d7c7c edi: ca010100 ebp: ed6ea0ac esp: c0367ec0 ds: 007b es: 007b ss: e021 Process swapper (pid: 0, threadinfo=c0366000 task=c030d7c0) Stack: <0>c200ce24 419c18e3 00000000 00000000 00000001 00000002 00000000 00000001 ed6ab7a0 00000000 00000000 c0367f6c c0133197 00000105 c090e000 c0367f6c 00000105 00008280 c035b680 00000105 ed6ab7a0 c013328f 00000105 0000000a Call Trace: [<c0133197>] handle_IRQ_event+0x38/0xa9 [<c013328f>] __do_IRQ+0x87/0xf8 [<c0106782>] do_IRQ+0x1a/0x25 [<c0228d85>] evtchn_do_upcall+0x95/0xa9 [<c010504d>] hypervisor_callback+0x3d/0x48 [<c0107ecf>] safe_halt+0x7a/0xb2 [<c0102efd>] xen_idle+0x2b/0x4e [<c0103014>] cpu_idle+0x52/0x67 [<c036871c>] start_kernel+0x2b8/0x33c [<c03681ea>] unknown_bootoption+0x0/0x27a Code: c7 04 24 e0 17 30 c0 e8 39 8b ee ff 8b 44 24 38 c7 80 00 14 00 00 00 00 00 00 89 04 24 e8 75 03 00 00 bb a1 ff ff ff 8b 54 24 0c <8b> 42 24 89 44 24 08 89 5c 24 04 89 14 24 e8 3b eb fb ff 85 c0 <0>Kernel panic - not syncing: Fatal exception in interrupt 2012/10/3 Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com>> Hi, > > I enabled debugging and console logging. This is where it crashes: > > Parsing config from /etc/xen/lightning.cfg > Daemon running with PID 4952 > Linux version 2.6.16.33-xen-domU-oldgame (root@lightning) (gcc version > 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Fri Sep 28 14:56:14 > EEST 2012 > BIOS-provided physical RAM map: > Xen: 0000000000000000 - 0000000080000000 (usable) > 1320MB HIGHMEM available. > 727MB LOWMEM available. > NX (Execute Disable) protection: active > early console enabled > Built 1 zonelists > Kernel command line: root=/dev/xvda1 ro console=xvc0 earlyprintk=xen > Enabling fast FPU save and restore... done. > Enabling unmasked SIMD FPU exception support... done. > Initializing CPU#0 > PID hash table entries: 4096 (order: 12, 65536 bytes) > Xen reported: 3392.374 MHz processor. > disabling early console > Console: colour dummy device 80x25 > Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) > Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) > Software IO TLB disabled > vmalloc area: ee000000-f51fe000, maxmem 2d7fe000 > Memory: 2072132k/2097152k available (1917k kernel code, 23952k reserved, > 537k data, 148k init, 1351688k highmem) > Checking if this processor honours the WP bit even in supervisor mode... > Ok. > Calibrating delay using timer specific routine.. 6819.95 BogoMIPS > (lpj=3409975) > Mount-cache hash table entries: 512 > CPU: L1 I cache: 32K, L1 D cache: 32K > CPU: L2 cache: 256K > CPU: L3 cache: 8192K > Checking ''hlt'' instruction... OK. > Initializing CPU#1 > Initializing CPU#2 > Initializing CPU#3 > Initializing CPU#4 > Initializing CPU#5 > Initializing CPU#6 > Brought up 8 CPUs > Initializing CPU#7 > migration_cost=3 > Grant table initialized > NET: Registered protocol family 16 > xen_mem: Initialising balloon driver. > SCSI subsystem initialized > highmem bounce pool size: 64 pages > Installing knfsd (copyright (C) 1996 okir@monad.swb.de). > Initializing Cryptographic API > io scheduler noop registered > io scheduler cfq registered (default) > rtc: IRQ 8 is not free. > i8042.c: No controller found. > loop: loaded (max 8 devices) > Xen virtual console successfully installed as tty1 > Event-channel device installed. > netfront: Initialising virtual ethernet driver. > mice: PS/2 mouse device common for all mice > Netfilter messages via NETLINK v0.30. > NET: Registered protocol family 2 > Registering block device major 202 > blkfront: xvda1: barriers enabled > netfront: device eth0 has copying receive path. > IP route cache hash table entries: 32768 (order: 5, 131072 bytes) > TCP established hash table entries: 131072 (order: 8, 1048576 bytes) > TCP bind hash table entries: 65536 (order: 7, 524288 bytes) > TCP: Hash tables configured (established 131072 bind 65536) > TCP reno registered > ip_conntrack version 2.4 (8192 buckets, 65536 max) - 232 bytes per > conntrack > ip_conntrack_pptp version 3.1 loaded > ip_nat_pptp version 3.0 loaded > ip_tables: (C) 2000-2006 Netfilter Core Team > ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>. > http://snowman.net/projects/ipt_recent/ > TCP bic registered > NET: Registered protocol family 1 > NET: Registered protocol family 17 > NET: Registered protocol family 15 > Bridge firewalling registered > 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com> > All bugs added by David S. Miller <davem@redhat.com> > Using IPI Shortcut mode > end_request: I/O error, dev xvda1, sector 2 > EXT3-fs: unable to read superblock > Unable to handle kernel paging request at virtual address 05de1ce8 > printing eip: > c0231fdc > 005c4000 -> *pde = 00000000:00000000 > Oops: 0000 [#1] > SMP > CPU: 0 > EIP: 0061:[<c0231fdc>] Not tainted VLI > EFLAGS: 00010007 (2.6.16.33-xen-domU-oldgame #1) > EIP is at blkif_int+0x7f/0x228 > eax: 189c9c00 ebx: c04df900 ecx: ed418000 edx: 05de1c00 > esi: 00000000 edi: ca010100 ebp: c043d0ac esp: c0367ec0 > ds: 007b es: 007b ss: e021 > Process swapper (pid: 0, threadinfo=c0366000 task=c030d7c0) > Stack: <0>c200ce24 20539c5e 00000000 00000001 00000001 00000002 00000000 > 00000001 > c04df900 00000000 00000000 c0367f6c c0133197 0000011a ed418000 > c0367f6c > 0000011a 00008d00 c035c100 0000011a c04df900 c013328f 0000011a > 0000000a > Call Trace: > [<c0133197>] handle_IRQ_event+0x38/0xa9 > [<c013328f>] __do_IRQ+0x87/0xf8 > [<c0106782>] do_IRQ+0x1a/0x25 > [<c0228d85>] evtchn_do_upcall+0x95/0xa9 > [<c010504d>] hypervisor_callback+0x3d/0x48 > [<c0107ecf>] safe_halt+0x7a/0xb2 > [<c0102efd>] xen_idle+0x2b/0x4e > [<c0103014>] cpu_idle+0x52/0x67 > [<c036871c>] start_kernel+0x2b8/0x33c > [<c03681ea>] unknown_bootoption+0x0/0x27a > Code: 83 ea 01 23 54 24 1c 8d 04 12 01 d0 8d 04 c0 8d 2c 85 40 00 00 00 03 > 69 28 8b 7d 00 8d 14 bf 89 d0 c1 e0 05 29 d0 01 f8 8d 14 08 <8b> 92 e8 00 > 00 00 89 54 24 0c 8d 74 08 7c 80 7e 01 00 74 29 31 > <0>Kernel panic - not syncing: Fatal exception in interrupt > Badness in smp_call_function at arch/i386/kernel/smp-xen.c:520 > [<c010c8fe>] smp_call_function+0x146/0x14b > [<c011ac6e>] printk+0x1b/0x1f > [<c021a120>] do_unblank_screen+0xe/0x129 > [<c010c9a9>] smp_send_stop+0x27/0x60 > [<c010c943>] stop_this_cpu+0x0/0x3f > [<c011a149>] panic+0x5e/0x155 > [<c0105948>] die+0x231/0x23b > [<c0110348>] do_page_fault+0x396/0xd30 > [<c011eb6b>] getnstimeofday+0x14/0x37 > [<c010ffb2>] do_page_fault+0x0/0xd30 > [<c010500b>] error_code+0x2b/0x30 > [<c0231fdc>] blkif_int+0x7f/0x228 > [<c0133197>] handle_IRQ_event+0x38/0xa9 > [<c013328f>] __do_IRQ+0x87/0xf8 > [<c0106782>] do_IRQ+0x1a/0x25 > [ > > - Valtteri > > > 2012/10/3 Ian Campbell <Ian.Campbell@citrix.com> > >> On Wed, 2012-10-03 at 11:09 +0100, Valtteri Kiviniemi wrote: >> > root@xen-2:/var/log/xen# cat xl-lightning.log >> > Waiting for domain lightning (domid 132) to die [pid 24083] >> > Domain 132 has shut down, reason code 3 0x3 >> >> Reason code 3 is SHUTDOWN_crash. >> >> Please can you try to enable guest console logging as described at >> http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Guest_console_logs >> and see if the kernel prints anything at all. >> >> I''m not sure if such an old kernel has this option but you could also >> add "earlyprintk=xen" to the guest command line. >> >> Do you get any output in the hypervisor dmesg? >> >> Ian. >> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Wed, 2012-10-03 at 11:42 +0100, Valtteri Kiviniemi wrote:> Hi, > > I tried to lower vcpus to 1, and now it produces a different crash: > > Unable to handle kernel NULL pointer dereference at virtual address > 00000024 > printing eip: > c0232139 > 005c4000 -> *pde = 00000000:00000000 > Oops: 0000 [#1] > SMP > CPU: 0 > EIP: 0061:[<c0232139>] Not tainted VLI > EFLAGS: 00010097 (2.6.16.33-xen-domU-oldgame #1) > EIP is at blkif_int+0x1dc/0x228I don''t suppose you have source / debug info for this kernel to resolve this into a location? You say this exact same config works with xend? If so then, since this appears to relate to the devices, one thing which might be worth trying is to set on_crash = "preserve" in your config and run under both xend and xl. You can then collect the content of xenstore (xenstore-ls -fp) in both cases (xend booted ok, xl preserved in the crashed state), and compare. There will be a bunch of differences relating to the xend one finishing its boot but something might stand out in the diff. Just posting both sets of output might be useful. If you run "xl -vvv create" you should also get a bunch of stuff relating to the domain builder and where it is placing things. Running under xend I think something similar is dumped under /var/log/xen (domain-build-ng.log?) What does your config file look like? Ian.
Valtteri Kiviniemi
2012-Oct-03 11:07 UTC
Re: Xen 4.2.0, xl toolstack cant launch older domUs
Hi, I dont have the kernel sources for that 2.6.16.33 any more, this is a very old domU but it still in use since we run some applications there which require old glibc and wont run on newer machines. The domU works perfectly with xend, and has always worked (since xen 3.0.0 every xen upgrade). But now when I decided to move from xend to xl the problems started. Here are the info that you asked, its going to be a long post and hopefully I remembered everything that you asked for: config: kernel = "/boot/vmlinuz-2.6.16.33-xen-domU-oldgame" builder = "linux" memory = "2048" name = "lightning" vcpus = "8" cpus = [ "0", "1", "2", "3", "4", "5", "6", "7" ] vif = [ "mac=00:16:3e:1d:0d:91, bridge=xenbr0" ] disk = [ "phy:/dev/virtuals/lightning,xvda1,w" ] root = "/dev/xvda1 ro" extra = "xencons=tty1 earlyprintk=xen" on_poweroff = "destroy" on_reboot = "restart" on_crash = "preserve" xenstore-ls -fp when started with xend and working: /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2 = "" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/image = "(linux (kernel /boot/bzImage-domU-oldgame) (args ''root=/dev/xvda1 ro console=xvc0 earlyprintk=xen'') (superpages 0) (videoram 4) (pci ()) (nomigrate 0) (tsc_mode 0) (notes (HV_START_LOW 411880652\..." (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/image/ostype = "linux" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/image/kernel "/boot/bzImage-domU-oldgame" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/image/cmdline = "root=/dev/xvda1 ro console=xvc0 earlyprintk=xen" (n0,r11) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/image/ramdisk = "" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device = "" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device/vbd = "" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device/vbd/51713 = "" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device/vbd/51713/frontend "/local/domain/11/device/vbd/51713" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device/vbd/51713/frontend-id "11" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device/vbd/51713/backend-id "0" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device/vbd/51713/backend "/local/domain/0/backend/vbd/11/51713" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device/vif = "" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device/vif/0 = "" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device/vif/0/frontend "/local/domain/11/device/vif/0" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device/vif/0/frontend-id = "11" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device/vif/0/backend-id = "0" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device/vif/0/backend "/local/domain/0/backend/vif/11/0" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device/console = "" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device/console/0 = "" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device/console/0/frontend "/local/domain/11/device/console/0" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device/console/0/frontend-id "11" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device/console/0/backend-id "0" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/device/console/0/backend "/local/domain/0/backend/console/11/0" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/on_xend_stop = "ignore" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/pool_name = "Pool-0" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/shadow_memory = "0" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/uuid "54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2" (n0,r11) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/on_reboot = "restart" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/start_time = "1349262041.78" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/on_poweroff = "destroy" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/bootloader_args = "" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/on_xend_start = "ignore" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/on_crash = "preserve" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/xend = "" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/xend/restart_count = "0" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/vcpus = "1" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/vcpu_avail = "1" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/bootloader = "" (n0) /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2/name = "lightning" (n0) xenstore-ls -fp when started with xl and crashed (preserved): /vm = "" (n0) /vm/e2261517-a75b-4c02-b9db-da9c21a05130 = "" (n0,r1) /vm/e2261517-a75b-4c02-b9db-da9c21a05130/uuid "e2261517-a75b-4c02-b9db-da9c21a05130" (n0,r1) /vm/e2261517-a75b-4c02-b9db-da9c21a05130/name = "lightning" (n0,r1) /vm/e2261517-a75b-4c02-b9db-da9c21a05130/image = "" (n0,r1) /vm/e2261517-a75b-4c02-b9db-da9c21a05130/image/ostype = "linux" (n0,r1) /vm/e2261517-a75b-4c02-b9db-da9c21a05130/image/kernel "/boot/bzImage-domU-oldgame" (n0,r1) /vm/e2261517-a75b-4c02-b9db-da9c21a05130/image/cmdline = "root=/dev/xvda1 ro console=xvc0 earlyprintk=xen" (n0,r1) /vm/e2261517-a75b-4c02-b9db-da9c21a05130/start_time = "1349262365.43" (n0,r1) /libxl = "" (n0) /libxl/1 = "" (n0) /libxl/1/dm-version = "qemu_xen" (n0) domU starter with xl -vvv create: root@xen-2:~# xl -vvv create /etc/xen/lightning.cfg -c Parsing config from /etc/xen/lightning.cfg libxl: debug: libxl_create.c:1173:do_domain_create: ao 0x6243d0: create: how=(nil) callback=(nil) poller=0x623b80 libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda1 spec.backend=unknown libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=xvda1, using backend phy libxl: debug: libxl_create.c:677: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:561:libxl__ev_xswatch_deregister: watch w=0x624750: deregister unregistered libxl: debug: libxl_numa.c:435:libxl__get_numa_candidate: New best NUMA placement candidate found: nr_nodes=1, nr_cpus=8, nr_vcpus=9, free_memkb=31043 libxl: detail: libxl_dom.c:192:numa_place_domain: NUMA placement candidate with 1 nodes, 8 cpus and 31043 KB free selected domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/xvda1 ro console=xvc0 earlyprintk=xen", features="(null)" libxl: debug: libxl_dom.c:380:libxl__build_pv: pv kernel mapped 0 path /boot/bzImage-domU-oldgame domainbuilder: detail: xc_dom_kernel_file: filename="/boot/bzImage-domU-oldgame" domainbuilder: detail: xc_dom_malloc_filemap : 1237 kB domainbuilder: detail: xc_dom_malloc : 2653 kB domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x135462 -> 0x297540 domainbuilder: detail: xc_dom_boot_xen_init: ver 4.2, caps xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 domainbuilder: detail: xc_dom_parse_image: called domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary loader ... domainbuilder: detail: loader probe failed domainbuilder: detail: xc_dom_find_loader: trying Linux bzImage loader ... domainbuilder: detail: xc_dom_probe_bzimage_kernel: kernel is not a bzImage domainbuilder: detail: loader probe failed domainbuilder: detail: xc_dom_find_loader: trying ELF-generic loader ... domainbuilder: detail: loader probe OK xc: detail: elf_parse_binary: phdr: paddr=0xc0100000 memsz=0x20d500 xc: detail: elf_parse_binary: phdr: paddr=0xc030d500 memsz=0xb3308 xc: detail: elf_parse_binary: memory: 0xc0100000 -> 0xc03c0808 xc: detail: elf_xen_parse_note: GUEST_OS = "linux" xc: detail: elf_xen_parse_note: GUEST_VERSION = "2.6" xc: detail: elf_xen_parse_note: XEN_VERSION = "xen-3.0" xc: detail: elf_xen_parse_note: VIRT_BASE = 0xc0000000 xc: detail: elf_xen_parse_note: PADDR_OFFSET = 0xc0000000 xc: detail: elf_xen_parse_note: ENTRY = 0xc0100000 xc: detail: elf_xen_parse_note: HYPERCALL_PAGE = 0xc0101000 xc: detail: elf_xen_parse_note: HV_START_LOW = 0xf5800000 xc: detail: elf_xen_parse_note: FEATURES "writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel" xc: detail: elf_xen_parse_note: PAE_MODE = "yes" xc: detail: elf_xen_parse_note: LOADER = "generic" xc: detail: elf_xen_parse: using notes from SHT_NOTE section xc: detail: elf_xen_addr_calc_check: addresses: xc: detail: virt_base = 0xc0000000 xc: detail: elf_paddr_offset = 0xc0000000 xc: detail: virt_offset = 0x0 xc: detail: virt_kstart = 0xc0100000 xc: detail: virt_kend = 0xc03c0808 xc: detail: virt_entry = 0xc0100000 xc: detail: p2m_base = 0xffffffffffffffff domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_32p: 0xc0100000 -> 0xc03c0808 domainbuilder: detail: xc_dom_mem_init: mem 2048 MB, pages 0x80000 pages, 4k each domainbuilder: detail: xc_dom_mem_init: 0x80000 pages domainbuilder: detail: xc_dom_boot_mem_init: called domainbuilder: detail: x86_compat: guest xen-3.0-x86_32p, address size 32 domainbuilder: detail: xc_dom_malloc : 4096 kB domainbuilder: detail: xc_dom_build_image: called domainbuilder: detail: xc_dom_alloc_segment: kernel : 0xc0100000 -> 0xc03c1000 (pfn 0x100 + 0x2c1 pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x100+0x2c1 at 0x7fcba1b83000 xc: detail: elf_load_binary: phdr 0 at 0x0x7fcba1b83000 -> 0x0x7fcba1d90500 xc: detail: elf_load_binary: phdr 1 at 0x0x7fcba1d90500 -> 0x0x7fcba1e0f93c domainbuilder: detail: xc_dom_alloc_segment: phys2mach : 0xc03c1000 -> 0xc05c1000 (pfn 0x3c1 + 0x200 pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x3c1+0x200 at 0x7fcba1983000 domainbuilder: detail: xc_dom_alloc_page : start info : 0xc05c1000 (pfn 0x5c1) domainbuilder: detail: xc_dom_alloc_page : xenstore : 0xc05c2000 (pfn 0x5c2) domainbuilder: detail: xc_dom_alloc_page : console : 0xc05c3000 (pfn 0x5c3) domainbuilder: detail: nr_page_tables: 0x00000000ffffffff/32: 0x0000000000000000 -> 0x00000000ffffffff, 1 table(s) domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30: 0x00000000c0000000 -> 0x00000000ffffffff, 1 table(s) domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21: 0x00000000c0000000 -> 0x00000000c07fffff, 4 table(s) domainbuilder: detail: xc_dom_alloc_segment: page tables : 0xc05c4000 -> 0xc05ca000 (pfn 0x5c4 + 0x6 pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x5c4+0x6 at 0x7fcba197d000 domainbuilder: detail: xc_dom_alloc_page : boot stack : 0xc05ca000 (pfn 0x5ca) domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0xc05cb000 domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0xc0800000 domainbuilder: detail: xc_dom_boot_image: called domainbuilder: detail: arch_setup_bootearly: doing nothing domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_64 domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_32p <= matches domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32 domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32p domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_64 domainbuilder: detail: xc_dom_update_guest_p2m: dst 32bit, pages 0x80000 domainbuilder: detail: clear_page: pfn 0x5c3, mfn 0x649f86 domainbuilder: detail: clear_page: pfn 0x5c2, mfn 0x649f87 domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x5c1+0x1 at 0x7fcba4599000 domainbuilder: detail: start_info_x86_32: called domainbuilder: detail: setup_hypercall_page: vaddr=0xc0101000 pfn=0x101 domainbuilder: detail: domain builder memory footprint domainbuilder: detail: allocated domainbuilder: detail: malloc : 6780 kB domainbuilder: detail: anon mmap : 0 bytes domainbuilder: detail: mapped domainbuilder: detail: file mmap : 1237 kB domainbuilder: detail: domU mmap : 4896 kB domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn 0xdbdf8 domainbuilder: detail: shared_info_x86_32: called domainbuilder: detail: vcpu_x86_32: called domainbuilder: detail: vcpu_x86_32: cr3: pfn 0x5c4 mfn 0x649f85 domainbuilder: detail: launch_vm: called, ctxt=0x7fff96435b40 domainbuilder: detail: xc_dom_release: called libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=xvda1 spec.backend=phy libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x625598 wpath=/local/domain/0/backend/vbd/2/51713/state token=3/0: register slotnum=3 libxl: debug: libxl_create.c:1186:do_domain_create: ao 0x6243d0: inprogress: poller=0x623b80, flags=i libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x625598 wpath=/local/domain/0/backend/vbd/2/51713/state token=3/0: event epath=/local/domain/0/backend/vbd/2/51713/state libxl: debug: libxl_event.c:596:devstate_watch_callback: backend /local/domain/0/backend/vbd/2/51713/state wanted state 2 ok libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch w=0x625598 wpath=/local/domain/0/backend/vbd/2/51713/state token=3/0: deregister slotnum=3 libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0x625598: deregister unregistered libxl: debug: libxl_device.c:916:device_hotplug: calling hotplug script: /etc/xen/scripts/block add libxl: debug: libxl_event.c:426:watchfd_callback: watch epath=/local/domain/0/backend/vbd/2/51713/state token=3/0: empty slot libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x626f38 wpath=/local/domain/0/backend/vif/2/0/state token=3/1: register slotnum=3 libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x626f38 wpath=/local/domain/0/backend/vif/2/0/state token=3/1: event epath=/local/domain/0/backend/vif/2/0/state libxl: debug: libxl_event.c:596:devstate_watch_callback: backend /local/domain/0/backend/vif/2/0/state wanted state 2 ok libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch w=0x626f38 wpath=/local/domain/0/backend/vif/2/0/state token=3/1: deregister slotnum=3 libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0x626f38: deregister unregistered libxl: debug: libxl_device.c:916:device_hotplug: calling hotplug script: /etc/xen/scripts/vif-bridge online libxl: debug: libxl_event.c:1677:libxl__ao_progress_report: ao 0x6243d0: progress report: callback queued aop=0x627700 libxl: debug: libxl_event.c:1497:libxl__ao_complete: ao 0x6243d0: complete, rc=0 libxl: debug: libxl_event.c:1090:egc_run_callbacks: ao 0x6243d0: progress report: callback aop=0x627700 libxl: debug: libxl_event.c:1469:libxl__ao__destroy: ao 0x6243d0: destroy Daemon running with PID 4881 Linux version 2.6.16.33-xen-domU-oldgame (root@lightning) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Fri Sep 28 14:56:14 EEST 2012 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000080000000 (usable) 1320MB HIGHMEM available. 727MB LOWMEM available. NX (Execute Disable) protection: active early console enabled Built 1 zonelists Kernel command line: root=/dev/xvda1 ro console=xvc0 earlyprintk=xen Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 65536 bytes) Xen reported: 3392.372 MHz processor. disabling early console Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB disabled vmalloc area: ee000000-f51fe000, maxmem 2d7fe000 Memory: 2072132k/2097152k available (1917k kernel code, 23952k reserved, 537k data, 148k init, 1351688k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 6820.46 BogoMIPS (lpj=3410231) Mount-cache hash table entries: 512 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 256K CPU: L3 cache: 8192K Checking ''hlt'' instruction... OK. Brought up 1 CPUs migration_cost=0 Grant table initialized NET: Registered protocol family 16 xen_mem: Initialising balloon driver. SCSI subsystem initialized highmem bounce pool size: 64 pages Installing knfsd (copyright (C) 1996 okir@monad.swb.de). Initializing Cryptographic API io scheduler noop registered io scheduler cfq registered (default) rtc: IRQ 8 is not free. i8042.c: No controller found. loop: loaded (max 8 devices) Xen virtual console successfully installed as tty1 Event-channel device installed. netfront: Initialising virtual ethernet driver. mice: PS/2 mouse device common for all mice Netfilter messages via NETLINK v0.30. NET: Registered protocol family 2 netfront: device eth0 has copying receive path. Registering block device major 202 blkfront: xvda1: barriers enabled IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 8, 1048576 bytes) TCP bind hash table entries: 65536 (order: 7, 524288 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered ip_conntrack version 2.4 (8192 buckets, 65536 max) - 232 bytes per conntrack ip_conntrack_pptp version 3.1 loaded ip_nat_pptp version 3.0 loaded ip_tables: (C) 2000-2006 Netfilter Core Team ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>. http://snowman.net/projects/ipt_recent/ TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 NET: Registered protocol family 15 Bridge firewalling registered 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com> All bugs added by David S. Miller <davem@redhat.com> Using IPI Shortcut mode end_request: I/O error, dev xvda1, sector 2 EXT3-fs: unable to read superblock Unable to handle kernel NULL pointer dereference at virtual address 00000024 printing eip: c0232139 005c4000 -> *pde = 00000000:00000000 Oops: 0000 [#1] SMP CPU: 0 EIP: 0061:[<c0232139>] Not tainted VLI EFLAGS: 00010097 (2.6.16.33-xen-domU-oldgame #1) EIP is at blkif_int+0x1dc/0x228 eax: 00000000 ebx: 00000001 ecx: c090e000 edx: 00000000 esi: d92d7c7c edi: ca010100 ebp: ed6ea0ac esp: c0367ec0 ds: 007b es: 007b ss: e021 Process swapper (pid: 0, threadinfo=c0366000 task=c030d7c0) Stack: <0>c200ce24 109c6373 00000000 00000000 00000001 00000002 00000000 00000001 ed6ab7a0 00000000 00000000 c0367f6c c0133197 00000105 c090e000 c0367f6c 00000105 00008280 c035b680 00000105 ed6ab7a0 c013328f 00000105 0000000a Call Trace: [<c0133197>] handle_IRQ_event+0x38/0xa9 [<c013328f>] __do_IRQ+0x87/0xf8 [<c0106782>] do_IRQ+0x1a/0x25 [<c0228d85>] evtchn_do_upcall+0x95/0xa9 [<c010504d>] hypervisor_callback+0x3d/0x48 [<c0107ecf>] safe_halt+0x7a/0xb2 [<c0102efd>] xen_idle+0x2b/0x4e [<c0103014>] cpu_idle+0x52/0x67 [<c036871c>] start_kernel+0x2b8/0x33c [<c03681ea>] unknown_bootoption+0x0/0x27a Code: c7 04 24 e0 17 30 c0 e8 39 8b ee ff 8b 44 24 38 c7 80 00 14 00 00 00 00 00 00 89 04 24 e8 75 03 00 00 bb a1 ff ff ff 8b 54 24 0c <8b> 42 24 89 44 24 08 89 5c 24 04 89 14 24 e8 3b eb fb ff 85 c0 <0>Kernel panic - not syncing: Fatal exception in interrupt And finally the domain-builder-ng.log when started with xend and working: 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/xvda1 ro console=xvc0 earlyprintk=xen", features="" 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_kernel_file: filename="/boot/bzImage-domU-oldgame" 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_malloc_filemap : 1237 kB 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_malloc : 2653 kB 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x135462 -> 0x297540 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_parse_image: called 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary loader ... 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: loader probe failed 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_find_loader: trying Linux bzImage loader ... 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_probe_bzimage_kernel: kernel is not a bzImage 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: loader probe failed 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_find_loader: trying ELF-generic loader ... 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: loader probe OK 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_parse_binary: phdr: paddr=0xc0100000 memsz=0x20d500 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_parse_binary: phdr: paddr=0xc030d500 memsz=0xb3308 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_parse_binary: memory: 0xc0100000 -> 0xc03c0808 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: GUEST_OS "linux" 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: GUEST_VERSION = "2.6" 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: XEN_VERSION = "xen-3.0" 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: VIRT_BASE 0xc0000000 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: PADDR_OFFSET = 0xc0000000 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: ENTRY 0xc0100000 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: HYPERCALL_PAGE = 0xc0101000 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: HV_START_LOW = 0xf5800000 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: FEATURES "writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel" 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: PAE_MODE "yes" 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: LOADER "generic" 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse: using notes from SHT_NOTE section 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_addr_calc_check: addresses: 2012-10-03 14:00:41 EEST [3773] xc: detail: virt_base 0xc0000000 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_paddr_offset 0xc0000000 2012-10-03 14:00:41 EEST [3773] xc: detail: virt_offset = 0x0 2012-10-03 14:00:41 EEST [3773] xc: detail: virt_kstart 0xc0100000 2012-10-03 14:00:41 EEST [3773] xc: detail: virt_kend 0xc03c0808 2012-10-03 14:00:41 EEST [3773] xc: detail: virt_entry 0xc0100000 2012-10-03 14:00:41 EEST [3773] xc: detail: p2m_base 0xffffffffffffffff 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_32p: 0xc0100000 -> 0xc03c0808 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_release: called 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/xvda1 ro console=xvc0 earlyprintk=xen", features="" 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_kernel_file: filename="/boot/bzImage-domU-oldgame" 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_malloc_filemap : 1237 kB 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_malloc : 2653 kB 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x135462 -> 0x297540 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_boot_xen_init: ver 4.2, caps xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_parse_image: called 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary loader ... 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: loader probe failed 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_find_loader: trying Linux bzImage loader ... 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_probe_bzimage_kernel: kernel is not a bzImage 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: loader probe failed 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_find_loader: trying ELF-generic loader ... 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: loader probe OK 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_parse_binary: phdr: paddr=0xc0100000 memsz=0x20d500 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_parse_binary: phdr: paddr=0xc030d500 memsz=0xb3308 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_parse_binary: memory: 0xc0100000 -> 0xc03c0808 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: GUEST_OS "linux" 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: GUEST_VERSION = "2.6" 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: XEN_VERSION = "xen-3.0" 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: VIRT_BASE 0xc0000000 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: PADDR_OFFSET = 0xc0000000 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: ENTRY 0xc0100000 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: HYPERCALL_PAGE = 0xc0101000 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: HV_START_LOW = 0xf5800000 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: FEATURES "writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel" 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: PAE_MODE "yes" 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse_note: LOADER "generic" 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_parse: using notes from SHT_NOTE section 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_xen_addr_calc_check: addresses: 2012-10-03 14:00:41 EEST [3773] xc: detail: virt_base 0xc0000000 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_paddr_offset 0xc0000000 2012-10-03 14:00:41 EEST [3773] xc: detail: virt_offset = 0x0 2012-10-03 14:00:41 EEST [3773] xc: detail: virt_kstart 0xc0100000 2012-10-03 14:00:41 EEST [3773] xc: detail: virt_kend 0xc03c0808 2012-10-03 14:00:41 EEST [3773] xc: detail: virt_entry 0xc0100000 2012-10-03 14:00:41 EEST [3773] xc: detail: p2m_base 0xffffffffffffffff 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_32p: 0xc0100000 -> 0xc03c0808 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_mem_init: mem 2048 MB, pages 0x80000 pages, 4k each 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_mem_init: 0x80000 pages 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_boot_mem_init: called 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: x86_compat: guest xen-3.0-x86_32p, address size 32 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_malloc : 4096 kB 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_build_image: called 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_alloc_segment: kernel : 0xc0100000 -> 0xc03c1000 (pfn 0x100 + 0x2c1 pages) 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x100+0x2c1 at 0x7fdebe53c000 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_load_binary: phdr 0 at 0x0x7fdebe53c000 -> 0x0x7fdebe749500 2012-10-03 14:00:41 EEST [3773] xc: detail: elf_load_binary: phdr 1 at 0x0x7fdebe749500 -> 0x0x7fdebe7c893c 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_alloc_segment: phys2mach : 0xc03c1000 -> 0xc05c1000 (pfn 0x3c1 + 0x200 pages) 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x3c1+0x200 at 0x7fdebe33c000 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_alloc_page : start info : 0xc05c1000 (pfn 0x5c1) 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_alloc_page : xenstore : 0xc05c2000 (pfn 0x5c2) 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_alloc_page : console : 0xc05c3000 (pfn 0x5c3) 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: nr_page_tables: 0x00000000ffffffff/32: 0x0000000000000000 -> 0x00000000ffffffff, 1 table(s) 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30: 0x00000000c0000000 -> 0x00000000ffffffff, 1 table(s) 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21: 0x00000000c0000000 -> 0x00000000c07fffff, 4 table(s) 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_alloc_segment: page tables : 0xc05c4000 -> 0xc05ca000 (pfn 0x5c4 + 0x6 pages) 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x5c4+0x6 at 0x7fdeca12d000 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_alloc_page : boot stack : 0xc05ca000 (pfn 0x5ca) 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0xc05cb000 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0xc0800000 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_boot_image: called 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: arch_setup_bootearly: doing nothing 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_64 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_32p <= matches 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32p 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_64 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_update_guest_p2m: dst 32bit, pages 0x80000 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: clear_page: pfn 0x5c3, mfn 0x697ee5 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: clear_page: pfn 0x5c2, mfn 0x697ee6 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x5c1+0x1 at 0x7fdeca12a000 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: start_info_x86_32: called 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: setup_hypercall_page: vaddr=0xc0101000 pfn=0x101 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: domain builder memory footprint 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: allocated 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: malloc : 6780 kB 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: anon mmap : 0 bytes 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: mapped 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: file mmap : 1237 kB 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: domU mmap : 4896 kB 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn 0xdbdf8 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: shared_info_x86_32: called 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: vcpu_x86_32: called 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: vcpu_x86_32: cr3: pfn 0x5c4 mfn 0x697ee4 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: launch_vm: called, ctxt=0x7fdebf7fa650 2012-10-03 14:00:41 EEST [3773] domainbuilder: detail: xc_dom_release: called - Valtteri 2012/10/3 Ian Campbell <Ian.Campbell@citrix.com>> On Wed, 2012-10-03 at 11:42 +0100, Valtteri Kiviniemi wrote: > > Hi, > > > > I tried to lower vcpus to 1, and now it produces a different crash: > > > > Unable to handle kernel NULL pointer dereference at virtual address > > 00000024 > > printing eip: > > c0232139 > > 005c4000 -> *pde = 00000000:00000000 > > Oops: 0000 [#1] > > SMP > > CPU: 0 > > EIP: 0061:[<c0232139>] Not tainted VLI > > EFLAGS: 00010097 (2.6.16.33-xen-domU-oldgame #1) > > EIP is at blkif_int+0x1dc/0x228 > > I don''t suppose you have source / debug info for this kernel to resolve > this into a location? > > You say this exact same config works with xend? > > If so then, since this appears to relate to the devices, one thing which > might be worth trying is to set on_crash = "preserve" in your config and > run under both xend and xl. You can then collect the content of xenstore > (xenstore-ls -fp) in both cases (xend booted ok, xl preserved in the > crashed state), and compare. > > There will be a bunch of differences relating to the xend one finishing > its boot but something might stand out in the diff. Just posting both > sets of output might be useful. > > If you run "xl -vvv create" you should also get a bunch of stuff > relating to the domain builder and where it is placing things. Running > under xend I think something similar is dumped under /var/log/xen > (domain-build-ng.log?) > > What does your config file look like? > > Ian. > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Wed, 2012-10-03 at 12:07 +0100, Valtteri Kiviniemi wrote:> > /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2 = "" (n0)The interesting stuff will be under /local/domain/0 and /local/domain/<domU> rather than under /vm. The builder logs were the same modulo some insignificant changes. Ian.
Valtteri Kiviniemi
2012-Oct-03 11:44 UTC
Re: Xen 4.2.0, xl toolstack cant launch older domUs
Hi, Ok, well lets do it thisway. Hopefully I got this right this time. Here is the ALL of the output available from xenstore-ls -fp when I''m only running dom0 and that problematic domU, and when it is launched with Xend and fully working: root@xen-2:~# xenstore-ls -fp /tool = "" (n0) /tool/xenstored = "" (n0) /local = "" (n0) /local/domain = "" (n0) /local/domain/0 = "" (r0) /local/domain/0/vm = "/vm/00000000-0000-0000-0000-000000000000" (r0) /local/domain/0/device = "" (n0) /local/domain/0/control = "" (n0) /local/domain/0/control/platform-feature-multiprocessor-suspend = "1" (n0) /local/domain/0/control/platform-feature-xs_reset_watches = "1" (n0) /local/domain/0/error = "" (n0) /local/domain/0/memory = "" (n0) /local/domain/0/memory/target = "1310720" (n0) /local/domain/0/guest = "" (n0) /local/domain/0/hvmpv = "" (n0) /local/domain/0/data = "" (n0) /local/domain/0/cpu = "" (r0) /local/domain/0/cpu/1 = "" (r0) /local/domain/0/cpu/1/availability = "online" (r0) /local/domain/0/cpu/3 = "" (r0) /local/domain/0/cpu/3/availability = "online" (r0) /local/domain/0/cpu/2 = "" (r0) /local/domain/0/cpu/2/availability = "online" (r0) /local/domain/0/cpu/4 = "" (r0) /local/domain/0/cpu/4/availability = "online" (r0) /local/domain/0/cpu/7 = "" (r0) /local/domain/0/cpu/7/availability = "online" (r0) /local/domain/0/cpu/0 = "" (r0) /local/domain/0/cpu/0/availability = "online" (r0) /local/domain/0/cpu/5 = "" (r0) /local/domain/0/cpu/5/availability = "online" (r0) /local/domain/0/cpu/6 = "" (r0) /local/domain/0/cpu/6/availability = "online" (r0) /local/domain/0/description = "" (r0) /local/domain/0/console = "" (r0) /local/domain/0/console/limit = "1048576" (r0) /local/domain/0/console/type = "xenconsoled" (r0) /local/domain/0/domid = "0" (r0) /local/domain/0/name = "Domain-0" (r0) /local/domain/0/backend = "" (r0) /local/domain/0/backend/vbd = "" (r0) /local/domain/0/backend/vbd/9 = "" (r0) /local/domain/0/backend/vbd/9/51713 = "" (n0,r9) /local/domain/0/backend/vbd/9/51713/domain = "lightning" (n0,r9) /local/domain/0/backend/vbd/9/51713/frontend "/local/domain/9/device/vbd/51713" (n0,r9) /local/domain/0/backend/vbd/9/51713/uuid "07c30250-23d0-45dc-a7fd-27c4705ab946" (n0,r9) /local/domain/0/backend/vbd/9/51713/bootable = "1" (n0,r9) /local/domain/0/backend/vbd/9/51713/dev = "xvda1" (n0,r9) /local/domain/0/backend/vbd/9/51713/state = "4" (n0,r9) /local/domain/0/backend/vbd/9/51713/params = "/dev/virtuals/lightning" (n0,r9) /local/domain/0/backend/vbd/9/51713/mode = "w" (n0,r9) /local/domain/0/backend/vbd/9/51713/online = "1" (n0,r9) /local/domain/0/backend/vbd/9/51713/frontend-id = "9" (n0,r9) /local/domain/0/backend/vbd/9/51713/type = "phy" (n0,r9) /local/domain/0/backend/vbd/9/51713/physical-device = "fd:7" (n0,r9) /local/domain/0/backend/vbd/9/51713/hotplug-status = "connected" (n0,r9) /local/domain/0/backend/vbd/9/51713/feature-flush-cache = "1" (n0,r9) /local/domain/0/backend/vbd/9/51713/feature-discard = "0" (n0,r9) /local/domain/0/backend/vbd/9/51713/feature-barrier = "1" (n0,r9) /local/domain/0/backend/vbd/9/51713/sectors = "104857600" (n0,r9) /local/domain/0/backend/vbd/9/51713/info = "0" (n0,r9) /local/domain/0/backend/vbd/9/51713/sector-size = "512" (n0,r9) /local/domain/0/backend/vif = "" (r0) /local/domain/0/backend/vif/9 = "" (r0) /local/domain/0/backend/vif/9/0 = "" (n0,r9) /local/domain/0/backend/vif/9/0/bridge = "xenbr0" (n0,r9) /local/domain/0/backend/vif/9/0/domain = "lightning" (n0,r9) /local/domain/0/backend/vif/9/0/handle = "0" (n0,r9) /local/domain/0/backend/vif/9/0/uuid "07ba2113-4679-843f-f4d8-eadaec462af0" (n0,r9) /local/domain/0/backend/vif/9/0/script = "/etc/xen/scripts/vif-bridge" (n0,r9) /local/domain/0/backend/vif/9/0/state = "4" (n0,r9) /local/domain/0/backend/vif/9/0/frontend = "/local/domain/9/device/vif/0" (n0,r9) /local/domain/0/backend/vif/9/0/mac = "00:16:3e:1d:0d:91" (n0,r9) /local/domain/0/backend/vif/9/0/online = "1" (n0,r9) /local/domain/0/backend/vif/9/0/frontend-id = "9" (n0,r9) /local/domain/0/backend/vif/9/0/feature-sg = "1" (n0,r9) /local/domain/0/backend/vif/9/0/feature-gso-tcpv4 = "1" (n0,r9) /local/domain/0/backend/vif/9/0/feature-rx-copy = "1" (n0,r9) /local/domain/0/backend/vif/9/0/feature-rx-flip = "0" (n0,r9) /local/domain/0/backend/vif/9/0/hotplug-status = "connected" (n0,r9) /local/domain/0/backend/console = "" (r0) /local/domain/0/backend/console/9 = "" (r0) /local/domain/0/backend/console/9/0 = "" (n0,r9) /local/domain/0/backend/console/9/0/domain = "lightning" (n0,r9) /local/domain/0/backend/console/9/0/protocol = "vt100" (n0,r9) /local/domain/0/backend/console/9/0/uuid "c17b2697-71ba-011d-9958-2094cf39a7e4" (n0,r9) /local/domain/0/backend/console/9/0/frontend "/local/domain/9/device/console/0" (n0,r9) /local/domain/0/backend/console/9/0/state = "1" (n0,r9) /local/domain/0/backend/console/9/0/location = "2" (n0,r9) /local/domain/0/backend/console/9/0/online = "1" (n0,r9) /local/domain/0/backend/console/9/0/frontend-id = "9" (n0,r9) /local/domain/9 = "" (n0,r9) /local/domain/9/vm = "/vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df" (n0,r9) /local/domain/9/device = "" (n9) /local/domain/9/device/vbd = "" (n9) /local/domain/9/device/vbd/51713 = "" (n9,r0) /local/domain/9/device/vbd/51713/virtual-device = "51713" (n9,r0) /local/domain/9/device/vbd/51713/device-type = "disk" (n9,r0) /local/domain/9/device/vbd/51713/protocol = "x86_32-abi" (n9,r0) /local/domain/9/device/vbd/51713/backend-id = "0" (n9,r0) /local/domain/9/device/vbd/51713/state = "4" (n9,r0) /local/domain/9/device/vbd/51713/backend "/local/domain/0/backend/vbd/9/51713" (n9,r0) /local/domain/9/device/vbd/51713/ring-ref = "8" (n9,r0) /local/domain/9/device/vbd/51713/event-channel = "6" (n9,r0) /local/domain/9/device/vif = "" (n9) /local/domain/9/device/vif/0 = "" (n9,r0) /local/domain/9/device/vif/0/mac = "00:16:3e:1d:0d:91" (n9,r0) /local/domain/9/device/vif/0/handle = "0" (n9,r0) /local/domain/9/device/vif/0/protocol = "x86_32-abi" (n9,r0) /local/domain/9/device/vif/0/backend-id = "0" (n9,r0) /local/domain/9/device/vif/0/state = "4" (n9,r0) /local/domain/9/device/vif/0/backend = "/local/domain/0/backend/vif/9/0" (n9,r0) /local/domain/9/device/vif/0/tx-ring-ref = "521" (n9,r0) /local/domain/9/device/vif/0/rx-ring-ref = "522" (n9,r0) /local/domain/9/device/vif/0/event-channel = "7" (n9,r0) /local/domain/9/device/vif/0/request-rx-copy = "1" (n9,r0) /local/domain/9/device/vif/0/feature-rx-notify = "1" (n9,r0) /local/domain/9/device/vif/0/feature-sg = "1" (n9,r0) /local/domain/9/device/vif/0/feature-gso-tcpv4 = "1" (n9,r0) /local/domain/9/device/console = "" (n9) /local/domain/9/device/console/0 = "" (n9,r0) /local/domain/9/device/console/0/protocol = "x86_32-abi" (n9,r0) /local/domain/9/device/console/0/state = "1" (n9,r0) /local/domain/9/device/console/0/backend-id = "0" (n9,r0) /local/domain/9/device/console/0/backend "/local/domain/0/backend/console/9/0" (n9,r0) /local/domain/9/control = "" (n9) /local/domain/9/control/platform-feature-multiprocessor-suspend = "1" (n9) /local/domain/9/control/platform-feature-xs_reset_watches = "1" (n9) /local/domain/9/control/feature-reboot = "1" (n9) /local/domain/9/control/feature-sysrq = "1" (n9) /local/domain/9/error = "" (n9) /local/domain/9/memory = "" (n9) /local/domain/9/memory/target = "2097152" (n9) /local/domain/9/guest = "" (n9) /local/domain/9/hvmpv = "" (n9) /local/domain/9/data = "" (n9) /local/domain/9/device-misc = "" (n0,r9) /local/domain/9/device-misc/vif = "" (n0,r9) /local/domain/9/device-misc/vif/nextDeviceID = "1" (n0,r9) /local/domain/9/device-misc/console = "" (n0,r9) /local/domain/9/device-misc/console/nextDeviceID = "1" (n0,r9) /local/domain/9/console = "" (n0,r9) /local/domain/9/console/ring-ref = "7027814" (n0,r9) /local/domain/9/console/port = "2" (n0,r9) /local/domain/9/console/limit = "1048576" (n0,r9) /local/domain/9/console/type = "xenconsoled" (n0,r9) /local/domain/9/console/tty = "/dev/pts/2" (n0,r9) /local/domain/9/image = "" (n0,r9) /local/domain/9/image/entry = "3222274048" (n0,r9) /local/domain/9/image/loader = "generic" (n0,r9) /local/domain/9/image/hv-start-low = "4118806528" (n0,r9) /local/domain/9/image/guest-os = "linux" (n0,r9) /local/domain/9/image/features = "" (n0,r9) /local/domain/9/image/features/writable-descriptor-tables = "1" (n0,r9) /local/domain/9/image/features/supervisor-mode-kernel = "1" (n0,r9) /local/domain/9/image/features/pae-pgdir-above-4gb = "1" (n0,r9) /local/domain/9/image/features/writable-page-tables = "1" (n0,r9) /local/domain/9/image/features/auto-translated-physmap = "1" (n0,r9) /local/domain/9/image/hypercall-page = "3222278144" (n0,r9) /local/domain/9/image/guest-version = "2.6" (n0,r9) /local/domain/9/image/pae-mode = "yes" (n0,r9) /local/domain/9/image/paddr-offset = "3221225472" (n0,r9) /local/domain/9/image/virt-base = "3221225472" (n0,r9) /local/domain/9/image/xen-version = "xen-3.0" (n0,r9) /local/domain/9/store = "" (n0,r9) /local/domain/9/store/ring-ref = "7027815" (n0,r9) /local/domain/9/store/port = "1" (n0,r9) /local/domain/9/description = "" (n0,r9) /local/domain/9/cpu = "" (n0,r9) /local/domain/9/cpu/0 = "" (n0,r9) /local/domain/9/cpu/0/availability = "online" (n0,r9) /local/domain/9/name = "lightning" (n0,r9) /local/domain/9/domid = "9" (n0,r9) /local/pool = "" (n0) /local/pool/0 = "" (n0) /local/pool/0/other_config = "" (n0) /local/pool/0/description = "Pool-0" (n0) /local/pool/0/uuid = "caa85392-7062-bd40-53ee-fd3a7c1a1a6f" (n0) /local/pool/0/name = "Pool-0" (n0) /vm = "" (n0) /vm/00000000-0000-0000-0000-000000000000 = "" (n0) /vm/00000000-0000-0000-0000-000000000000/on_xend_stop = "ignore" (n0) /vm/00000000-0000-0000-0000-000000000000/pool_name = "Pool-0" (n0) /vm/00000000-0000-0000-0000-000000000000/shadow_memory = "0" (n0) /vm/00000000-0000-0000-0000-000000000000/uuid "00000000-0000-0000-0000-000000000000" (r0) /vm/00000000-0000-0000-0000-000000000000/on_reboot = "restart" (n0) /vm/00000000-0000-0000-0000-000000000000/image = "(linux (kernel '''') (superpages 0) (nomigrate 0) (tsc_mode 0))" (n0) /vm/00000000-0000-0000-0000-000000000000/image/ostype = "linux" (n0) /vm/00000000-0000-0000-0000-000000000000/image/kernel = "" (n0) /vm/00000000-0000-0000-0000-000000000000/image/cmdline = "" (r0) /vm/00000000-0000-0000-0000-000000000000/image/ramdisk = "" (n0) /vm/00000000-0000-0000-0000-000000000000/on_poweroff = "destroy" (n0) /vm/00000000-0000-0000-0000-000000000000/bootloader_args = "" (n0) /vm/00000000-0000-0000-0000-000000000000/on_xend_start = "ignore" (n0) /vm/00000000-0000-0000-0000-000000000000/on_crash = "restart" (n0) /vm/00000000-0000-0000-0000-000000000000/xend = "" (n0) /vm/00000000-0000-0000-0000-000000000000/xend/restart_count = "0" (n0) /vm/00000000-0000-0000-0000-000000000000/vcpus = "8" (n0) /vm/00000000-0000-0000-0000-000000000000/vcpu_avail = "255" (n0) /vm/00000000-0000-0000-0000-000000000000/bootloader = "" (n0) /vm/00000000-0000-0000-0000-000000000000/name = "Domain-0" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df = "" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/image = "(linux (kernel /boot/bzImage-domU-oldgame) (args ''root=/dev/xvda1 ro console=xvc0 earlyprintk=xen'') (superpages 0) (videoram 4) (pci ()) (nomigrate 0) (tsc_mode 0) (notes (HV_START_LOW 411880652\..." (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/image/ostype = "linux" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/image/kernel "/boot/bzImage-domU-oldgame" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/image/cmdline = "root=/dev/xvda1 ro console=xvc0 earlyprintk=xen" (n0,r9) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/image/ramdisk = "" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device = "" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device/vbd = "" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device/vbd/51713 = "" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device/vbd/51713/frontend "/local/domain/9/device/vbd/51713" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device/vbd/51713/frontend-id "9" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device/vbd/51713/backend-id "0" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device/vbd/51713/backend "/local/domain/0/backend/vbd/9/51713" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device/vif = "" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device/vif/0 = "" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device/vif/0/frontend "/local/domain/9/device/vif/0" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device/vif/0/frontend-id = "9" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device/vif/0/backend-id = "0" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device/vif/0/backend "/local/domain/0/backend/vif/9/0" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device/console = "" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device/console/0 = "" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device/console/0/frontend "/local/domain/9/device/console/0" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device/console/0/frontend-id "9" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device/console/0/backend-id "0" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/device/console/0/backend "/local/domain/0/backend/console/9/0" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/on_xend_stop = "ignore" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/pool_name = "Pool-0" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/shadow_memory = "0" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/uuid "f73e32ee-c0ee-2d58-98df-d7f2f6e062df" (n0,r9) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/on_reboot = "restart" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/start_time = "1349264227.39" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/on_poweroff = "destroy" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/bootloader_args = "" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/on_xend_start = "ignore" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/on_crash = "preserve" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/xend = "" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/xend/restart_count = "0" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/vcpus = "1" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/vcpu_avail = "1" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/bootloader = "" (n0) /vm/f73e32ee-c0ee-2d58-98df-d7f2f6e062df/name = "lightning" (n0) ...And Here is the ALL of the output available from xenstore-ls -fp when I''m only running dom0 and that problematic domU and when it is launched with xl and crashed (preserved): root@xen-2:~# xenstore-ls -fp /tool = "" (n0) /tool/xenstored = "" (n0) /local = "" (n0) /local/domain = "" (n0) /local/domain/0 = "" (n0) /local/domain/0/name = "Domain-0" (n0) /local/domain/0/device-model = "" (n0) /local/domain/0/device-model/0 = "" (n0) /local/domain/0/device-model/0/state = "running" (n0) /local/domain/0/libxl = "" (n0) /local/domain/0/libxl/disable_udev = "1" (n0) /local/domain/0/backend = "" (n0) /local/domain/0/backend/vbd = "" (n0) /local/domain/0/backend/vbd/1 = "" (n0) /local/domain/0/backend/vbd/1/51713 = "" (n0,r1) /local/domain/0/backend/vbd/1/51713/frontend "/local/domain/1/device/vbd/51713" (n0,r1) /local/domain/0/backend/vbd/1/51713/params = "/dev/virtuals/lightning" (n0,r1) /local/domain/0/backend/vbd/1/51713/script = "/etc/xen/scripts/block" (n0,r1) /local/domain/0/backend/vbd/1/51713/physical-device = "fd:7" (n0,r1) /local/domain/0/backend/vbd/1/51713/frontend-id = "1" (n0,r1) /local/domain/0/backend/vbd/1/51713/online = "1" (n0,r1) /local/domain/0/backend/vbd/1/51713/removable = "0" (n0,r1) /local/domain/0/backend/vbd/1/51713/bootable = "1" (n0,r1) /local/domain/0/backend/vbd/1/51713/state = "4" (n0,r1) /local/domain/0/backend/vbd/1/51713/dev = "xvda1" (n0,r1) /local/domain/0/backend/vbd/1/51713/type = "phy" (n0,r1) /local/domain/0/backend/vbd/1/51713/mode = "w" (n0,r1) /local/domain/0/backend/vbd/1/51713/device-type = "disk" (n0,r1) /local/domain/0/backend/vbd/1/51713/feature-flush-cache = "1" (n0,r1) /local/domain/0/backend/vbd/1/51713/feature-discard = "0" (n0,r1) /local/domain/0/backend/vbd/1/51713/feature-barrier = "1" (n0,r1) /local/domain/0/backend/vbd/1/51713/sectors = "104857600" (n0,r1) /local/domain/0/backend/vbd/1/51713/info = "0" (n0,r1) /local/domain/0/backend/vbd/1/51713/sector-size = "512" (n0,r1) /local/domain/0/backend/console = "" (n0) /local/domain/0/backend/console/1 = "" (n0) /local/domain/0/backend/console/1/0 = "" (n0,r1) /local/domain/0/backend/console/1/0/frontend = "/local/domain/1/console" (n0,r1) /local/domain/0/backend/console/1/0/frontend-id = "1" (n0,r1) /local/domain/0/backend/console/1/0/online = "1" (n0,r1) /local/domain/0/backend/console/1/0/state = "1" (n0,r1) /local/domain/0/backend/console/1/0/domain = "lightning" (n0,r1) /local/domain/0/backend/console/1/0/protocol = "vt100" (n0,r1) /local/domain/0/backend/vif = "" (n0) /local/domain/0/backend/vif/1 = "" (n0) /local/domain/0/backend/vif/1/0 = "" (n0,r1) /local/domain/0/backend/vif/1/0/frontend = "/local/domain/1/device/vif/0" (n0,r1) /local/domain/0/backend/vif/1/0/frontend-id = "1" (n0,r1) /local/domain/0/backend/vif/1/0/online = "1" (n0,r1) /local/domain/0/backend/vif/1/0/state = "4" (n0,r1) /local/domain/0/backend/vif/1/0/script = "/etc/xen/scripts/vif-bridge" (n0,r1) /local/domain/0/backend/vif/1/0/mac = "00:16:3e:1d:0d:91" (n0,r1) /local/domain/0/backend/vif/1/0/bridge = "xenbr0" (n0,r1) /local/domain/0/backend/vif/1/0/handle = "0" (n0,r1) /local/domain/0/backend/vif/1/0/type = "vif" (n0,r1) /local/domain/0/backend/vif/1/0/feature-sg = "1" (n0,r1) /local/domain/0/backend/vif/1/0/feature-gso-tcpv4 = "1" (n0,r1) /local/domain/0/backend/vif/1/0/feature-rx-copy = "1" (n0,r1) /local/domain/0/backend/vif/1/0/feature-rx-flip = "0" (n0,r1) /local/domain/0/backend/vif/1/0/hotplug-status = "connected" (n0,r1) /local/domain/1 = "" (n0,r1) /local/domain/1/vm = "/vm/55f79877-0895-400a-97ce-da869599a1ce" (n0,r1) /local/domain/1/name = "lightning" (n0,r1) /local/domain/1/cpu = "" (n0,r1) /local/domain/1/cpu/0 = "" (n0,r1) /local/domain/1/cpu/0/availability = "online" (n0,r1) /local/domain/1/memory = "" (n0,r1) /local/domain/1/memory/static-max = "2097152" (n0,r1) /local/domain/1/memory/target = "2097153" (n0,r1) /local/domain/1/memory/videoram = "-1" (n0,r1) /local/domain/1/device = "" (n0,r1) /local/domain/1/device/suspend = "" (n0,r1) /local/domain/1/device/suspend/event-channel = "" (n1) /local/domain/1/device/vbd = "" (n0,r1) /local/domain/1/device/vbd/51713 = "" (n1,r0) /local/domain/1/device/vbd/51713/backend "/local/domain/0/backend/vbd/1/51713" (n1,r0) /local/domain/1/device/vbd/51713/backend-id = "0" (n1,r0) /local/domain/1/device/vbd/51713/state = "4" (n1,r0) /local/domain/1/device/vbd/51713/virtual-device = "51713" (n1,r0) /local/domain/1/device/vbd/51713/device-type = "disk" (n1,r0) /local/domain/1/device/vbd/51713/ring-ref = "8" (n1,r0) /local/domain/1/device/vbd/51713/event-channel = "6" (n1,r0) /local/domain/1/device/vif = "" (n0,r1) /local/domain/1/device/vif/0 = "" (n1,r0) /local/domain/1/device/vif/0/backend = "/local/domain/0/backend/vif/1/0" (n1,r0) /local/domain/1/device/vif/0/backend-id = "0" (n1,r0) /local/domain/1/device/vif/0/state = "4" (n1,r0) /local/domain/1/device/vif/0/handle = "0" (n1,r0) /local/domain/1/device/vif/0/mac = "00:16:3e:1d:0d:91" (n1,r0) /local/domain/1/device/vif/0/tx-ring-ref = "521" (n1,r0) /local/domain/1/device/vif/0/rx-ring-ref = "522" (n1,r0) /local/domain/1/device/vif/0/event-channel = "7" (n1,r0) /local/domain/1/device/vif/0/request-rx-copy = "1" (n1,r0) /local/domain/1/device/vif/0/feature-rx-notify = "1" (n1,r0) /local/domain/1/device/vif/0/feature-sg = "1" (n1,r0) /local/domain/1/device/vif/0/feature-gso-tcpv4 = "1" (n1,r0) /local/domain/1/control = "" (n0,r1) /local/domain/1/control/shutdown = "" (n1) /local/domain/1/control/platform-feature-multiprocessor-suspend = "1" (n0,r1) /local/domain/1/control/platform-feature-xs_reset_watches = "1" (n0,r1) /local/domain/1/data = "" (n1) /local/domain/1/domid = "1" (n0,r1) /local/domain/1/store = "" (n0,r1) /local/domain/1/store/port = "1" (n0,r1) /local/domain/1/store/ring-ref = "6594439" (n0,r1) /local/domain/1/console = "" (n1,r0) /local/domain/1/console/backend = "/local/domain/0/backend/console/1/0" (n1,r0) /local/domain/1/console/backend-id = "0" (n1,r0) /local/domain/1/console/limit = "1048576" (n1,r0) /local/domain/1/console/type = "xenconsoled" (n1,r0) /local/domain/1/console/output = "pty" (n1,r0) /local/domain/1/console/port = "2" (n1,r0) /local/domain/1/console/ring-ref = "6594438" (n1,r0) /local/domain/1/console/tty = "/dev/pts/3" (n1,r0) /vm = "" (n0) /vm/55f79877-0895-400a-97ce-da869599a1ce = "" (n0,r1) /vm/55f79877-0895-400a-97ce-da869599a1ce/uuid "55f79877-0895-400a-97ce-da869599a1ce" (n0,r1) /vm/55f79877-0895-400a-97ce-da869599a1ce/name = "lightning" (n0,r1) /vm/55f79877-0895-400a-97ce-da869599a1ce/image = "" (n0,r1) /vm/55f79877-0895-400a-97ce-da869599a1ce/image/ostype = "linux" (n0,r1) /vm/55f79877-0895-400a-97ce-da869599a1ce/image/kernel "/boot/bzImage-domU-oldgame" (n0,r1) /vm/55f79877-0895-400a-97ce-da869599a1ce/image/cmdline = "root=/dev/xvda1 ro console=xvc0 earlyprintk=xen" (n0,r1) /vm/55f79877-0895-400a-97ce-da869599a1ce/start_time = "1349264651.94" (n0,r1) /libxl = "" (n0) /libxl/1 = "" (n0) /libxl/1/dm-version = "qemu_xen" (n0) - Valtteri 2012/10/3 Ian Campbell <Ian.Campbell@citrix.com>> On Wed, 2012-10-03 at 12:07 +0100, Valtteri Kiviniemi wrote: > > > > /vm/54fd0bf5-0cc8-802a-880e-f5f9dc0e4ec2 = "" (n0) > > The interesting stuff will be under /local/domain/0 > and /local/domain/<domU> rather than under /vm. > > The builder logs were the same modulo some insignificant changes. > > Ian. > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Wed, 2012-10-03 at 12:44 +0100, Valtteri Kiviniemi wrote:> Hi, > > Ok, well lets do it thisway. Hopefully I got this right this time.You did, thanks. (aside, can you not top-post please) A bit of a shot in the dark but what is the address size (i.e. 64 bit or 32 bit) for each of your hypervisor, dom0 and domU kernels? Does this change anything: xl cr -p lightning.cfg xenstore-write /local/domain/$(xl domid lightning)/device/vbd/51713/protocol x86_32-abi xl unpause lightning (this assumes the domains cfg is lightning.cfg and name is lightning) Ian.
Valtteri Kiviniemi
2012-Oct-03 12:19 UTC
Re: Xen 4.2.0, xl toolstack cant launch older domUs
2012/10/3 Ian Campbell <Ian.Campbell@citrix.com>> On Wed, 2012-10-03 at 12:44 +0100, Valtteri Kiviniemi wrote: > > Hi, > > > > Ok, well lets do it thisway. Hopefully I got this right this time. > > You did, thanks. (aside, can you not top-post please) > > A bit of a shot in the dark but what is the address size (i.e. 64 bit or > 32 bit) for each of your hypervisor, dom0 and domU kernels? > > Does this change anything: > xl cr -p lightning.cfg > xenstore-write /local/domain/$(xl domid > lightning)/device/vbd/51713/protocol x86_32-abi > xl unpause lightning > > (this assumes the domains cfg is lightning.cfg and name is lightning) > > Ian. > >Hi, Sorry for the top posting, I''m at work at the moment and using different mail client which is is configured for top posting and I was too lazy to change it. But that did do the trick, the domU is now fillu booting and working! - Valtteri _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Valtteri Kiviniemi
2012-Oct-03 12:25 UTC
Re: Xen 4.2.0, xl toolstack cant launch older domUs
2012/10/3 Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com>> > 2012/10/3 Ian Campbell <Ian.Campbell@citrix.com> > >> On Wed, 2012-10-03 at 12:44 +0100, Valtteri Kiviniemi wrote: >> > Hi, >> > >> > Ok, well lets do it thisway. Hopefully I got this right this time. >> >> You did, thanks. (aside, can you not top-post please) >> >> A bit of a shot in the dark but what is the address size (i.e. 64 bit or >> 32 bit) for each of your hypervisor, dom0 and domU kernels? >> >> Does this change anything: >> xl cr -p lightning.cfg >> xenstore-write /local/domain/$(xl domid >> lightning)/device/vbd/51713/protocol x86_32-abi >> xl unpause lightning >> >> (this assumes the domains cfg is lightning.cfg and name is lightning) >> >> Ian. >> >> > Hi, > > Sorry for the top posting, I''m at work at the moment and using different > mail client which is is configured for top posting and I was too lazy to > change it. > > But that did do the trick, the domU is now fillu booting and working! > > - Valtteri > >Hi, dom0 is 64bit, hypervisor is 64bit and that domU (lightning) is 32bit. - Valtteri _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Valtteri Kiviniemi
2012-Oct-03 15:29 UTC
Re: Xen 4.2.0, xl toolstack cant launch older domUs
2012/10/3 Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com>> > > 2012/10/3 Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com> > >> >> 2012/10/3 Ian Campbell <Ian.Campbell@citrix.com> >> >>> On Wed, 2012-10-03 at 12:44 +0100, Valtteri Kiviniemi wrote: >>> > Hi, >>> > >>> > Ok, well lets do it thisway. Hopefully I got this right this time. >>> >>> You did, thanks. (aside, can you not top-post please) >>> >>> A bit of a shot in the dark but what is the address size (i.e. 64 bit or >>> 32 bit) for each of your hypervisor, dom0 and domU kernels? >>> >>> Does this change anything: >>> xl cr -p lightning.cfg >>> xenstore-write /local/domain/$(xl domid >>> lightning)/device/vbd/51713/protocol x86_32-abi >>> xl unpause lightning >>> >>> (this assumes the domains cfg is lightning.cfg and name is lightning) >>> >>> Ian. >>> >>> >> Hi, >> >> Sorry for the top posting, I''m at work at the moment and using different >> mail client which is is configured for top posting and I was too lazy to >> change it. >> >> But that did do the trick, the domU is now fillu booting and working! >> >> - Valtteri >> >> > Hi, > > dom0 is 64bit, hypervisor is 64bit and that domU (lightning) is 32bit. > > - Valtteri >Hi, I have now made a startup script that starts the domU first by pausing it, then writes that thingy in xenstore and then unpauses it. Its working now fine. I assume that this is some kind of bug that will be fixed on later Xen versions, or is this caused by something in my end? Do I have to do something else to get the domU to startup normally? - Valtteri _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Wed, 2012-10-03 at 16:29 +0100, Valtteri Kiviniemi wrote:> > > 2012/10/3 Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com> > > > 2012/10/3 Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com> > > 2012/10/3 Ian Campbell <Ian.Campbell@citrix.com> > On Wed, 2012-10-03 at 12:44 +0100, Valtteri > Kiviniemi wrote: > > Hi, > > > > Ok, well lets do it thisway. Hopefully I got > this right this time. > > > You did, thanks. (aside, can you not top-post > please) > > A bit of a shot in the dark but what is the > address size (i.e. 64 bit or > 32 bit) for each of your hypervisor, dom0 and > domU kernels? > > Does this change anything: > xl cr -p lightning.cfg > xenstore-write /local/domain/$(xl > domid lightning)/device/vbd/51713/protocol > x86_32-abi > xl unpause lightning > > (this assumes the domains cfg is lightning.cfg > and name is lightning) > > Ian. > > > Hi, > > Sorry for the top posting, I''m at work at the moment > and using different mail client which is is configured > for top posting and I was too lazy to change it. > > But that did do the trick, the domU is now fillu > booting and working! > > - Valtteri > > > > > Hi, > > dom0 is 64bit, hypervisor is 64bit and that domU (lightning) > is 32bit. > > - Valtteri > > Hi, > > I have now made a startup script that starts the domU first by pausing > it, then writes that thingy in xenstore and then unpauses it. Its > working now fine. I assume that this is some kind of bug that will be > fixed on later Xen versions, or is this caused by something in my end? > Do I have to do something else to get the domU to startup normally?I''m undecided at the moment whether this represents a bug in the old domU kernel, or something wrong with the toolstack. Can you tell me what flavour (i.e. address width, 32 or 64) of hypervisor, dom0 kernel and domU kernel you are using is? Ian.
Valtteri Kiviniemi
2012-Oct-03 15:39 UTC
Re: Xen 4.2.0, xl toolstack cant launch older domUs
2012/10/3 Ian Campbell <Ian.Campbell@citrix.com>> On Wed, 2012-10-03 at 16:29 +0100, Valtteri Kiviniemi wrote: > > > > > > 2012/10/3 Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com> > > > > > > 2012/10/3 Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com> > > > > 2012/10/3 Ian Campbell <Ian.Campbell@citrix.com> > > On Wed, 2012-10-03 at 12:44 +0100, Valtteri > > Kiviniemi wrote: > > > Hi, > > > > > > Ok, well lets do it thisway. Hopefully I got > > this right this time. > > > > > > You did, thanks. (aside, can you not top-post > > please) > > > > A bit of a shot in the dark but what is the > > address size (i.e. 64 bit or > > 32 bit) for each of your hypervisor, dom0 and > > domU kernels? > > > > Does this change anything: > > xl cr -p lightning.cfg > > xenstore-write /local/domain/$(xl > > domid lightning)/device/vbd/51713/protocol > > x86_32-abi > > xl unpause lightning > > > > (this assumes the domains cfg is lightning.cfg > > and name is lightning) > > > > Ian. > > > > > > Hi, > > > > Sorry for the top posting, I''m at work at the moment > > and using different mail client which is is configured > > for top posting and I was too lazy to change it. > > > > But that did do the trick, the domU is now fillu > > booting and working! > > > > - Valtteri > > > > > > > > > > Hi, > > > > dom0 is 64bit, hypervisor is 64bit and that domU (lightning) > > is 32bit. > > > > - Valtteri > > > > Hi, > > > > I have now made a startup script that starts the domU first by pausing > > it, then writes that thingy in xenstore and then unpauses it. Its > > working now fine. I assume that this is some kind of bug that will be > > fixed on later Xen versions, or is this caused by something in my end? > > Do I have to do something else to get the domU to startup normally? > > I''m undecided at the moment whether this represents a bug in the old > domU kernel, or something wrong with the toolstack. > > Can you tell me what flavour (i.e. address width, 32 or 64) of > hypervisor, dom0 kernel and domU kernel you are using is? > > Ian. > >Hi, Hypervisor is 64bit, dom0 is 64bit but the domU is 32bit. If this is what you meant? - Valtteri _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Valtteri Kiviniemi
2012-Oct-03 16:23 UTC
Re: Xen 4.2.0, xl toolstack cant launch older domUs
2012/10/3 Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com>> > > 2012/10/3 Ian Campbell <Ian.Campbell@citrix.com> > >> On Wed, 2012-10-03 at 16:29 +0100, Valtteri Kiviniemi wrote: >> > >> > >> > 2012/10/3 Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com> >> > >> > >> > 2012/10/3 Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com> >> > >> > 2012/10/3 Ian Campbell <Ian.Campbell@citrix.com> >> > On Wed, 2012-10-03 at 12:44 +0100, Valtteri >> > Kiviniemi wrote: >> > > Hi, >> > > >> > > Ok, well lets do it thisway. Hopefully I got >> > this right this time. >> > >> > >> > You did, thanks. (aside, can you not top-post >> > please) >> > >> > A bit of a shot in the dark but what is the >> > address size (i.e. 64 bit or >> > 32 bit) for each of your hypervisor, dom0 and >> > domU kernels? >> > >> > Does this change anything: >> > xl cr -p lightning.cfg >> > xenstore-write /local/domain/$(xl >> > domid lightning)/device/vbd/51713/protocol >> > x86_32-abi >> > xl unpause lightning >> > >> > (this assumes the domains cfg is lightning.cfg >> > and name is lightning) >> > >> > Ian. >> > >> > >> > Hi, >> > >> > Sorry for the top posting, I''m at work at the moment >> > and using different mail client which is is configured >> > for top posting and I was too lazy to change it. >> > >> > But that did do the trick, the domU is now fillu >> > booting and working! >> > >> > - Valtteri >> > >> > >> > >> > >> > Hi, >> > >> > dom0 is 64bit, hypervisor is 64bit and that domU (lightning) >> > is 32bit. >> > >> > - Valtteri >> > >> > Hi, >> > >> > I have now made a startup script that starts the domU first by pausing >> > it, then writes that thingy in xenstore and then unpauses it. Its >> > working now fine. I assume that this is some kind of bug that will be >> > fixed on later Xen versions, or is this caused by something in my end? >> > Do I have to do something else to get the domU to startup normally? >> >> I''m undecided at the moment whether this represents a bug in the old >> domU kernel, or something wrong with the toolstack. >> >> Can you tell me what flavour (i.e. address width, 32 or 64) of >> hypervisor, dom0 kernel and domU kernel you are using is? >> >> Ian. >> >> > Hi, > > Hypervisor is 64bit, dom0 is 64bit but the domU is 32bit. If this is what > you meant? > > - Valtteri >Hi, I managed to find the sources for my domU kernel, so if you are interested about this problem I can send you a link for the sources and the domU kernel config that I''m using. Maybe you can then figure out if the bug is in the old domU kernel or in the toolstack. - Valtteri _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Wed, 2012-10-03 at 16:39 +0100, Valtteri Kiviniemi wrote:> Hypervisor is 64bit, dom0 is 64bit but the domU is 32bit. If this is > what you meant?It is. I think the underlying bug here is that your 32bit domU kernel predates the ability to run 32 bit guests on 64 bit hypervisors. Guest kernels are supposed to write that protocol node themselves. It appears that xend includes some sort of workaround for this which xl does not. Ian.
On Wed, Oct 03, 2012 at 05:35:50PM +0100, Ian Campbell wrote:> On Wed, 2012-10-03 at 16:39 +0100, Valtteri Kiviniemi wrote: > > Hypervisor is 64bit, dom0 is 64bit but the domU is 32bit. If this is > > what you meant? > > It is. > > I think the underlying bug here is that your 32bit domU kernel predates > the ability to run 32 bit guests on 64 bit hypervisors. Guest kernels > are supposed to write that protocol node themselves. > > It appears that xend includes some sort of workaround for this which xl > does not. >So from a user''s point-of-view this is a regression in xl.. similar workaround probably should be added in xl to be able to run old guests? -- Pasi
On Sun, 2012-10-14 at 12:03 +0100, Pasi Kärkkäinen wrote:> On Wed, Oct 03, 2012 at 05:35:50PM +0100, Ian Campbell wrote: > > On Wed, 2012-10-03 at 16:39 +0100, Valtteri Kiviniemi wrote: > > > Hypervisor is 64bit, dom0 is 64bit but the domU is 32bit. If this is > > > what you meant? > > > > It is. > > > > I think the underlying bug here is that your 32bit domU kernel predates > > the ability to run 32 bit guests on 64 bit hypervisors. Guest kernels > > are supposed to write that protocol node themselves. > > > > It appears that xend includes some sort of workaround for this which xl > > does not. > > > > So from a user''s point-of-view this is a regression in xl.. > similar workaround probably should be added in xl to be able to run old guests?I don''t know when I''m going to have time to look into this. Patches gratefully received. Ian.
On Mon, Oct 15, 2012 at 8:56 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:>> > It appears that xend includes some sort of workaround for this which xl >> > does not. >> > >> >> So from a user''s point-of-view this is a regression in xl.. >> similar workaround probably should be added in xl to be able to run old guests? > > I don''t know when I''m going to have time to look into this. Patches > gratefully received.I suppose this kind of thing should be tracked, to make sure it doesn''t fall on the floor. I''ll add it to my list (with no owner ATM). -George
George Dunlap writes ("Re: [Xen-devel] Xen 4.2.0, xl toolstack cant launch older domUs"):> On Mon, Oct 15, 2012 at 8:56 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote: > >> > It appears that xend includes some sort of workaround for this which xl > >> > does not.... This relates to writing /local/domain/$(xl domid lightning)/device/vbd/51713/protocol x86_32-abi> I suppose this kind of thing should be tracked, to make sure it > doesn''t fall on the floor. I''ll add it to my list (with no owner > ATM).Did this ever get fixed ? Ian.
On Fri, Nov 16, 2012 at 05:01:17PM +0000, Ian Jackson wrote:> George Dunlap writes ("Re: [Xen-devel] Xen 4.2.0, xl toolstack cant launch older domUs"): > > On Mon, Oct 15, 2012 at 8:56 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote: > > >> > It appears that xend includes some sort of workaround for this which xl > > >> > does not. > ... > > This relates to writing > /local/domain/$(xl domid lightning)/device/vbd/51713/protocol x86_32-abi > > > I suppose this kind of thing should be tracked, to make sure it > > doesn''t fall on the floor. I''ll add it to my list (with no owner > > ATM). > > Did this ever get fixed ? >I don''t think it''s fixed yet.. -- Pasi
On Fri, 2012-11-16 at 17:01 +0000, Ian Jackson wrote:> George Dunlap writes ("Re: [Xen-devel] Xen 4.2.0, xl toolstack cant launch older domUs"): > > On Mon, Oct 15, 2012 at 8:56 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote: > > >> > It appears that xend includes some sort of workaround for this which xl > > >> > does not. > ... > > This relates to writing > /local/domain/$(xl domid lightning)/device/vbd/51713/protocol x86_32-abi > > > I suppose this kind of thing should be tracked, to make sure it > > doesn''t fall on the floor. I''ll add it to my list (with no owner > > ATM). > > Did this ever get fixed ?Not AFAIK. The xc dombuild has a concept of the "native_protocol" for the guest which it has just built, you''d want to add a mechanism to feed this back out to libxl and remember it somewhere for use when adding the devices. A bit of a pain but not too hard I don''t think. e.g. in libxl__build_pv you have struct xc_dom_image *dom and can read dom->arch_hooks->native_protocol (this is what xend does). I''m not sure what the equivalent for hvm guests would be. Perhaps they are required to right it themselves, since you can''t know a priori what sort of kernel they will load. Actually a PV guest is expected to right it to and doing it in the toolstack is just a workaround for broken guests. Ian.
Valtteri Kiviniemi
2013-Jan-10 19:24 UTC
Re: Xen 4.2.0, xl toolstack cant launch older domUs
2012/11/19 Ian Campbell <Ian.Campbell@citrix.com>> On Fri, 2012-11-16 at 17:01 +0000, Ian Jackson wrote: > > George Dunlap writes ("Re: [Xen-devel] Xen 4.2.0, xl toolstack cant > launch older domUs"): > > > On Mon, Oct 15, 2012 at 8:56 AM, Ian Campbell <Ian.Campbell@citrix.com> > wrote: > > > >> > It appears that xend includes some sort of workaround for this > which xl > > > >> > does not. > > ... > > > > This relates to writing > > /local/domain/$(xl domid lightning)/device/vbd/51713/protocol > x86_32-abi > > > > > I suppose this kind of thing should be tracked, to make sure it > > > doesn''t fall on the floor. I''ll add it to my list (with no owner > > > ATM). > > > > Did this ever get fixed ? > > Not AFAIK. > > The xc dombuild has a concept of the "native_protocol" for the guest > which it has just built, you''d want to add a mechanism to feed this back > out to libxl and remember it somewhere for use when adding the devices. > > A bit of a pain but not too hard I don''t think. > > e.g. in libxl__build_pv you have struct xc_dom_image *dom and can read > dom->arch_hooks->native_protocol (this is what xend does). > > I''m not sure what the equivalent for hvm guests would be. Perhaps they > are required to right it themselves, since you can''t know a priori what > sort of kernel they will load. Actually a PV guest is expected to right > it to and doing it in the toolstack is just a workaround for broken > guests. > > > Ian. > > Hi,I suppose that this is not still fixed in Xen 4.2.1? - Valtteri _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel