From owner-freebsd-xen@FreeBSD.ORG Mon Jul 30 11:07:32 2012 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7D7E1065677 for ; Mon, 30 Jul 2012 11:07:32 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7148C8FC2B for ; Mon, 30 Jul 2012 11:07:32 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6UB7WXA002011 for ; Mon, 30 Jul 2012 11:07:32 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6UB7VTQ002009 for freebsd-xen@FreeBSD.org; Mon, 30 Jul 2012 11:07:31 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 30 Jul 2012 11:07:31 GMT Message-Id: <201207301107.q6UB7VTQ002009@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-xen@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jul 2012 11:07:32 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/166174 xen [xen] Problems ROOT MOUNT ERROR o kern/165418 xen [xen] Problems mounting root filesystem from XENHVM o kern/164630 xen [xen] XEN HVM kernel: run_interrupt_driven_hooks: stil o kern/164450 xen [xen] Failed to install FreeeBSD 9.0-RELEASE from CD i o kern/162677 xen [xen] FreeBSD not compatible with "Current Stable Xen" o kern/161318 xen [xen] sysinstall crashes with floating point exception o kern/155468 xen [xen] Xen PV i386 multi-kernel CPU system is not worki o kern/155353 xen [xen] [patch] put "nudging TOD" message under boot_ver o kern/154833 xen [xen]: xen 4.0 - DomU freebsd8.2RC3 i386, XEN kernel. o kern/154473 xen [xen] xen 4.0 - DomU freebsd8.1 i386, XEN kernel. Not o kern/154472 xen [xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel reboot o kern/154428 xen [xen] xn0 network interface and PF - Massive performan o kern/153674 xen [xen] i386/XEN idle thread shows wrong percentages o kern/153672 xen [xen] [panic] i386/XEN panics under heavy fork load o kern/153620 xen [xen] Xen guest system clock drifts in AWS EC2 (FreeBS o kern/153477 xen [xen] XEN pmap code abuses vm page queue lock o kern/153150 xen [xen] xen/ec2: disable checksum offloading on interfac o kern/152228 xen [xen] [panic] Xen/PV panic with machdep.idle_mwait=1 o kern/144629 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143398 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143340 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor f kern/143069 xen [xen] [panic] Xen Kernel Panic - Memory modified after f kern/135667 xen ufs filesystem corruption on XEN DomU system f kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. f kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i p kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all f i386/124516 xen [xen] FreeBSD-CURRENT Xen Kernel Segfaults when config o kern/118734 xen [xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to b 28 problems total. From owner-freebsd-xen@FreeBSD.ORG Wed Aug 1 05:32:46 2012 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 280111065AAC for ; Wed, 1 Aug 2012 05:32:46 +0000 (UTC) (envelope-from wei.xu.prc@gmail.com) Received: from mail-gh0-f182.google.com (mail-gh0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id D8F888FC14 for ; Wed, 1 Aug 2012 05:32:45 +0000 (UTC) Received: by ghbz22 with SMTP id z22so8014627ghb.13 for ; Tue, 31 Jul 2012 22:32:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=M8PsKi22zIRcYbGz2h9Wv0gX68Q1tDtzVlr9rg09uo4=; b=YYoDAFig6luenmy7j3Noo/YTgq5/8cjeP1R7VMnI5T8NDpInOjUrA4q19MXbsAFxKh yHpURDPDHlX3bE2bNNInxXuq/QWR3wLXYU1fhYmTnOxANIXXP40he21vkxeZhwy7tDSW YG9zAxQAeo8t88zKbo56B0p7FoGl4jskm0G9l2CJph1RmCOg8Uhp+YTE+PXUVqOz6hOt OI9Zqnup6Yiehg1QyEFIrXkxS1i9viqdcvPVoovFR8pLCOwTZTi2XkbtUxWRdA9K+glw vAZhXxJd70HSOcsdOdJcukKaiXv8mKkxNP2F/qrswh3mryydFxoFabKEygADUBNMpa2b Qsjw== MIME-Version: 1.0 Received: by 10.50.158.229 with SMTP id wx5mr4275615igb.23.1343799164587; Tue, 31 Jul 2012 22:32:44 -0700 (PDT) Received: by 10.64.33.8 with HTTP; Tue, 31 Jul 2012 22:32:44 -0700 (PDT) Date: Wed, 1 Aug 2012 13:32:44 +0800 Message-ID: From: Wei Xu To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Compiling error for amd64 on FreeBSD9.0 with XENHVM when include xen console driver. X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Aug 2012 05:32:46 -0000 Hi All, I'm trying to compile new kernel with Xen Console driver on AMD 64 platform, it's not included by default, I got compile error like this , I checked the code and i386 has the pc_ipi_to_irq but amd64 doesn't, look like it hasn't been experience with amd64, is there anyone know whether it can work? thanks. /usr/src/sys/xen/evtchn/evtchn.c: In function 'ipi_pcpu': /usr/src/sys/xen/evtchn/evtchn.c:236: error: 'struct pcpu' has no member named 'pc_ipi_to_irq' /usr/src/sys/xen/evtchn/evtchn.c: In function 'bind_virq_to_irq': /usr/src/sys/xen/evtchn/evtchn.c:347: error: 'struct pcpu' has no member named 'pc_virq_to_irq' /usr/src/sys/xen/evtchn/evtchn.c:360: error: 'struct pcpu' has no member named 'pc_virq_to_irq' /usr/src/sys/xen/evtchn/evtchn.c: In function 'bind_ipi_to_irq': /usr/src/sys/xen/evtchn/evtchn.c:383: error: 'struct pcpu' has no member named 'pc_ipi_to_irq' /usr/src/sys/xen/evtchn/evtchn.c:394: error: 'struct pcpu' has no member named 'pc_ipi_to_irq' /usr/src/sys/xen/evtchn/evtchn.c: In function 'unbind_from_irq': /usr/src/sys/xen/evtchn/evtchn.c:424: error: 'struct pcpu' has no member named 'pc_virq_to_irq' /usr/src/sys/xen/evtchn/evtchn.c:428: error: 'struct pcpu' has no member named 'pc_ipi_to_irq' /usr/src/sys/xen/evtchn/evtchn.c: In function 'irq_resume': /usr/src/sys/xen/evtchn/evtchn.c:1012: error: 'struct pcpu' has no member named 'pc_virq_to_irq' /usr/src/sys/xen/evtchn/evtchn.c:1034: error: 'struct pcpu' has no member named 'pc_ipi_to_irq' /usr/src/sys/xen/evtchn/evtchn.c: In function 'evtchn_init': /usr/src/sys/xen/evtchn/evtchn.c:1067: error: 'struct pcpu' has no member named 'pc_virq_to_irq' /usr/src/sys/xen/evtchn/evtchn.c:1069: error: 'struct pcpu' has no member named 'pc_ipi_to_irq Regards, Wei From owner-freebsd-xen@FreeBSD.ORG Wed Aug 1 18:03:09 2012 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C478F106564A for ; Wed, 1 Aug 2012 18:03:09 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout1-b.corp.bf1.yahoo.com (mrout1-b.corp.bf1.yahoo.com [98.139.253.104]) by mx1.freebsd.org (Postfix) with ESMTP id 7BC0E8FC08 for ; Wed, 1 Aug 2012 18:03:09 +0000 (UTC) Received: from [IPv6:::1] (rideseveral.corp.yahoo.com [10.73.160.231]) by mrout1-b.corp.bf1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id q71I2Tgb008935; Wed, 1 Aug 2012 11:02:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1343844150; bh=aNuSBnJx+QHoPVfncmD5+w1CtAvrVvtTYdjI01E3PeU=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=IvV58TGL5PPaTOcKLQzKPVxO0/15e8p6KlIbGFn4Y/G6NWhdRG+HJPw+X4CcCuPt/ t/2O313W6Riu0BjtcORjjxsOKCgA8fV2sCPPbfUIM/cthIbn5zFv8sp1TArzuHtkyP z+OfiPIAykZOvgjPcf3fulCVoZb2wdWwoLCeO0aQ= From: Sean Bruno To: Wei Xu In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Wed, 01 Aug 2012 11:02:28 -0700 Message-ID: <1343844148.5229.1.camel@powernoodle.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Milter-Version: master.31+4-gbc07cd5+ X-CLX-ID: 844149000 Cc: "freebsd-xen@freebsd.org" Subject: Re: Compiling error for amd64 on FreeBSD9.0 with XENHVM when include xen console driver. X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Aug 2012 18:03:09 -0000 On Tue, 2012-07-31 at 22:32 -0700, Wei Xu wrote: > Hi All, > I'm trying to compile new kernel with Xen Console driver on AMD 64 > platform, it's not included by default, > I got compile error like this , I checked the code and i386 has the > pc_ipi_to_irq but amd64 doesn't, > look like it hasn't been experience with amd64, is there anyone know > whether it can work? thanks. > Since there's no PV support for amd64 yet. I don't think you need the console driver. QEMU will emulate the uart(4) device for you and freebsd will use the device as its serial console. >From the dom0, you would run "xm console ". Is this what you mean to do? Sean From owner-freebsd-xen@FreeBSD.ORG Thu Aug 2 09:36:53 2012 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5AF1C106566B for ; Thu, 2 Aug 2012 09:36:53 +0000 (UTC) (envelope-from wei.xu.prc@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 11D628FC08 for ; Thu, 2 Aug 2012 09:36:52 +0000 (UTC) Received: by yhfs35 with SMTP id s35so9872117yhf.13 for ; Thu, 02 Aug 2012 02:36:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YHJvwvfz/nysPS2i10wVsxjN8bvF5+xbQ+NbqAxnoe4=; b=eRAEQ8J+fiMenWMPoRV0Qz4yvd5/h8uYdDWY4BqdLfjtDnn4Y5M6jxRnfGgm9ekR5X n75ICthaV9pLiV9YO3K4q5E33MuipLwzAwnJ9TniZtzPs6G8BH6ae4VZzPxD7jgTzQHx AKDgp87SQFrtIh+MK+6jePf1cqRAkw+pQusvfoN6xM93FgjEFvslJOZBBe0M3mgZ0fv+ AMhgLcqsUy/MB4BHEjCVZal8uLGjey53ZbEV2eXbBXLAKjSYTjnlV1md1cns9BekV1R5 IjFRgYbYj9ypn79WraxvnKPJO7hZR72x0AUtGlaEug+cvvx7j/nuDuu4eMvdyvfxLxKf pMnA== MIME-Version: 1.0 Received: by 10.42.29.4 with SMTP id p4mr3002935icc.30.1343900211706; Thu, 02 Aug 2012 02:36:51 -0700 (PDT) Received: by 10.64.33.8 with HTTP; Thu, 2 Aug 2012 02:36:51 -0700 (PDT) In-Reply-To: <1343844148.5229.1.camel@powernoodle.corp.yahoo.com> References: <1343844148.5229.1.camel@powernoodle.corp.yahoo.com> Date: Thu, 2 Aug 2012 17:36:51 +0800 Message-ID: From: Wei Xu To: Sean Bruno Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-xen@freebsd.org" Subject: Re: Compiling error for amd64 on FreeBSD9.0 with XENHVM when include xen console driver. X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Aug 2012 09:36:53 -0000 Sean, Thanks for your comments. Current I'm trying to investigate if I can porting the Console Driver to Solaris. I know the uart emulated by QEMU, but it's not my purpose to use it, I just want to try the console driver with Hypervisor itself, Must it bundle with PV? Does XENHVM make sense too? I am not familiar with how the console driver works by comparing to Qemu serial, so I'll be really appreciated if you can give some words about that, thanks. To verify it, I installed a new 32 bit i386 FreeBSD guest domain and compiled the kernel with XEN support, that means already included the console driver, but after I installed the new kernel, system can't boot up after loaded the kernel, both the Xen and the Dom0 are 64 bit, so i guess maybe it can't work for 64bit Hypervisor and Dom0, I wonder how can I verify the console driver? Regards, Wei On Thu, Aug 2, 2012 at 2:02 AM, Sean Bruno wrote: > On Tue, 2012-07-31 at 22:32 -0700, Wei Xu wrote: > > Hi All, > > I'm trying to compile new kernel with Xen Console driver on AMD 64 > > platform, it's not included by default, > > I got compile error like this , I checked the code and i386 has the > > pc_ipi_to_irq but amd64 doesn't, > > look like it hasn't been experience with amd64, is there anyone know > > whether it can work? thanks. > > > > Since there's no PV support for amd64 yet. I don't think you need the > console driver. QEMU will emulate the uart(4) device for you and > freebsd will use the device as its serial console. > > From the dom0, you would run "xm console ". Is this what you > mean to do? > > Sean > > From owner-freebsd-xen@FreeBSD.ORG Thu Aug 2 17:41:38 2012 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C3654106570B for ; Thu, 2 Aug 2012 17:41:38 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout1-b.corp.bf1.yahoo.com (mrout1-b.corp.bf1.yahoo.com [98.139.253.104]) by mx1.freebsd.org (Postfix) with ESMTP id 76D088FC1E for ; Thu, 2 Aug 2012 17:41:38 +0000 (UTC) Received: from [IPv6:::1] (rideseveral.corp.yahoo.com [10.73.160.231]) by mrout1-b.corp.bf1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id q72HeL38001373; Thu, 2 Aug 2012 10:40:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1343929223; bh=WG82deOJeU/xz0IJiRVp6SFBMni0rCTE+8xte46iqmM=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=q5WkvwjJngMcA+TzYLfrW11UJNo3jIyxuqpbFr5OfCcv+kNbYeRR+glP1n6QI6dLL bPWIcOUvm12naCo0hmQcu5QgJHG5BMSagGiK9YNfUJfdk1lalm5vCsGXsXmV3T8IpY oJRZlzVS8+4GCl/dyIDi/4P6TyKg8AbqkrLk3eXg= From: Sean Bruno To: Wei Xu In-Reply-To: References: <1343844148.5229.1.camel@powernoodle.corp.yahoo.com> Content-Type: text/plain; charset="UTF-8" Date: Thu, 02 Aug 2012 10:40:21 -0700 Message-ID: <1343929221.2573.5.camel@powernoodle.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Milter-Version: master.31+4-gbc07cd5+ X-CLX-ID: 929222005 Cc: "freebsd-xen@freebsd.org" Subject: Re: Compiling error for amd64 on FreeBSD9.0 with XENHVM when include xen console driver. X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Aug 2012 17:41:38 -0000 I run a linux Dom0 (64bit RHEL 5) currently for testing purposes in the freebsd cluster. We have 32bit (PV) and 64bit (HVM) instances running there. How are you installing FreeBSD on your Dom0? Are you starting with HVM support and the ISO image and then converting to PV support? Sean On Thu, 2012-08-02 at 02:36 -0700, Wei Xu wrote: > Sean, > Thanks for your comments. > > Current I'm trying to investigate if I can porting the Console Driver > to Solaris. > > I know the uart emulated by QEMU, but it's not my purpose to use it, I > just want to try the console driver with Hypervisor itself, Must it > bundle with PV? Does XENHVM make sense too? > > I am not familiar with how the console driver works by comparing to > Qemu serial, so I'll be really appreciated if you can give some words > about that, thanks. > > To verify it, I installed a new 32 bit i386 FreeBSD guest domain and > compiled the kernel with XEN support, that means already included the > console driver, but after I installed the new kernel, system can't > boot up after loaded the kernel, both the Xen and the Dom0 are 64 bit, > so i guess maybe it can't work for 64bit Hypervisor and Dom0, I wonder > how can I verify the console driver? > > Regards, > Wei > > > On Thu, Aug 2, 2012 at 2:02 AM, Sean Bruno > wrote: > On Tue, 2012-07-31 at 22:32 -0700, Wei Xu wrote: > > Hi All, > > I'm trying to compile new kernel with Xen Console driver on > AMD 64 > > platform, it's not included by default, > > I got compile error like this , I checked the code and i386 > has the > > pc_ipi_to_irq but amd64 doesn't, > > look like it hasn't been experience with amd64, is there > anyone know > > whether it can work? thanks. > > > > > Since there's no PV support for amd64 yet. I don't think you > need the > console driver. QEMU will emulate the uart(4) device for you > and > freebsd will use the device as its serial console. > > >From the dom0, you would run "xm console ". Is this > what you > mean to do? > > Sean > > From owner-freebsd-xen@FreeBSD.ORG Fri Aug 3 02:21:41 2012 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 89951106566B for ; Fri, 3 Aug 2012 02:21:41 +0000 (UTC) (envelope-from wei.xu.prc@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3E3BA8FC14 for ; Fri, 3 Aug 2012 02:21:40 +0000 (UTC) Received: by yenl8 with SMTP id l8so300800yen.13 for ; Thu, 02 Aug 2012 19:21:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8hBcdXiBm8EJIxjEz8RQ1hDYilSPi2kWMhv3+1TP7oM=; b=ycyRtHH92+pPw2I60ZzJIf/UtV76NKaWCyDO5HAdSy3/f5i2Sehpl/skMdBy/M+NP+ /CIMjiWqgv4wQQ9zOvRdRhkfqWzNwUme53bD6gbXPzq1bmh5KP6o6/tymX7/6+rLVB8V gueXvk8Poo/vxoIS19EN6u+wwKeNJExI6AWyBG3VNr8dhILtdJILflWL28qYczZYDsKV QM5PLIfYKuP6xRxiL1zZJ201bCmnb3c7XjkSYrGuO6kh2BKzXNj7MAbO3y1qjSbhtE2f KQPWQKJE27CibjuGtJPmcFaGOgsJkRB6kCfG/94/IpuOMLY919gOxmelTMiBzghRuG+A B3Yw== MIME-Version: 1.0 Received: by 10.42.86.20 with SMTP id s20mr212787icl.21.1343960499918; Thu, 02 Aug 2012 19:21:39 -0700 (PDT) Received: by 10.64.33.8 with HTTP; Thu, 2 Aug 2012 19:21:39 -0700 (PDT) In-Reply-To: <1343929221.2573.5.camel@powernoodle.corp.yahoo.com> References: <1343844148.5229.1.camel@powernoodle.corp.yahoo.com> <1343929221.2573.5.camel@powernoodle.corp.yahoo.com> Date: Fri, 3 Aug 2012 10:21:39 +0800 Message-ID: From: Wei Xu To: Sean Bruno Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-xen@freebsd.org" Subject: Re: Compiling error for amd64 on FreeBSD9.0 with XENHVM when include xen console driver. X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Aug 2012 02:21:41 -0000 My Dom0 is Oracle Linux(64bit too), Xen version is 4.0.2, I installed FreeBSD with the official iso image, that's "FreeBSD-9.0-RELEASE-i386-dvd1.iso", I'm not sure if it was started as HVM by default, how can i check it? How to convert it to PV support, i just compiled and installed the src with the "XEN" config in the source tree, I think that will include PV support, since "XEN" is defined in the options, right? On Fri, Aug 3, 2012 at 1:40 AM, Sean Bruno wrote: > I run a linux Dom0 (64bit RHEL 5) currently for testing purposes in the > freebsd cluster. > > We have 32bit (PV) and 64bit (HVM) instances running there. > > How are you installing FreeBSD on your Dom0? Are you starting with HVM > support and the ISO image and then converting to PV support? > > Sean > > On Thu, 2012-08-02 at 02:36 -0700, Wei Xu wrote: > > Sean, > > Thanks for your comments. > > > > Current I'm trying to investigate if I can porting the Console Driver > > to Solaris. > > > > I know the uart emulated by QEMU, but it's not my purpose to use it, I > > just want to try the console driver with Hypervisor itself, Must it > > bundle with PV? Does XENHVM make sense too? > > > > I am not familiar with how the console driver works by comparing to > > Qemu serial, so I'll be really appreciated if you can give some words > > about that, thanks. > > > > To verify it, I installed a new 32 bit i386 FreeBSD guest domain and > > compiled the kernel with XEN support, that means already included the > > console driver, but after I installed the new kernel, system can't > > boot up after loaded the kernel, both the Xen and the Dom0 are 64 bit, > > so i guess maybe it can't work for 64bit Hypervisor and Dom0, I wonder > > how can I verify the console driver? > > > > Regards, > > Wei > > > > > > On Thu, Aug 2, 2012 at 2:02 AM, Sean Bruno > > wrote: > > On Tue, 2012-07-31 at 22:32 -0700, Wei Xu wrote: > > > Hi All, > > > I'm trying to compile new kernel with Xen Console driver on > > AMD 64 > > > platform, it's not included by default, > > > I got compile error like this , I checked the code and i386 > > has the > > > pc_ipi_to_irq but amd64 doesn't, > > > look like it hasn't been experience with amd64, is there > > anyone know > > > whether it can work? thanks. > > > > > > > > > Since there's no PV support for amd64 yet. I don't think you > > need the > > console driver. QEMU will emulate the uart(4) device for you > > and > > freebsd will use the device as its serial console. > > > > >From the dom0, you would run "xm console ". Is this > > what you > > mean to do? > > > > Sean > > > > > > > From owner-freebsd-xen@FreeBSD.ORG Fri Aug 3 16:22:41 2012 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 25334106564A for ; Fri, 3 Aug 2012 16:22:41 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout1-b.corp.bf1.yahoo.com (mrout1-b.corp.bf1.yahoo.com [98.139.253.104]) by mx1.freebsd.org (Postfix) with ESMTP id E34178FC18 for ; Fri, 3 Aug 2012 16:22:40 +0000 (UTC) Received: from [IPv6:::1] (rideseveral.corp.yahoo.com [10.73.160.231]) by mrout1-b.corp.bf1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id q73GM4Dv067457; Fri, 3 Aug 2012 09:22:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1344010925; bh=Z+gLf5f2T1MbTl/LAzLQKGHzWkrcbWk7pq2tZhHbyLk=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=cMUxpA5KNjPappyg4uinHU0RaLv2L18kE29GByLCIrBZdJ/NyRjPiwQUfURuBLyb9 6vw2XyWofn8iPRmBhytOWsq5p3d9avqhKtuO6rkTvmjmeqNI1nZr+aeyp8+2ZfbqUi hVYcu0Iru/Heiu63Y/NrRyjulAPVQNnuPSqlgEY0= From: Sean Bruno To: Wei Xu In-Reply-To: References: <1343844148.5229.1.camel@powernoodle.corp.yahoo.com> <1343929221.2573.5.camel@powernoodle.corp.yahoo.com> Content-Type: text/plain; charset="UTF-8" Date: Fri, 03 Aug 2012 09:22:04 -0700 Message-ID: <1344010924.2552.7.camel@powernoodle.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Milter-Version: master.31+4-gbc07cd5+ X-CLX-ID: 010924002 Cc: "freebsd-xen@freebsd.org" Subject: Re: Compiling error for amd64 on FreeBSD9.0 with XENHVM when include xen console driver. X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Aug 2012 16:22:41 -0000 On Thu, 2012-08-02 at 19:21 -0700, Wei Xu wrote: > My Dom0 is Oracle Linux(64bit too), Xen version is 4.0.2, I installed > FreeBSD with the official iso image, that's > "FreeBSD-9.0-RELEASE-i386-dvd1.iso", I'm not sure if it was started as > HVM by default, how can i check it? > If the VM started up at all, it had to be running via full hardware virtualization. :-) > How to convert it to PV support, i just compiled and installed the src > with the "XEN" config in the source tree, I think that will include PV > support, since "XEN" is defined in the options, right? > Correct. You compile your i386 kernel with the XEN kernel config, then you need to copy that kernel into your Dom0 and reconfigure the VM to be PV and boot with no HVM options. I'm not sure how to do that with the tools that you have access to, but I did this by editing the xen domU config file for the virtual machine. Here's an example of my DomU config for your reference. Of course, this is a Xen 3 hypervisor, so your changes might have to be different( xl create vs xm create). #============================================================================ # Python configuration setup for 'xm create'. # This script sets the parameters used when a domain is created using 'xm create'. # You use a separate script for each domain you want to create, or # you can set the parameters for the domain on the xm command line. #============================================================================ #---------------------------------------------------------------------------- # Kernel image file. #kernel = "/usr/lib/xen/boot/hvmloader" kernel = "/var/virt/freebsd-9.current-i386-domu-kernel" #---------------------------------------------------------------------------- # device model to use: only qemu-dm available for now #device_model = '/usr/lib64/xen/bin/qemu-dm' #builder='hvm' # Initial memory allocation (in megabytes) for the new domain. memory = 2048 # number of CPUS vcpus = 1 # A name for your domain. All domains must have different names. name = "ref9-xen32" arch = "i386" #Network interface. By default emules a realtek 8139. For a NetBSD guest you # have to disable re(4) and let rtk attach to use it. # ne2k_pci emulates a pci ne2000 clone; this his cpu-hungry in dom0 # pcnet emulates a AMD PCnet-PCI controller; but it corrupts packets with # pcn(4) under NetBSD. #vif = [ 'mac=00:16:3e:00:00:03, bridge=xenbr0, type=ioemu' ] vif = [ 'mac=00:16:3e:00:00:03, bridge=xenbr0, type=vbd' ] # Define the disk devices you want the domain to have access to, and # what you want them accessible as. # Each disk entry is of the form phy:UNAME,DEV,MODE # where UNAME is the device, DEV is the device name the domain will see, # and MODE is r for read-only, w for read-write. # For hvm domains you can only use hda to hdd. You can set extra types # (e.g. cdrom) disk = [ 'file:/var/virt/ref9-xen32.bin,hda,w', 'file:/var/virt/ref9-xen32_scratch.bin,hdb,w' ] # floppy images; this doesn't seem to work currently. Use a iso image instead. #fda = '/home/domains/boot1.fs' extra = "vfs.root.mountfrom=ufs:/dev/ad0p2,kern.hz=100" # boot device: a = floppy, c= hard drive, d= cdrom (with the disk entry # before) # # boot CDROM image #boot='d' # boot from DISK file #boot='c' # boot from DHCP/PXE then DISK file boot='nc' # By default, 'xm create' will try to open an X window on the current display # for the virtal framebuffer. You can have the virtal framebuffer in vnc # instead, and connect using a vnc client (using localhost:$vncdisplay) # If vncunused is set to 1 (this is the default value), vncdisplay # will be set to the first unused port; so it's recommended to #vnc = 1 #vncdisplay = 3 #vncunused = 1 #vncpasswd='' #Xen emulates a PS/2 mouse, but the pointer in the guest has difficulties # tracking the absolute position. Xen can emulate a USB tablet in addition # to the mouse which will report the absolute position of the pointer, # and make the mouse much easier to use. # usb=1 usbdevice='tablet' #usbdevice='mouse' acpi = 1 serial='pty' on_reboot='restart' #============================================================================ From owner-freebsd-xen@FreeBSD.ORG Sat Aug 4 00:50:01 2012 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDB23106564A for ; Sat, 4 Aug 2012 00:50:01 +0000 (UTC) (envelope-from wei.xu.prc@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 96A188FC0C for ; Sat, 4 Aug 2012 00:50:01 +0000 (UTC) Received: by yenl8 with SMTP id l8so1759556yen.13 for ; Fri, 03 Aug 2012 17:50:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=icfwDy0f73/g5bfT0z++qZ/9TwZepgHhQP8PIGomjGg=; b=oZQFpUltHecvnyUbjwbCjhfNRZkvyLFYQivGFaDFwkO1pbWHOwi3jmTxVAAgBbex73 xMuG9mb4dN2tDkAZ5hcWmhctLqCBiTRNINKVfv4zuckehIdt9hrOpIBz8hmS0fDjLlaH /eWmn8JmyTukx0KfCgBYR7mlrN6x91MazTo9rZ5rw1eaaqctRr6LC0yqKeVowmYdMi8b wDZqJFdnxw+ODv2HbkKIuU5MjZ9sQ5pRwOhlHvXNE65LjD+cgv/iBTUb9S8DaRDVYj1w 8PeTCt231rYQaeNlTyUG9e3snkzI/EUVTK2MzVkmAJHWn8TV+gfkA7glwFWjgHCMN5XT 0qMA== MIME-Version: 1.0 Received: by 10.50.6.197 with SMTP id d5mr91880iga.44.1344041400424; Fri, 03 Aug 2012 17:50:00 -0700 (PDT) Received: by 10.64.33.8 with HTTP; Fri, 3 Aug 2012 17:50:00 -0700 (PDT) In-Reply-To: <1344010924.2552.7.camel@powernoodle.corp.yahoo.com> References: <1343844148.5229.1.camel@powernoodle.corp.yahoo.com> <1343929221.2573.5.camel@powernoodle.corp.yahoo.com> <1344010924.2552.7.camel@powernoodle.corp.yahoo.com> Date: Sat, 4 Aug 2012 08:50:00 +0800 Message-ID: From: Wei Xu To: Sean Bruno Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-xen@freebsd.org" Subject: Re: Compiling error for amd64 on FreeBSD9.0 with XENHVM when include xen console driver. X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Aug 2012 00:50:02 -0000 Sean=EF=BC=8C Thanks=EF=BC=8Ci'll try it. On Saturday, August 4, 2012, Sean Bruno wrote: > > > > On Thu, 2012-08-02 at 19:21 -0700, Wei Xu wrote: > > My Dom0 is Oracle Linux(64bit too), Xen version is 4.0.2, I installed > > FreeBSD with the official iso image, that's > > "FreeBSD-9.0-RELEASE-i386-dvd1.iso", I'm not sure if it was started as > > HVM by default, how can i check it? > > > > If the VM started up at all, it had to be running via full hardware > virtualization. :-) > > > > How to convert it to PV support, i just compiled and installed the src > > with the "XEN" config in the source tree, I think that will include PV > > support, since "XEN" is defined in the options, right? > > > > Correct. You compile your i386 kernel with the XEN kernel config, then > you need to copy that kernel into your Dom0 and reconfigure the VM to be > PV and boot with no HVM options. I'm not sure how to do that with the > tools that you have access to, but I did this by editing the xen domU > config file for the virtual machine. Here's an example of my DomU > config for your reference. Of course, this is a Xen 3 hypervisor, so > your changes might have to be different( xl create vs xm create). > > > #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D > # Python configuration setup for 'xm create'. > # This script sets the parameters used when a domain is created using > 'xm create'. > # You use a separate script for each domain you want to create, or > # you can set the parameters for the domain on the xm command line. > > #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D > > > #------------------------------------------------------------------------= ---- > # Kernel image file. > #kernel =3D "/usr/lib/xen/boot/hvmloader" > kernel =3D "/var/virt/freebsd-9.current-i386-domu-kernel" > > > #------------------------------------------------------------------------= ---- > # device model to use: only qemu-dm available for now > #device_model =3D '/usr/lib64/xen/bin/qemu-dm' > > #builder=3D'hvm' > > # Initial memory allocation (in megabytes) for the new domain. > memory =3D 2048 > > # number of CPUS > vcpus =3D 1 > > # A name for your domain. All domains must have different names. > name =3D "ref9-xen32" > arch =3D "i386" > > #Network interface. By default emules a realtek 8139. For a NetBSD guest > you > # have to disable re(4) and let rtk attach to use it. > # ne2k_pci emulates a pci ne2000 clone; this his cpu-hungry in dom0 > # pcnet emulates a AMD PCnet-PCI controller; but it corrupts packets > with > # pcn(4) under NetBSD. > #vif =3D [ 'mac=3D00:16:3e:00:00:03, bridge=3Dxenbr0, type=3Dioemu' ] > vif =3D [ 'mac=3D00:16:3e:00:00:03, bridge=3Dxenbr0, type=3Dvbd' ] > > # Define the disk devices you want the domain to have access to, and > # what you want them accessible as. > # Each disk entry is of the form phy:UNAME,DEV,MODE > # where UNAME is the device, DEV is the device name the domain will see, > # and MODE is r for read-only, w for read-write. > # For hvm domains you can only use hda to hdd. You can set extra types > # (e.g. cdrom) > > disk =3D [ > 'file:/var/virt/ref9-xen32.bin,hda,w', > 'file:/var/virt/ref9-xen32_scratch.bin,hdb,w' > ] > # floppy images; this doesn't seem to work currently. Use a iso image > instead. > #fda =3D '/home/domains/boot1.fs' > > extra =3D "vfs.root.mountfrom=3Dufs:/dev/ad0p2,kern.hz=3D100" > > # boot device: a =3D floppy, c=3D hard drive, d=3D cdrom (with the disk e= ntry > # before) > # > # boot CDROM image > #boot=3D'd' > # boot from DISK file > #boot=3D'c' > # boot from DHCP/PXE then DISK file > boot=3D'nc' > > # By default, 'xm create' will try to open an X window on the current > display > # for the virtal framebuffer. You can have the virtal framebuffer in vnc > # instead, and connect using a vnc client (using localhost:$vncdisplay) > # If vncunused is set to 1 (this is the default value), vncdisplay > # will be set to the first unused port; so it's recommended to > #vnc =3D 1 > #vncdisplay =3D 3 > #vncunused =3D 1 > #vncpasswd=3D'' > > #Xen emulates a PS/2 mouse, but the pointer in the guest has > difficulties > # tracking the absolute position. Xen can emulate a USB tablet in > addition > # to the mouse which will report the absolute position of the pointer, > # and make the mouse much easier to use. > # > usb=3D1 > usbdevice=3D'tablet' > #usbdevice=3D'mouse' > > acpi =3D 1 > serial=3D'pty' > on_reboot=3D'restart' > > #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D > > > > > > > >