search for: controlsets

On Wed, Aug 17, 2016 at 08:59:43PM +0300, Roman Kagan wrote: > It will be used in new code in a followup patch. > > Signed-off-by: Roman Kagan <rkagan@virtuozzo.com> > --- > v2v/convert_windows.ml | 17 +++++++++-------- > 1 file changed, 9 insertions(+), 8 deletions(-) > > diff --git a/v2v/convert_windows.ml b/v2v/convert_windows.ml > index 55bb3ef..751a6ab

[Partly using the mailing list as a backup again ...] This commit changes virt-v2v to make registry changes to all ControlSets, not just the CurrentControlSet. Not sure what difference if any this would make. Rich.

On Thu, Sep 01, 2016 at 11:50:18AM +0300, Roman Kagan wrote: > It will be used in new code in a followup patch. > > Signed-off-by: Roman Kagan <rkagan at virtuozzo.com> > --- > v1 -> v2: > - revert debug -> printf regression > > v2v/convert_windows.ml | 15 ++++++++------- > 1 file changed, 8 insertions(+), 7 deletions(-) > > diff --git

If a Windows boot fails and the user boots the last known good configuration, ControlSet001 will be marked as failed and no longer used. However, virt-v2v would only install viostor to ControlSet001, meaning it will fail to boot this guest after conversion. This patch looks up the current controlset and always installs registry keys to the correct one. Fixes RHBZ#644254 ---

I am trying to connect a windows xp client to a samba PDC. The user exists on the PDC and has an entry in the /etc/samba/smbpasswd file. In my smb.conf file, I have the following: add user script = /usr/sbin/useradd -s /bin/false %u && /usr/bin/smbpasswd -a %u add machine script = /usr/sbin/useradd -d /dev/null -g machines -s /bin/false -M %u && /usr/bin/smbpasswd -m -a %u

Wait for driver installations fired by the PnP manager to complete before running firstboot scripts. The first patch is a minor refactoring to pave the way for the second patch. The latter contains the bulk of the changes as well as the description of the idea. Roman Kagan (2): v2v:windows: factor out getting CurrentControlSet v2v:windows: prevent conflicts with PnP on firstboot --- v1

SUSE VMDP comes with a replacement for rhsrvany.exe named pvvxsvc.exe. Check for either one of them instead of only rhsrvany. --- builder/virt-builder.pod | 13 +++- customize/firstboot.ml | 169 +++++++++++++++++++++++-------------------- customize/virt-customize.pod | 6 ++ sysprep/virt-sysprep.pod | 6 ++ v2v/virt-v2v.pod | 6 ++ 5 files changed, 117

This adds most of the hivex APIs directly to the libguestfs API, so that you can read and write Windows Registry hive files from libguestfs without needing to download and upload hive files from the guest. This is analogous to how Augeas APIs are exposed already (guestfs_aug_*) Also, inspection is now done using the new APIs, which fixes the following bug:

Parallels proprietary hypervisor uses RDPMC as the hypercall instruction. As this instruction is supported since early P6 family, the drivers didn't even bother to check for the presence of the corresponding feature in CPUID. In QEMU/KVM, however, this instruction triggers #GP unless the VM is run with PMU (performance monitoring unit) enabled, which is often not the case (due to its impact

I have read through the mail archives to find a solution to my problem... to no avail. Here is the issue: I have a Samba 2.2.2 acting as a PDC, with Win2k I can join the domain and logon as a domain user. No problem. (So it is working and set up properly). With WinXP - Pro, I can join the domain, successfully. However, once I do the reboot I cannot logon as a domain user as I did with

A very miscellaneous set of cleanups to how we handle the Windows registry in virt-v2v, firstboot, and inspection code. This should all be straightforward non-controversial refactoring. Some highlights: - Add a new mllib Registry module containing various utility functions that are currently scattered all around. - Only compute the software/system hive paths once during inspection, and

Don't remove the Processor and Intelppm nodes since that just breaks the device driver. The only remaining node being removed by the original code was "rhelscsi" (the xenpv-win driver). I changed this so that instead of deleting the whole node, it simply disables that driver. If you look at RHBZ#737600, it's not even clear that deleting nodes was the right fix for anything. I

G'day. I'm having a great time trying to get a whole heap of XP workstations (from what I understand, they've been hotfixed+windows updated+whatever else a few days ago) to authenticate against Samba running on a FreeBSD 4.5-STABLE box. Basically, I add user accounts, machine accounts (with both "pw" and "smbpasswd"), then I can get the XP machines to successfully

This allows users to see stop errors, so we can get an accurate report when things go wrong. --- v2v/convert_windows.ml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/v2v/convert_windows.ml b/v2v/convert_windows.ml index e37c6b8..c8db860 100644 --- a/v2v/convert_windows.ml +++ b/v2v/convert_windows.ml @@ -191,6 +191,7 @@ echo uninstalling Xen PV driver if verbose then

On Wed, Aug 17, 2016 at 08:59:44PM +0300, Roman Kagan wrote: > When put on new virtual hardware Windows will start driver installation > for newly discovered devices. > > The problem is that it happens asynchronously and concurrently with > other activities, in particular, the firstboot scripts. This may result > in conflicts (because a firstboot script may want to install or

On Thu, Sep 01, 2016 at 11:50:19AM +0300, Roman Kagan wrote: > When put on new virtual hardware Windows will start driver installation > for newly discovered devices. > > The problem is that it happens asynchronously and concurrently with > other activities, in particular, the firstboot scripts. This may result > in conflicts (because a firstboot script may want to install or

Hi. I am running SAMBA 2.0.7 on HP-UX 11.00 and HP-UX 10.20. I have tried adding the MultipleUsersOnConnection registry key onto my Microsoft Windows NT Server 4 Terminal Server Edition servers, running with Service Pack 6. After I make this change in the registry and reboot my WTS servers all my samba connections from the servers are still being made with one process instead of being split

Add a common debug function for printing debugging messages. It only emits the debug message when the verbose (-v) flag is used on the command line. It sends the output to stderr, which is flushed immediately after the message is printed (to help with debugging unexpected crashes). There are good arguments for sending the debug to either stdout or stderr, and almost all existing debug messages

Add a Common_utils.debug function for printing messages only when in verbose mode. Rich.

can someone please tell me why everyone else can connect to my samba server but me? I mean I even went as far as installing a new OS ("down-graded" back to win2k). I really need help trying to figure out why. If someone can help me in figuring that out, please let me know. And by the way...I already tried the router thing....same issue. So the router doesnt matter because I disabled the