similar to: Vista guest doesn't start after libvirt upgrade

Dom0: Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version 3.2.41-2+deb7u2, package blktap-dkms and all dependency packages for xen, spice and usb redirection. Seabios 1.7.2-3 and latest spice and usbredir compiled from debian unstable sources. ------------------------- /etc/modules ------------ loop max_loop=64 xenfs xen-evtchn blktap ------------------------- git clone

I''ve been trying to have all spice features working on xen domUs since the end of 2011. Basic functions were already working. Adding qemu parameters manually for vdagent and usbredirection was and is also working (I made the patches to support them directly on xl). Qxl was never working: one bug on xen and one on qemu about qxl are fixed, the other xen bug found months ago on the

Hi, As you all know, CentOS 7 is shipping PHP 5.4, which is OK in some situations. Unfortunately, some applications like OwnCloud require a more recent version of PHP. Up until recently, I've been using PHP 5.6 packages from the Webtatic repository. Despite the bad press this third party repo seems to have, it has been working perfectly for me for a few years. Here's the PHP 5.6 packages

v2 -> v3 - Don't make a special case for WdfCoInstaller* files. There is a difference of opinion about whether copying these is necessary, but it seems like it is not harmful. Rich.

On Tue, Nov 17, 2015 at 08:49:54PM +0000, Richard W.M. Jones wrote: > There was a copy and paste error. It should have read: > > $ md5sum viostor/2k8/amd64/* viostor/w7/amd64/* > d1132fbd27c98f25ea71a6eb4037b2f8 viostor/2k8/amd64/viostor.cat > defccbe48aca1cd97fee4d7b16053b72 viostor/2k8/amd64/viostor.inf > 6da6120368c097806e4ac7fc6b940810 viostor/2k8/amd64/viostor.pdb >

Since v1: - Fix a bug in the calculation of lc_basename. By luck this doesn't affect anything given the contents of the current ISO. - Don't copy the WdfCoInstaller*.dll files. Rich.

I think one - maybe final? - problem. How can I tell the difference between drivers for "client" versions of Windows (eg. Windows 7) and server versions of Windows (eg. Windows 2008 Server)? It seems in many or most cases the drivers are identical, eg: $ md5sum viostor/2k12/amd64/* viostor/w8/amd64/* bbe250c13bf891fd7292ccab9908a63a viostor/2k12/amd64/viostor.cat

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

Patch 1 moves the v2v/fake-virtio-win and v2v/fake-virt-tools directories to the recently created test-data/ hierarchy. This is just refactoring with no functional change at all. Patches 2-4 then extend the available (fake) virtio-win drivers: - Patch 2 adds all of the drivers from the virtio-win RPM. - Patch 3 adds all of the drivers from the virtio-win ISO (which are different from the

https://bugzilla.samba.org/show_bug.cgi?id=7809 Summary: I/O errors other than IOERR_GENERAL should not suppress deletion Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org

I have been improving my DC. I now have a DC01, DC02 and a DCMEMBER01. All running sernet-samba 4.1.16 on Debian 7.8.0 thanks to Louis' (old) scripts. (Any linux client work has gone on hold, for the moment.) Next step was to adjust the file permissions as instructed on "Setup and configure file shares with Windows ACLs". When I access the "Computer Management" (thru ADUC

Moved the hdd of my DC over to nicer P4 machine. It started as expected. (I have resolved the eth0 driver issue that happens with Debian/Ubuntu servers when you move a functional hdd to a different machine.) Then I decided to change the static ip address of the DC from 192.168.**.54 to 192.168.**.51. That went as expected, except it seems my W7 client cannot connect to my domain, now. It says

W7 client domain member? yes. Logged in as domainAdministrator? yes. "SeDiskOperatorPrivilege" set? yes Read "/Setup_and_configure_file_shares_with_Windows_ACLs"? yes. --- ------------------------- Bob Wooden of Donelson Trophy 615.885.2846 (main) www.donelsontrophy.com [2] "Everyone deserves an award!!" On 2015-01-28 10:40, Marcel de Reuver wrote: >

On 30/01/15 20:48, Bob of Donelson Trophy wrote: > > > Okay, added 'gidNumber: 10000' to the domain users group on DC1. (Was > within my range 500-40000.) > > getnet passwd [user] returns nothing on DC1. > > W7 client still a "no". > > And now? > > Have you tried getent on the member server ? Lets forget W7 for the moment, get the Unix

Hai Manu, > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Manu > Baylac via samba > Verzonden: vrijdag 3 november 2017 20:21 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Unable to upload printer drivers > > Hello Louis and list, > > > Le 03/11/2017 à 10:25, L.P.H. van Belle via samba a écrit :

On 30/01/15 20:10, Bob of Donelson Trophy wrote: > > > Leaving and re-joining the domain is easy. Tried that, no difference. > > Checking the gidNumber for the Domain Admin group . . not sure how to do > that? Easy, use ldbedit again :-) ldbedit -e nano -H /var/lib/samba/private/sam.ldb -b "DC=example,DC=com" -s sub '(&(objectclass=group)(cn=Domain

First, I am sorry. I should know this by now. Last week had an issue with W7 client could not update. I made some adjustments to get W7 updated. Now I am having an issue with update resolution. (Run apt-get update and repositories cannot be find, etc.) So, this tells me that I have messed up my dns resolution. All clients (W7 & linux) point to my DC for DNS nameserver. All clients (W7

Hi I have folder redirection working fine in XP. I see that W7 has taken the same configuration as I made in XP. Here is a screenshot: http://dl.dropbox.com/u/45150875/gpo.png Unfortunately, on w7, whilst the roaming profile is correctly set, there is no folder redirection. Nothing appears in the \\hh1\USERS folder for the user who has logged in. Upon opening the GPO editor as Administrator

> The domain user does login eventually. Mostly. Roaming Profiles are > very broken on W7: the top level "Vista.V2" directory is created, but > nothing is stored back into it on the server, and the logged in domain > user ends up with a C:\Users\Temp profile. Thanks to Drew Vonada-Smith the roaming profiles are working again. The problem was that information stored in