Hi, AFAIK, the status of Xen in lenny is currently the following: - no dom0 kernel - domU kernel only for i386 (no domU kernel for amd64) I was told (I don't remember where) that this is because the vanilla kernel only supports domU for i386, and has no dom0 support, so distros have to port the patches to their kernels (please correct me if I'm wrong). However: - etch shipped with dom0 and domU kernels on i386 and amd64 - all major distros shipped with "full" Xen support What are the plans for Xen for lenny? Is this situation likely to change before the release? -- | Lucas Nussbaum | lucas at lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lucas at nussbaum.fr GPG: 1024D/023B3F4F |
On Thu, 2008-07-10 at 21:53 +0200, Lucas Nussbaum wrote:> Hi, > > AFAIK, the status of Xen in lenny is currently the following: > - no dom0 kernel > - domU kernel only for i386 (no domU kernel for amd64) > > I was told (I don't remember where) that this is because the vanilla > kernel only supports domU for i386, and has no dom0 support, so distros > have to port the patches to their kernels (please correct me if I'm > wrong).That is correct. The upstream -tip tree currently has some 64 bit domU patches queued (probably for 2.6.27). They are rather new and far reaching ??since they make some some nice infrastructure cleanups along the way etc. There's a rather slim chance they might make it in for Lenny but given their young age I'm not quite happy to say we could support a kernel with them for the lifetime of Lenny. dom0 support is being worked on by Fedora people (I think) but there are no patches upstream yet.> However: > - etch shipped with dom0 and domU kernels on i386 and amd64 > - all major distros shipped with "full" Xen supportFWIW fc9 didn't ship with dom0 support -- that is targeted for fc10. For now I think they recommend you stick with fc8 for dom0.? I think we will be in a similar situation -- recommending sticking with Etch for dom0 (or at least the Etch kernel, which I run on sid for my Xen uses just fine) is probably the best we can do at the moment.> What are the plans for Xen for lenny? Is this situation likely to change > before the release?Without a massive injection of manpower (Debian side or upstream) I don't see much changing. I've heard that maybe a Lenny + 1/2 kernel might be able to add the features (64bit + dom0) which are missed this time around if they are available upstream, but that isn't my call to make. Ian. -- Ian Campbell People usually get what's coming to them ... unless it's been mailed.
On Thu, Jul 10, 2008 at 09:53:25PM +0200, Lucas Nussbaum wrote:> AFAIK, the status of Xen in lenny is currently the following: > - no dom0 kernelYep. There are some preliminary patches but they break non-paravirt usage for now.> - domU kernel only for i386 (no domU kernel for amd64)x86_64 is currently worked on, but the stuff in fedora 9 is rather unclean.> However: > - etch shipped with dom0 and domU kernels on i386 and amd64Well, it ships a slightly broken variant.> - all major distros shipped with "full" Xen supportRHEL5/FC8 are 2.6.18 based and ships full support. SLES10 is 2.6.16 based and ships full support. FC9 is 2.6.24 based and ships only domU support. Anything else can be considered more or less broken.> What are the plans for Xen for lenny? Is this situation likely to change > before the release?It will ship the hypervisor and a domU kernel. For dom0 it will need either the etch or my own[1] kernel. This may be changed later if we can get a new kernel in the stable release. Bastian [1]: deb http://kernel-archive.buildserver.net/debian-kernel/waldi/xen-extra all main -- I have never understood the female capacity to avoid a direct answer to any question. -- Spock, "This Side of Paradise", stardate 3417.3 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20080711/9e13e87a/attachment.pgp
On Thu, Jul 10, 2008 at 09:53:25PM +0200, Lucas Nussbaum wrote:> What are the plans for Xen for lenny? Is this situation likely to change > before the release?As we have seen, there is no real plan. So lets summarize the possibilities: Option 1: Use alternatives =========================Well, I don't know any real alternative. There are some other virtualization techniques, but the decision which one may be usable needs an evaluation of the actual usecase. Option 2: Stick to Etch ======================Ask the users to stick to Etch until we can get a kernel into Lenny which supports this type of operation. Contra: - No new software for Xen users. - May hit the end of the security support for Etch. Needed work: Documentation. Option 3: Lenny with Etch kernel ===============================Ask the users to use the old Etch kernel with a Lenny userland. Pro: - New software. Contra: - May hit the end of the security support for Etch. Needed work: Some documentation how to do this. Option 4: 2.6.18 kernel in Lenny, until Lenny+1/2 ================================================Push a (Xen-only) 2.6.18 kernel into Lenny. Either with the Etch or preferably a newer Xen patch. This kernel will be supported until Lenny+1/2 hopefully pushs a kernel with the necessary support into the stable release, but at most until the Lenny+1 release. It may be possible that this will also need a Xen update to work with the new kernels. Pro: - New software. - Full support for the beginning. Contra: - We have to overwrite the decision to support only one Linux kernel in a stable release. - Dropping support of a package during the lifetime of a stable release was always a last resort solution. So this needs a fat warning in the release notes.[1] Needed work for kernel/security team[2]: - Until end of Etch support: Push the same update in oldstable-security and stable-security. - After end of Etch support: Continue the support for this old kernel. Lets hope that this will not take too long. Needed work for other teams: Documentation. Option 5: 2.6.18 kernel in Lenny ===============================Push a (Xen-only) 2.6.18 kernel into Lenny. Either with the Etch or preferably a newer Xen patch. This kernel will be supported until the normal end of the normal support. Pro: - New software. - Full support. Contra: - We have to overwrite the decision to support only one Linux kernel in a stable release. Needed work for kernel/security team: - Until end of Etch support: Push the same update in oldstable-security and stable-security. - After end of Etch support: Continue the support for this old kernel. For further, not applicable options, see http://fedoraproject.org/wiki/Features/XenPvops. Conclusion =========Xen got a often used technique in the last two years. All of the large distributions got some sort of support for it. Debian Etch have full support for it. There was several requests of various people so I think not providing at least a minimal support in Lenny is wrong. I think option 4 would be the solution which produces the least amount of extra work and provides our users with support for there systems. I would provide the necessary packages but I want an okay for that solution from the security and the release team. Bastian, with his kernel and Xen hat on [1]: Maybe it would be possible to replace the not-longer supported packages with a critical warning in preinst. This package would never allow themself to be configured. [2]: Kernel security support is mostly done by Dann Frazier, who does it as member of the kernel team. -- Is truth not truth for all? -- Natira, "For the World is Hollow and I have Touched the Sky", stardate 5476.4. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20080715/1014b2b1/attachment.pgp
On Thu, Sep 18, 2008 at 12:28:53PM +0200, Bastian Blank wrote:> Next try: http://194.39.182.225/debian/xen/try3. > This fixes a warning in the PCI registration and again uses xencons.This kernel have a critical problem: | Bad pte = 11764060, process = vsftpd, vm_flags = 100071, vaddr = b7f85000 | Pid: 8129, comm: vsftpd Not tainted 2.6.26-1-xen-686 #1 | [<c015edcd>] handle_mm_fault+0x61b/0xe78 | [<c0162b8f>] mprotect_fixup+0x6d3/0x735 | [<c010ee3e>] do_page_fault+0x684/0xbd6 | [<c0162d6b>] sys_mprotect+0x17a/0x1df | [<c0162dbd>] sys_mprotect+0x1cc/0x1df | [<c010e7ba>] do_page_fault+0x0/0xbd6 | [<c02ccbe5>] error_code+0x35/0x3c | ======================| VM: killing process vsftpd The pte have bit 6 set: PAGE_DIRTY aka PAGE_FILE. But the vm flags lacks the marker for a nonlinear (file based) mapping. Later kswap got killed: | BUG: unable to handle kernel NULL pointer dereference at 00000000 | IP: [<c0164a81>] page_referenced+0x72/0xcd | *pdpt = 000000005c78f001 *pde = 0000000000000000 | Oops: 0000 [#1] SMP | Modules linked in: rfcomm l2cap bluetooth xt_tcpudp tun xt_physdev ppdev lp video output ac battery ipv6 bridge iptable_nat iptable_filter nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack_ipv4 nf_conntrack ip_tablesx_tables fuse sbp2 loop snd_ens1371 gameport snd_ac97_codec ac97_bus snd_pcm_oss snd_pcm snd_mixer_oss snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore snd_page_alloc serio_raw shpchp parport_pc parport pcspkr pci_hotplug psmouse i2c_i801 iTCO_wdt button i2c_core joydev intel_agp agpgart evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod sg usbhid hid ff_memless sr_mod cdrom sd_mod ata_generic usb_storage ata_piix libata scsi_mod dock tulip ohci1394 ieee1394 ide_pci_generic ide_core ehci_hcd uhci_hcd usbcore e1000e thermal processor fan thermal_sys | | Pid: 216, comm: kswapd0 Not tainted (2.6.26-1-xen-686 #1) | EIP: 0061:[<c0164a81>] EFLAGS: 00010293 CPU: 2 | EIP is at page_referenced+0x72/0xcd | EAX: 00000001 EBX: c19cdc80 ECX: 00000000 EDX: 00000000 | ESI: ffffffc8 EDI: c49635dc EBP: 00000000 ESP: ecc39e8c | DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0069 | Process kswapd0 (pid: 216, ti=ecc38000 task=ed5609c0 task.ti=ecc38000) | Stack: 00000000 00000001 c19cdc98 c03611c0 c19cdc80 ecc39f74 c0156a34 00000006 | 0000000f ecc39f74 00000020 00000000 00000001 000004a4 0001ef73 00000000 | 00000001 c18afde0 c1bda360 c1b69460 c1c43160 c19a8620 c1acb2c0 c19d2c60 | Call Trace: | [<c0156a34>] shrink_active_list+0x215/0x52f | [<c0157797>] shrink_zone+0x97/0xcd | [<c0157f01>] kswapd+0x27b/0x3ed | [<c0156778>] isolate_pages_global+0x0/0x42 | [<c012f06c>] autoremove_wake_function+0x0/0x2d | [<c0157c86>] kswapd+0x0/0x3ed | [<c012efa9>] kthread+0x38/0x5f | [<c012ef71>] kthread+0x0/0x5f | [<c01042af>] kernel_thread_helper+0x7/0x10 | ======================| Code: 74 41 8b 43 08 40 89 44 24 04 8b 77 04 eb 19 8d 4c 24 04 89 f2 89 d8 e8 67 f3 ff ff 01 c5 83 7c 24 04 00 74 17 8b 76 38 83 ee 38 <8b> 46 38 0f 18 00 90 8d 56 38 8d 47 04 39 c2 75 d3 89 f8 e8 bc | EIP: [<c0164a81>] page_referenced+0x72/0xcd SS:ESP 0069:ecc39e8c | ---[ end trace c7883867761bd19d ]--- Bastian -- ... The prejudices people feel about each other disappear when they get to know each other. -- Kirk, "Elaan of Troyius", stardate 4372.5
On Thu, Sep 18, 2008 at 6:43 PM, Bastian Blank <waldi at debian.org> wrote:> This kernel have a critical problem: > > | Bad pte = 11764060, process = vsftpd, vm_flags = 100071, vaddr = b7f85000 > | Pid: 8129, comm: vsftpd Not tainted 2.6.26-1-xen-686 #1 > | [<c015edcd>] handle_mm_fault+0x61b/0xe78 > | [<c0162b8f>] mprotect_fixup+0x6d3/0x735 > | [<c010ee3e>] do_page_fault+0x684/0xbd6 > | [<c0162d6b>] sys_mprotect+0x17a/0x1df > | [<c0162dbd>] sys_mprotect+0x1cc/0x1df > | [<c010e7ba>] do_page_fault+0x0/0xbd6 > | [<c02ccbe5>] error_code+0x35/0x3c > | ======================> | VM: killing process vsftpd > > The pte have bit 6 set: PAGE_DIRTY aka PAGE_FILE. But the vm flags lacks > the marker for a nonlinear (file based) mapping.Here it is another one: | Bad pte = 5e164060, process = BORGChat.exe, vm_flags = 100075, vaddr = 340000 | Pid: 8575, comm: BORGChat.exe Not tainted 2.6.26-1-xen-686 #1 | [<c015edcd>handle_mm_fault+0x61b/0xe78 | [<c017040a>do_sync_read+0xbf/0xfe | [<c012f06c>autoremove_wake_function+0x0/0x2d | [<c010ee3e>do_page_fault+0x684/0xbd6 | [<c01470d1>audit_syscall_exit+0x2a1/0x2bd | [<c010974e>do_syscall_trace+0x62/0x165 | [<c010e7ba>do_page_fault+0x0/0xbd6 | [<c02ccbe5>error_code+0x35/0x3c | ======================| VM: killing process BORGChat.exe Cheers
On Thu, Sep 18, 2008 at 05:43:24PM +0200, Bastian Blank wrote:> This kernel have a critical problem: > > | Bad pte = 11764060, process = vsftpd, vm_flags = 100071, vaddr = b7f85000 > | Pid: 8129, comm: vsftpd Not tainted 2.6.26-1-xen-686 #1 > | [<c015edcd>] handle_mm_fault+0x61b/0xe78 > | [<c0162b8f>] mprotect_fixup+0x6d3/0x735 > | [<c010ee3e>] do_page_fault+0x684/0xbd6 > | [<c0162d6b>] sys_mprotect+0x17a/0x1df > | [<c0162dbd>] sys_mprotect+0x1cc/0x1df > | [<c010e7ba>] do_page_fault+0x0/0xbd6 > | [<c02ccbe5>] error_code+0x35/0x3c > | ======================> | VM: killing process vsftpd > > The pte have bit 6 set: PAGE_DIRTY aka PAGE_FILE. But the vm flags lacks > the marker for a nonlinear (file based) mapping.Got a response from Novell, including a workaround. Next try: http://194.39.182.225/debian/xen/try4. | a01d76fa67414fd157c7f50be89525cc1f03dace linux-headers-2.6.26-1-xen-686_2.6.26-6_i386.deb | 6ed1653d3f8f68026803529bee10dec9e772f706 linux-headers-2.6.26-1-xen-amd64_2.6.26-6_amd64.deb | 7d70566bda9719b9e4c1c310150da76768019d9c linux-image-2.6.26-1-xen-686_2.6.26-6_i386.deb | 19e1a1d2f2dc085ac38968246fcb0e375c9cd14c linux-image-2.6.26-1-xen-amd64_2.6.26-6_amd64.deb | e09de4e292cd7f00fc98689ddec3ad7712ec47e1 linux-modules-2.6.26-1-xen-686_2.6.26-6_i386.deb | 9af0b3015f8d0ea433d06cf2fe9d0055697be485 linux-modules-2.6.26-1-xen-amd64_2.6.26-6_amd64.deb | cafb31d7ef45b26b23f1e3c30b0785b4bfc2cd4d xen-linux-system-2.6.26-1-xen-686_2.6.26-6_i386.deb | 250d7f2a59603e9203840f465a00dd0e990103d1 xen-linux-system-2.6.26-1-xen-amd64_2.6.26-6_amd64.deb Bastian -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20080920/788a2f7d/attachment.pgp
Bastian Blank wrote:> Got a response from Novell, including a workaround. > > Next try: http://194.39.182.225/debian/xen/try4. > >Hi Bastian, great stuff! Do you have any idea where I might get the package linux-headers-2.6.26-1-common-xen for amd64 needed by your provided package linux-headers-2.6.26-1-xen-amd64_2.6.26-6_amd64.deb Or is there another way to build modules like drbd8 for this kernel ..? WR, Bruno -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: OpenPGP digital signature Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20080920/4d6991e0/attachment.pgp
On Sat, Sep 20, 2008 at 12:43:36PM +0200, Bastian Blank wrote:> On Thu, Sep 18, 2008 at 05:43:24PM +0200, Bastian Blank wrote: > > This kernel have a critical problem: > > > > | Bad pte = 11764060, process = vsftpd, vm_flags = 100071, vaddr = b7f85000 > > | Pid: 8129, comm: vsftpd Not tainted 2.6.26-1-xen-686 #1 > > | [<c015edcd>] handle_mm_fault+0x61b/0xe78 > > | [<c0162b8f>] mprotect_fixup+0x6d3/0x735 > > | [<c010ee3e>] do_page_fault+0x684/0xbd6 > > | [<c0162d6b>] sys_mprotect+0x17a/0x1df > > | [<c0162dbd>] sys_mprotect+0x1cc/0x1df > > | [<c010e7ba>] do_page_fault+0x0/0xbd6 > > | [<c02ccbe5>] error_code+0x35/0x3c > > | ======================> > | VM: killing process vsftpd > > > > The pte have bit 6 set: PAGE_DIRTY aka PAGE_FILE. But the vm flags lacks > > the marker for a nonlinear (file based) mapping. > > Got a response from Novell, including a workaround. > > Next try: http://194.39.182.225/debian/xen/try4. >Hmm.. these packages are not available anymore? URL changed? -- Pasi
Hi, Pasi K?rkk?inen wrote:>> Next try: http://194.39.182.225/debian/xen/try4. > Hmm.. these packages are not available anymore? > URL changed?Your local Debian sid mirror, e.g. package xen-linux-system-2.6.26-1-xen-amd64. Kind regards T. -- Thomas Viehmann, http://thomas.viehmann.net/
Pasi Kärkkäinen
2008-Oct-08 15:14 UTC
[Pkg-xen-devel] Xen status in lenny / linux-image-2.6.26-1-xen in sid with dom0 support included
On Mon, Oct 06, 2008 at 07:07:54PM +0200, Thomas Viehmann wrote:> Hi, > > Pasi K?rkk?inen wrote: > >> Next try: http://194.39.182.225/debian/xen/try4. > > Hmm.. these packages are not available anymore? > > URL changed? > Your local Debian sid mirror, e.g. package > xen-linux-system-2.6.26-1-xen-amd64. >Oh, nice. http://packages.debian.org/sid/linux-image-2.6.26-1-xen-686 http://packages.debian.org/changelogs/pool/main/l/linux-2.6/linux-2.6_2.6.26-7/changelog "* [xen] Add SuSE Xen patch. (closes: #495895)" Thanks! -- Pasi
Laurent Léonard
2008-Oct-08 16:07 UTC
[Pkg-xen-devel] Xen status in lenny / linux-image-2.6.26-1-xen in sid with dom0 support included
Le mercredi 08 octobre 2008 ? 17:14, Pasi K?rkk?inen a ?crit?:> On Mon, Oct 06, 2008 at 07:07:54PM +0200, Thomas Viehmann wrote: > > Hi, > > > > Pasi K?rkk?inen wrote: > > >> Next try: http://194.39.182.225/debian/xen/try4. > > > > > > Hmm.. these packages are not available anymore? > > > URL changed? > > > > Your local Debian sid mirror, e.g. package > > xen-linux-system-2.6.26-1-xen-amd64. > > Oh, nice. > > http://packages.debian.org/sid/linux-image-2.6.26-1-xen-686 > http://packages.debian.org/changelogs/pool/main/l/linux-2.6/linux-2.6_2.6.2 >6-7/changelog > > "* [xen] Add SuSE Xen patch. (closes: #495895)" > > Thanks! > > -- Pasi > > _______________________________________________ > Pkg-xen-devel mailing list > Pkg-xen-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-xen-develNice ! But what about amd64 support ? -- Laurent L?onard -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20081008/521c5dd2/attachment.pgp