|
Bugzilla – Full Text Bug Listing |
| Summary: | openSUSE 11.2 rc2 fails to boot in para virtualized Xen VM on openSUSE 11.1 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Jared Hudson <jared.hudson> |
| Component: | Xen | Assignee: | Jan Beulich <jbeulich> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P2 - High | CC: | carnold, coolo, felix.richter2, forgotten_EG0D-KeeCG, jdouglas, mt, rob, seuchato, syntron, udo1 |
| Version: | Final | ||
| Target Milestone: | unspecified | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.2 | ||
| Whiteboard: | maint:released:11.2:29469 | ||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
output via xm con when vm-install tries to start the install
/var/log/boot.msg of paravirtual 11.2 Xen VM on 11.1 Host |
||
|
Description
Jared Hudson
2009-10-31 17:21:28 UTC
Created attachment 324991 [details]
output via xm con when vm-install tries to start the install
you can get rid of the initial error by recompiling the kernel to not include DMI (CONFIG_DMI=n and associated settings) but it still crashes near the end, when it says [ 3.073836] blk: request botched [ 3.073848] ------------[ cut here ]------------ [ 3.073855] Kernel BUG at ffffffff80221310 [verbose debug info unavailable] [ 3.073864] invalid opcode: 0000 [#1] SMP [ 3.073963] last sysfs file: /sys/module/xenblk/initstate [ 3.073970] CPU 0 [ 3.073980] Modules linked in: xennet(+) xenblk(+) cdrom [ 3.074089] Pid: 10, comm: xenwatch Not tainted 2.6.31.5-xen #1 [ 3.074096] RIP: e030:[<ffffffff80221310>] [<ffffffff80221310>] __blk_end_request_all+0x40/0x80 [ 3.074113] RSP: e02b:ffffc90000003dd8 EFLAGS: 00010002 [ 3.074120] RAX: 0000000000000001 RBX: ffff88000deef300 RCX: ffff880017970dc0 [ 3.074127] RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001 [ 3.074135] RBP: ffffc90000003df8 R08: ffff880017970e30 R09: ffff880017970dc0 [ 3.074145] R10: ffff88000a06d000 R11: 0000000000000e00 R12: 00000000fffffffb [ 3.074153] R13: ffff88000e174210 R14: ffff88000e174000 R15: 0000000000000001 [ 3.074165] FS: 00007f62110846f0(0000) GS:ffffc90000000000(0000) knlGS:0000000000000000 [ 3.074173] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b [ 3.074180] CR2: 0000000000631ab8 CR3: 000000000eaa7000 CR4: 0000000000000660 [ 3.074188] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 3.074282] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 3.074290] Process xenwatch (pid: 10, threadinfo ffff880017894000, task ffff880017892280) [ 3.074298] Stack: [ 3.074303] 00000000a277ef96 00000000a277ef96 ffff88000e174000 00000000fffffffb [ 3.074323] <0> ffffc90000003e78 ffffffffa0017f59 ffff88000e1741f0 000000008003a10d [ 3.074350] <0> ffff88000deef300 00000001806ec0c0 0000000000000000 0000000000000000 [ 3.074467] Call Trace: [ 3.074484] [<ffffffffa0017f59>] blkif_int+0x19f/0x242 [xenblk] [ 3.074496] [<ffffffff800ab7ff>] handle_IRQ_event+0x7f/0x1e0 [ 3.074508] [<ffffffff800ae94a>] handle_level_irq+0xaa/0x1a0 [ 3.074520] [<ffffffff8000ebee>] handle_irq+0x2e/0x50 [ 3.074531] [<ffffffff802f9420>] evtchn_do_upcall+0x180/0x270 [ 3.074544] [<ffffffff8000ce6e>] do_hypervisor_callback+0x1e/0x30 [ 3.074556] [<ffffffff8000822a>] 0xffffffff8000822a [ 3.074569] [<ffffffff802f8b50>] force_evtchn_callback+0x20/0x40 [ 3.074582] [<ffffffff80226d40>] blk_execute_rq_nowait+0x110/0x120 [ 3.074593] [<ffffffff80226dcf>] blk_execute_rq+0x7f/0xe0 [ 3.074606] [<ffffffffa0019234>] submit_message+0xab/0xd2 [xenblk] [ 3.074620] [<ffffffffa0019af9>] register_vcd+0xc3/0x236 [xenblk] [ 3.074634] [<ffffffffa00185b8>] backend_changed+0x210/0x2e6 [xenblk] [ 3.074646] [<ffffffff80306db2>] otherend_changed+0x102/0x1e0 [ 3.074659] [<ffffffff8030458c>] xenwatch_handle_callback+0x2c/0x80 [ 3.074671] [<ffffffff803047b0>] xenwatch_thread+0x1d0/0x200 [ 3.074682] [<ffffffff8006f0d6>] kthread+0xb6/0xd0 [ 3.074694] [<ffffffff8000d30a>] child_rip+0xa/0x20 [ 3.074703] Code: 8b 04 25 28 00 00 00 48 89 45 e8 31 c0 48 8b 87 48 01 00 00 48 85 c0 75 42 8b 53 60 44 89 e6 48 89 df e8 34 f1 ff ff 84 c0 74 08 <0f> 0b eb fe 0f 1f 40 00 44 89 e6 48 89 df e8 4d fd ff ff 48 8b [ 3.075413] RIP [<ffffffff80221310>] __blk_end_request_all+0x40/0x80 [ 3.075427] RSP <ffffc90000003dd8> [ 3.075435] ---[ end trace 8844f7fb1d0a0226 ]--- [ 3.075443] Kernel panic - not syncing: Fatal exception in interrupt And this is *only* when the host is running 11.1? I had tried para-virtualized only on openSUSE 11.1 until just now. I've confirmed that the error is the same if I try to install it under a para-virtualized VM in SLES 11 as well. Fully-virtualized does not work in SLES 10 or 11 either. (bug #551598) I don't have hardware capable of running fully-virtualized VMs under openSUSE 11.1 so I have not tried that combination yet. The question really was towards 11.2 as the host (SLE11 and 11.1 really don't differ in kernel or hypervisor). At the moment I dont have any systems available to install openSUSE 11.2rc2 on to see how it performs as a VM under itself as a host. What is the second disk you assign to the guest? Physical CD-ROM drive, ISO image, or yet something else? ISO image containing the openSUSE 11.2rc2 install or network install image. I'm using virt-manager/vm-install to install the OS. @Jan, correct. It fails to even install. the gui/ncurses installer never even starts up. If I'm in vm-install, at the summary screen, I click Ok. VM console window pops up. I see several kernel errors, as pasted above, then the screen disappears. vm-install says, "Error\nNo Kernel was found. The installation may have failed."
It's only by doing a while(true); do xm con opensuse11; done
in dom0 that I was able to see what even went wrong. It flies on and off the screen very fast.
If I pass console=xvc0 I can see that it last said,
>>> openSUSE installation program v3.4.7 (c) 1996-2009 SUSE Linux Products GmbH <<<
Starting udev... [ 2.839358] udev: starting version 146
[ 2.989860] netfront: Initialising virtual ethernet driver.
[ 3.001460] xen-vbd: registered block device major 202
[ 3.001496] blkfront: xvda: barriers enabled
[ 3.005031] xvda: unknown partition table
[ 3.005718] blkfront: xvdb: barriers enabled
[ 3.009240] blk: request botched
[ 3.009258] ------------[ cut here ]------------
[ 3.009265] kernel BUG at /usr/src/packages/BUILD/kernel-xen-2.6.31.5/linux-2.6.31/block/blk-core.c:2216!
[ 3.009272] invalid opcode: 0000 [#1] SMP
[ 3.009286] last sysfs file: /sys/module/xenblk/initstate
[ 3.009374] CPU 0
[ 3.009383] Modules linked in: xennet(+) xenblk(+) cdrom
[ 3.009407] Pid: 11, comm: xenwatch Tainted: G W 2.6.31.5-0.1-xen #1
[ 3.009414] RIP: e030:[<ffffffff80222730>] [<ffffffff80222730>] __blk_end_request_all+0x40/0x80
except for the console msgs, this is all in the attachment.
Created attachment 325619 [details]
/var/log/boot.msg of paravirtual 11.2 Xen VM on 11.1 Host
I had the same problem. By copying the kernel and initrd from the ISO to /tmp/... I could get the installation to start (btw: mouse did not work in VNC), and finally editing the VM definition file I could get it to boot. When booting there are lots of the following: [ 2.595222] WARNING: at /usr/src/packages/BUILD/kernel-xen-2.6.31.5/linux-2.6.31/drivers/firmware/dmi_scan.c:427 ... (see attaches boot.msg) Installing as a fully-virtualized VM on OpenSUSE 11.1 Xen host works. Fix committed (also for the DMI warnings). Will a new ISO be created that fixes my issue? Unfortunately this fix wasn't taken for the final release, so the shipped ISO images will remain broken, while the fix will be in an eventual kernel update. I have the same problem trying to install a xen 11.2RC2 under a 11.2RC2 host (2009/11/11). Where will a fixed kernel image be found? (And when?) I installed all updates for the host but I still get the same error. [ 4.662001] ------------[ cut here ]------------ [ 4.662014] WARNING: at /usr/src/packages/BUILD/kernel-xen-2.6.31.5/linux-2.6.31/drivers/firmware/dmi_scan.c:427 dmi_matches+0x98/0xa0() [ 4.662028] dmi check: not initialized yet. [ 4.662036] Modules linked in: [ 4.662047] Pid: 1, comm: swapper Tainted: G W 2.6.31.5-0.1-xen #1 [ 4.662057] Call Trace: [ 4.662070] [<c000b2ea>] try_stack_unwind+0x17a/0x1a0 [ 4.662086] [<c0008a7c>] dump_trace+0x6c/0x130 [ 4.662099] [<c000ae98>] show_trace_log_lvl+0x58/0x80 [ 4.662113] [<c000aee6>] show_trace+0x26/0x40 [ 4.662125] [<c03d1c56>] dump_stack+0x79/0x91 [ 4.662138] [<c003fde8>] warn_slowpath_common+0x78/0xc0 [ 4.662152] [<c003fea1>] warn_slowpath_fmt+0x31/0x50 [ 4.662166] [<c0324d28>] dmi_matches+0x98/0xa0 [ 4.662180] [<c0324db7>] dmi_check_system+0x27/0x70 [ 4.662194] [<c0662cc2>] atkbd_init+0x1b/0x3f [ 4.662206] [<c00040b8>] do_one_initcall+0x38/0x1d0 [ 4.662220] [<c063d7e5>] do_basic_setup+0x55/0x77 [ 4.662234] [<c063d888>] kernel_init+0x81/0xda [ 4.662247] [<c0006e5b>] kernel_thread_helper+0x7/0x10 [ 4.662258] ---[ end trace a7919e7f17c0a79d ]--- The graphical installation gets to the point where it tries to access the disc (I think) and then aborts. Trying a console installation it ends with [ 4.662659] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 [ 4.663441] TCP cubic registered [ 4.663620] registered taskstats version 1 [ 4.663682] PCI IO multiplexer device installed. [ 4.663725] Magic number: 1:252:3141 [ 4.663767] XENBUS: Device with no driver: device/vbd/51712 [ 4.663777] XENBUS: Device with no driver: device/vif/0 [ 4.663785] XENBUS: Device with no driver: device/console/0 [ 4.663798] /usr/src/packages/BUILD/kernel-xen-2.6.31.5/linux-2.6.31/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 4.665556] Freeing unused kernel memory: 328k freed [ 4.670069] Write protecting the kernel text: 3940k [ 4.671883] Write protecting the kernel read-only data: 2256k Moving into tmpfs... done. [ 5.095651] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [ 5.095706] EDD information not available. insmod: error inserting '/modules/edd.ko': -1 No such device >>> openSUSE installation program v3.4.7 (c) 1996-2009 SUSE Linux Products GmbH <<< Starting udev... [ 5.134043] udev: starting version 146 [ 5.259663] netfront: Initialising virtual ethernet driver. [ 5.292168] xen-vbd: registered block device major 202 [ 5.292251] blkfront: xvda: barriers enabled [ 5.295402] xvda: unknown partition table ok [ 5.579024] init[1]: segfault at 46 ip b74c0033 sp bfc46630 error 4 in libc-2.10.1.so[b7482000+159000] Linuxrc crashed. :-(( Press ENTER to continue. It is a i586 system using yast > Virtualisation > Installation using a 4G file as backend for the hard disk. As Installation source http://download.opensuse.org/distribution/11.2/repo/oss/ is selected. If the fix was committed on the 5th, why was it not accepted for the final build? Because the release manager decided not to take it. Would it be possible to give an hint where to find a rpm with the fix? (update to 11.2; a special repo?) I would like to install opensuse 11.2 on my server which uses xen. Until an official kernel update get released, you might want to look at using ftp://ftp.suse.com/pub/projects/kernel/kotd/openSUSE-11.2/. *** Bug 556255 has been marked as a duplicate of this bug. *** You can also use the following work around to install using an ISO file. Select 'Create Virtual Machine" from the Yast menu or vm-install from the command line or via virt-manager. The instructions start once you get to the "Summary" screen. Step 1: From the "Summary" screen, Select "Operating System Installation". Step 2: From the "Operating System Installation" screen, select "Virtual Disk" and then "Add". Step 3: From the "Virtual Disk" Screen, select your ISO file. Step 4: Press "Ok" and "Apply" to return to the "Summary" screen. Step 5: From the "Summary" screen, select "Disks". Step 6: From the "Disks" screen highlight the ISO you just added as an installation source and Select "Remove". Step 7: From the "Disks" screen select "Harddisk". Step 8: From the "Virtual Disks" screen select your ISO file. Check the "Read-Only Access" box. Step 9: Press "Ok" and "Apply" to return to the "Summary" screen. Step 10: From the "Summary" screen Press "Ok" to start the installation (assuming other settings are correct). During the installation of the guest, you may see a warning on the "Installation Settings" screen under the "Booting" section that says 'It was not possible to determine the exact order of disks for device map. The order of disks can be changed in "Boot Loader Installation Details"'. So far, we have not seen any adverse effects from this warning by simply ignoring it. Why is this bug marked as RESOLVED? There is a workaround, but not resolved and still exist in the final release, so what is RESOLVED with resolution FIXED mean? It should be VERIFIED or not? So under opensuse 11.2 you are not to able install 11.2 para guest... I do not understand the release manager... So xen is not important for opensuse anymore? Is at least an updated ISO planned, or will everybody have to use this workaround till 11.3 final DVD available? (In reply to comment #29) > Why is this bug marked as RESOLVED? The bug is technically resolved, but the release manager decided not to incorporate the fix (hence the target milestone "unspecified"). Hence the workaround. At this point there do not seem to be plans remaster the ISO. Any discussion regarding this decision should probably be had on mailing lists, not in bugzilla. It is not only an ISO / vm installation related issue, but the Oopses occur without any ISO bound to the vm (just a disk file) after the installation as well. Mr Maintenance, please consider for update. Changed version to final. BTW: In my case it is 11.2 on 11.2 host. With the 11.2 final kernel I'm getting # dmesg | grep "Call Trace" | wc -l 119 and the kernel is Tainted after. The kotd seems to work fine: ftp://ftp.suse.com/pub/projects/kernel/kotd/openSUSE-11.2/x86_64/kernel-xen-base-2.6.31.9-0.0.0.3.3490791.x86_64.rpm As stated above (and confirmed by your testing of kotd), the bug is fixed (and the fix will make it into an eventual kernel maintenance update), but the media will not get fixed as per the release manager's decision. Update released for: kernel-debug, kernel-debug-base, kernel-debug-base-debuginfo, kernel-debug-debuginfo, kernel-debug-debugsource, kernel-debug-devel, kernel-debug-devel-debuginfo, kernel-default, kernel-default-base, kernel-default-base-debuginfo, kernel-default-debuginfo, kernel-default-debugsource, kernel-default-devel, kernel-default-devel-debuginfo, kernel-desktop, kernel-desktop-base, kernel-desktop-base-debuginfo, kernel-desktop-debuginfo, kernel-desktop-debugsource, kernel-desktop-devel, kernel-desktop-devel-debuginfo, kernel-pae, kernel-pae-base, kernel-pae-base-debuginfo, kernel-pae-debuginfo, kernel-pae-debugsource, kernel-pae-devel, kernel-pae-devel-debuginfo, kernel-source, kernel-source-vanilla, kernel-syms, kernel-trace, kernel-trace-base, kernel-trace-base-debuginfo, kernel-trace-debuginfo, kernel-trace-debugsource, kernel-trace-devel, kernel-trace-devel-debuginfo, kernel-vanilla, kernel-vanilla-base, kernel-vanilla-base-debuginfo, kernel-vanilla-debuginfo, kernel-vanilla-debugsource, kernel-vanilla-devel, kernel-vanilla-devel-debuginfo, kernel-xen, kernel-xen-base, kernel-xen-base-debuginfo, kernel-xen-debuginfo, kernel-xen-debugsource, kernel-xen-devel, kernel-xen-devel-debuginfo, preload-kmp-default, preload-kmp-desktop Products: openSUSE 11.2 (debug, i586, x86_64) *** Bug 570055 has been marked as a duplicate of this bug. *** Hi, I opt for reopening this bug. I run 11.2, updates as per 2010, Feb 08, stock Kernel 2.6.31.5 and KOTD 2.6.31.12-0.1.99.1.a5eb2b3-xen. I cannot find a working kernel on KOTD repo. I observe *exactly* the same behaviour everytime I try using vm-install and the workaround did not work at all for me. I have a text based setup, so I can only use vm-install. Ther is no "Summary" screen there. Also I use an ftp install source, as there is no option to choose set a ISO for installation source, see below: "Specify the bootable virtual disk (often labeled as Disk 1) or the network installation source URL. Each CD, DVD, or ISO image required for installation must be added as a virtual disk. 1: Network URL (ftp://, http://, nfs://, smb://) [1] > Type the install URL: > ftp://mirror.switch.ch/mirror/opensuse/distribution/11.2/repo/oss/" greets chris |