Displaying 11 results from an estimated 11 matches for "buildlabex".
2015 Oct 28
8
Re: Fwd: [PATCH] v2v: virtio-win: include *.dll too
On Wed, Oct 28, 2015 at 12:10:19PM +1100, Vadim Rozenfeld wrote:
> > > > To sum up, the packaging and naming policy of the virtio-win rpm and the
> > > > virtio-win iso therein are different and neither is clear. Hardcoding
> > > > the policy in v2v without actually knowing it appears risky at best.
>
> It's due to historical reasons mostly. The best
2015 Oct 29
2
Re: Fwd: [PATCH] v2v: virtio-win: include *.dll too
...does.
This is good information:
> First of all you will need
> to obtain the Windows kernel version by reading the following Registry
> key - "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it
> 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx"
> string from the same hive will give you information about the platform
> bitness. Next you need to go through inf files, and find "DriverVer"
> string, like this one . taken from from vioscsi.inf
>
> DriverVer=08/01/2015,62.72.104.10800
>
> This string conta...
2015 Nov 05
3
Re: Fwd: [PATCH] v2v: virtio-win: include *.dll too
...en it shouldn't be too complicated. Firs of all you will need
> to obtain the Windows kernel version by reading the following Registry
> key - "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it
> 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx"
> string from the same hive will give you information about the platform
> bitness. Next you need to go through inf files, and find "DriverVer"
> string, like this one . taken from from vioscsi.inf
>
> DriverVer=08/01/2015,62.72.104.10800
>
> This string conta...
2015 Nov 08
2
Re: [PATCH] v2v: virtio-win: include *.dll too
...oo complicated. Firs of all you will need
>>> to obtain the Windows kernel version by reading the following Registry
>>> key - "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it
>>> 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx"
>>> string from the same hive will give you information about the platform
>>> bitness. Next you need to go through inf files, and find "DriverVer"
>>> string, like this one . taken from from vioscsi.inf
>>>
>>> DriverVer=08/01/2015,62.7...
2015 Oct 29
0
Re: [PATCH] v2v: virtio-win: include *.dll too
...nformation:
>
>> First of all you will need
>> to obtain the Windows kernel version by reading the following Registry
>> key - "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it
>> 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx"
>> string from the same hive will give you information about the platform
>> bitness. Next you need to go through inf files, and find "DriverVer"
>> string, like this one . taken from from vioscsi.inf
>>
>> DriverVer=08/01/2015,62.72.104.10800
>>...
2015 Oct 29
0
Re: Fwd: [PATCH] v2v: virtio-win: include *.dll too
...ate
utility, then it shouldn't be too complicated. Firs of all you will need
to obtain the Windows kernel version by reading the following Registry
key - "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it
6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx"
string from the same hive will give you information about the platform
bitness. Next you need to go through inf files, and find "DriverVer"
string, like this one . taken from from vioscsi.inf
DriverVer=08/01/2015,62.72.104.10800
This string contains build time and version stamps....
2015 Nov 09
1
Re: [PATCH] v2v: virtio-win: include *.dll too
...u will need
> > >>> to obtain the Windows kernel version by reading the following Registry
> > >>> key - "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it
> > >>> 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx"
> > >>> string from the same hive will give you information about the platform
> > >>> bitness. Next you need to go through inf files, and find "DriverVer"
> > >>> string, like this one . taken from from vioscsi.inf
> > >>>...
2015 Nov 06
0
Re: Fwd: [PATCH] v2v: virtio-win: include *.dll too
...39;t be too complicated. Firs of all you will need
> > to obtain the Windows kernel version by reading the following Registry
> > key - "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it
> > 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx"
> > string from the same hive will give you information about the platform
> > bitness. Next you need to go through inf files, and find "DriverVer"
> > string, like this one . taken from from vioscsi.inf
> >
> > DriverVer=08/01/2015,62.72.104.10800
>...
2015 Nov 09
0
Re: [PATCH] v2v: virtio-win: include *.dll too
...Firs of all you will need
> >>> to obtain the Windows kernel version by reading the following Registry
> >>> key - "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion". Let's say it
> >>> 6.3, which means that it is Win8.1 or WS2012R2, parsing "BuildLabEx"
> >>> string from the same hive will give you information about the platform
> >>> bitness. Next you need to go through inf files, and find "DriverVer"
> >>> string, like this one . taken from from vioscsi.inf
> >>>
> >>>...
2015 May 28
3
Re: Concurrent scanning of same disk
...proc 359 (hivex_value_key) took 0.00 seconds
libguestfs: trace: hivex_value_key = "BuildLab"
libguestfs: trace: hivex_value_key 32800272
guestfsd: main_loop: new request, len 0x30
guestfsd: main_loop: proc 359 (hivex_value_key) took 0.00 seconds
libguestfs: trace: hivex_value_key = "BuildLabEx"
libguestfs: trace: hivex_value_key 32802488
guestfsd: main_loop: new request, len 0x30
guestfsd: main_loop: proc 359 (hivex_value_key) took 0.00 seconds
libguestfs: trace: hivex_value_key = "BuildGUID"
libguestfs: trace: hivex_value_key 32802328
guestfsd: main_loop: new request, len...
2015 May 27
3
Concurrent scanning of same disk
Greetings,
I am suffering of several weird errors which show randomly and make me
suspect some concurrency issue.
Libguestfs version is 1.28.1, linux kernel 3.16, libvirt 1.2.9 and qemu 2.1.
What I'm trying to do is comparing the disk state at two different point of
a guest execution.
Disk snapshots are taken through libvirt in different moments (I am aware
of caching issue), from such