[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] domU guest for xcp 0.1.1
On Sun, Mar 21, 2010 at 10:22:06AM -0700, Ritu kaur wrote: > Hi, > > I am running out of options to test pci passthrough with shared > interrupts, since xen/next kernel doesn't work with xcp0.1.1 dom0. I tried > couple of combinations > > 1. xen 3.4.3 with xen/next kernel, dom0 continuous reboot, boot messages > goes off pretty fast so not sure what's going wrong here. > You need to set up a serial console so you can capture the boot messages: http://wiki.xensource.com/xenwiki/XenSerialConsole > 2. xen 3.4.3 with 2.6.27.42-0.1.1.xs0.1.1.737.1065xen(i.e which comes with > xcp 0.1.1 default) system boots fine. > > 3. Assuming "1" is related to wrong .config file, copied > kernel-2.6.27.42-0.1.1.xs0.1.1.737.1065-i686-xen.config which comes with > dom0 kernel code, compiled and still same result as "1". > You can't really use the "xenlinux" kernel-2.6.27.42-0.1.1.xs0.1.1.737.1065-i686-xen.config with a pvops dom0 kernel. They're different kernels with different .config options. > Note: All 3, I tested by copying just xen3.4.3.gz, tools and stubdom is > not copied. If there is any viable options left to try out let me know. > Set up the serial console and figure out why xen/next pvops dom0 kernel doesn't boot for you. Make sure you have these options for the dom0 kernel: console=hvc0 earlyprintk=xen nomodeset More help here: http://wiki.xensource.com/xenwiki/XenParavirtOps -- Pasi > Thanks > > On Sat, Mar 20, 2010 at 6:50 PM, Ritu kaur <[1]ritu.kaur.us@[2]gmail.com> > wrote: > > with 3.4.3 xen and kernel code from Jeremy's xen/next puts dom0 into > continuous reboot mode. > > 1. downloaded xen/next code into DDK and generated tar-pkg, it generates > linux-2.6.32.tar. Copied this tar file into root directory of dom0 and > extracted the file. > > 2. Copied xen code from > [3]http://xenbits.xensource.com/xen-3.4-testing.hg into DDK and did > "make xen", copied xen.3.4.3.gz into /boot of dom0. > > modified extlinux.conf to point to new vmlinuz and xen. dom0 is in > continuous reboot mode, let me know what am I doing wrong? > > Thanks > > On Fri, Mar 19, 2010 at 8:27 AM, Ritu kaur > <[4]ritu.kaur.us@[5]gmail.com> wrote: > > Thanks Konrad. I downloaded kernel code from xen/next. I believe this > requires 3.4.3 or 4.0.0 xen hypervisor code, I downloaded xen > hypervisor from [6]xenbits.xensource.com/xen-unstable.hg. For xcp dom0 > all compilation happens in DDK and no make utility is available and as > I understand I need to execute make install-* in dom0. For install-xen > probably I can copy xen.gz into /boot and modify files to reflect that > but I am not sure what's the needed to install tools and stubdom in > xcp dom0? > > make xen > make tools > make stubdom > > make install-xen > make install-tools > make install-stubdom > > Thanks > > On Thu, Mar 18, 2010 at 9:26 AM, Konrad Rzeszutek Wilk > <[7]konrad.wilk@xxxxxxxxxx> wrote: > > On Thu, Mar 18, 2010 at 08:28:18AM -0700, Ritu kaur wrote: > > Thanks Ian for clarification on interrupt handling mechanism. > > > > Thanks Konrad. Should I use xen/next in dom0 or domU? > > Both. > > References > > Visible links > 1. http://ritu.kaur.us/ > 2. http://gmail.com/ > 3. http://xenbits.xensource.com/xen-3.4-testing.hg > 4. http://ritu.kaur.us/ > 5. http://gmail.com/ > 6. http://xenbits.xensource.com/xen-unstable.hg > 7. mailto:konrad.wilk@xxxxxxxxxx > _______________________________________________ > Xen-devel mailing list > Xen-devel@xxxxxxxxxxxxxxxxxxx > http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |