8:18 a.m.
Hi all,
If people have time to try out a tentative first "Libvirt Windows Installer",
it's
online here:
http://libvirt.org/sources/win32_experimental/Libvirt-0.8.5-0.exe
At the moment it includes the libvirt development headers and libraries
for compiling against, plus the virsh shell with it's needed dependencies,
and that's about it.
It's been compiled on Windows 7 x86_64, but (in theory) might also work
on earlier windows versions like Vista and XP. (not yet tested)
A couple of notes:
+ This installer is _not_ production ready. More like early, early stage
alpha. ;)
+ This installer just repackages the files compiled using Matthias
Bolte's msys_setup scripting:
https://github.com/photron/msys_setup
+ This is a .exe installer, created using NSIS. Mathias Bolte mentioned,
it might be a better idea to use something that creates .msi files, which
I kind of agree with. So, next versions will probably not be NSIS based,
but no idea what they will be based upon yet.
+ The only connection type I've tried, and that's known to work for sure,
is qemu+tcp://. qemu+ssh:// doesn't work on windows (at this stage),
and qemu+tls:// (on windows) doesn't work due to a problem with
GnuTLS.
If anyone has time to look into the GnuTLS problem, that would be really
helpful. :)
+ This version includes Python bindings, but I haven't tried/tested them. :)
+ Suggestions for what else to include are welcome. ie. other bindings (C#,
what else?), and so on
+ The NSIS installer scripting is on github if anyone's interested:
https://github.com/justinclift/nsis_libvirt_installer
Regards and best wishes,
Justin Clift
8:45 a.m.
?Hi Justin,
I have made a MSI/EXE installer with these libs also for my personal use. I
don't know if it can help.
I think it could be a good idea to include C# bindings in the installer, but
for that, I have to work on the GAC inscription of the bindings...
I'll take a look on your installer, and give a return.
Nice to see that anyway, I have searched for it a year ago ;)
Arnaud
--------------------------------------------------
From: "Justin Clift" <jclift(a)redhat.com>
Sent: Sunday, November 14, 2010 3:18 PM
To: <libvir-list(a)redhat.com>
Cc: "Matthias Bolte" <matthias.bolte(a)googlemail.com>;
<arnaud.champion(a)devatom.fr>
Subject: Experimental 32-bit windows libvirt installer
Hi all,
If people have time to try out a tentative first "Libvirt Windows
Installer", it's
online here:
http://libvirt.org/sources/win32_experimental/Libvirt-0.8.5-0.exe
At the moment it includes the libvirt development headers and libraries
for compiling against, plus the virsh shell with it's needed dependencies,
and that's about it.
It's been compiled on Windows 7 x86_64, but (in theory) might also work
on earlier windows versions like Vista and XP. (not yet tested)
A couple of notes:
+ This installer is _not_ production ready. More like early, early stage
alpha. ;)
+ This installer just repackages the files compiled using Matthias
Bolte's msys_setup scripting:
https://github.com/photron/msys_setup
+ This is a .exe installer, created using NSIS. Mathias Bolte mentioned,
it might be a better idea to use something that creates .msi files,
which
I kind of agree with. So, next versions will probably not be NSIS
based,
but no idea what they will be based upon yet.
+ The only connection type I've tried, and that's known to work for sure,
is qemu+tcp://. qemu+ssh:// doesn't work on windows (at this stage),
and qemu+tls:// (on windows) doesn't work due to a problem with
GnuTLS.
If anyone has time to look into the GnuTLS problem, that would be
really
helpful. :)
+ This version includes Python bindings, but I haven't tried/tested them.
:)
+ Suggestions for what else to include are welcome. ie. other bindings
(C#,
what else?), and so on
+ The NSIS installer scripting is on github if anyone's interested:
https://github.com/justinclift/nsis_libvirt_installer
Regards and best wishes,
Justin Clift
8:51 a.m.
?It seems your libvirt hasn't been compiled with esx support. No problem at
all, but if you add the esx support you also need the libcurl dll.
Arnaud
--------------------------------------------------
From: <arnaud.champion(a)devatom.fr>
Sent: Sunday, November 14, 2010 3:45 PM
To: "Justin Clift" <jclift(a)redhat.com>; <libvir-list(a)redhat.com>
Subject: Re: [libvirt] Experimental 32-bit windows libvirt installer
?Hi Justin,
I have made a MSI/EXE installer with these libs also for my personal use.
I don't know if it can help.
I think it could be a good idea to include C# bindings in the installer,
but for that, I have to work on the GAC inscription of the bindings...
I'll take a look on your installer, and give a return.
Nice to see that anyway, I have searched for it a year ago ;)
Arnaud
--------------------------------------------------
From: "Justin Clift" <jclift(a)redhat.com>
Sent: Sunday, November 14, 2010 3:18 PM
To: <libvir-list(a)redhat.com>
Cc: "Matthias Bolte" <matthias.bolte(a)googlemail.com>;
<arnaud.champion(a)devatom.fr>
Subject: Experimental 32-bit windows libvirt installer
> Hi all,
>
> If people have time to try out a tentative first "Libvirt Windows
> Installer", it's
> online here:
>
> http://libvirt.org/sources/win32_experimental/Libvirt-0.8.5-0.exe
>
> At the moment it includes the libvirt development headers and libraries
> for compiling against, plus the virsh shell with it's needed
> dependencies,
> and that's about it.
>
> It's been compiled on Windows 7 x86_64, but (in theory) might also work
> on earlier windows versions like Vista and XP. (not yet tested)
>
> A couple of notes:
>
> + This installer is _not_ production ready. More like early, early stage
> alpha. ;)
>
> + This installer just repackages the files compiled using Matthias
> Bolte's msys_setup scripting:
>
> https://github.com/photron/msys_setup
>
> + This is a .exe installer, created using NSIS. Mathias Bolte mentioned,
> it might be a better idea to use something that creates .msi files,
> which
> I kind of agree with. So, next versions will probably not be NSIS
> based,
> but no idea what they will be based upon yet.
>
> + The only connection type I've tried, and that's known to work for sure,
> is qemu+tcp://. qemu+ssh:// doesn't work on windows (at this stage),
> and qemu+tls:// (on windows) doesn't work due to a problem with
> GnuTLS.
>
> If anyone has time to look into the GnuTLS problem, that would be
> really
> helpful. :)
>
> + This version includes Python bindings, but I haven't tried/tested them.
> :)
>
> + Suggestions for what else to include are welcome. ie. other bindings
> (C#,
> what else?), and so on
>
> + The NSIS installer scripting is on github if anyone's interested:
>
> https://github.com/justinclift/nsis_libvirt_installer
>
> Regards and best wishes,
>
> Justin Clift
--
libvir-list mailing list
libvir-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
9:17 a.m.
On 15/11/2010, at 1:51 AM, <arnaud.champion(a)devatom.fr> wrote:
?It seems your libvirt hasn't been compiled with esx support. No
problem at all, but if you add the esx support you also need the libcurl dll.
Yeah. ESX relies on TLS being supported, and there are two options:
+ GnuTLS, which is LGPL licensed, but broken on windows at the moment
+ PolarSSL, which is GPL licensed, but works
The GPL license for PolarSSL rules it out, so that means we're only able to compile
against
the broken GnuTLS.
Hopefully someone that knows more about GnuTLS and Windows will be able to fix it
the problem. :)
9:21 a.m.
On 15/11/2010, at 1:45 AM, <arnaud.champion(a)devatom.fr> wrote:
?Hi Justin,
I have made a MSI/EXE installer with these libs also for my personal use. I don't
know if it can help.
Sure. Which installer creation package did you use?
I haven't yet looked around for something better than NSIS, but will shortly. :)
I think it could be a good idea to include C# bindings in the
installer, but for that, I have to work on the GAC inscription of the bindings...
Ok. I'd like to include them too. If you have time to work on the GAC bit, then we
can package them when you say they're ready. :)
I'll take a look on your installer, and give a return.
Nice to see that anyway, I have searched for it a year ago ;)
Yeah. Hoping to make this easier for future developers over time. :)
9:38 a.m.
?I have used visual studio 2010 to create a standard setup, but for now it
just provide dll, no virsh but why not...
GAC inscription is now next goal. I'll try to see that this week.
Arnaud
--------------------------------------------------
From: "Justin Clift" <jclift(a)redhat.com>
Sent: Sunday, November 14, 2010 4:21 PM
To: <arnaud.champion(a)devatom.fr>
Cc: <libvir-list(a)redhat.com>; "Matthias Bolte"
<matthias.bolte(a)googlemail.com>
Subject: Re: Experimental 32-bit windows libvirt installer
On 15/11/2010, at 1:45 AM, <arnaud.champion(a)devatom.fr> wrote:
> ?Hi Justin,
>
> I have made a MSI/EXE installer with these libs also for my personal use.
> I don't know if it can help.
Sure. Which installer creation package did you use?
I haven't yet looked around for something better than NSIS, but will
shortly. :)
> I think it could be a good idea to include C# bindings in the installer,
> but for that, I have to work on the GAC inscription of the bindings...
Ok. I'd like to include them too. If you have time to work on the GAC
bit, then we can package them when you say they're ready. :)
> I'll take a look on your installer, and give a return.
>
> Nice to see that anyway, I have searched for it a year ago ;)
Yeah. Hoping to make this easier for future developers over time. :)
9:41 a.m.
On 15/11/2010, at 2:38 AM, <arnaud.champion(a)devatom.fr> wrote:
?I have used visual studio 2010 to create a standard setup, but for
now it just provide dll, no virsh but why not...
GAC inscription is now next goal. I'll try to see that this week.
Heh, no worries. I'll look around for an open source tool that does it instead,
as using Visual Studio 2010 just for creating an installer seems like a bit
of overkill (for me). :)
9:49 a.m.
?Well, I understand :) For me, VS is my usual development tools so... :)
--------------------------------------------------
From: "Justin Clift" <jclift(a)redhat.com>
Sent: Sunday, November 14, 2010 4:41 PM
To: <arnaud.champion(a)devatom.fr>
Cc: <libvir-list(a)redhat.com>; "Matthias Bolte"
<matthias.bolte(a)googlemail.com>
Subject: Re: Experimental 32-bit windows libvirt installer
On 15/11/2010, at 2:38 AM, <arnaud.champion(a)devatom.fr> wrote:
> ?I have used visual studio 2010 to create a standard setup, but for now
> it just provide dll, no virsh but why not...
> GAC inscription is now next goal. I'll try to see that this week.
Heh, no worries. I'll look around for an open source tool that does it
instead,
as using Visual Studio 2010 just for creating an installer seems like a
bit
of overkill (for me). :)
7:41 p.m.
On 15/11/2010, at 2:49 AM, <arnaud.champion(a)devatom.fr>
<arnaud.champion(a)devatom.fr> wrote:
?Well, I understand :) For me, VS is my usual development tools so...
:)
Yep, all good.
Just as a follow up for anyone interested, this installer is also known to function
"ok" on WinXP SP3.
It installs and uninstalls ok, and the installed virsh.exe client program is able to
connect to a remote QEMU instance (on Fedora) using qemu+tcp://.
For the creation of .msi package files, WiX seems to be the right tool these days (open
source):
http://wix.sourceforge.net
Actually kind of think I've heard of it before, as it got some press a few years back
from being one of the very first Open Source projects by Microsoft itself.
(or something along those lines)
Still it looks like the best candidate. We'll see how it goes. Next weekend
probably. :)
Regards and best wishes,
Justin Clift
4:44 a.m.
On Mon, Nov 15, 2010 at 12:41:35PM +1100, Justin Clift wrote:
For the creation of .msi package files, WiX seems to be the right
tool these days (open source):
http://wix.sourceforge.net
Actually kind of think I've heard of it before, as it got some press
a few years back from being one of the very first Open Source
projects by Microsoft itself. (or something along those lines)
WiX itself is open source, but it has closed source dependencies, so
it is of no use. That's why we're still using NSIS, despite all its
failings.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://et.redhat.com/~rjones/virt-top
11:42 a.m.
On 16/11/2010, at 9:44 PM, Richard W.M. Jones wrote:
On Mon, Nov 15, 2010 at 12:41:35PM +1100, Justin Clift wrote:
> For the creation of .msi package files, WiX seems to be the right
> tool these days (open source):
>
> http://wix.sourceforge.net
>
> Actually kind of think I've heard of it before, as it got some press
> a few years back from being one of the very first Open Source
> projects by Microsoft itself. (or something along those lines)
WiX itself is open source, but it has closed source dependencies, so
it is of no use. That's why we're still using NSIS, despite all its
failings.
Do you remember what the closed source dependencies are?
Other Open Source projects are producing MSI's (ie 7-zip), so it's
something we should follow up. :)
12:26 p.m.
On Wed, Nov 17, 2010 at 04:42:46AM +1100, Justin Clift wrote:
On 16/11/2010, at 9:44 PM, Richard W.M. Jones wrote:
> On Mon, Nov 15, 2010 at 12:41:35PM +1100, Justin Clift wrote:
>> For the creation of .msi package files, WiX seems to be the right
>> tool these days (open source):
>>
>> http://wix.sourceforge.net
>>
>> Actually kind of think I've heard of it before, as it got some press
>> a few years back from being one of the very first Open Source
>> projects by Microsoft itself. (or something along those lines)
>
> WiX itself is open source, but it has closed source dependencies, so
> it is of no use. That's why we're still using NSIS, despite all its
> failings.
Do you remember what the closed source dependencies are?
The bottom line is this email:
http://www.mailinglistarchive.com/fedora-devel-list@redhat.com/msg61468.html
I don't know whether this is true, or still true, but I do know that
the build system for WiX is out of bizarro-land. You will need to ask
on the Fedora Mono SIG list to find out what the current status of WiX
is (and how to build it on Fedora).
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://et.redhat.com/~rjones/libguestfs/
See what it can do: http://et.redhat.com/~rjones/libguestfs/recipes.html
1:57 p.m.
On 17/11/2010, at 5:26 AM, Richard W.M. Jones wrote:
The bottom line is this email:
http://www.mailinglistarchive.com/fedora-devel-list@redhat.com/msg61468.html
I don't know whether this is true, or still true, but I do know that
the build system for WiX is out of bizarro-land. You will need to ask
on the Fedora Mono SIG list to find out what the current status of WiX
is (and how to build it on Fedora).
Thanks Rich. Will look into it, probably on the weekend. The MS SDK
mentioned doesn't sound like a problem, unless it's licensing has GPL/LGPL
unfriendly stuff in it (possible).
Building on Windows anyway, so not really concerned about cross
compilation. :)
3:24 p.m.
On 11/16/2010 02:57 PM, Justin Clift wrote:
On 17/11/2010, at 5:26 AM, Richard W.M. Jones wrote:
> The bottom line is this email:
>
> http://www.mailinglistarchive.com/fedora-devel-list@redhat.com/msg61468.html
>
> I don't know whether this is true, or still true, but I do know that
> the build system for WiX is out of bizarro-land. You will need to ask
> on the Fedora Mono SIG list to find out what the current status of WiX
> is (and how to build it on Fedora).
Thanks Rich. Will look into it, probably on the weekend. The MS SDK
mentioned doesn't sound like a problem, unless it's licensing has GPL/LGPL
unfriendly stuff in it (possible).
Building on Windows anyway, so not really concerned about cross
compilation. :)
But that may be a problem for others in the future who may want to
enhance it or fix bugs.
3:37 p.m.
On 17/11/2010, at 8:24 AM, Laine Stump wrote:
On 11/16/2010 02:57 PM, Justin Clift wrote:
> On 17/11/2010, at 5:26 AM, Richard W.M. Jones wrote:
>> The bottom line is this email:
>>
>> http://www.mailinglistarchive.com/fedora-devel-list@redhat.com/msg61468.html
>>
>> I don't know whether this is true, or still true, but I do know that
>> the build system for WiX is out of bizarro-land. You will need to ask
>> on the Fedora Mono SIG list to find out what the current status of WiX
>> is (and how to build it on Fedora).
> Thanks Rich. Will look into it, probably on the weekend. The MS SDK
> mentioned doesn't sound like a problem, unless it's licensing has GPL/LGPL
> unfriendly stuff in it (possible).
>
> Building on Windows anyway, so not really concerned about cross
> compilation. :)
But that may be a problem for others in the future who may want to enhance it or fix
bugs.
Sure. "Tough luck" for the moment. :)
4:42 a.m.
On Mon, Nov 15, 2010 at 02:41:15AM +1100, Justin Clift wrote:
On 15/11/2010, at 2:38 AM, <arnaud.champion(a)devatom.fr> wrote:
> ?I have used visual studio 2010 to create a standard setup, but for now it just
provide dll, no virsh but why not...
> GAC inscription is now next goal. I'll try to see that this week.
Heh, no worries. I'll look around for an open source tool that does it instead,
as using Visual Studio 2010 just for creating an installer seems like a bit
of overkill (for me). :)
We previously built the installer from the Fedora Windows
cross-compiler:
http://www.redhat.com/archives/libvir-list/2008-October/msg00191.html
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://et.redhat.com/~rjones/virt-top
4:56 a.m.
2010/11/16 Richard W.M. Jones <rjones(a)redhat.com>:
On Mon, Nov 15, 2010 at 02:41:15AM +1100, Justin Clift wrote:
> On 15/11/2010, at 2:38 AM, <arnaud.champion(a)devatom.fr> wrote:
> > ?I have used visual studio 2010 to create a standard setup, but for now it just
provide dll, no virsh but why not...
> > GAC inscription is now next goal. I'll try to see that this week.
>
> Heh, no worries. I'll look around for an open source tool that does it instead,
> as using Visual Studio 2010 just for creating an installer seems like a bit
> of overkill (for me). :)
We previously built the installer from the Fedora Windows
cross-compiler:
http://www.redhat.com/archives/libvir-list/2008-October/msg00191.html
Rich.
I recently tested the Fedora provided mingw32-libvirt on Windows and
virsh just segfaults before main() for me.
Justin, msys_setup contains a download_libvirt-fedora.sh script that
downloads and unpacks to
msys\fedora\usr\i686-pc-mingw32\sys-root\mingw\bin
if you want to give that a try.
Matthias
5 a.m.
On Tue, Nov 16, 2010 at 11:56:12AM +0100, Matthias Bolte wrote:
2010/11/16 Richard W.M. Jones <rjones(a)redhat.com>:
> On Mon, Nov 15, 2010 at 02:41:15AM +1100, Justin Clift wrote:
>> On 15/11/2010, at 2:38 AM, <arnaud.champion(a)devatom.fr> wrote:
>> > ?I have used visual studio 2010 to create a standard setup, but for now it
just provide dll, no virsh but why not...
>> > GAC inscription is now next goal. I'll try to see that this week.
>>
>> Heh, no worries. I'll look around for an open source tool that does it
instead,
>> as using Visual Studio 2010 just for creating an installer seems like a bit
>> of overkill (for me). :)
>
> We previously built the installer from the Fedora Windows
> cross-compiler:
>
> http://www.redhat.com/archives/libvir-list/2008-October/msg00191.html
>
> Rich.
>
I recently tested the Fedora provided mingw32-libvirt on Windows and
virsh just segfaults before main() for me.
Sounds like a bug in a shared library. Can you get a stack trace
from this?
(This is not a generic problem -- obviously even huge Windows binaries
built using the cross-compiler do work)
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
New in Fedora 11: Fedora Windows cross-compiler. Compile Windows
programs, test, and build Windows installers. Over 70 libraries supprt'd
http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw
5:09 a.m.
2010/11/16 Richard W.M. Jones <rjones(a)redhat.com>:
On Tue, Nov 16, 2010 at 11:56:12AM +0100, Matthias Bolte wrote:
> 2010/11/16 Richard W.M. Jones <rjones(a)redhat.com>:
> > On Mon, Nov 15, 2010 at 02:41:15AM +1100, Justin Clift wrote:
> >> On 15/11/2010, at 2:38 AM, <arnaud.champion(a)devatom.fr> wrote:
> >> > ?I have used visual studio 2010 to create a standard setup, but for now
it just provide dll, no virsh but why not...
> >> > GAC inscription is now next goal. I'll try to see that this week.
> >>
> >> Heh, no worries. I'll look around for an open source tool that does it
instead,
> >> as using Visual Studio 2010 just for creating an installer seems like a bit
> >> of overkill (for me). :)
> >
> > We previously built the installer from the Fedora Windows
> > cross-compiler:
> >
> > http://www.redhat.com/archives/libvir-list/2008-October/msg00191.html
> >
> > Rich.
> >
>
> I recently tested the Fedora provided mingw32-libvirt on Windows and
> virsh just segfaults before main() for me.
Sounds like a bug in a shared library. Can you get a stack trace
from this?
(This is not a generic problem -- obviously even huge Windows binaries
built using the cross-compiler do work)
Rich.
Sure, here it is:
Program received signal SIGSEGV, Segmentation fault.
0x6cc7cf5f in _pei386_runtime_relocator ()
from F:\msys_setup\msys\fedora\usr\i686-pc-mingw32\sys-root\mingw\bin\libvirt-0.dll
(gdb) bt
#0 0x6cc7cf5f in _pei386_runtime_relocator ()
from F:\msys_setup\msys\fedora\usr\i686-pc-mingw32\sys-root\mingw\bin\libvirt-0.dll
#1 0x00000001 in ?? ()
#2 0x0022f9f0 in ?? ()
#3 0x6cc0113d in DllMainCRTStartup@12 (hDll=<value optimized out>,
dwReason=<value optimized out>, lpReserved=<value optimized out>)
at dllcrt1.c:67
#4 0x7c9111a7 in ntdll!LdrSetAppCompatDllRedirectionCallback ()
from C:\WINDOWS\system32\ntdll.dll
#5 0x6cc00000 in ?? ()
#6 0x7c92cbab in ntdll!LdrHotPatchRoutine ()
from C:\WINDOWS\system32\ntdll.dll
#7 0x7c93173e in ntdll!RtlMapGenericMask ()
from C:\WINDOWS\system32\ntdll.dll
#8 0x7c931639 in ntdll!RtlMapGenericMask ()
from C:\WINDOWS\system32\ntdll.dll
#9 0x7c91eac7 in ntdll!LdrCreateOutOfProcessImage ()
from C:\WINDOWS\system32\ntdll.dll
(gdb)
I used this packages from http://kojipkgs.fedoraproject.org/packages
mingw32-libvirt-0.8.3-1.fc15.noarch.rpm
mingw32-libvirt-debuginfo-0.8.3-1.fc15.noarch.rpm
mingw32-gnutls-2.6.4-3.fc13.noarch.rpm
mingw32-libgcrypt-1.4.4-4.fc12.noarch.rpm
mingw32-libgpg-error-1.6-13.fc13.noarch.rpm
mingw32-gettext-0.17-12.fc12.noarch.rpm
mingw32-iconv-1.12-12.fc12.noarch.rpm
mingw32-zlib-1.2.3-19.fc12.noarch.rpm
mingw32-portablexdr-4.9.1-1.fc15.noarch.rpm
mingw32-libxml2-2.7.6-1.fc13.noarch.rpm
mingw32-readline-5.2-7.fc12.noarch.rpm
mingw32-termcap-1.3.1-8.fc12.noarch.rpm
Matthias
5:20 a.m.
[CC-ing to the cross-compiler mailing list]
On Tue, Nov 16, 2010 at 12:09:29PM +0100, Matthias Bolte wrote:
2010/11/16 Richard W.M. Jones <rjones(a)redhat.com>:
> On Tue, Nov 16, 2010 at 11:56:12AM +0100, Matthias Bolte wrote:
>> I recently tested the Fedora provided mingw32-libvirt on Windows and
>> virsh just segfaults before main() for me.
>
> Sounds like a bug in a shared library. Can you get a stack trace
> from this?
Sure, here it is:
Program received signal SIGSEGV, Segmentation fault.
0x6cc7cf5f in _pei386_runtime_relocator ()
from F:\msys_setup\msys\fedora\usr\i686-pc-mingw32\sys-root\mingw\bin\libvirt-0.dll
(gdb) bt
#0 0x6cc7cf5f in _pei386_runtime_relocator ()
from F:\msys_setup\msys\fedora\usr\i686-pc-mingw32\sys-root\mingw\bin\libvirt-0.dll
#1 0x00000001 in ?? ()
#2 0x0022f9f0 in ?? ()
#3 0x6cc0113d in DllMainCRTStartup@12 (hDll=<value optimized out>,
dwReason=<value optimized out>, lpReserved=<value optimized out>)
at dllcrt1.c:67
#4 0x7c9111a7 in ntdll!LdrSetAppCompatDllRedirectionCallback ()
from C:\WINDOWS\system32\ntdll.dll
#5 0x6cc00000 in ?? ()
#6 0x7c92cbab in ntdll!LdrHotPatchRoutine ()
from C:\WINDOWS\system32\ntdll.dll
#7 0x7c93173e in ntdll!RtlMapGenericMask ()
from C:\WINDOWS\system32\ntdll.dll
#8 0x7c931639 in ntdll!RtlMapGenericMask ()
from C:\WINDOWS\system32\ntdll.dll
#9 0x7c91eac7 in ntdll!LdrCreateOutOfProcessImage ()
from C:\WINDOWS\system32\ntdll.dll
(gdb)
I used this packages from http://kojipkgs.fedoraproject.org/packages
mingw32-libvirt-0.8.3-1.fc15.noarch.rpm
mingw32-libvirt-debuginfo-0.8.3-1.fc15.noarch.rpm
mingw32-gnutls-2.6.4-3.fc13.noarch.rpm
mingw32-libgcrypt-1.4.4-4.fc12.noarch.rpm
mingw32-libgpg-error-1.6-13.fc13.noarch.rpm
mingw32-gettext-0.17-12.fc12.noarch.rpm
mingw32-iconv-1.12-12.fc12.noarch.rpm
mingw32-zlib-1.2.3-19.fc12.noarch.rpm
mingw32-portablexdr-4.9.1-1.fc15.noarch.rpm
mingw32-libxml2-2.7.6-1.fc13.noarch.rpm
mingw32-readline-5.2-7.fc12.noarch.rpm
mingw32-termcap-1.3.1-8.fc12.noarch.rpm
Matthias
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into Xen guests.
http://et.redhat.com/~rjones/virt-p2v
12:04 p.m.
Richard W.M. Jones schreef op di 16-11-2010 om 11:20 [+0000]:
[CC-ing to the cross-compiler mailing list]
On Tue, Nov 16, 2010 at 12:09:29PM +0100, Matthias Bolte wrote:
> 2010/11/16 Richard W.M. Jones <rjones(a)redhat.com>:
> > On Tue, Nov 16, 2010 at 11:56:12AM +0100, Matthias Bolte wrote:
> >> I recently tested the Fedora provided mingw32-libvirt on Windows and
> >> virsh just segfaults before main() for me.
> >
> > Sounds like a bug in a shared library. Can you get a stack trace
> > from this?
>
> Sure, here it is:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x6cc7cf5f in _pei386_runtime_relocator ()
> from
F:\msys_setup\msys\fedora\usr\i686-pc-mingw32\sys-root\mingw\bin\libvirt-0.dll
> (gdb) bt
> #0 0x6cc7cf5f in _pei386_runtime_relocator ()
> from
F:\msys_setup\msys\fedora\usr\i686-pc-mingw32\sys-root\mingw\bin\libvirt-0.dll
> #1 0x00000001 in ?? ()
> #2 0x0022f9f0 in ?? ()
> #3 0x6cc0113d in DllMainCRTStartup@12 (hDll=<value optimized out>,
> dwReason=<value optimized out>, lpReserved=<value optimized out>)
> at dllcrt1.c:67
> #4 0x7c9111a7 in ntdll!LdrSetAppCompatDllRedirectionCallback ()
> from C:\WINDOWS\system32\ntdll.dll
> #5 0x6cc00000 in ?? ()
> #6 0x7c92cbab in ntdll!LdrHotPatchRoutine ()
> from C:\WINDOWS\system32\ntdll.dll
> #7 0x7c93173e in ntdll!RtlMapGenericMask ()
> from C:\WINDOWS\system32\ntdll.dll
> #8 0x7c931639 in ntdll!RtlMapGenericMask ()
> from C:\WINDOWS\system32\ntdll.dll
> #9 0x7c91eac7 in ntdll!LdrCreateOutOfProcessImage ()
> from C:\WINDOWS\system32\ntdll.dll
> (gdb)
>
> I used this packages from http://kojipkgs.fedoraproject.org/packages
>
> mingw32-libvirt-0.8.3-1.fc15.noarch.rpm
> mingw32-libvirt-debuginfo-0.8.3-1.fc15.noarch.rpm
> mingw32-gnutls-2.6.4-3.fc13.noarch.rpm
> mingw32-libgcrypt-1.4.4-4.fc12.noarch.rpm
> mingw32-libgpg-error-1.6-13.fc13.noarch.rpm
> mingw32-gettext-0.17-12.fc12.noarch.rpm
> mingw32-iconv-1.12-12.fc12.noarch.rpm
> mingw32-zlib-1.2.3-19.fc12.noarch.rpm
> mingw32-portablexdr-4.9.1-1.fc15.noarch.rpm
> mingw32-libxml2-2.7.6-1.fc13.noarch.rpm
> mingw32-readline-5.2-7.fc12.noarch.rpm
> mingw32-termcap-1.3.1-8.fc12.noarch.rpm
>
> Matthias
Hi Matthias,
There are currently some known issues with the mingw32 toolchain in
Fedora 15. See https://bugzilla.redhat.com/show_bug.cgi?id=629209 for
more details. As I'm currently preparing the introduction of a mingw-w64
based tool chain (which can build both win32 as well as win64 targets) I
don't plan to spend much time in researching these issues.
For now I would recommend to use the F14 packages. Those should be fully
stable.
Regards,
Erik van Pienbroek
11:43 a.m.
On 16/11/2010, at 9:56 PM, Matthias Bolte wrote:
<snip>
I recently tested the Fedora provided mingw32-libvirt on Windows and
virsh just segfaults before main() for me.
Justin, msys_setup contains a download_libvirt-fedora.sh script that
downloads and unpacks to
msys\fedora\usr\i686-pc-mingw32\sys-root\mingw\bin
if you want to give that a try.
Will do, but on the weekend. :)
5120
days inactive
5122
days old
21 comments
6 participants
participants (6)
-
arnaud.champion＠devatom.fr -
Erik van Pienbroek -
Justin Clift -
Laine Stump -
Matthias Bolte -
Richard W.M. Jones