From dsrinivasmail at yahoo.com Sun Feb 1 10:28:14 2009 From: dsrinivasmail at yahoo.com (srinivas d) Date: Sun, 1 Feb 2009 02:28:14 -0800 (PST) Subject: [Fedora-xen] (no subject) Message-ID: <777006.58635.qm@web33308.mail.mud.yahoo.com> D.Srinivas From pasik at iki.fi Tue Feb 3 20:24:47 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 3 Feb 2009 22:24:47 +0200 Subject: [Fedora-xen] bzImage dom0 kernel support in latest rawhide Xen packages Message-ID: <20090203202447.GU15052@edu.joroinen.fi> Hello! For those interested in testing pv_ops dom0 kernels it seems latest Xen packages in rawhide contain bzImage dom0 kernel support in Xen hypervisor. rawhide report: 20090203 changes xen-3.3.1-3.fc11 ---------------- * Tue Feb 3 17:00:00 2009 Gerd Hoffmann - 3.3.1-3 - backport bzImage support for dom0 builder. -- Pasi From pasik at iki.fi Wed Feb 4 11:03:50 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 4 Feb 2009 13:03:50 +0200 Subject: [Fedora-xen] Re: [fedora-virt] bzImage dom0 kernel support in latest rawhide Xen packages In-Reply-To: References: <20090203202447.GU15052@edu.joroinen.fi> Message-ID: <20090204110350.GW15052@edu.joroinen.fi> On Tue, Feb 03, 2009 at 10:18:53PM -0200, Itamar Reis Peixoto wrote: > I need to configure something to boot dom0 ? > Well you need to have dom0 kernel.. (there's no dom0 capable kernel in fedora/rawhide yet, so you need to compile/build/get one yourself). Nothing to configure really.. just configure grub.conf in the normal way to boot Xen and dom0 kernel. -- Pasi > > On Tue, Feb 3, 2009 at 6:24 PM, Pasi K?rkk?inen wrote: > > Hello! > > > > For those interested in testing pv_ops dom0 kernels it seems latest Xen > > packages in rawhide contain bzImage dom0 kernel support in Xen hypervisor. > > > > > > rawhide report: 20090203 changes > > > > > > xen-3.3.1-3.fc11 > > ---------------- > > * Tue Feb 3 17:00:00 2009 Gerd Hoffmann - 3.3.1-3 > > - backport bzImage support for dom0 builder. > > > > > > -- Pasi > > > > _______________________________________________ > > Fedora-virt mailing list > > Fedora-virt at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-virt > > > > > > -- > ------------ > > Itamar Reis Peixoto > > e-mail/msn: itamar at ispbrasil.com.br > sip: itamar at ispbrasil.com.br > skype: itamarjp > icq: 81053601 > +55 11 4063 5033 > +55 34 3221 8599 From ondrejj at salstar.sk Wed Feb 4 12:16:28 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Wed, 4 Feb 2009 13:16:28 +0100 Subject: [Fedora-xen] Re: [fedora-virt] bzImage dom0 kernel support in latest rawhide Xen packages In-Reply-To: <20090204110350.GW15052@edu.joroinen.fi> References: <20090203202447.GU15052@edu.joroinen.fi> <20090204110350.GW15052@edu.joroinen.fi> Message-ID: <20090204121628.GI18191@salstar.sk> > > On Tue, Feb 3, 2009 at 6:24 PM, Pasi K?rkk?inen wrote: > > > Hello! > > > > > > For those interested in testing pv_ops dom0 kernels it seems latest Xen > > > packages in rawhide contain bzImage dom0 kernel support in Xen hypervisor. I am trying to compile current 2.6.29 kernel (as described here: http://wiki.xensource.com/xenwiki/XenParavirtOps), but without success yet. When trying to boot ./vmlinux ro ./arch/x86/boot/bzImage (also with xen-hypervisor-3.3.1-3.fc11) I still get something like this: (XEN) *** LOADING DOMAIN 0 *** (XEN) elf_xen_note_check: ERROR: Will only load images built for the generic loader or Linux images My grub.conf entry: title Xen TEST root (hd0,0) kernel /boot/xen-3.3.gz noreboot module /boot/xen/vmlinux root=/dev/sda1 ro earlyprintk=xen pci=nomsi module /boot/xen/initrd.img [root at note ~]# file /boot/xen-3.3.gz /boot/xen/vmlinux /boot/xen/initrd.img /boot/xen/bzImage /boot/xen-3.3.gz: gzip compressed data, from Unix, last modified: Tue Feb 3 12:36:39 2009, max compression /boot/xen/vmlinux: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, stripped /boot/xen/initrd.img: gzip compressed data, from Unix, last modified: Wed Feb 4 12:00:01 2009, max compression /boot/xen/bzImage: Linux kernel x86 boot executable RO-rootFS, swap_dev 0x2, Normal VGA [root at note ~]# rpm -q xen-hypervisor xen-hypervisor-3.3.1-3.fc11.i386 [root at note ~]# My bzImage boots well with modified grub to boot it as "kernel" and not using xen-3.3 loader. What I am doing wrong? Can sombody send me kernel.config file for 2.6.29, something similar to old kernel-xen rpm package's config? SAL From kraxel at redhat.com Wed Feb 4 12:29:39 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Wed, 04 Feb 2009 13:29:39 +0100 Subject: [Fedora-xen] Re: [fedora-virt] bzImage dom0 kernel support in latest rawhide Xen packages In-Reply-To: <20090204121628.GI18191@salstar.sk> References: <20090203202447.GU15052@edu.joroinen.fi> <20090204110350.GW15052@edu.joroinen.fi> <20090204121628.GI18191@salstar.sk> Message-ID: <49898A33.1080703@redhat.com> Jan ONDREJ (SAL) wrote: >>> On Tue, Feb 3, 2009 at 6:24 PM, Pasi K?rkk?inen wrote: >>>> Hello! >>>> >>>> For those interested in testing pv_ops dom0 kernels it seems latest Xen >>>> packages in rawhide contain bzImage dom0 kernel support in Xen hypervisor. > > I am trying to compile current 2.6.29 kernel (as described here: > http://wiki.xensource.com/xenwiki/XenParavirtOps), but without success yet. > > When trying to boot ./vmlinux ro ./arch/x86/boot/bzImage (also with > xen-hypervisor-3.3.1-3.fc11) I still get something like this: > > (XEN) *** LOADING DOMAIN 0 *** > (XEN) elf_xen_note_check: ERROR: Will only load images built for the generic > loader or Linux images > > My grub.conf entry: > title Xen TEST > root (hd0,0) > kernel /boot/xen-3.3.gz noreboot > module /boot/xen/vmlinux root=/dev/sda1 ro earlyprintk=xen pci=nomsi > module /boot/xen/initrd.img > [root at note ~]# file /boot/xen-3.3.gz /boot/xen/vmlinux /boot/xen/initrd.img /boot/xen/bzImage > /boot/xen-3.3.gz: gzip compressed data, from Unix, last modified: Tue Feb 3 12:36:39 2009, max compression > /boot/xen/vmlinux: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, stripped "stripped". This probably is the problem. > /boot/xen/initrd.img: gzip compressed data, from Unix, last modified: Wed Feb 4 12:00:01 2009, max compression > /boot/xen/bzImage: Linux kernel x86 boot executable RO-rootFS, swap_dev 0x2, Normal VGA Try this one instead of vmlinux (unstripped vmlinux should work too). HTH Gerd From ondrejj at salstar.sk Wed Feb 4 12:35:23 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Wed, 4 Feb 2009 13:35:23 +0100 Subject: [Fedora-xen] Re: [fedora-virt] bzImage dom0 kernel support in latest rawhide Xen packages In-Reply-To: <49898A33.1080703@redhat.com> References: <20090203202447.GU15052@edu.joroinen.fi> <20090204110350.GW15052@edu.joroinen.fi> <20090204121628.GI18191@salstar.sk> <49898A33.1080703@redhat.com> Message-ID: <20090204123523.GL18191@salstar.sk> On Wed, Feb 04, 2009 at 01:29:39PM +0100, Gerd Hoffmann wrote: > Jan ONDREJ (SAL) wrote: > > [root at note ~]# file /boot/xen-3.3.gz /boot/xen/vmlinux /boot/xen/initrd.img /boot/xen/bzImage > > /boot/xen-3.3.gz: gzip compressed data, from Unix, last modified: Tue Feb 3 12:36:39 2009, max compression > > /boot/xen/vmlinux: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, stripped > > "stripped". This probably is the problem. > > > /boot/xen/initrd.img: gzip compressed data, from Unix, last modified: Wed Feb 4 12:00:01 2009, max compression > > /boot/xen/bzImage: Linux kernel x86 boot executable RO-rootFS, swap_dev 0x2, Normal VGA > > Try this one instead of vmlinux (unstripped vmlinux should work too). Already tryed both of them. Stripped, unstripped vmlinux, gzip compressed vmlinux, bzImage. Always same problem. SAL From pasik at iki.fi Wed Feb 4 16:29:57 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 4 Feb 2009 18:29:57 +0200 Subject: [Fedora-xen] Re: [fedora-virt] bzImage dom0 kernel support in latest rawhide Xen packages In-Reply-To: <20090204123523.GL18191@salstar.sk> References: <20090203202447.GU15052@edu.joroinen.fi> <20090204110350.GW15052@edu.joroinen.fi> <20090204121628.GI18191@salstar.sk> <49898A33.1080703@redhat.com> <20090204123523.GL18191@salstar.sk> Message-ID: <20090204162957.GZ15052@edu.joroinen.fi> On Wed, Feb 04, 2009 at 01:35:23PM +0100, Jan ONDREJ (SAL) wrote: > On Wed, Feb 04, 2009 at 01:29:39PM +0100, Gerd Hoffmann wrote: > > Jan ONDREJ (SAL) wrote: > > > [root at note ~]# file /boot/xen-3.3.gz /boot/xen/vmlinux /boot/xen/initrd.img /boot/xen/bzImage > > > /boot/xen-3.3.gz: gzip compressed data, from Unix, last modified: Tue Feb 3 12:36:39 2009, max compression > > > /boot/xen/vmlinux: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, stripped > > > > "stripped". This probably is the problem. > > > > > /boot/xen/initrd.img: gzip compressed data, from Unix, last modified: Wed Feb 4 12:00:01 2009, max compression > > > /boot/xen/bzImage: Linux kernel x86 boot executable RO-rootFS, swap_dev 0x2, Normal VGA > > > > Try this one instead of vmlinux (unstripped vmlinux should work too). > > Already tryed both of them. Stripped, unstripped vmlinux, gzip compressed > vmlinux, bzImage. Always same problem. > I've been using gzipped vmlinux pv_ops dom0 kernel successfully. I still haven't tried that new bzImage support .. will try that today or tomorrow. -- Pasi From pasik at iki.fi Thu Feb 5 08:03:58 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Thu, 5 Feb 2009 10:03:58 +0200 Subject: [Fedora-xen] Re: [fedora-virt] bzImage dom0 kernel support in latest rawhide Xen packages In-Reply-To: <20090204162957.GZ15052@edu.joroinen.fi> References: <20090203202447.GU15052@edu.joroinen.fi> <20090204110350.GW15052@edu.joroinen.fi> <20090204121628.GI18191@salstar.sk> <49898A33.1080703@redhat.com> <20090204123523.GL18191@salstar.sk> <20090204162957.GZ15052@edu.joroinen.fi> Message-ID: <20090205080358.GC15052@edu.joroinen.fi> On Wed, Feb 04, 2009 at 06:29:57PM +0200, Pasi K?rkk?inen wrote: > On Wed, Feb 04, 2009 at 01:35:23PM +0100, Jan ONDREJ (SAL) wrote: > > On Wed, Feb 04, 2009 at 01:29:39PM +0100, Gerd Hoffmann wrote: > > > Jan ONDREJ (SAL) wrote: > > > > [root at note ~]# file /boot/xen-3.3.gz /boot/xen/vmlinux /boot/xen/initrd.img /boot/xen/bzImage > > > > /boot/xen-3.3.gz: gzip compressed data, from Unix, last modified: Tue Feb 3 12:36:39 2009, max compression > > > > /boot/xen/vmlinux: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, stripped > > > > > > "stripped". This probably is the problem. > > > > > > > /boot/xen/initrd.img: gzip compressed data, from Unix, last modified: Wed Feb 4 12:00:01 2009, max compression > > > > /boot/xen/bzImage: Linux kernel x86 boot executable RO-rootFS, swap_dev 0x2, Normal VGA > > > > > > Try this one instead of vmlinux (unstripped vmlinux should work too). > > > > Already tryed both of them. Stripped, unstripped vmlinux, gzip compressed > > vmlinux, bzImage. Always same problem. > > > > I've been using gzipped vmlinux pv_ops dom0 kernel successfully. > > I still haven't tried that new bzImage support .. will try that today or tomorrow. > I can confirm that bzImage pv_ops dom0 kernels boot OK with xen 3.3.1-3. I'm running on x86-32 (PAE) and I was using arch/x86/boot/bzImage from 2.6.29-rc3-tip as a dom0 kernel. -- Pasi From itamar at ispbrasil.com.br Thu Feb 5 11:02:17 2009 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Thu, 5 Feb 2009 09:02:17 -0200 Subject: [Fedora-xen] Re: [fedora-virt] bzImage dom0 kernel support in latest rawhide Xen packages In-Reply-To: <20090205080358.GC15052@edu.joroinen.fi> References: <20090203202447.GU15052@edu.joroinen.fi> <20090204110350.GW15052@edu.joroinen.fi> <20090204121628.GI18191@salstar.sk> <49898A33.1080703@redhat.com> <20090204123523.GL18191@salstar.sk> <20090204162957.GZ15052@edu.joroinen.fi> <20090205080358.GC15052@edu.joroinen.fi> Message-ID: any chance to someone build a rpm with dom0 available for testing ? > I can confirm that bzImage pv_ops dom0 kernels boot OK with xen 3.3.1-3. > > I'm running on x86-32 (PAE) and I was using arch/x86/boot/bzImage from > 2.6.29-rc3-tip as a dom0 kernel. > > -- Pasi > > _______________________________________________ > Fedora-virt mailing list > Fedora-virt at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-virt > -- ------------ Itamar Reis Peixoto e-mail/msn: itamar at ispbrasil.com.br sip: itamar at ispbrasil.com.br skype: itamarjp icq: 81053601 +55 11 4063 5033 +55 34 3221 8599 From m.a.young at durham.ac.uk Thu Feb 5 12:23:27 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Thu, 5 Feb 2009 12:23:27 +0000 (GMT) Subject: [Fedora-xen] Re: [fedora-virt] bzImage dom0 kernel support in latest rawhide Xen packages In-Reply-To: References: <20090203202447.GU15052@edu.joroinen.fi> <20090204110350.GW15052@edu.joroinen.fi> <20090204121628.GI18191@salstar.sk> <49898A33.1080703@redhat.com> <20090204123523.GL18191@salstar.sk> <20090204162957.GZ15052@edu.joroinen.fi> <20090205080358.GC15052@edu.joroinen.fi> Message-ID: On Thu, 5 Feb 2009, Itamar Reis Peixoto wrote: > any chance to someone build a rpm with dom0 available for testing ? I am not convinced that dom0 support is really stable enough to do that yet, because some key aspects are broken such as some hard disk support, and the code is still rather a moving target which doesn't always build. Michael Young From ondrejj at salstar.sk Thu Feb 5 12:37:06 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Thu, 5 Feb 2009 13:37:06 +0100 Subject: [Fedora-xen] Re: [fedora-virt] bzImage dom0 kernel support in latest rawhide Xen packages In-Reply-To: References: <20090203202447.GU15052@edu.joroinen.fi> <20090204110350.GW15052@edu.joroinen.fi> <20090204121628.GI18191@salstar.sk> <49898A33.1080703@redhat.com> <20090204123523.GL18191@salstar.sk> <20090204162957.GZ15052@edu.joroinen.fi> <20090205080358.GC15052@edu.joroinen.fi> Message-ID: <20090205123706.GU18191@salstar.sk> On Thu, Feb 05, 2009 at 12:23:27PM +0000, M A Young wrote: > On Thu, 5 Feb 2009, Itamar Reis Peixoto wrote: > >> any chance to someone build a rpm with dom0 available for testing ? I am trying to create one, but without success yet. I have an 2.6.29-rc3-tip kernel with dom0 support, it now can boot using xen-3.3.gz, but immediatelly after boot my fonts are gone. I don't know what to do without console. My cursor is sometimes moving, just I can't control it (may be console and keyboard are not working). Can somebody help me, what I am doing wrong? My last functional compiled kernel was 1.3.XX and it is some years ago. :) > I am not convinced that dom0 support is really stable enough to do that > yet, because some key aspects are broken such as some hard disk support, > and the code is still rather a moving target which doesn't always build. Right. When trying to compile 2.6.29-rc3+xen, I need to turn off xen*frontentds and xen*backend drivers have to be compiled into kernel, not as modules. After this I have a functional kernel, but after booting with xen-3.3.gz, my screen is blank. SAL From pasik at iki.fi Thu Feb 5 14:34:14 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Thu, 5 Feb 2009 16:34:14 +0200 Subject: [Fedora-xen] Re: [fedora-virt] bzImage dom0 kernel support in latest rawhide Xen packages In-Reply-To: <20090205123706.GU18191@salstar.sk> References: <20090204110350.GW15052@edu.joroinen.fi> <20090204121628.GI18191@salstar.sk> <49898A33.1080703@redhat.com> <20090204123523.GL18191@salstar.sk> <20090204162957.GZ15052@edu.joroinen.fi> <20090205080358.GC15052@edu.joroinen.fi> <20090205123706.GU18191@salstar.sk> Message-ID: <20090205143414.GG15052@edu.joroinen.fi> On Thu, Feb 05, 2009 at 01:37:06PM +0100, Jan ONDREJ (SAL) wrote: > On Thu, Feb 05, 2009 at 12:23:27PM +0000, M A Young wrote: > > On Thu, 5 Feb 2009, Itamar Reis Peixoto wrote: > > > >> any chance to someone build a rpm with dom0 available for testing ? > > I am trying to create one, but without success yet. > > I have an 2.6.29-rc3-tip kernel with dom0 support, it now can boot using > xen-3.3.gz, but immediatelly after boot my fonts are gone. I don't know what > to do without console. My cursor is sometimes moving, just I can't control > it (may be console and keyboard are not working). Can somebody help me, what > I am doing wrong? My last functional compiled kernel was 1.3.XX and it is > some years ago. :) > > > I am not convinced that dom0 support is really stable enough to do that > > yet, because some key aspects are broken such as some hard disk support, > > and the code is still rather a moving target which doesn't always build. > > Right. > > When trying to compile 2.6.29-rc3+xen, I need to turn off xen*frontentds > and xen*backend drivers have to be compiled into kernel, not as modules. > After this I have a functional kernel, but after booting with xen-3.3.gz, my > screen is blank. > I haven't gotten the pv_ops dom0 kernel VGA text console to work at all yet.. I've been using serial console. I guess fixing the console would be the next thing to do after disk problems are fixed:) -- Pasi From m.a.young at durham.ac.uk Fri Feb 6 00:37:42 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Fri, 6 Feb 2009 00:37:42 +0000 (GMT) Subject: [Fedora-xen] Re: [fedora-virt] bzImage dom0 kernel support in latest rawhide Xen packages In-Reply-To: <20090205143414.GG15052@edu.joroinen.fi> References: <20090204110350.GW15052@edu.joroinen.fi> <20090204121628.GI18191@salstar.sk> <49898A33.1080703@redhat.com> <20090204123523.GL18191@salstar.sk> <20090204162957.GZ15052@edu.joroinen.fi> <20090205080358.GC15052@edu.joroinen.fi> <20090205123706.GU18191@salstar.sk> <20090205143414.GG15052@edu.joroinen.fi> Message-ID: On Thu, 5 Feb 2009, Pasi K?rkk?inen wrote: > On Thu, Feb 05, 2009 at 01:37:06PM +0100, Jan ONDREJ (SAL) wrote: >> When trying to compile 2.6.29-rc3+xen, I need to turn off xen*frontentds >> and xen*backend drivers have to be compiled into kernel, not as modules. >> After this I have a functional kernel, but after booting with xen-3.3.gz, my >> screen is blank. >> > > I haven't gotten the pv_ops dom0 kernel VGA text console to work at all > yet.. > > I've been using serial console. I have the VGA console printing boot messages from the kernel with the configuration title xen test root (hd0,5) kernel /xen-3.3.gz module /vmlinuz-2.6.29-rc3-tip ro root=UUID=00000000-0000-0000-0000-000000000000 single pci=nomsi maxcpus=1 module /initrd-2.6.29-rc3-tip.img though it crashes before it gets as far as a prompt. This is x86_64. However I have another machine that goes blank after the XEN output (though I am not sure I have tried it with precisely the same options) which is an i686. The difference might be nothing to do with the boot options though, and could relate to graphics cards or precisely how plymouth is set up. Michael Young From pasik at iki.fi Fri Feb 6 11:42:38 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Fri, 6 Feb 2009 13:42:38 +0200 Subject: [Fedora-xen] Re: [fedora-virt] bzImage dom0 kernel support in latest rawhide Xen packages In-Reply-To: References: <20090204121628.GI18191@salstar.sk> <49898A33.1080703@redhat.com> <20090204123523.GL18191@salstar.sk> <20090204162957.GZ15052@edu.joroinen.fi> <20090205080358.GC15052@edu.joroinen.fi> <20090205123706.GU18191@salstar.sk> <20090205143414.GG15052@edu.joroinen.fi> Message-ID: <20090206114238.GO15052@edu.joroinen.fi> On Fri, Feb 06, 2009 at 12:37:42AM +0000, M A Young wrote: > On Thu, 5 Feb 2009, Pasi K?rkk?inen wrote: > > >On Thu, Feb 05, 2009 at 01:37:06PM +0100, Jan ONDREJ (SAL) wrote: > >>When trying to compile 2.6.29-rc3+xen, I need to turn off xen*frontentds > >>and xen*backend drivers have to be compiled into kernel, not as modules. > >>After this I have a functional kernel, but after booting with xen-3.3.gz, > >>my > >>screen is blank. > >> > > > >I haven't gotten the pv_ops dom0 kernel VGA text console to work at all > >yet.. > > > >I've been using serial console. > > I have the VGA console printing boot messages from the kernel with the > configuration > > title xen test > root (hd0,5) > kernel /xen-3.3.gz > module /vmlinuz-2.6.29-rc3-tip ro > root=UUID=00000000-0000-0000-0000-000000000000 single pci=nomsi > maxcpus=1 > module /initrd-2.6.29-rc3-tip.img > > though it crashes before it gets as far as a prompt. This is x86_64. > However I have another machine that goes blank after the XEN output > (though I am not sure I have tried it with precisely the same options) > which is an i686. The difference might be nothing to do with the boot > options though, and could relate to graphics cards or precisely how > plymouth is set up. > Yeah, that's my problem too.. VGA text console goes blank when dom0 kernel is booted.. Xen hypervisor messages are displayed OK (before the dom0 kernel). I'm running also 32bit Xen and dom0. -- Pasi From m.a.young at durham.ac.uk Mon Feb 9 00:59:13 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Mon, 9 Feb 2009 00:59:13 +0000 (GMT) Subject: [Fedora-xen] Dom0 Xen kernel RPM Message-ID: I have built a kernel based on kernel-2.6.29-0.41.rc2.fc11.src.rpm and Changeset 2342 from http://xenbits.xen.org/paravirt_ops/patches.hg/ and uploaded selected files which are at http://compsoc.dur.ac.uk/~may/xen/kernel-2.6.29-0.41.rc2.pvops2342.fc10.src.rpm http://compsoc.dur.ac.uk/~may/xen/kernel-2.6.29-0.41.rc2.pvops2342.fc10.x86_64.rpm http://compsoc.dur.ac.uk/~may/xen/kernel-firmware-2.6.29-0.41.rc2.pvops2342.fc10.noarch.rpm I got it to boot as Dom0 with a Rawhide based live CD image on a USB stick with several kernel tracebacks. I have not managed to get it to boot on my main Fedora 10 system either dom0 or as an ordinary kernel (but nor does the the unaltered kernel - presumably there is some incompatibility between Fedora 10 systems and Fedora 11 kernels that I haven't spotted yet), so you use it very much at your own risk. Michael Young From kraxel at redhat.com Wed Feb 4 16:23:02 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Wed, 04 Feb 2009 17:23:02 +0100 Subject: [Fedora-xen] Re: [fedora-virt] bzImage dom0 kernel support in latest rawhide Xen packages In-Reply-To: <20090204123523.GL18191@salstar.sk> References: <20090203202447.GU15052@edu.joroinen.fi> <20090204110350.GW15052@edu.joroinen.fi> <20090204121628.GI18191@salstar.sk> <49898A33.1080703@redhat.com> <20090204123523.GL18191@salstar.sk> Message-ID: <4989C0E6.1060103@redhat.com> Jan ONDREJ (SAL) wrote: > On Wed, Feb 04, 2009 at 01:29:39PM +0100, Gerd Hoffmann wrote: >> Jan ONDREJ (SAL) wrote: >>> [root at note ~]# file /boot/xen-3.3.gz /boot/xen/vmlinux /boot/xen/initrd.img /boot/xen/bzImage >>> /boot/xen-3.3.gz: gzip compressed data, from Unix, last modified: Tue Feb 3 12:36:39 2009, max compression >>> /boot/xen/vmlinux: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, stripped >> "stripped". This probably is the problem. >> >>> /boot/xen/initrd.img: gzip compressed data, from Unix, last modified: Wed Feb 4 12:00:01 2009, max compression >>> /boot/xen/bzImage: Linux kernel x86 boot executable RO-rootFS, swap_dev 0x2, Normal VGA >> Try this one instead of vmlinux (unstripped vmlinux should work too). > > Already tryed both of them. Stripped, unstripped vmlinux, gzip compressed > vmlinux, bzImage. Always same problem. Hmm. Works for me. x86_64 box boots up fine (until the not-yet fixed storage issues kick in, see xen-devel). Old i386 laptop has an early kernel crash (probably due to lack of an io-apic, the pv_ops kernel reportly can't deal with that very well). The bootup passes the point where the dom0 domain builder parses the guest kernel though. 32bit config attached. HTH, Gerd -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: dot.config URL: From kraxel at redhat.com Mon Feb 9 14:24:59 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Mon, 09 Feb 2009 15:24:59 +0100 Subject: [Fedora-xen] Re: [fedora-virt] bzImage dom0 kernel support in latest rawhide Xen packages In-Reply-To: <20090206114238.GO15052@edu.joroinen.fi> References: <20090204121628.GI18191@salstar.sk> <49898A33.1080703@redhat.com> <20090204123523.GL18191@salstar.sk> <20090204162957.GZ15052@edu.joroinen.fi> <20090205080358.GC15052@edu.joroinen.fi> <20090205123706.GU18191@salstar.sk> <20090205143414.GG15052@edu.joroinen.fi> <20090206114238.GO15052@edu.joroinen.fi> Message-ID: <49903CBB.30403@redhat.com> Pasi K?rkk?inen wrote: > Yeah, that's my problem too.. VGA text console goes blank when dom0 kernel is > booted.. Xen hypervisor messages are displayed OK (before the dom0 kernel). > > I'm running also 32bit Xen and dom0. Noticed that the laptop shows dom0 kernel messages when booting xen with "vga=gfx-1024x768x16". Text mode stays blank for me too. cheers, Gerd From m.a.young at durham.ac.uk Wed Feb 11 17:24:56 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Wed, 11 Feb 2009 17:24:56 +0000 (GMT) Subject: [Fedora-xen] Re: Dom0 Xen kernel RPM In-Reply-To: References: Message-ID: On Mon, 9 Feb 2009, M A Young wrote: > I have built a kernel based on kernel-2.6.29-0.41.rc2.fc11.src.rpm and > Changeset 2342 from http://xenbits.xen.org/paravirt_ops/patches.hg/ > and uploaded selected files which are at > http://compsoc.dur.ac.uk/~may/xen/kernel-2.6.29-0.41.rc2.pvops2342.fc10.src.rpm > http://compsoc.dur.ac.uk/~may/xen/kernel-2.6.29-0.41.rc2.pvops2342.fc10.x86_64.rpm > http://compsoc.dur.ac.uk/~may/xen/kernel-firmware-2.6.29-0.41.rc2.pvops2342.fc10.noarch.rpm > > I got it to boot as Dom0 with a Rawhide based live CD image on a USB stick > with several kernel tracebacks. I have not managed to get it to boot on my > main Fedora 10 system either dom0 or as an ordinary kernel (but nor does the > the unaltered kernel - presumably there is some incompatibility between > Fedora 10 systems and Fedora 11 kernels that I haven't spotted yet), so you > use it very much at your own risk. It turns out (probably due to an overlooked "hg update") that those were actually based on changeset 2336. I have replaced them with the files below which really are based on changeset 2342, which contains a fix to a significant bug and reduces the kernel tracebacks I see from 3 (ignoring duplication) to 2. It actually boots (single user) for me as dom0 on my Fedora 10 system, though X crashed when I tried to go multiuser, and there seem to be a long delay due to some ata problems during boot. Michael Young http://compsoc.dur.ac.uk/~may/xen/kernel-2.6.29-0.41.rc2.pvops2342.1.fc10.src.rpm http://compsoc.dur.ac.uk/~may/xen/kernel-2.6.29-0.41.rc2.pvops2342.1.fc10.x86_64.rpm http://compsoc.dur.ac.uk/~may/xen/kernel-firmware-2.6.29-0.41.rc2.pvops2342.1.fc10.noarch.rpm From markmc at redhat.com Wed Feb 11 20:46:57 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Wed, 11 Feb 2009 20:46:57 +0000 Subject: [Fedora-xen] Re: Dom0 Xen kernel RPM In-Reply-To: References: Message-ID: <1234385217.14052.250.camel@blaa> On Wed, 2009-02-11 at 17:24 +0000, M A Young wrote: > It turns out (probably due to an overlooked "hg update") that those were > actually based on changeset 2336. I have replaced them with the files > below which really are based on changeset 2342, which contains a fix to a > significant bug and reduces the kernel tracebacks I see from 3 (ignoring > duplication) to 2. It actually boots (single user) for me as dom0 on my > Fedora 10 system, though X crashed when I tried to go multiuser, and there > seem to be a long delay due to some ata problems during boot. That sounds like excellent progress, well done! I wonder are you planning on doing these builds regularly? Would it help if you could do it as a branch in Fedora's pkgs CVS, build in koji and host a yum repo on fedorapeople.org? Cheers, Mark. From siddharth.wagh at gmail.com Wed Feb 11 21:32:13 2009 From: siddharth.wagh at gmail.com (Siddharth Wagh) Date: Wed, 11 Feb 2009 16:32:13 -0500 Subject: [Fedora-xen] 3 failed approaches to create guest domains Message-ID: Hello all, I am a Masters student working on my thesis and have to go use Xen for live migration purposes. I have a Xen installation on Fedora 8, and been trying for past 3 months to create guest domains and get them running for further migration work. I took 3 different approaches, but got stuck with each of those. I would be very grateful if you could point out as to where I am going wrong... * 1. Basic command: xm create -c vm01-config.sxp vmid=1* The config file is kept in /etc/xen folder. ERROR: VFS: Cannot open root device "hd0" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) WHAT I PUT IN: root = '/dev/hd0' or '/dev/hda' or '/dev/sda2' None worked. I am not sure what the option should be. * 2. Using the command: virt-install -f /etc/xen/xen1 -r 256* WHAT IT DOES: Asks for config parameters and creates virtual machine, but I am not sure how to proceed with completion process. In the install location, I put in a OS image at a mirror site: http://ringtail.its.monash.edu.au/pub/fedora/linux/releases/8/Fedora/i386/os/ ERROR: Unable to find image at given location This is the only approach which creates a VM, but the machine is not completely running (not functional or doesnt consume any memory). Am I supposed to have the guest image on my machine? *3. Using "virt-manager" in GUI* ERROR: Asks for "Connect to host network" *but "shared physical devices" list is empty*. It is supposed to list eth0, peth0 etc. Something to do with creating a bridge. I tried the approach of NAT, but for that I have to use approach 1 to create a machine, which gets stuck on "root" error. Libvirtd is not running. It gave the message: libvir: Remote error : Connection refused libvir: warning : Failed to find the network: Is the daemon running ? libvir: Remote error : Connection refused xend is running, I checked status. If anyone could devote a little of their time to help me out, as I am not comfortable with kernel administration/OS admin, I would be really thankful. Thanks & Regards, Siddharth Wagh ----------------------------------------------------------------------------------------- To ensure perfect aim, shoot first and call whatever you hit the target... ----------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From m.a.young at durham.ac.uk Wed Feb 11 22:09:48 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Wed, 11 Feb 2009 22:09:48 +0000 (GMT) Subject: [Fedora-xen] Re: Dom0 Xen kernel RPM In-Reply-To: <1234385217.14052.250.camel@blaa> References: <1234385217.14052.250.camel@blaa> Message-ID: On Wed, 11 Feb 2009, Mark McLoughlin wrote: > That sounds like excellent progress, well done! I am just tracking the pvops upstream, with a small amount of editing to get it to fit together with a Fedora kernel. > I wonder are you planning on doing these builds regularly? Would it help > if you could do it as a branch in Fedora's pkgs CVS, build in koji and > host a yum repo on fedorapeople.org? At the moment I am tracking it mainly for my own interest (and I don't know how long that interest will last), but I could certainly try to get it up onto a CVS branch (though I don't currently have a fedoraproject login). Howevere, it sounds from this post http://lists.xensource.com/archives/html/xen-devel/2009-02/msg00333.html that a fair proportion of the dom0 patches may go into 2.6.29. Michael Young From markmc at redhat.com Thu Feb 12 07:28:02 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Thu, 12 Feb 2009 07:28:02 +0000 Subject: [Fedora-xen] Re: Dom0 Xen kernel RPM In-Reply-To: References: <1234385217.14052.250.camel@blaa> Message-ID: <1234423682.3707.10.camel@blaa> On Wed, 2009-02-11 at 22:09 +0000, M A Young wrote: > On Wed, 11 Feb 2009, Mark McLoughlin wrote: > > I wonder are you planning on doing these builds regularly? Would it help > > if you could do it as a branch in Fedora's pkgs CVS, build in koji and > > host a yum repo on fedorapeople.org? > > At the moment I am tracking it mainly for my own interest (and I don't > know how long that interest will last), but I could certainly try to get > it up onto a CVS branch (though I don't currently have a fedoraproject > login). Cool, well creating a Fedora account is easy: http://fedoraproject.org/wiki/PackageMaintainers/Join#Get_a_Fedora_Account Once you've done that and requested to be added to the packager group, let me know and I can sponsor you. After that we just need to get you commit ACLs and you're good to go. > Howevere, it sounds from this post > http://lists.xensource.com/archives/html/xen-devel/2009-02/msg00333.html > that a fair proportion of the dom0 patches may go into 2.6.29. "planning to get at least basic dom0 support into the next merge window" That means 2.6.30 - the merge window for 2.6.29 is closed. Cheers, Mark. From ondrejj at salstar.sk Thu Feb 12 08:28:06 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Thu, 12 Feb 2009 09:28:06 +0100 Subject: [Fedora-xen] Re: Dom0 Xen kernel RPM In-Reply-To: <1234423682.3707.10.camel@blaa> References: <1234385217.14052.250.camel@blaa> <1234423682.3707.10.camel@blaa> Message-ID: <20090212082806.GH26100@salstar.sk> On Thu, Feb 12, 2009 at 07:28:02AM +0000, Mark McLoughlin wrote: > On Wed, 2009-02-11 at 22:09 +0000, M A Young wrote: > > On Wed, 11 Feb 2009, Mark McLoughlin wrote: > > > > I wonder are you planning on doing these builds regularly? Would it help > > > if you could do it as a branch in Fedora's pkgs CVS, build in koji and > > > host a yum repo on fedorapeople.org? > > > > At the moment I am tracking it mainly for my own interest (and I don't > > know how long that interest will last), but I could certainly try to get > > it up onto a CVS branch (though I don't currently have a fedoraproject > > login). > > Cool, well creating a Fedora account is easy: > > http://fedoraproject.org/wiki/PackageMaintainers/Join#Get_a_Fedora_Account > > Once you've done that and requested to be added to the packager group, > let me know and I can sponsor you. > > After that we just need to get you commit ACLs and you're good to go. I can help him to do this (I am an fedora packager), but there is no functional 2.6.29+ kernel for dom0. Also M.A.Young's rpm can't be compiled on my i686 machine (aha1542 driver should me disabled, before it will be fixed). I am planning to support Fedora 10 kernel in my repository, but I can't make progress with current kernels (tryed to recompile CentOS kernel, kernel-2.6.27+xen (by suse) and 2.6.29 from mercurial without any success. > > Howevere, it sounds from this post > > http://lists.xensource.com/archives/html/xen-devel/2009-02/msg00333.html > > that a fair proportion of the dom0 patches may go into 2.6.29. > > "planning to get at least basic dom0 support into the next merge > window" > > That means 2.6.30 - the merge window for 2.6.29 is closed. Right. There is no new patches for dom0 in 2.6.29, because Jeremy is moving code from mercurial to git, but it in the middle of this work. I am trying to daily update from mercurial and seeing also git status, but no change in mercurial aprox. 5 days ago ang git does not contain dom0. SAL From kraxel at redhat.com Thu Feb 12 10:50:12 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Thu, 12 Feb 2009 11:50:12 +0100 Subject: [Fedora-xen] Re: Dom0 Xen kernel RPM In-Reply-To: <20090212082806.GH26100@salstar.sk> References: <1234385217.14052.250.camel@blaa> <1234423682.3707.10.camel@blaa> <20090212082806.GH26100@salstar.sk> Message-ID: <4993FEE4.4060504@redhat.com> Jan ONDREJ (SAL) wrote: > I can help him to do this (I am an fedora packager), but there is no > functional 2.6.29+ kernel for dom0. Thats why I didn't even try to package it up. At this point in time this all is still very experimental and IMHO too far away from being usable. I'm testing the kernels on two machines here. The i386 laptop doesn't even boot. The x86_64 box suffers from the mysterious ahci issue (sata suddenly stops working at some point). Also the network backend doesn't compile right now, so your guests can't have network connectivity. Also blktap isn't there yet. > There is no new patches for dom0 in 2.6.29, because Jeremy is moving code > from mercurial to git, but it in the middle of this work. He sends out pull requests already, queuing up xen stuff (and x86 cleanups) in ingos tip tree. If it goes well .30 boots as dom0 kernel. I don't expect much of the backend infrastructure makes it into .30 though (i.e. you need patches to actually run guests). At this point the changes needed might be non-invasive enougth that it might be reasonable to carry them as patches in the fedora kernel. > I am trying to daily update from mercurial and seeing also git status, but > no change in mercurial aprox. 5 days ago ang git does not contain dom0. Looks like the mercurial repo is dead. cheers, Gerd From m.a.young at durham.ac.uk Thu Feb 12 12:23:09 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Thu, 12 Feb 2009 12:23:09 +0000 (GMT) Subject: [Fedora-xen] Re: Dom0 Xen kernel RPM In-Reply-To: <4993FEE4.4060504@redhat.com> References: <1234385217.14052.250.camel@blaa> <1234423682.3707.10.camel@blaa> <20090212082806.GH26100@salstar.sk> <4993FEE4.4060504@redhat.com> Message-ID: On Thu, 12 Feb 2009, Gerd Hoffmann wrote: > Also the network backend doesn't compile right now, so your guests can't > have network connectivity. I think it does if you pick the right combination of options. I am not at my development box right now, but from what I remember there are some dependencies missing from the configuration options meaning that you can pick combinations of module/non-module configurations that don't build. (I guess I should probably identify these more precisely and report them upstream). Michael Young From mmcgrath at redhat.com Thu Feb 12 16:03:50 2009 From: mmcgrath at redhat.com (Mike McGrath) Date: Thu, 12 Feb 2009 10:03:50 -0600 (CST) Subject: [Fedora-xen] Fedora 10 on RHEL5.3 x86_64 Message-ID: Anyone having issues doing F10 on RHEL5.3? I'm seeing this (with debug enabled: hu, 12 Feb 2009 16:00:18 DEBUG No guest running yet virDomainLookupByName() failed Domain not found: xenUnifiedDomainLookupByName Thu, 12 Feb 2009 16:00:18 DEBUG No guest running yet virDomainLookupByName() failed Domain not found: xenUnifiedDomainLookupByName Thu, 12 Feb 2009 16:00:18 DEBUG No guest running yet virDomainLookupByName() failed Domain not found: xenUnifiedDomainLookupByName Thu, 12 Feb 2009 16:00:18 DEBUG No guest running yet virDomainLookupByName() failed Domain not found: xenUnifiedDomainLookupByName Thu, 12 Feb 2009 16:00:19 DEBUG No guest running yet virDomainLookupByName() failed Domain not found: xenUnifiedDomainLookupByName Thu, 12 Feb 2009 16:00:19 DEBUG No guest running yet virDomainLookupByName() failed Domain not found: xenUnifiedDomainLookupByName Thu, 12 Feb 2009 16:00:19 DEBUG Removing /var/lib/xen/virtinst-vmlinuz.V9IWB3 Thu, 12 Feb 2009 16:00:19 DEBUG Removing /var/lib/xen/virtinst-initrd.img.tUWkKJ ERROR: It appears that your installation has crashed. You should be able to find more information in the logs Except the info in the logs isn't very revealing. I get this when doing a virt-install -p. any ideas? -Mike From jswanson at valuecommerce.co.jp Fri Feb 13 01:00:47 2009 From: jswanson at valuecommerce.co.jp (Jon Swanson) Date: Fri, 13 Feb 2009 10:00:47 +0900 Subject: [Fedora-xen] RE: Fedora-xen Digest, Vol 39, Issue 8 References: <20090212170019.83FE18E009E@hormel.redhat.com> Message-ID: Hey Mike, If you are trying to boot an x86_64 f10 domU, you might want to check to make sure that the host supports the NX cpu flag. This might not have anything to do with your issue, but worth checking. https://bugzilla.redhat.com/show_bug.cgi?id=480880 http://forums.fedoraforum.org/showthread.php?t=210763 -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of fedora-xen-request at redhat.com Sent: Friday, February 13, 2009 2:00 AM To: fedora-xen at redhat.com Subject: Fedora-xen Digest, Vol 39, Issue 8 Send Fedora-xen mailing list submissions to fedora-xen at redhat.com To subscribe or unsubscribe via the World Wide Web, visit https://www.redhat.com/mailman/listinfo/fedora-xen or, via email, send a message with subject or body 'help' to fedora-xen-request at redhat.com You can reach the person managing the list at fedora-xen-owner at redhat.com When replying, please edit your Subject line so it is more specific than "Re: Contents of Fedora-xen digest..." Today's Topics: 1. Fedora 10 on RHEL5.3 x86_64 (Mike McGrath) ---------------------------------------------------------------------- Message: 1 Date: Thu, 12 Feb 2009 10:03:50 -0600 (CST) From: Mike McGrath Subject: [Fedora-xen] Fedora 10 on RHEL5.3 x86_64 To: fedora-xen at redhat.com Message-ID: Content-Type: TEXT/PLAIN; charset=US-ASCII Anyone having issues doing F10 on RHEL5.3? I'm seeing this (with debug enabled: hu, 12 Feb 2009 16:00:18 DEBUG No guest running yet virDomainLookupByName() failed Domain not found: xenUnifiedDomainLookupByName Thu, 12 Feb 2009 16:00:18 DEBUG No guest running yet virDomainLookupByName() failed Domain not found: xenUnifiedDomainLookupByName Thu, 12 Feb 2009 16:00:18 DEBUG No guest running yet virDomainLookupByName() failed Domain not found: xenUnifiedDomainLookupByName Thu, 12 Feb 2009 16:00:18 DEBUG No guest running yet virDomainLookupByName() failed Domain not found: xenUnifiedDomainLookupByName Thu, 12 Feb 2009 16:00:19 DEBUG No guest running yet virDomainLookupByName() failed Domain not found: xenUnifiedDomainLookupByName Thu, 12 Feb 2009 16:00:19 DEBUG No guest running yet virDomainLookupByName() failed Domain not found: xenUnifiedDomainLookupByName Thu, 12 Feb 2009 16:00:19 DEBUG Removing /var/lib/xen/virtinst-vmlinuz.V9IWB3 Thu, 12 Feb 2009 16:00:19 DEBUG Removing /var/lib/xen/virtinst-initrd.img.tUWkKJ ERROR: It appears that your installation has crashed. You should be able to find more information in the logs Except the info in the logs isn't very revealing. I get this when doing a virt-install -p. any ideas? -Mike ------------------------------ -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen End of Fedora-xen Digest, Vol 39, Issue 8 ***************************************** From orenault at redhat.com Thu Feb 12 19:48:54 2009 From: orenault at redhat.com (Olivier Renault) Date: Thu, 12 Feb 2009 20:48:54 +0100 Subject: [Fedora-xen] 3 failed approaches to create guest domains In-Reply-To: References: Message-ID: <49947D26.6030602@redhat.com> Siddharth Wagh wrote: > Hello all, > > I am a Masters student working on my thesis and have to go use Xen for > live migration purposes. I have a Xen installation on Fedora 8, and been > trying for past 3 months to create guest domains and get them running > for further migration work. I took 3 different approaches, but got stuck > with each of those. I would be very grateful if you could point out as > to where I am going wrong... > * > 1. Basic command: > xm create -c vm01-config.sxp vmid=1* > > The config file is kept in /etc/xen folder. > > ERROR: > VFS: Cannot open root device "hd0" or unknown-block(0,0) > Please append a correct "root=" boot option > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,0) > > WHAT I PUT IN: > root = '/dev/hd0' or '/dev/hda' or '/dev/sda2' > > None worked. I am not sure what the option should be. > > * > 2. Using the command: > virt-install -f /etc/xen/xen1 -r 256* > > WHAT IT DOES: > Asks for config parameters and creates virtual machine, but I am not > sure how to proceed with completion process. In the install location, I > put in a OS image at a mirror site: > > http://ringtail.its.monash.edu.au/pub/fedora/linux/releases/8/Fedora/i386/os/ > > ERROR: > Unable to find image at given location > > This is the only approach which creates a VM, but the machine is not > completely running (not functional or doesnt consume any memory). Am I > supposed to have the guest image on my machine? > > > *3. Using "virt-manager" in GUI* > > ERROR: Asks for "Connect to host network" *but "shared physical > devices" list is empty*. It is supposed to list eth0, peth0 etc. > Something to do with creating a bridge. I tried the approach of NAT, but > for that I have to use approach 1 to create a machine, which gets stuck > on "root" error. > > > Libvirtd is not running. It gave the message: > > libvir: Remote error : Connection refused > libvir: warning : Failed to find the network: Is the daemon running ? > libvir: Remote error : Connection refused > > xend is running, I checked status. > Commenting on method 2: If you have got a iso of F8 DVD somewhere, mount it loopback on /var/www/html/pub & start your web server # mount -o loop F8.iso /var/www/html/pub # service httpd start Then you should be able to do the installation # virt-install \ --paravirt \ --name demo \ --ram 500 \ --file /var/lib/xen/images/demo.img \ --file-size 6 \ --nographics \ --location http://ip of your web server/pub Good luck. Olivier From orenault at redhat.com Thu Feb 12 20:21:31 2009 From: orenault at redhat.com (Olivier Renault) Date: Thu, 12 Feb 2009 21:21:31 +0100 Subject: [Fedora-xen] Fedora 10 on RHEL5.3 x86_64 In-Reply-To: References: Message-ID: <499484CB.7090908@redhat.com> Mike McGrath wrote: > Anyone having issues doing F10 on RHEL5.3? I'm seeing this (with debug > enabled: > > hu, 12 Feb 2009 16:00:18 DEBUG No guest running yet > virDomainLookupByName() failed Domain not found: > xenUnifiedDomainLookupByName > Thu, 12 Feb 2009 16:00:18 DEBUG No guest running yet > virDomainLookupByName() failed Domain not found: > xenUnifiedDomainLookupByName > Thu, 12 Feb 2009 16:00:18 DEBUG No guest running yet > virDomainLookupByName() failed Domain not found: > xenUnifiedDomainLookupByName > Thu, 12 Feb 2009 16:00:18 DEBUG No guest running yet > virDomainLookupByName() failed Domain not found: > xenUnifiedDomainLookupByName > Thu, 12 Feb 2009 16:00:19 DEBUG No guest running yet > virDomainLookupByName() failed Domain not found: > xenUnifiedDomainLookupByName > Thu, 12 Feb 2009 16:00:19 DEBUG No guest running yet > virDomainLookupByName() failed Domain not found: > xenUnifiedDomainLookupByName > Thu, 12 Feb 2009 16:00:19 DEBUG Removing > /var/lib/xen/virtinst-vmlinuz.V9IWB3 > Thu, 12 Feb 2009 16:00:19 DEBUG Removing > /var/lib/xen/virtinst-initrd.img.tUWkKJ > ERROR: It appears that your installation has crashed. You should be able > to find more information in the logs > > > Except the info in the logs isn't very revealing. I get this when doing a > virt-install -p. > > any ideas? > There is no xen kernel within F10 so you will need to install it as a FV VM. Olivier From markmc at redhat.com Fri Feb 13 09:53:40 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Fri, 13 Feb 2009 09:53:40 +0000 Subject: [Fedora-xen] Fedora 10 on RHEL5.3 x86_64 In-Reply-To: <499484CB.7090908@redhat.com> References: <499484CB.7090908@redhat.com> Message-ID: <1234518820.3644.46.camel@blaa> On Thu, 2009-02-12 at 21:21 +0100, Olivier Renault wrote: > There is no xen kernel within F10 so you will need to install it as a > FV VM. Yes, there is - the bare-metal kernel has pv_ops Xen support. You may have been bitten by this bug, though: https://bugzilla.redhat.com/470905 anaconda installs the wrong kernel for i686 xen guests. Cheers, Mark. From mmcgrath at redhat.com Fri Feb 13 19:33:45 2009 From: mmcgrath at redhat.com (Mike McGrath) Date: Fri, 13 Feb 2009 13:33:45 -0600 (CST) Subject: [Fedora-xen] Fedora 10 on RHEL5.3 x86_64 In-Reply-To: <1234518820.3644.46.camel@blaa> References: <499484CB.7090908@redhat.com> <1234518820.3644.46.camel@blaa> Message-ID: On Fri, 13 Feb 2009, Mark McLoughlin wrote: > On Thu, 2009-02-12 at 21:21 +0100, Olivier Renault wrote: > > > There is no xen kernel within F10 so you will need to install it as a > > FV VM. > > Yes, there is - the bare-metal kernel has pv_ops Xen support. You may > have been bitten by this bug, though: > > https://bugzilla.redhat.com/470905 > anaconda installs the wrong kernel for i686 xen guests. > Its not even getting to stage 2 during install I'm afraid. -Mike From m.a.young at durham.ac.uk Sat Feb 14 18:08:01 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Sat, 14 Feb 2009 18:08:01 +0000 (GMT) Subject: [Fedora-xen] Re: Dom0 Xen kernel RPM In-Reply-To: References: Message-ID: I tweaked a couple of configuration settings in my previous kernel to get an i686 kernel to build (links below). I tried it and found two main problems; * the ATA driver is serious enough in this case to stop disk access * when I booted off a USB image logging to a serial console, it booted eventually, and from the way the cursor responded to the keyboard, I think there was a login session on the monitor, but everything except the cursor was blank (as if there was black text on a black screen), which might point to an issue with the frame buffer console drivers. I am also told that xend doesn't start for my kernels. This may be a real problem, or it may be necessary to load the right modules before it will start. Michael Young http://compsoc.dur.ac.uk/~may/xen/kernel-2.6.29-0.41.rc2.pvops2342.2.fc10.src.rpm http://compsoc.dur.ac.uk/~may/xen/kernel-PAE-2.6.29-0.41.rc2.pvops2342.2.fc10.i686.rpm http://compsoc.dur.ac.uk/~may/xen/kernel-firmware-2.6.29-0.41.rc2.pvops2342.2.fc10.noarch.rpm From m.a.young at durham.ac.uk Tue Feb 24 19:01:20 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Tue, 24 Feb 2009 19:01:20 +0000 (GMT) Subject: [Fedora-xen] Dom0 kernels Message-ID: I have built a new set of kernel packages based on fedora rawhide kernels and the xen/dom0/hackery branch of Jeremy's git repository ( http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=summary ). This batch (kernel-2.6.29-0.114.2.6.rc6.fc11) is available via the koji build system at http://koji.fedoraproject.org/koji/taskinfo?taskID=1149500 These are really for development and debugging purposes only, as I am still having problems getting them to boot, but others have reported more success at getting kernels based on this git repository working, so you might be lucky. Note to install these packages on Fedora 10 you will need to have rpm-4.6.0-1.fc10 installed (currently in updates-testing but it should be available in updates soon) because of the change to SHA-256 file digest hashing in recent Fedora 11 builds. Michael Young From kraxel at redhat.com Tue Feb 24 21:03:30 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Tue, 24 Feb 2009 22:03:30 +0100 Subject: [Fedora-xen] Re: [fedora-virt] Dom0 kernels In-Reply-To: References: Message-ID: <49A460A2.1060401@redhat.com> M A Young wrote: > I have built a new set of kernel packages based on fedora rawhide > kernels and the xen/dom0/hackery branch of Jeremy's git repository ( > http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=summary ). > This batch (kernel-2.6.29-0.114.2.6.rc6.fc11) is available via the > koji build system at > http://koji.fedoraproject.org/koji/taskinfo?taskID=1149500 > > These are really for development and debugging purposes only, as I am > still having problems getting them to boot, but others have reported > more success at getting kernels based on this git repository > working, so you might be lucky Try "pci=nomsi", msi support for xen isn't there yet. Last week a major bug in IO-APIC setup has been fixed and the kernels run quite stable on modern hardware now. My old, apic-less i386 laptop still doesn't boot though. cheers, Gerd From m.a.young at durham.ac.uk Tue Feb 24 21:46:48 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Tue, 24 Feb 2009 21:46:48 +0000 (GMT) Subject: [Fedora-xen] Re: [fedora-virt] Dom0 kernels In-Reply-To: <49A460A2.1060401@redhat.com> References: <49A460A2.1060401@redhat.com> Message-ID: On Tue, 24 Feb 2009, Gerd Hoffmann wrote: > Try "pci=nomsi", msi support for xen isn't there yet. Last week a major > bug in IO-APIC setup has been fixed and the kernels run quite stable on > modern hardware now. My old, apic-less i386 laptop still doesn't boot > though. That particular kernel has CONFIG_PCI_MSI turned off at build, and I think the most recent git updates disable it within the kernel. My problem at the moment is that it doesn't seem to see the disks, so it never gets past the initrd. I also sometimes get IRQ related tracebacks. Michael Young From m.a.young at durham.ac.uk Thu Feb 26 00:41:19 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Thu, 26 Feb 2009 00:41:19 +0000 (GMT) Subject: [Fedora-xen] Re: Dom0 kernels In-Reply-To: References: Message-ID: On Tue, 24 Feb 2009, M A Young wrote: > I have built a new set of kernel packages based on fedora rawhide kernels and > the xen/dom0/hackery branch of Jeremy's git repository > ( http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=summary ). > This batch (kernel-2.6.29-0.114.2.6.rc6.fc11) is available via the koji build > system at > http://koji.fedoraproject.org/koji/taskinfo?taskID=1149500 And I have now done an update (kernel-2.6.29-0.114.2.8.rc6.fc11) which is available via http://koji.fedoraproject.org/koji/taskinfo?taskID=1178436 > These are really for development and debugging purposes only, as I am still > having problems getting them to boot, but others have reported more success > at getting kernels based on this git repository working, so you might be > lucky. This one does allow one of my machines to boot in single user mode (which is all I have really tested so far), though I am sure there are still plenty of other bugs to find. > Note to install these packages on Fedora 10 you will need to have > rpm-4.6.0-1.fc10 installed (currently in updates-testing but it should be > available in updates soon) because of the change to SHA-256 file digest > hashing in recent Fedora 11 builds. Michael Young From pasik at iki.fi Thu Feb 26 19:12:35 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Thu, 26 Feb 2009 21:12:35 +0200 Subject: [Fedora-xen] Adding qemu disable pci devices patch to Fedora Xen Message-ID: <20090226191235.GI15052@edu.joroinen.fi> Hello. Would it be possible to add Qemu "disable pci devices" patch to Fedora Xen packages? It allows HVM domains (or more specifically PV drivers running in HVM domains) to hide qemu emulated disk/network devices in a sane way to prevent possible corruption and other problems when both the PV devices and Qemu emulated devices are present at the same time.. It's mostly needed for Xen gplpv drivers by James Harper. The same code/feature is also being used by Citrix/Xensource commercial Windows PV drivers. The patch has been in xen-unstable (3.4) for a while already without problems. Patch against Xen 3.3.1 (by James Harper): http://www.meadowcourt.org/downloads/qemu_disable_patches.zip Discussion about it on xen-devel: http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00705.html This would be a needed feature soon when HVM domains start working ok with pv_ops dom0 :) -- Pasi From berrange at redhat.com Thu Feb 26 20:27:14 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 26 Feb 2009 20:27:14 +0000 Subject: [Fedora-xen] Adding qemu disable pci devices patch to Fedora Xen In-Reply-To: <20090226191235.GI15052@edu.joroinen.fi> References: <20090226191235.GI15052@edu.joroinen.fi> Message-ID: <20090226202714.GA8351@redhat.com> On Thu, Feb 26, 2009 at 09:12:35PM +0200, Pasi K?rkk?inen wrote: > Hello. > > Would it be possible to add Qemu "disable pci devices" patch to Fedora Xen > packages? It allows HVM domains (or more specifically PV drivers running > in HVM domains) to hide qemu emulated disk/network devices in a sane way to > prevent possible corruption and other problems when both the PV devices and Qemu > emulated devices are present at the same time.. > > It's mostly needed for Xen gplpv drivers by James Harper. The same > code/feature is also being used by Citrix/Xensource commercial Windows PV > drivers. > > The patch has been in xen-unstable (3.4) for a while already without > problems. Since its merged in xen-unstable & feedback seems positive, I've no objections to it being added to the xen RPM in F11. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From mateenaslam at hotmail.com Sat Feb 28 14:23:01 2009 From: mateenaslam at hotmail.com (MOHAMMAD MATEEN ASLAM) Date: Sat, 28 Feb 2009 14:23:01 +0000 Subject: [Fedora-xen] Xen to KVM Migration - How to resize LVM Partisions using KVM Message-ID: Hi, I am migrating from Xen to KVM. I have created a VM which is based on LVM (/dev/VolGroupV00/vm). I have installed FC-10 on VM with swap, / and /var partisions. Now i want to resize my / and /var partisions. I have resized LVM (/dev/VolGroupV00/vm), how to resize inner partisions (/, /var) of LVM ? Can anyone guide me how KVM deals with LVM and how to manage resizing in a painless way. Regards Mohammad Mateen _________________________________________________________________ Windows Live? Contacts: Organize your contact list. http://windowslive.com/connect/post/marcusatmicrosoft.spaces.live.com-Blog-cns!503D1D86EBB2B53C!2285.entry?ocid=TXT_TAGLM_WL_UGC_Contacts_032009 -------------- next part -------------- An HTML attachment was scrubbed... URL: