Re: xen-unstable+pvops kernel, I don't have xenbus and xenwatch kernel thread.

[Min Lee <min.lee@gatech.edu>]

Thanks a lot! I used to work on old xen versions mainly..
I've updated the kernel also, and it now has xen/...,
so now it's working. Thanks again, Jeremy!
Min

On 6/9/2010 2:54 PM, Jeremy Fitzhardinge wrote:
> On 06/09/2010 11:51 AM, Min Lee wrote:
>> [root@vmphone210 ~]# cat /proc/misc
>>   57 autofs
>> 224 tpm0
>>   58 device-mapper
>>   59 network_throughput
>>   60 network_latency
>>   61 cpu_dma_latency
>> 144 nvram
>> 228 hpet
>>   62 evtchn
>> 227 mcelog
>>   63 vga_arbiter
>> [root@vmphone210 ~]#
>>
>> As you see, evtchn is there, but no gntdev,
>> thanks!
>
> Ah, you just haven't compiled it in.  qemu now relies on it, so you need
> to compile it in.  And if you're running a current xen-unstable, you
> should update the kernel to get the fixed evtchn and gntdev device names
> (ie, with xen/).
>
>      J
>
>>
>> On 6/9/2010 2:43 PM, Jeremy Fitzhardinge wrote:
>>> On 06/09/2010 11:37 AM, Min Lee wrote:
>>>> Hi, Jeremy.
>>>> Yes, xenstored is running and xenstore-ls dumps its contents, although
>>>> I had to start it manually.
>>>> I have only evtchn in /dev/xen. No gntdev.
>>>
>>> What does /proc/misc say?  Does it list "xen/evtchn" and "xen/gntdev" or
>>> just the non-xen/ versions?
>>>
>>>       J
>>>
>>>>
>>>>
>>>> On 6/9/2010 2:23 PM, Jeremy Fitzhardinge wrote:
>>>>> On 06/09/2010 08:05 AM, Min Lee wrote:
>>>>>> Hello. folks.
>>>>>> I've tried Xen-unstable + Jeremy's pvops kernel on ibm x3550M2 server
>>>>>> machine, on centos 5.4.
>>>>>> Also I've already checked these instructions..
>>>>>> http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher
>>>>>> Now, it seems like domain creation cannot find its virtual devices..
>>>>>> So I couldn't start my domains. I had these messages..
>>>>>>
>>>>>> xenconsole: Could not read tty from store: No such file or directory
>>>>>> Error: Device 0 (vif) could not be connected. Hotplug scripts not
>>>>>> working.
>>>>>> Error: Device 2049 (vbd) could not be connected. Path closed or
>>>>>> removed during hotplug add: backend/vbd/5/2049 state: 1
>>>>>>
>>>>>> /proc/xen has these files.
>>>>>>
>>>>>> -r--r--r-- 1 root root 0 Jun  8 09:57 capabilities
>>>>>> -rw------- 1 root root 0 Jun  8 09:57 privcmd
>>>>>> -rw------- 1 root root 0 Jun  8 09:57 xenbus
>>>>>> -rw------- 1 root root 0 Jun  8 09:57 xsd_kva
>>>>>> -rw------- 1 root root 0 Jun  8 09:57 xsd_port
>>>>>>
>>>>>> 'make install-tools' didn't install links in my /etc/rc directories,
>>>>>> so I had to run manually xenconsoled, xenstored, and xend, but
>>>>>> I found that I have no xenbus and xenwatch kernel threads.
>>>>>> Is this why it can't finds virtual devices??
>>>>>
>>>>> Is xenstored running?  Do you have the evtchn and gntdev devices in
>>>>> /dev/xen?
>>>>>
>>>>>        J
>>>>>
>>>>
>>>
>>>
>>
>
>