Hi all, I have a little question about a problem i''m experiencing with the new xen 2.0.7: I installed in on a debian box, dom0 starts with no problem, also the domains i copied over from my 2.0.6 box start rightaway BUT: i needed a custom kernel (i want to play with PCI device acces in domU) so i grabbed the 2.0.7 source and compiled the 2.6.11-domU kernel (with the standard config) and tried booting one of my 2.0.6 systems. result : debian:/mnt/temp/xen/xenU/xen-2.0/linux-2.6.11-xenU# xm create /etc/xen/mythtv -c Using config file "/etc/xen/mythtv". Started domain mythtv, console on port 9618 ************ REMOTE CONSOLE: CTRL-] TO QUIT ******** ************ REMOTE CONSOLE EXITED ***************** .... eg : nothing at all this domain tries to boot from hda1 (lvm backed on dom0) and works fine with the kernel from 2.0.6 I noticed that in the default .config, the "CONFIG_XEN_PHYSDEV_ACCESS" was selected, so i tried disabling that and recompiled. Now the system comes up with no problems, but obviously, i have no access to my PCI device. Is there anything else i need to do besides: 1. hiding the pci''s from dom0 by specifing the pci = [ x,y,z ] in the config file and the physdev_dom0_hide option for xen-2.0.gz 2. enabling CONFIG_XEN_PHYSDEV_ACCESS for the domU kernel 3. including the correct drivers in the domU kernel Do any of you see a reason why my kernel would not come up if i enable "CONFIG_XEN_PHYSDEV_ACCESS" in domU ? Thanks, Ban **************************************************************************** Disclaimer: This electronic transmission and any files attached to it are strictly confidential and intended solely for the addressee. If you are not the intended addressee, you must not disclose, copy or take any action in reliance of this transmission. If you have received this transmission in error, please notify the sender by return and delete the transmission. Although the sender endeavors to maintain a computer virus free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Thank You. **************************************************************************** _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
PAINCHAUD Christophe
2005-Nov-03 18:06 UTC
[Xen-users] Re: domU device access : kernel problem
It looks like we ran into the same problem, I posted a mail to the mailing list a few hours ago. I got same bug, whatever option I enabled or disabled. Let''s hope someone will be able to answer ;) http://lists.xensource.com/archives/html/xen-users/2005-11/msg00048.html PAINCHAUD Christophe _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
PAINCHAUD Christophe
2005-Nov-03 18:15 UTC
[Xen-users] RE: Re: domU device access : kernel problem
In fact I just re-read your post and I don''t have exactly the same problem. But your post answers mine :p Just disabled Physical Acess and it''s working now. I will also need a pci access later for an externel encryption pci device, so I am curious to know about solution for your problem since I will for sure run into it. Regards, Christophe -----Message d''origine----- De : PAINCHAUD Christophe Envoyé : jeudi 3 novembre 2005 19:06 À : ''Sven.Waeyenbergh@atosorigin.com'' Cc : ''xen-users@lists.xensource.com'' Objet : Re: domU device access : kernel problem It looks like we ran into the same problem, I posted a mail to the mailing list a few hours ago. I got same bug, whatever option I enabled or disabled. Let''s hope someone will be able to answer ;) http://lists.xensource.com/archives/html/xen-users/2005-11/msg00048.html PAINCHAUD Christophe _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I would like to know some more information here. 1) Does this happens by just enabling the "CONFIG_XEN_PHYSDEV_ACCESS" in domU, without hiding any PCI device from Dom0 and without passing pci device to DomU. 2) If you are doing all these: a). hiding the pci''s from dom0 by specifing the pci = [ x,y,z ] in the config file and the physdev_dom0_hide option for xen-2.0.gz b). enabling CONFIG_XEN_PHYSDEV_ACCESS for the domU kernel c). including the correct drivers in the domU kernel then, make sure that the pci device values are given in Hexadecimal numbers Can you provide pci device values here. On 11/3/05, PAINCHAUD Christophe <cpainchaud@ecritel.net> wrote:> > > In fact I just re-read your post and I don''t have exactly the same > problem. But your post answers mine :p Just disabled Physical Acess and it''s > working now. I will also need a pci access later for an externel encryption > pci device, so I am curious to know about solution for your problem since I > will for sure run into it. > > Regards, > > Christophe > > -----Message d''origine----- > De : PAINCHAUD Christophe > Envoyé : jeudi 3 novembre 2005 19:06 > À : ''Sven.Waeyenbergh@atosorigin.com'' > Cc : ''xen-users@lists.xensource.com'' > Objet : Re: domU device access : kernel problem > > It looks like we ran into the same problem, I posted a mail to the mailing > list a few hours ago. I got same bug, whatever option I enabled or disabled. > > Let''s hope someone will be able to answer ;) > > http://lists.xensource.com/archives/html/xen-users/2005-11/msg00048.html > > PAINCHAUD Christophe > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Waeyenbergh, Sven schrieb:> i needed a custom kernel (i want to play with PCI device acces in domU) so i grabbed the 2.0.7 source > and compiled the 2.6.11-domU kernel (with the standard config) and tried booting one of my 2.0.6 systems. > result : > debian:/mnt/temp/xen/xenU/xen-2.0/linux-2.6.11-xenU# xm create /etc/xen/mythtv -c > Using config file "/etc/xen/mythtv". > Started domain mythtv, console on port 9618 > ************ REMOTE CONSOLE: CTRL-] TO QUIT ******** > > ************ REMOTE CONSOLE EXITED ***************** > > .... eg : nothing at allThat looks exactly like the problem I reported about 2 month ago under the topic "What''s the magic to compile a unified dom0 and domU kernel image?". Very nice to see that I''m not the only one with problems like this. I think there MUST be some type of bug in the XEN 2.0.7 (?) code. I just tried with my failing kernel config: When disabling CONFIG_XEN_PHYSDEV_ACCESS the domU comes up, otherwise not. Greetings, Markus _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi all, I finally managed to get my kernel booting. It seems like when your are accessing hardware directly from a domU kernel, you need to set CONFIG_XEN_PHYSDEV_ACCESS but you also need to enable CONFIG_XEN_PRIVILEGED_GUEST for the kernel to boot. Please note that there are several steps to get this to work : 1. find the device (or devices - some cards have more then 1) by running lspci on dom0 2. hide devices from dom0 by specifying the physdev_dom0_hide kernel option at the xen-2.0.gz kernel command line example : kernel /xen-2.0.gz dom0_mem=131072 physdev_dom0_hide=(03:02.1)(03:02.0) 3. give your domU kernel hardware access by specifying CONFIG_XEN_PHYSDEV_ACCESS in your domU kernel config 4. enable CONFIG_XEN_PRIVILEGED_GUEST in your domU kernel config - do not know why, but seems needed to boot 5. enable the drivers you need in the domU kernel config - both the device drivers and the bus drivers example : for a tvcard: CONFIG_I2C, CONFIG_i2C_ALGOBIT,CONFIG_VIDEO_DEV,CONFIG_VIDEO_BT848 and CONFIG_PCI note that making modules here is easy for debugging 5. if you made modules, copy them to the domU filesystem 6. make the domU kernel and edit the config file to boot from it 7. give the domU access to the specified devices by adding pci=[''x,y,z''] in you domain config file example: pci = [''03,02,1'',''03,02,0''] and boot tha booty ... Hope it helps, Ban -----Original Message----- From: Markus Schuster [mailto:ma.schuster@gmx.de] Sent: 04 November 2005 00:00 To: xen-users@lists.xensource.com Subject: [Xen-users] Re: domU device access : kernel problem Waeyenbergh, Sven schrieb:> i needed a custom kernel (i want to play with PCI device acces in domU) so i grabbed the 2.0.7 source > and compiled the 2.6.11-domU kernel (with the standard config) and tried booting one of my 2.0.6 systems. > result : > debian:/mnt/temp/xen/xenU/xen-2.0/linux-2.6.11-xenU# xm create /etc/xen/mythtv -c > Using config file "/etc/xen/mythtv". > Started domain mythtv, console on port 9618 > ************ REMOTE CONSOLE: CTRL-] TO QUIT ******** > > ************ REMOTE CONSOLE EXITED ***************** > > .... eg : nothing at allThat looks exactly like the problem I reported about 2 month ago under the topic "What''s the magic to compile a unified dom0 and domU kernel image?". Very nice to see that I''m not the only one with problems like this. I think there MUST be some type of bug in the XEN 2.0.7 (?) code. I just tried with my failing kernel config: When disabling CONFIG_XEN_PHYSDEV_ACCESS the domU comes up, otherwise not. Greetings, Markus *** eSafe scanned this email for malicious content *** *** IMPORTANT: Do not open attachments from unrecognized senders *** **************************************************************************** Disclaimer: This electronic transmission and any files attached to it are strictly confidential and intended solely for the addressee. If you are not the intended addressee, you must not disclose, copy or take any action in reliance of this transmission. If you have received this transmission in error, please notify the sender by return and delete the transmission. Although the sender endeavors to maintain a computer virus free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Thank You. **************************************************************************** _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
PAINCHAUD Christophe
2005-Nov-04 10:42 UTC
[Xen-users] RE: Re: domU device access : kernel problem
>1) Does this happens by just enabling the "CONFIG_XEN_PHYSDEV_ACCESS" in >domU, without hiding any PCI device from Dom0 and without passing pci >device to DomU.I think it does. Basically, I missed the fact that I had to hide all devices.>2) If you are doing all these: > a). hiding the pci''s from dom0 by specifing the pci = [ x,y,z ] in >the config file and the physdev_dom0_hide option for xen-2.0.gz > b). enabling CONFIG_XEN_PHYSDEV_ACCESS for the domU kernel > c). including the correct drivers in the domU kernel >then, make sure that the pci device values are given in Hexadecimal numbersThis procedure seems to solve my problem, I can boot with a kernel that is CONFIG_XEN_PHYSDEV_ACCESS enabled. I will try my crypto pci device later, I don''t have it yet. Thank you, PAINCHAUD Christophe _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users