Hi, I''m trying to install Debian Squeeze as DomU on an openSUSE 11.4 Xen host but fail all the time. I''ve also searched Google and Debian as well as openSUSE resources but haven''t found any hint about my issue :-( First I''ve tried to install it as a paravirtualized guest but when the Debian installer tries to detect the disks I get this: [ 173.233735] Process xenwatch (pid: 12, threadinfo ffff88003fe04000, task ffff88003fddce20) [ 173.233746] Stack: [ 173.233752] 0000000000000001 ffff8800027ed858 ffff8800027ed800 ffff8800027ed800 [ 173.233768] <0> ffff8800027ed800 ffff8800026c11a0 ffff8800027ed858 ffff880002038000 [ 173.233788] <0> 0000000000000000 ffffffff81180e8e 0000000000000000 ffff8800027ed800 [ 173.233811] Call Trace: [ 173.233823] [<ffffffff81180e8e>] ? blk_register_queue+0xbe/0xcc [ 173.233836] [<ffffffff81184c89>] ? add_disk+0xb8/0x108 [ 173.233850] [<ffffffffa000f224>] ? backend_changed+0x44e/0x468 [xen_blkfront] [ 173.233865] [<ffffffff811f1c8f>] ? xenwatch_thread+0x117/0x14a [ 173.233878] [<ffffffff81065042>] ? autoremove_wake_function+0x0/0x2e [ 173.233890] [<ffffffff811f1b78>] ? xenwatch_thread+0x0/0x14a [ 173.233902] [<ffffffff81064d75>] ? kthread+0x79/0x81 [ 173.233913] [<ffffffff81011baa>] ? child_rip+0xa/0x20 [ 173.233925] [<ffffffff81010d61>] ? int_ret_from_sys_call+0x7/0x1b [ 173.233937] [<ffffffff8101151d>] ? retint_restore_args+0x5/0x6 [ 173.233950] [<ffffffff8100e22f>] ? xen_restore_fl_direct_end+0x0/0x1 [ 173.233963] [<ffffffff81011ba0>] ? child_rip+0x0/0x20 [ 173.233971] Code: 41 5d c3 41 57 49 89 d7 41 56 41 55 49 89 fd 41 54 55 53 48 83 ec 18 48 85 ff 89 74 24 04 74 0b 85 f6 75 0b 48 83 7f 30 00 75 14 <0f> 0b eb fe 48 83 7f 30 00 bb ea ff ff ff 0f 84 03 01 00 00 49 [ 173.234105] RIP [<ffffffff81141dd7>] internal_create_group+0x28/0x15a [ 173.234120] RSP <ffff88003fe05d30> [ 173.234129] ---[ end trace e52b5afb691890a0 ]--- [ 178.140021] XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s... If I wait until the timeout expires the installer goes on but the partitioner only recognizes two of my three configured disks and therefore I cannot install as desired. Now today I finally tried to install it as HVM but I get exactly the same stacktrace and issue. Any hints what to do or what the culprit could be? Xen on openSUSE is version 4.0.2, Linux kernel 2.6.37.6. I have several other openSUSE PV guests running on that host already w/o issues. The Debian initrd and kernel are from http://cdn.debian.net/debian/dists/squeeze/main/installer-amd64/current/images/netboot/xen/ Any feedback is appreciated if only that I know where to open a bugreport about it. Thanks, Wolfgang
Am 22.08.2012 17:48, schrieb Wolfgang Rosenauer:> Hi, > > I''m trying to install Debian Squeeze as DomU on an openSUSE 11.4 Xen > host but fail all the time. > I''ve also searched Google and Debian as well as openSUSE resources but > haven''t found any hint about my issue :-( > > First I''ve tried to install it as a paravirtualized guest but when the > Debian installer tries to detect the disks I get this: > > [ 173.233735] Process xenwatch (pid: 12, threadinfo ffff88003fe04000, > task ffff88003fddce20) > [ 173.233746] Stack: > [ 173.233752] 0000000000000001 ffff8800027ed858 ffff8800027ed800 > ffff8800027ed800 > [ 173.233768] <0> ffff8800027ed800 ffff8800026c11a0 ffff8800027ed858 > ffff880002038000 > [ 173.233788] <0> 0000000000000000 ffffffff81180e8e 0000000000000000 > ffff8800027ed800 > [ 173.233811] Call Trace: > [ 173.233823] [<ffffffff81180e8e>] ? blk_register_queue+0xbe/0xcc > [ 173.233836] [<ffffffff81184c89>] ? add_disk+0xb8/0x108 > [ 173.233850] [<ffffffffa000f224>] ? backend_changed+0x44e/0x468 > [xen_blkfront] > [ 173.233865] [<ffffffff811f1c8f>] ? xenwatch_thread+0x117/0x14a > [ 173.233878] [<ffffffff81065042>] ? autoremove_wake_function+0x0/0x2e > [ 173.233890] [<ffffffff811f1b78>] ? xenwatch_thread+0x0/0x14a > [ 173.233902] [<ffffffff81064d75>] ? kthread+0x79/0x81 > [ 173.233913] [<ffffffff81011baa>] ? child_rip+0xa/0x20 > [ 173.233925] [<ffffffff81010d61>] ? int_ret_from_sys_call+0x7/0x1b > [ 173.233937] [<ffffffff8101151d>] ? retint_restore_args+0x5/0x6 > [ 173.233950] [<ffffffff8100e22f>] ? xen_restore_fl_direct_end+0x0/0x1 > [ 173.233963] [<ffffffff81011ba0>] ? child_rip+0x0/0x20 > [ 173.233971] Code: 41 5d c3 41 57 49 89 d7 41 56 41 55 49 89 fd 41 54 > 55 53 48 83 ec 18 48 85 ff 89 74 24 04 74 0b 85 f6 75 0b 48 83 7f 30 00 > 75 14 <0f> 0b eb fe 48 83 7f 30 00 bb ea ff ff ff 0f 84 03 01 00 00 49 > [ 173.234105] RIP [<ffffffff81141dd7>] internal_create_group+0x28/0x15a > [ 173.234120] RSP <ffff88003fe05d30> > [ 173.234129] ---[ end trace e52b5afb691890a0 ]--- > [ 178.140021] XENBUS: Waiting for devices to initialise: > 295s...290s...285s...280s...275s... > > If I wait until the timeout expires the installer goes on but the > partitioner only recognizes two of my three configured disks and > therefore I cannot install as desired. > > Now today I finally tried to install it as HVM but I get exactly the > same stacktrace and issue. > > Any hints what to do or what the culprit could be? > > Xen on openSUSE is version 4.0.2, Linux kernel 2.6.37.6. I have several > other openSUSE PV guests running on that host already w/o issues. > > The Debian initrd and kernel are from > http://cdn.debian.net/debian/dists/squeeze/main/installer-amd64/current/images/netboot/xen/ > > Any feedback is appreciated if only that I know where to open a > bugreport about it. > > > Thanks, > Wolfgang > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-usersHello Wolfgang, have you already tried to setup the DomU manually with debootstrap? This is mostly the best way to get a Debian based DomU get to work. Then you can simply install the Xen Kernel of Debian and boot the DomU with pygrub. Best Regards
Am 22.08.2012 18:42, schrieb Lukas Laukamp:> > Hello Wolfgang, > > have you already tried to setup the DomU manually with debootstrap? This > is mostly the best way to get a Debian based DomU get to work. Then you > can simply install the Xen Kernel of Debian and boot the DomU with pygrub.Hmm, I haven''t tried it. One problem would be that I run all my guests on physical LVM volumes and I''d like to do the same for Debian. That''s also the reason why I do a real installation usually. Wolfgang
Am 22.08.2012 19:17, schrieb Wolfgang Rosenauer:> Am 22.08.2012 18:42, schrieb Lukas Laukamp: >> Hello Wolfgang, >> >> have you already tried to setup the DomU manually with debootstrap? This >> is mostly the best way to get a Debian based DomU get to work. Then you >> can simply install the Xen Kernel of Debian and boot the DomU with pygrub. > Hmm, I haven''t tried it. One problem would be that I run all my guests > on physical LVM volumes and I''d like to do the same for Debian. That''s > also the reason why I do a real installation usually. > > > Wolfgang > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-usersHello, it''s no problem to do this with LVM. You simply create one Volume for / and one for swap. The volume for / you format with the wanted filesystem (ext3/ext4) and the one for swap you format as swap with mkswap. Then you simply mount the Volume for /, install the base system with debootstrap and configure the basesystem by chrooting into it. Best Regards
On Wed, 2012-08-22 at 17:42 +0100, Lukas Laukamp wrote:> Am 22.08.2012 17:48, schrieb Wolfgang Rosenauer: > > Hi, > > > > I''m trying to install Debian Squeeze as DomU on an openSUSE 11.4 Xen > > host but fail all the time. > > I''ve also searched Google and Debian as well as openSUSE resources but > > haven''t found any hint about my issue :-( > > > > First I''ve tried to install it as a paravirtualized guest but when the > > Debian installer tries to detect the disks I get this: > > > > [ 173.233735] Process xenwatch (pid: 12, threadinfo ffff88003fe04000, > > task ffff88003fddce20)I think a bunch of the useful information has scrolled off the top here. Are you able to scroll up and see some more? Or perhaps you could enable guest console logging as described at: http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Guest_console_logs Ian.