Re: Reboot on *DOM0* while/after installing GPLPV drivers

["Mike C." <miguelmclara%gmail.com@localhost>]

On 10/16/13 00:38, John Hayward wrote:
> Sorry Mike,
> This was tangentially related to the reboot of Dom0 - I was trying to see 
> what happened with GPLPV drivers on NetBSD-5.1.2 since under NetBSD-6.1 we 
> observe a reboot of DOM0.
> 
> With the suggestion that I move xen.gz to / and use xl - I am now able to 
> boot windows7-64 bit under NetBSD-5.1.2
> using xen 4.2.3 I can install the GPLPV pci driver without issue.
> Attempting to install the block device - I got the blue screen both at the 
> end of install and when rebooting and selecting start windows normally.  I 
> had set restore points before installing GPLPV drivers and windows was able 
> to recover to the point before drivers.
> 
> It did not cause Dom0 to reboot.
>

This was reported too... There's was already a report about netbsd 5.1
with the same setup you tested now, but thanks for the feedback, this
helps to prove that there's some issue with the block drivers, the issue
seems to be in 5.1 too only in 6.1 some other change makes the Dom0
reboot when the error occurs!


NOTE: this doesn't happen with a linux Dom0 (at least not Debian)

> I think there may be an issue with 6.1 since Manuel indicated he thought he 
> had had success with an early version of 6.0.
> 

I think he was only able to do this for Windows XP not 7...


> Would be nice to have GPLPV drivers for win7-64 fully functional.
> The version of GPLPV I used is Vista2008-0.11.0372
> 
> We will refocus on the GPLPV drivers and versions of NetBSD.
> johnh...
> ________________________________________
> From: Mike C. [miguelmclara%gmail.com@localhost]
> Sent: Tuesday, October 15, 2013 5:08 PM
> To: John Hayward; Manuel Bouyer
> Cc: Adiel; Takahiro HAYASHI; port-xen%NetBSD.org@localhost
> Subject: Re: Reboot on *DOM0* while/after installing GPLPV drivers
> 
> Sorry for pointing this out, but wouldn't it be best to start a new
> thread about this?
> 
> Its just because what's being discussed now has nothing to do with the
> thread subject I started and to be honest I'm lost on the status of that
> now...
> 
> So could you please open a new thread?
> 
> Has the subject It seems that someone send some serial console output a
> few days ago? Was that helpful?
> 
> 
> On 10/15/13 20:07, John Hayward wrote:
>> also -- typing control-t after ls
>> root@johnhxen:xen{522}: ls /kern/xen
>> load: 0.00  cmd: ls 194 [tstile] 0.00u 0.00s 0% 960k
>> load: 0.00  cmd: ls 194 [tstile] 0.00u 0.00s 0% 960k
>> load: 0.00  cmd: ls 194 [tstile] 0.00u 0.00s 0% 960k
>> load: 0.00  cmd: ls 194 [tstile] 0.00u 0.00s 0% 960k
>> johnh...
>> ________________________________________
>> From: John Hayward
>> Sent: Tuesday, October 15, 2013 2:05 PM
>> To: Manuel Bouyer
>> Cc: Adiel; Takahiro HAYASHI; port-xen%NetBSD.org@localhost; Mike C.
>> Subject: RE: Reboot on *DOM0* while/after installing GPLPV drivers
>>
>> Now back to the wedge state with xen-debug.gz for kernel
>> output of ps axl
>> ====
>>  UID PID PPID  CPU PRI NI    VSZ    RSS WCHAN    STAT TTY      TIME COMMAND
>>    0   0    0    0 125  0      0 133144 schedule DKl  ?     0:01.11 [system]
>>    0   1    0    0  85  0   6520   1068 wait     Is   ?     0:00.01 init
>>    0  96    1  244  85  0  71608   5300 wait     I    ?     0:00.01 
>> /usr/pkg/bin/python2.7 /usr/pkg/sbin/xend start
>>    0  97   96  170 117  0  75704  14584 tstile   Sl   ?     0:00.11 
>> /usr/pkg/bin/python2.7 /usr/pkg/sbin/xend start
>> ====
>> Looks like tstile is wchan for pid 97.
>>
>> I'm also seeing in /var/log/xen/xend-debug.log
>> ====
>> Xend started at Tue Oct 15 13:57:19 2013.
>> brctl: not found
>> brctl: not found
>> ====
>> johnh...
>> ________________________________________
>> From: John Hayward
>> Sent: Tuesday, October 15, 2013 1:53 PM
>> To: Manuel Bouyer
>> Cc: Adiel; Takahiro HAYASHI; port-xen%NetBSD.org@localhost; Mike C.
>> Subject: RE: Reboot on *DOM0* while/after installing GPLPV drivers
>>
>> Thanks for your patience!
>> Now I get an error on xc:
>> ====
>> xc: error: Could not obtain handle on privileged command interface (2 = No 
>> such file or directory): Internal error
>> Traceback (most recent call last):
>>   File "/usr/pkg/sbin/xend", line 36, in <module>
>>     from xen.xend.server import SrvDaemon
>>   File "/usr/pkg/lib/python2.7/site-packages/xen/xend/server/SrvDaemon.py", 
>> line 26, in <module>
>>     import relocate
>>   File "/usr/pkg/lib/python2.7/site-packages/xen/xend/server/relocate.py", 
>> line 28, in <module>
>>     from xen.xend import XendDomain
>>   File "/usr/pkg/lib/python2.7/site-packages/xen/xend/XendDomain.py", line 
>> 36, in <module>
>>     from xen.xend import XendOptions, XendCheckpoint, XendDomainInfo
>>   File "/usr/pkg/lib/python2.7/site-packages/xen/xend/XendCheckpoint.py", 
>> line 20, in <module>
>>     from xen.xend import balloon, sxp, image
>>   File "/usr/pkg/lib/python2.7/site-packages/xen/xend/image.py", line 46, in 
>> <module>
>>     xc = xen.lowlevel.xc.xc()
>> xen.lowlevel.xc.Error: (1, 'Internal error', 'xc_interface_open failed: No 
>> such file or directory')
>> =====
>>
>> I'm going to try xen-debug.gz to see if there is more info.
>> I have 768MB for memory for dom0 - could that be an issue with xen4.2.3?
>> johnh...
>> _________________________________
>> From: port-xen-owner%NetBSD.org@localhost 
>> [port-xen-owner%NetBSD.org@localhost] on behalf of Manuel Bouyer 
>> [bouyer%antioche.eu.org@localhost]
>> Sent: Tuesday, October 15, 2013 1:36 PM
>> To: John Hayward
>> Cc: Adiel; Takahiro HAYASHI; port-xen%NetBSD.org@localhost; Mike C.
>> Subject: Re: Reboot on *DOM0* while/after installing GPLPV drivers
>>
>> On Tue, Oct 15, 2013 at 06:33:07PM +0000, John Hayward wrote:
>>> Thanks for the note back.
>>> The initial problem was that I had put the xen.gz in a different directory 
>>> - I got that fixed.
>>> I also removed the duplicate xend in /etc/rc.d
>>>
>>> Now I am putting things back to 4.2.3 and when xend starts it hangs and 
>>> when HUP is sent:
>>> ====
>>> ^CTraceback (most recent call last):
>>>   File "/usr/pkg/sbin/xend", line 110, in <module>
>>>     sys.exit(main())
>>>   File "/usr/pkg/sbin/xend", line 92, in main
>>>     return daemon.start()
>>>   File "/usr/pkg/lib/python2.7/site-packages/xen/xend/server/SrvDaemon.py", 
>>> line 181, in start
>>>     s = r.read()
>>> KeyboardInterrupt
>>> ====
>>> Looking at the svrDaemond.pv it appears to be attempting to read from a 
>>> socket of a forked child.
>>>
>>> Any program attempting to access /kern (including on shutdown) seems to get 
>>> wedged.
>>
>> Can you see on what channel it's wedged ?
>> ^T, or ps axl should tell you.
>>
>> --
>> Manuel Bouyer <bouyer%antioche.eu.org@localhost>
>>      NetBSD: 26 ans d'experience feront toujours la difference
>> --
>>
>>
> 
> --
> Melhores Cumprimentos // Best Regards
> ------------------------------------------------------------------------
> Miguel Clara
> *nix Sys Admin Freelance
> 
> 

-- 
Melhores Cumprimentos // Best Regards
------------------------------------------------------------------------
Miguel Clara
*nix Sys Admin Freelance



http://www.linkedin.com/in/miguelmclara/
Mike_C_PT <https://twitter.com/Mike_C_PT>
http://about.me/miguelmclara
------------------------------------------------------------------------