From: list user <xktnniuymlla@mailinator.com>
To: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: [Xen-devel] Re: BUG? domU reboot fails when using "pci =" option
Date: Thu, 04 May 2006 16:04:28 -0700 [thread overview]
Message-ID: <445A887C.7080900@mailinator.com> (raw)
In-Reply-To: <1146774246.10010.16.camel@moss-tarheels.epoch.ncsc.mil>
Ryan wrote:
> On Thu, 2006-05-04 at 10:53 -0700, list user wrote:
>
>>list user wrote:
>>
>>Additional info.
>>
>>If xend and xendomains are set to run automatically at boot time via
>>chkconfig the same error occurs, but ONLY when the pci device has been
>>exported to a domU. An "xm list" starts at domid 2, showing that one
>>domU has failed at startup.
>>
>>Again, the error is familiar, but this time displays on the domain-0
>>console:
>>
>> local variable dev_config referenced before assignment
>>
>>:m)
>>
>>
>>>Hope that's helpful to someone.
>>>
>>>Mike Wright
>>>
>
>
> I'm not quite sure how this python error could be causing your reboot
> problem, but you did find a typo in that script. I'll submit a patch for
> it to xen-unstable. If you'd like to fix it yourself, just change
> dev_config to config.
Thanks Ryan,
I tried the fix but it just gave a different symptom. (same error,
different variable)
So... rpm --erase xen JIC there were any ghosts around. Manually
removed all traces of xen from the system. Then did a ./install.sh from
the xen-3.0.2-2 directory, which had a clean "make world".
The results are the same.
I've found a more generic error about a local variable being used before
assignment, but I think it's referring to dev_config.
Again, this only happens on auto-boot or domU reboot, and only when
there is a "pci =" line in the domU's definition file.
Any ideas how I can help debug this?
:m)
>
> Did you upgrade your box from xen 2.0.x to xen 3.0.2? That code path is
> unlikely to be followed unless you either used an SXP configuration file
> (which I didn't think you had done because "pci = ['00:0d.0']" wouldn't
> work in an SXP file) or your Xen 3.0.2 installation didn't completely
> overwrite all of the Xen 2.0.x files.
>
> Ryan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
prev parent reply other threads:[~2006-05-04 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 16:47 BUG? domU reboot fails when using "pci =" option list user
2006-05-04 17:53 ` list user
2006-05-04 20:24 ` Ryan
2006-05-04 23:04 ` list user [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=445A887C.7080900@mailinator.com \
--to=xktnniuymlla@mailinator.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.