From m.a.young at durham.ac.uk Sun May 3 14:15:31 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Sun, 3 May 2009 15:15:31 +0100 (BST) Subject: [Fedora-xen] Dom0 kernels In-Reply-To: References: <20090328163545.GM31725@salstar.sk> <20090414143618.GH351@redhat.com> Message-ID: Another kernel is available at http://koji.fedoraproject.org/koji/taskinfo?taskID=1333417 and at the repository http://fedorapeople.org/~myoung/dom0/ This version (2.6.30-0.1.2.23.rc4.xendom0.fc12) is based on the xen-tip/master branch, and also contains a bit of experimentation as CONFIG_XEN_GNTDEV and CONFIG_XEN_PCI_PASSTHROUGH are now enabled, and I have done a bit of hacking to get CONFIG_CC_STACKPROTECTOR working. Michael Young From jelutz at config.com Fri May 1 05:40:07 2009 From: jelutz at config.com (Jim Lutz) Date: Fri, 01 May 2009 01:40:07 -0400 Subject: [Fedora-xen] No pcifront in F10? Message-ID: <49FA8B37.3050905@config.com> I have a virtual machine landscape consisting of a CentOS 5.3 Dom0 with Xen 3.1.2, some PV CentOS DomU's with PCI passthrough (same versions), and I'm trying to implement a F10 DomU with PCI passthrough. I set everything up for the passthrough, and the F10 guest can't see any of the devices with lspci. If I boot a CentOS PV machine with the same PCI passthrough configuration, the devices show up with lspci. I've seen some posts in various places about this issue, but no solutions. How do I implement this? From schwier at rrzn.uni-hannover.de Sat May 2 11:06:25 2009 From: schwier at rrzn.uni-hannover.de (Harald Schwier) Date: Sat, 02 May 2009 13:06:25 +0200 Subject: [Fedora-xen] Live migration fails depending on on the kernel Version of DomU In-Reply-To: <64e30f320904300401i6923122ehb7e59c2b8293d087@mail.gmail.com> References: <49F80526.2030205@rvs.uni-hannover.de> <20090430071435.GL24960@edu.joroinen.fi> <64e30f320904300401i6923122ehb7e59c2b8293d087@mail.gmail.com> Message-ID: <49FC2931.6030909@rrzn.uni-hannover.de> The architecture is x86_64 for Dom-0 and Dum-U. (Dell 2950) > what is the architecture of Dom-0 and userdomain? both the same (e.g. 32bit)? > > > > On Thu, Apr 30, 2009 at 9:14 AM, Pasi K?rkk?inen wrote: > >> On Wed, Apr 29, 2009 at 09:43:34AM +0200, Harald Schwier wrote: >> >>> Hi, >>> I'm running a two node cluster xen-Cluster with CentOS 5.3. I'm using >>> gfs2 for the cluster filesystem and kernel 2.6.18-128.1.6.el5xen #1 SMP >>> for the Dom0 kernel. >>> >>> Live migration works fine as long as the DomU guest is running CentOS 5.3 >>> or SLC 4.7 with kernel version 2.6.9-55.EL.cern. But if the SLC 4.7 guest is >>> running the current 2.6.9-78.0.17.EL.cern kernel, the migration freezes >>> without >>> an error message. >>> >>> Any idea why the DomU kernel has an impact on live migration? Is there a >>> possibility to migrate a DomU guest running kernel 2.6.9-78.0.17.EL.cern? >>> Thanks in advance, >>> Harald >>> >>> >> This is fedora-xen list, not centos-virt .. :) >> >> This _sounds_ like upstream bug/issue, so you might want to get RHEL support >> contract and then report it to Redhat.. >> >> Or you could try rhelv5-list or xen-devel. >> I can't really help you with the actual issue.. >> >> -- Pasi >> >> -- >> Fedora-xen mailing list >> Fedora-xen at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen >> >> > > From pasik at iki.fi Mon May 4 15:18:18 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 4 May 2009 18:18:18 +0300 Subject: [Fedora-xen] Problems rebuilding fedora xen-3.3.1-11.fc11.src.rpm with debug enabled Message-ID: <20090504151818.GQ24960@edu.joroinen.fi> Hello. I'm trying to rebuild xen-3.3.1-11.fc11.src.rpm with debug enabled to be able to get more debug information from pv_ops dom0 kernels. .. and I have a problem. Has someone else seen this problem? I modified xen.spec and added "debug=y verbose=y crash_debug=y" options to "%if %{hv_build}" section to make command. Running "rpmbuild -bb xen.spec" gives this error: traps.c: Assembler messages: traps.c:1343: Error: bad register name `%sil' make[4]: *** [traps.o] Error 1 make[4]: Leaving directory `/root/rpmbuild/BUILD/xen-3.3.1/xen/arch/x86' Based on some googling it could be a gcc problem? I'm running: # rpm -qa|grep gcc gcc-gfortran-4.4.0-3.i586 libgcc-4.4.0-3.i586 gcc-c++-4.4.0-3.i586 gcc-debuginfo-4.3.2-7.i386 gcc-4.4.0-3.i586 -- Pasi From fedora.lists at burns.me.uk Mon May 4 18:51:37 2009 From: fedora.lists at burns.me.uk (Andy Burns) Date: Mon, 4 May 2009 19:51:37 +0100 Subject: [Fedora-xen] No pcifront in F10? In-Reply-To: <49FA8B37.3050905@config.com> References: <49FA8B37.3050905@config.com> Message-ID: 2009/5/1 Jim Lutz : > I have a virtual machine landscape consisting of a CentOS 5.3 Dom0 with Xen > 3.1.2, some PV CentOS DomU's with PCI passthrough (same versions), and I'm > trying to implement a F10 DomU with PCI passthrough. I set everything up for > the passthrough, and the F10 guest can't see any of the devices with lspci. > If I boot a CentOS PV machine with the same PCI passthrough configuration, > the devices show up with lspci. I've seen some posts in various places about > this issue, but no solutions. How do I implement this? There has been no pcifront in recent Fedora kernels, you'll have to stick with older centOS kernels. or wait until pv_ops domU has landed (so 2.6.31 at the earliest) *and* the pcifront has been re-implemented (not sure if anyone other than Jeremy has this in their sights) or look at ubuntu which I think has forward ported the old non-pv_ops xen to more recent kernels From pasik at iki.fi Tue May 5 06:53:10 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 5 May 2009 09:53:10 +0300 Subject: [Fedora-xen] Problems rebuilding fedora xen-3.3.1-11.fc11.src.rpm with debug enabled In-Reply-To: <20090504151818.GQ24960@edu.joroinen.fi> References: <20090504151818.GQ24960@edu.joroinen.fi> Message-ID: <20090505065310.GU24960@edu.joroinen.fi> On Mon, May 04, 2009 at 06:18:18PM +0300, Pasi K?rkk?inen wrote: > Hello. > > I'm trying to rebuild xen-3.3.1-11.fc11.src.rpm with debug enabled to be > able to get more debug information from pv_ops dom0 kernels. > > .. and I have a problem. Has someone else seen this problem? > > I modified xen.spec and added "debug=y verbose=y crash_debug=y" options to > "%if %{hv_build}" section to make command. > > Running "rpmbuild -bb xen.spec" gives this error: > > traps.c: Assembler messages: > traps.c:1343: Error: bad register name `%sil' > make[4]: *** [traps.o] Error 1 > make[4]: Leaving directory `/root/rpmbuild/BUILD/xen-3.3.1/xen/arch/x86' > > Based on some googling it could be a gcc problem? I'm running: > > # rpm -qa|grep gcc > gcc-gfortran-4.4.0-3.i586 > libgcc-4.4.0-3.i586 > gcc-c++-4.4.0-3.i586 > gcc-debuginfo-4.3.2-7.i386 > gcc-4.4.0-3.i586 > http://lists.xensource.com/archives/html/xen-devel/2009-05/msg00075.html OK it's a Xen bug. Patch from the above mail should fix the problem. -- Pasi From pasik at iki.fi Wed May 6 19:00:21 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 6 May 2009 22:00:21 +0300 Subject: [Fedora-xen] Re: [fedora-virt] Re: Dom0 kernels / VGA text console works now In-Reply-To: <49C746F0.3050704@redhat.com> References: <49C0B8BC.1050301@redhat.com> <20090322115432.GX15052@edu.joroinen.fi> <49C746F0.3050704@redhat.com> Message-ID: <20090506190021.GZ24960@edu.joroinen.fi> On Mon, Mar 23, 2009 at 09:23:12AM +0100, Gerd Hoffmann wrote: > Pasi K?rkk?inen wrote: > > On Wed, Mar 18, 2009 at 10:02:52AM +0100, Gerd Hoffmann wrote: > >> M A Young wrote: > >>> (with nomodeset I get no text characters during > >>> boot - only a cursor that moves as invisible characters are presumably > >>> printed to the screen > >> known issue with vga text mode (32bit only, 64bit works ok). vga window > >> at 0xc0000 isn't mapped correctly. Workaround: drive the card in gfx > >> mode. Either kernel mode setting or vesafb (use something like > >> vga=gfx-1024x768x16 on the *xen* kernel command line). > > > > So the reason for this issue is known.. any patches available? > > According to jeremy someone works on unifying 32bit and 64bit page table > initalization, which should nicely fix this issue as a side effect. > VGA text console works OK for me now, on 32bit PAE pv_ops dom0, using the latest xen-tip/next tree! -- Pasi From pasik at iki.fi Wed May 6 19:31:50 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 6 May 2009 22:31:50 +0300 Subject: [Fedora-xen] Fedora 11 (rawhide) success with Xen pv_ops dom0 kernel (2.6.30-rc3) Message-ID: <20090506193150.GA24960@edu.joroinen.fi> Hello! Earlier I was testing Xen pv_ops dom0 kernel with Fedora 10, and after I got it working I decided to repeat the tests with Fedora 11 (rawhide). There was problems with the latest pv_ops dom0 xen-tip/next kernel tree for a while, but those problems are now resolved, and I got my Fedora 11 testbox working, so I decided to write here about my success. My setup: - Fedora 11 (rawhide as of 2009-05-05) - Xen included in F11, no external patches (xen-3.3.1-11.fc11) - xen-tip/next pv_ops dom0 kernel as of 2009-05-06, Linux 2.6.30-rc3. - All the rest was standard stuff included in Fedora 11 aswell With this setup I'm able to run Xen paravirtual (PV) domUs, install new domUs using virt-install and also install and manage domains with virt-manager. Current limitations: - Xen HVM support is not yet working with pv_ops dom0 kernel Earlier problems with VGA text console have also been fixed, so grub menu.lst entry like this now works: title Fedora Xen pv_ops dom0-test (2.6.30-rc3-tip) root (hd0,0) kernel /xen-3.3.gz dom0_mem=1024M loglvl=all guest_loglvl=all module /vmlinuz-2.6.30-rc3-tip ro root=/dev/vg00/lv01 module /initrd-2.6.30-rc3-tip.img Or if you want to have serial console, use this: title Fedora Xen pv_ops dom0-test (2.6.30-rc3-tip) / serial console root (hd0,0) kernel /xen-3.3.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 module /vmlinuz-2.6.30-rc3-tip ro root=/dev/vg00/lv01 console=hvc0 earlyprintk=xen module /initrd-2.6.30-rc3-tip.img Hopefully someone finds this information interesting! :) -- Pasi From m.a.young at durham.ac.uk Fri May 8 19:12:26 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Fri, 8 May 2009 20:12:26 +0100 (BST) Subject: [Fedora-xen] Dom0 kernels In-Reply-To: References: <20090328163545.GM31725@salstar.sk> <20090414143618.GH351@redhat.com> Message-ID: My latest build is at http://koji.fedoraproject.org/koji/taskinfo?taskID=1340915 and at the repository http://fedorapeople.org/~myoung/dom0/ i686 boots again, due to an upstream problem fix, and I turned off CC_STACKPROTECTOR for i686 again because my test code wasn't enough to get it working in this case. Michael Young From shoom013 at gmail.com Sun May 10 23:43:55 2009 From: shoom013 at gmail.com (shoom) Date: Sun, 10 May 2009 16:43:55 -0700 (PDT) Subject: [Fedora-xen] Xen HVM Wink2k3 guest network problem Message-ID: <23475221.post@talk.nabble.com> I have a pain-staking problem with network on Win2k3 guest on IA64 host with Red Hat 5.3 - by default it uses Realtek 8139 which is not supported on Win2k3 in any way, and changing the model (model=whatever in vif=...) doesn't change anything - it always ends with *!@#! Realtek ... now, I am very tired of trying out different things (compiling Xen from src.rpm, from xensource xen-unstable.hg, trying vfirmware from xensource, different parameters in guest specification, I don't know ..) - nothing helps. Thing is that I am trying to make the proof of concept in my company for RHEL5.3 as platform for Itanium virtualization (BL380c) in order to get full support contract with Red Hat as a breakthrough ... but it seems that Microsoft always has to win, I vae tried to ring every bell available, but nothing came and now I am tired and worn out completely ... If anyone has any idea, hint, something, please tell me. shoom013 at gmail.com -- View this message in context: http://www.nabble.com/Xen-HVM-Wink2k3-guest-network-problem-tp23475221p23475221.html Sent from the Fedora Xen mailing list archive at Nabble.com. From mdcrawford at gmail.com Mon May 11 00:45:49 2009 From: mdcrawford at gmail.com (Michael Crawford) Date: Sun, 10 May 2009 17:45:49 -0700 Subject: [Fedora-xen] How to build Xen with my own Linux sources? Message-ID: I asked about this on the xen-devel list a few days ago, but no one responded. I just asked a second time, but it has been my experience that the other xen-devel subscribers just ignore pleas for help. I'm an experienced developer, and I've tried searching the list archives as well as Google. I've done my best to ask intelligent questions - but still I am *completely* stymied. What I want to do is to build the xen and linux kernels without having the xen build download the linux source tarball from kernel.org. I have used git to get the tip/master branch of Linux - that's the version of Linux that is in development from the Xen folks. I can build a working kernel from it if I only build linux itself, without trying to also build xen. What I want to do is to get xen to build, but when it wants to build the Dom0 and DomU kernels, I want it to use my tip/master branch of the Linux sources that I retrieved with git. I have seen documentation that says I should be able to do this by rolling a .tar.bz2 of the kernel source, and then setting the environment variable XEN_LINUX_SOURCE=tarball, but it simply does not work - the kernel tarball is still downloaded with wget. I am incredibly frustrated. I'm grateful for any help you can give me. Mike -- Michael David Crawford mdcrawford at gmail dot com GoingWare's Bag of Programming Tricks http://www.goingware.com/tips/ From pasik at iki.fi Mon May 11 07:29:10 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 11 May 2009 10:29:10 +0300 Subject: [Fedora-xen] Xen HVM Wink2k3 guest network problem In-Reply-To: <23475221.post@talk.nabble.com> References: <23475221.post@talk.nabble.com> Message-ID: <20090511072910.GQ24960@edu.joroinen.fi> On Sun, May 10, 2009 at 04:43:55PM -0700, shoom wrote: > > I have a pain-staking problem with network on Win2k3 guest on IA64 host with > Red Hat 5.3 - by default it uses Realtek 8139 which is not supported on > Win2k3 in any way, and changing the model (model=whatever in vif=...) > doesn't change anything - it always ends with *!@#! Realtek ... now, I am > very tired of trying out different things (compiling Xen from src.rpm, from > xensource xen-unstable.hg, trying vfirmware from xensource, different > parameters in guest specification, I don't know ..) - nothing helps. Thing > is that I am trying to make the proof of concept in my company for RHEL5.3 > as platform for Itanium virtualization (BL380c) in order to get full support > contract with Red Hat as a breakthrough ... but it seems that Microsoft > always has to win, I vae tried to ring every bell available, but nothing > came and now I am tired and worn out completely ... If anyone has any idea, > hint, something, please tell me. Did you try installing paravirtualized windows drivers provided by Redhat? And also, you might have better luck on rhelv5-list instead of fedora-xen.. -- Pasi From shoom013 at gmail.com Mon May 11 12:33:18 2009 From: shoom013 at gmail.com (shoom) Date: Mon, 11 May 2009 05:33:18 -0700 (PDT) Subject: [Fedora-xen] Xen HVM Wink2k3 guest network problem In-Reply-To: <20090511072910.GQ24960@edu.joroinen.fi> References: <23475221.post@talk.nabble.com> <20090511072910.GQ24960@edu.joroinen.fi> Message-ID: <23482415.post@talk.nabble.com> > Did you try installing paravirtualized windows drivers provided by Redhat? These are just for x86 an x64, unapplicable for ia64 ... > And also, you might have better luck on rhelv5-list instead of > fedora-xen.. Ok, I will try there, too ... 10x for the reply, ZP. -- View this message in context: http://www.nabble.com/Xen-HVM-Wink2k3-guest-network-problem-tp23475221p23482415.html Sent from the Fedora Xen mailing list archive at Nabble.com. From dlbewley at lib.ucdavis.edu Fri May 15 17:51:41 2009 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Fri, 15 May 2009 10:51:41 -0700 Subject: [Fedora-xen] How to build Xen with my own Linux sources? In-Reply-To: References: Message-ID: <1242409901.32290.6.camel@tofu.lib.ucdavis.edu> On Sun, 2009-05-10 at 17:45 -0700, Michael Crawford wrote: > What I want to do is to get xen to build, but when it wants to build > the Dom0 and DomU kernels, I want it to use my tip/master branch of > the Linux sources that I retrieved with git. I'm of little help, but have you looked for clues in the Fedora spec files? There are at least a couple folks on this list wading in similar waters to you. I think they are using the prebuilt Fedora Xen RPMs though. http://fedoraproject.org/wiki/FWN/Issue169#Success_with_Experimental_Fedora_10_pv_ops_dom0 http://fedoraproject.org/wiki/FWN/Issue173#Dom0_Kernel_Not_Before_2.6.31 From pasik at iki.fi Mon May 18 12:51:58 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 18 May 2009 15:51:58 +0300 Subject: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.4.0 released! Message-ID: <20090518125158.GQ24960@edu.joroinen.fi> ----- Forwarded message from Keir Fraser ----- From: Keir Fraser To: "xen-devel at lists.xensource.com" , xen-users at lists.xensource.com Cc: Date: Mon, 18 May 2009 05:26:28 -0700 Subject: [Xen-devel] [ANNOUNCE] Xen 3.4.0 released! Folks, We're pleased to announce the official release of Xen 3.4.0! This release contains a number of important new features and updates including: - Device passthrough improvements, with particular emphasis on support for client devices (further support is available as part of the XCI project at http://xenbits.xensource.com/xenclient/) - RAS features: cpu and memory offlining - Power management - improved frequency/voltage controls and deep-sleep support. Scheduler and timers optimised for peak power savings. - Support for the Viridian (Hyper-V) enlightenment interface - Many other x86 and ia64 enhancements and fixes You can get the source using mercurial from: http://xenbits.xensource.com/xen-3.4-testing.hg A pre-prepared source tarball is available from: http://www.xen.org/download/ Cheers, Keir (on behalf of the whole Xen dev team) _______________________________________________ Xen-devel mailing list Xen-devel at lists.xensource.com http://lists.xensource.com/xen-devel ----- End forwarded message ----- From m.a.young at durham.ac.uk Fri May 22 23:26:29 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Sat, 23 May 2009 00:26:29 +0100 (BST) Subject: [Fedora-xen] Dom0 kernels In-Reply-To: References: <20090328163545.GM31725@salstar.sk> <20090414143618.GH351@redhat.com> Message-ID: This build http://koji.fedoraproject.org/koji/taskinfo?taskID=1371327 updates to the latest xen-tip/next version, and is of courase available via the repository http://fedorapeople.org/~myoung/dom0/ Michael Young From pasik at iki.fi Sat May 23 18:16:28 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sat, 23 May 2009 21:16:28 +0300 Subject: [fedora-virt] Re: [Fedora-xen] Dom0 kernels In-Reply-To: References: <20090328163545.GM31725@salstar.sk> <20090414143618.GH351@redhat.com> Message-ID: <20090523181628.GF24960@edu.joroinen.fi> On Sat, May 23, 2009 at 12:26:29AM +0100, M A Young wrote: > This build http://koji.fedoraproject.org/koji/taskinfo?taskID=1371327 > updates to the latest xen-tip/next version, and is of courase available > via the repository http://fedorapeople.org/~myoung/dom0/ > I assume this is a version which should have Xen HVM guests working now? "[Xen-devel] [GIT] privcmd fixes --> working HVM": http://lists.xensource.com/archives/html/xen-devel/2009-05/msg00839.html -- Pasi From m.a.young at durham.ac.uk Sat May 23 19:39:31 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Sat, 23 May 2009 20:39:31 +0100 (BST) Subject: [fedora-virt] Re: [Fedora-xen] Dom0 kernels In-Reply-To: <20090523181628.GF24960@edu.joroinen.fi> References: <20090328163545.GM31725@salstar.sk> <20090414143618.GH351@redhat.com> <20090523181628.GF24960@edu.joroinen.fi> Message-ID: On Sat, 23 May 2009, Pasi K?rkk?inen wrote: > On Sat, May 23, 2009 at 12:26:29AM +0100, M A Young wrote: >> This build http://koji.fedoraproject.org/koji/taskinfo?taskID=1371327 >> updates to the latest xen-tip/next version, and is of courase available >> via the repository http://fedorapeople.org/~myoung/dom0/ >> > > I assume this is a version which should have Xen HVM guests working now? > > "[Xen-devel] [GIT] privcmd fixes --> working HVM": > http://lists.xensource.com/archives/html/xen-devel/2009-05/msg00839.html Yes, that patch is in, as is the followup patch that takes it out again and puts it somewhere else. Michael Young From pasik at iki.fi Sat May 23 20:42:20 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sat, 23 May 2009 23:42:20 +0300 Subject: [fedora-virt] Re: [Fedora-xen] Dom0 kernels with HVM guest support In-Reply-To: References: <20090414143618.GH351@redhat.com> <20090523181628.GF24960@edu.joroinen.fi> Message-ID: <20090523204219.GG24960@edu.joroinen.fi> On Sat, May 23, 2009 at 08:39:31PM +0100, M A Young wrote: > On Sat, 23 May 2009, Pasi K?rkk?inen wrote: > > >On Sat, May 23, 2009 at 12:26:29AM +0100, M A Young wrote: > >>This build http://koji.fedoraproject.org/koji/taskinfo?taskID=1371327 > >>updates to the latest xen-tip/next version, and is of courase available > >>via the repository http://fedorapeople.org/~myoung/dom0/ > >> > > > >I assume this is a version which should have Xen HVM guests working now? > > > >"[Xen-devel] [GIT] privcmd fixes --> working HVM": > >http://lists.xensource.com/archives/html/xen-devel/2009-05/msg00839.html > > Yes, that patch is in, as is the followup patch that takes it out again > and puts it somewhere else. > Great. Now we just have to get that blktap2 in and most of the common features are there.. -- Pasi From mj at mjw.se Sat May 30 23:38:51 2009 From: mj at mjw.se (mattias) Date: Sun, 31 May 2009 01:38:51 +0200 Subject: [Fedora-xen] debian Message-ID: <000101c9e17f$c9bc5930$7b16e255@jonsson2> Can i install debian with virt-install I meen para-virt From paul at xelerance.com Sun May 31 00:33:39 2009 From: paul at xelerance.com (Paul Wouters) Date: Sat, 30 May 2009 20:33:39 -0400 (EDT) Subject: [Fedora-xen] debian In-Reply-To: <000101c9e17f$c9bc5930$7b16e255@jonsson2> References: <000101c9e17f$c9bc5930$7b16e255@jonsson2> Message-ID: On Sun, 31 May 2009, mattias wrote: > Can i install debian with virt-install > I meen para-virt I don't know about virt-install, but probably not. I always had to have two different initrd's between fedora and debian based machines. Though I did use whatever kernel fedora put on my dom0. Paul From mj at mjw.se Sun May 31 00:35:29 2009 From: mj at mjw.se (mattias) Date: Sun, 31 May 2009 02:35:29 +0200 Subject: SV: [Fedora-xen] debian In-Reply-To: Message-ID: <000001c9e187$b2cb6b00$7b16e255@jonsson2> Do you not use pygrub I think if you use pygrub you don't need the initrd on the host? -----Ursprungligt meddelande----- Fr?n: Paul Wouters [mailto:paul at xelerance.com] Skickat: den 31 maj 2009 02:34 Till: mattias Kopia: fedora-xen at redhat.com ?mne: Re: [Fedora-xen] debian On Sun, 31 May 2009, mattias wrote: > Can i install debian with virt-install > I meen para-virt I don't know about virt-install, but probably not. I always had to have two different initrd's between fedora and debian based machines. Though I did use whatever kernel fedora put on my dom0. Paul