This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Weekly Bug List Update

Xen developers:


This week we are only tracking two new bugs in Bugzilla: 1224 & 1226.  You can find out more information on this week’s bug at http://wiki.xensource.com/xenwiki/XenBugs.  This wiki site also contains previous weekly bug lists.


If you would like to add comments about this bug, please update the Bugzilla database or the Wiki as I will monitor both to ensure that no one does any duplicate work. As always, if you have any questions or ideas about the community, please contact me via email or phone.


BUG 1224

I built and installed Xen 3.2 onto a Fedora system running x86_64 Fedora 6. 
pygrub built and installed, but when I created a config that used pygrub as the
bootloader, pygrub failed with an error 'can't find fsimage'.
I looked at the pygrub code, and found the line:
sys.path = [ '/usr/lib/python' ] + sys.path
I changed this to:
sys.path = [ '/usr/lib64/python' ] + sys.path
and everything worked normally.
Not sure if it's an implementation issue on my end (quite possible) or if there
is a way to detect where the fsimage stuff lands on a 64-bit system.
relatively easy fix, so minimal pain, but I thought it may help to bring it up.


BUG 1226

Sometimes while installing some applications (or updating the windows operating

system) a bluescreen will be displayed.

This error occures on Microsoft Windows 2003 Server Standard AND Enterprise. It

never occures, when installed directly on the physical server..

Screenshot of bluescreen:


NOTE – Files are uploaded to this bug tracking with more details




Stephen Spector

Sr. Program Manager, Xen.org




Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>