From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 1B7F413881D for ; Sat, 26 Sep 2015 12:00:58 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A094421C024; Sat, 26 Sep 2015 12:00:44 +0000 (UTC) Received: from gw2.antarean.org (gw2.antarean.org [141.105.125.208]) by pigeon.gentoo.org (Postfix) with ESMTP id 34F51E07ED for ; Sat, 26 Sep 2015 12:00:43 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by gw2.antarean.org (Postfix) with ESMTP id DEEEF121730 for ; Sat, 26 Sep 2015 12:00:30 +0000 () X-Virus-Scanned: amavisd-new at antarean.org Received: from gw2.antarean.org ([127.0.0.1]) by localhost (gw2.antarean.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g5MvYH6EHBHN for ; Sat, 26 Sep 2015 12:00:30 +0000 (%Z) Received: from data.antarean.org (localhost [127.0.0.1]) by gw2.antarean.org (Postfix) with ESMTP id 10FD9121726 for ; Sat, 26 Sep 2015 12:00:30 +0000 () Received: from andromeda.localnet (unknown [10.20.13.50]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by data.antarean.org (Postfix) with ESMTPSA id 235D84C for ; Sat, 26 Sep 2015 13:59:17 +0200 (CEST) From: "J. Roeleveld" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] installing Gentoo as a xen guest Date: Sat, 26 Sep 2015 14:00:31 +0200 Message-ID: <7846197.TrGdNNXtG4@andromeda> User-Agent: KMail/4.14.8 (Linux/4.0.5-gentoo; KDE/4.14.8; x86_64; ; ) In-Reply-To: <5603FBA8.1090508@alstadheim.priv.no> References: <5603CAEB.2050709@gc-24.de> <5603FBA8.1090508@alstadheim.priv.no> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" X-Archives-Salt: 3f4f2a9c-bda1-4351-b447-b3f42a51d0da X-Archives-Hash: c1e17d515cb64f8e502c1a045394162e On Thursday, September 24, 2015 03:33:28 PM H=E5kon Alstadheim wrote: > Den 24. sep. 2015 14:53, skrev Rich Freeman: > > On Thu, Sep 24, 2015 at 6:05 AM, hw wrote: > >> Hi, > >>=20 > >> I'm installing Gentoo as a xen PV guest. Do I need to install a > >> bootloader > >> like grub, or should I rather just specify the kernel to boot in t= he > >> definition file of the guest? If I do the latter, what about the = kernel > >> command line? > >>=20 > >> Is there anything I should consider? The host is also running Gen= too. > >=20 > > You can do either. I suspect it would be easier to just use grub. = I > > don't know if xen provides a way to provide a command-line, if not = you > > could build a default command-line into your kernel. >=20 > Depending on your hardware you will want to use hvm or pvm for > efficiency. (VT-x means hvm is more efficient). What do you base this on? Without VT-x, HVM doesn't even work, which means PV is only option. With VT-x, PV still has higher performance as the drivers inside the gu= est=20 talk directly to the host. > If running hvm on > quemu-xen-traditional, you HAVE to use a bootloader inside the VM, or= > some kind of netboot/pvgrub thing. If running upstream quemu for a hv= m, > you can choose. I find it less of a hassle to use bootloader inside t= he > VM. It's simple, if you don't have full access to the host. If you have full access, it's actually simpler as you don't have to wor= ry=20 about boot-order, partitioning and a bootloader. > If running pv, I BELIEVE you have to specify kernel and boot options > outside the VM-image, possibly through pvgrub. Pvgrub is supposed to = be > able to fish out kernel and initrd from the VM disk. I never bothered= to > get that working. Here is an example excerpt from a PVM I use (for a > debian vm): > --print.pvm--- > builder =3D "generic" > kernel =3D "/etc/xen/wheezy/vmlinuz-3.16.0-0.bpo.4-amd64" > ramdisk =3D "/etc/xen/wheezy/initrd.img-3.16.0-0.bpo.4-amd64" > extra =3D "root=3D/dev/xvda console=3Dhvc0 tmem" > -- > For explanation check "man xl.cfg". When you specify > kernel&ramdisk¶meters in the vm config, you do NOT need a /boot/ > directory on your vm. Obviously when you build a kernel inside the v= m, > it will end up in /boot, so you have to provide a way for the > dom0/hypervisor to load your kernel, either (when using full > virtualization) a regular boot-loader inside the vm, or (for a PV gue= st) > through some other means to let the dom0/hypervisor load your image. -- Joost