search for: coinstallable

On Thu, Oct 29, 2015 at 10:33:57AM +0200, Yan Vugenfirer wrote: > > On 29 Oct 2015, at 10:28, Richard W.M. Jones <rjones@redhat.com> wrote: > > On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld wrote: > > > > Seems like looking at this field in the .inf file is better than our > > current approach of matching path names. > > You just need to

On Fri, Mar 04, 2016 at 01:58:12PM +0300, Roman Kagan wrote: > On Fri, Mar 04, 2016 at 09:11:00AM +0000, Richard W.M. Jones wrote: > > 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

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

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

On Fri, Mar 04, 2016 at 09:11:00AM +0000, Richard W.M. Jones wrote: > 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

Hi, By using virtio-win-0.1.109.iso , it looks like vport0p devices are not configured (on a Windows 2008 R2 guest) due to no suitable driver found ( below setupapi.dev.log): [Boot Session: 2015/09/16 17:29:32.375] >>> [Device Install (Hardware initiated) - {6fde7547-1b65-48ae-b628-80be62016026}\vioserialport\4&7e8053e&1&03] >>> Section start 2015/09/16

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

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

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:

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

This simple parser has (limited) understanding of the Windows '*.inf' file format. This is a Windows config file with some peculiarities. This commit also has a unit test. --- po/POTFILES-ml | 1 + v2v/Makefile.am | 5 +- v2v/v2v_unit_tests.ml | 104 +++++++++++++++++++++++++++++++++++- v2v/windows_inf.ml | 143 ++++++++++++++++++++++++++++++++++++++++++++++++++

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

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

...; > 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 '...