Displaying 15 results from an estimated 15 matches for "coinstall".
Did you mean:
toinstall
2015 Oct 29
2
Re: [PATCH] v2v: virtio-win: include *.dll too
...is.
Besides, ATM there's at least one driver -- qemupciserial -- which
doesn't fit in this scheme (or any scheme at all :).
There are other peculiarities which we don't know what to do:
- the netkvm driver directory on virtio-win.iso contains netkvmco.dll
(I'm assuming it's coinstaller dll). However, netkvm.inf doesn't
mention it, and the driver installs just fine without it.
- the balloon driver directory on virtio-win.iso contains blnsvr.exe
(and .pdb) which is apparently a usermode service to report memory
stats to host via balloon virtio queue. However nothing...
2016 Mar 04
1
Re: [PATCH] v2v: Copy *.dll files since they can be part of the driver (RHBZ#1311373).
...908f803f0a89c3b1e3166cfe33aad originally introduced
> > the filtering of files by extension. For the QXL driver at least,
> > there is a qxldd.dll file which is part of the driver, so that must be
> > copied to the guest as well.
> >
> > This patch will cause 'WdfCoInstaller*.dll' files to be copied too.
> > While I'm not sure if this is correct,
>
> It is. They are coinstaller dlls and are mentioned in the corresponding
> .inf and .cat files, so the driver wouldn't install without them.
>
> There are also other files that sometime...
2017 Jan 17
2
Bug#851654: Prerm maintainer script unconditionally stops xend/xenconsoled
Hi Ian,
On Tue, Jan 17, 2017 at 10:58 +0000, Ian Jackson wrote:
> Wolodja Wentland writes ("Bug#851654: Prerm maintainer script unconditionally
> stops xend/xenconsoled"): > We triggered a xen stop by removing obsolete
> xen-utils-4.1 packages while already using xen-utils-4.4.
> I think a xenconsoled restart should be harmless, so I think it is
> probably right that
2016 Mar 04
3
[PATCH] v2v: Copy *.dll files since they can be part of the driver (RHBZ#1311373).
Commit 47b5f245bec908f803f0a89c3b1e3166cfe33aad originally introduced
the filtering of files by extension. For the QXL driver at least,
there is a qxldd.dll file which is part of the driver, so that must be
copied to the guest as well.
This patch will cause 'WdfCoInstaller*.dll' files to be copied too.
While I'm not sure if this is correct, it seems as if it will be safe
as although there are multiple copies of this file, they are all the
same (per architecture).
Thanks: Vadim Rozenfeld, Tingting Zheng.
---
v2v/windows_virtio.ml | 2 +-
1 file changed, 1...
2016 Mar 04
0
Re: [PATCH] v2v: Copy *.dll files since they can be part of the driver (RHBZ#1311373).
...:
> Commit 47b5f245bec908f803f0a89c3b1e3166cfe33aad originally introduced
> the filtering of files by extension. For the QXL driver at least,
> there is a qxldd.dll file which is part of the driver, so that must be
> copied to the guest as well.
>
> This patch will cause 'WdfCoInstaller*.dll' files to be copied too.
> While I'm not sure if this is correct,
It is. They are coinstaller dlls and are mentioned in the corresponding
.inf and .cat files, so the driver wouldn't install without them.
There are also other files that sometimes are and sometimes aren't...
2015 Sep 17
0
vport0p devices no suitable drver found ..
...n directory: 'C:\Windows\inf'
dvi: {Build Driver List - exit(0x00000000)} 17:29:59.000
ndv: Selecting best match from Driver Store (including Device Path)...
dvi: {DIF_SELECTBESTCOMPATDRV} 17:29:59.000
dvi: No class installer for 'vport0p3'
dvi: No CoInstallers found
dvi: Default installer: Enter 17:29:59.015
dvi: {Select Best Driver}
! dvi: Selecting driver failed(0xe0000228)
dvi: {Select Best Driver - exit(0xe0000228)}
! dvi: Default installer: failed!
! dvi: Error 0xe0000228:...
2016 Sep 26
1
Re: [PATCH] Improve memory management of nbdkit python plugin example
Hi,
sorry for the resend. My mailer mangled the previous attempt.
On 26.09.2016 17:19, Pino Toscano wrote:
> On Monday, 26 September 2016 17:07:41 CEST Carl-Daniel Hailfinger wrote:
>> the nbdkit python plugin example has suboptimal memory management:
>> - it creates the disk image as a string on init
>> - it casts the string to bytearray on every read
>> - it copies
2017 Jan 25
7
Bug#852545: Config file in xen-hypervisor package likely causes problems on upgrade
Package: xen
Version: 4.8.0-1
Severity: important
Starting with 4.8 the xen-hypervisor-4.8* package will contain a grub config
file in /etc/default/grub.d/xen.cfg. This will be causing problem when moving to
Xen 4.9 because then xen-hypervisor-4.9* will try to install the same file again.
This will prevent two versions of the hypervisor to be co-installable. Maybe the
solution would be to have a
2012 Apr 23
9
[PATCH] tools: Improve make deb
2015 Oct 29
2
Re: Fwd: [PATCH] v2v: virtio-win: include *.dll too
On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld wrote:
> > 1) tell which devices can be configured
> Not sure that I fully understated your question. but if you are going to
> create some sort of off-line automatic virtio-win drivers update
> utility, then it shouldn't be too complicated.
Roman is talking about what virt-v2v already does.
This is good information:
2017 Jan 25
2
Feedback on merge of Xen-4.8.0
Hi Ian,
first thanks for picking up so many things in your upload. Unfortunately it took
me a while to merge this back into Ubuntu. So it is a bit late for the feedback
but I hope it still helps a bit.
Sadly I think that by picking up the grub default file, you picked up some
trouble. It is not the contents but the packaging. Logically it belongs to the
hypervisor, but that is versioned in
2015 Nov 17
0
[PATCH 2/3] v2v: windows: Add a Windows '*.inf' file parser.
..."servicebinary", "%12%\\balloon.sys";
+ ];
+ "balloon_logging_inst", [
+ "addreg", "BALLOON_Logging_Inst_AddReg";
+ ];
+ "balloon_logging_inst_addreg", [];
+ "destinationdirs", [
+ "balloon_device_coinstaller_copyfiles", "11";
+ ];
+ "balloon_device.nt.coinstallers", [
+ "addreg", "BALLOON_Device_CoInstaller_AddReg";
+ "copyfiles", "BALLOON_Device_CoInstaller_CopyFiles";
+ ];
+ "balloon_device_coinstaller_addre...
2016 Mar 07
2
Windows port
Hi!
I would like to ask about current state of Windows port. Is it frozen? It will be cool to know the plans :)
Where are a lot of Windows-branches at GitHub. What is the most actual one?
The Windows builder looks like turned off, am I right that it is not available currently and where were no builds after version 2.6.5-6?
I couldn't find any info about proper environment to build Windows
2015 Nov 17
8
[PATCH 0/3] v2v: windows: Use '*.inf' files to control how Windows drivers are installed.
https://github.com/rwmjones/libguestfs/tree/rewrite-virtio-copy-drivers
Instead of trying to split and parse elements from virtio-win paths,
use the '*.inf' files supplied with the drivers to control how Windows
drivers are installed.
The following emails best explain how this works:
https://www.redhat.com/archives/libguestfs/2015-October/msg00352.html
2013 Jan 26
0
Processed: switching email address
...;
> submitter 662590 !
Bug #662590 [leafnode] leafnode: fails to upgrade from sid
Changed Bug submitter to 'Andreas Beckmann <anbe at debian.org>' from 'Andreas Beckmann <debian at abeckmann.de>'
> submitter 682260 !
Bug #682260 [libpulse0] libpulse0: not multiarch-coinstallable due to differing /etc/pulse/client.conf
Changed Bug submitter to 'Andreas Beckmann <anbe at debian.org>' from 'Andreas Beckmann <debian at abeckmann.de>'
> submitter 461874 !
Bug #461874 [pbuilder] invalid $HOME in pbuilder -login session
Changed Bug submitter to...