[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] GPLPV questions



Il 13/02/2013 23:26, James Harper ha scritto:
I have tried to build gplpv from source with makedist.bat but it gave me
some errors about files not found.
I saw that latest commits were big. Is there something incomplete and
must I wait other commits before build it?
It's possible I missed a commit but I can't see any missing files.

Can you post the output of makedist?

But yes the latest commits involve a pretty major change and I haven't tested 
save/restore yet so that is probably more broken than before.

I have installed WDK 7600.1 and wix3, I have downloaded gplpv hg at rev 1020. I launched makedist.bat but it gives same errors on each arch build, see below the output:

...
1>Compiling - waitnopendinginstallevents\waitnopendinginstallevents.c
1>Linking Executable - waitnopendinginstallevents\waitnopendinginstallevents\obj
fre_wlh_amd64\amd64\waitnopendinginstallevents.exe
BUILD: Finish time: Thu Feb 14 11:53:50 2013
BUILD: Done

    75 files compiled
    2 libraries built
    8 executables built
Microsoft (R) Windows Installer Xml Compiler version 3.0.5419.0
Copyright (C) Microsoft Corporation. All rights reserved.

installer.wxs
Microsoft (R) Windows Installer Xml Linker version 3.0.5419.0
Copyright (C) Microsoft Corporation. All rights reserved.

C:\hg\win-pvdrivers\installer.wxs(75) : error LGHT0103 : The system cannot find
the file 'xenpci\objfre_wlh_AMD64\amd64\xenpci.cat'.
C:\hg\win-pvdrivers\installer.wxs(78) : error LGHT0103 : The system cannot find
the file 'xenpci\objfre_wlh_AMD64\amd64\WdfCoInstaller01009.dll'.
C:\hg\win-pvdrivers\installer.wxs(95) : error LGHT0103 : The system cannot find
the file 'xenvbd_storport\objfre_wlh_AMD64\amd64\xenvbd.cat'.
C:\hg\win-pvdrivers\installer.wxs(105) : error LGHT0103 : The system cannot find
 the file 'xenscsi\objfre_wlh_AMD64\amd64\xenscsi.cat'.
C:\hg\win-pvdrivers\installer.wxs(106) : error LGHT0103 : The system cannot find
 the file 'xenscsi\objfre_wlh_AMD64\amd64\xenscsi.inf'.
C:\hg\win-pvdrivers\installer.wxs(107) : error LGHT0103 : The system cannot find
 the file 'xenscsi\objfre_wlh_AMD64\amd64\xenscsi.sys'.
C:\hg\win-pvdrivers\installer.wxs(114) : error LGHT0103 : The system cannot find
 the file 'xennet\objfre_wlh_AMD64\amd64\xennet.cat'.
C:\hg\win-pvdrivers\installer.wxs(123) : error LGHT0103 : The system cannot find
 the file 'xenusb\objfre_wlh_AMD64\amd64\xenusb.cat'.
C:\hg\win-pvdrivers\installer.wxs(124) : error LGHT0103 : The system cannot find
 the file 'xenusb\objfre_wlh_AMD64\amd64\xenusb.inf'.
C:\hg\win-pvdrivers\installer.wxs(125) : error LGHT0103 : The system cannot find
 the file 'xenusb\objfre_wlh_AMD64\amd64\xenusb.sys'.
C:\hg\win-pvdrivers\installer.wxs(127) : error LGHT0103 : The system cannot find
 the file 'xenpci\objfre_wlh_AMD64\amd64\WdfCoInstaller01009.dll'.
SignTool Error: File not found: /t


I would like to see if new build fix network not working after restore
on windows domUs using upstream qemu.
Dom0 is wheezy with xen-unstable from source.
Tested with Windows 7 pro 64 bit with gplpv 0.11.0.357, I not found
error on xen for now, probably is problem of gplpv with qemu upstream.
Linux hvm domUs seem not have that problem, tested with quantal (ubuntu
12.10) and network works also after restore.
If you need more details and tests tell me and I'll post it.

Another problem present on both traditional/upstream qemu  with
older/new xen and  older/new gplpv is domU's time not correctly updated
after restore (it remains the time at the save operation), this is a big
problem with windows domUs (DC and client) in a windows domain where
the time source is DC by default.
I noticed that recently. I can't think how it could be a GPLPV bug though.

What can we try to narrow down the problem?


James


Attachment: smime.p7s
Description: Firma crittografica S/MIME

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.