similar to: Using WINE to install device drivers for Windows XP

One of the things we would really like to be able to do for V2V is to install a new driver in a Windows guest. There are a couple of reasons for this: * The guest may not be bootable without the driver installed, for example because the underlying virtual hardware has changed from vmscsi to virtio. * If the guest can boot, the alternative is to modify the guest to run a script on next boot.

Hey, In windows we have a concept of "hive" in the registry. I'm trying to load the hive to wine registry, but wine is not able to recognizing the format of hive. Please help me out. Thanks, karthik

>> > vmware esxi 5.5.0 (free, using vsphere client to manage), vm is minimal > centos 7 64bit. I added a 16gb vdisk and immediately see this in dmesg... > > [155484.386792] vmw_pvscsi: msg type: 0x0 - MSG RING: 1/0 (5) > [155484.386796] vmw_pvscsi: msg: device added at scsi0:1:0 > [155484.388250] scsi 0:0:1:0: Direct-Access VMware Virtual disk > 1.0 PQ: 0 ANSI:

Hi, I see some strange and dangerous things happening on a HPE server with HPE Smart Array controller where EL9 ends up with wrong device nodes/symlinks to the attached disks/raid volumes: (I didn't touch anything here but at 08:09 some symlinks were changed) /dev/disk/by-id/: lrwxrwxrwx 1 root root 9 Mar 1 07:57 scsi-0HP_LOGICAL_VOLUME_00000000 -> ../../sdc lrwxrwxrwx 1 root root 10

Hi everyone, I have a udev rule file that contains a singular rule: SUBSYSTEM=="block", ACTION=="add|change", ENV{ID_VENDOR}=="*Google*", ENV{DEVTYPE}=="disk", ATTR{queue/scheduler}:="noop" When I use a Google Cloud instance and boot it, things work as expected and /dev/sda (a persistent disk) uses the noop scheduler. If the instance also has a

Have a quad core workstation that was running WinXP_64 that I want to blow away and install CentOS 6. C6 install process finds raid metadata associated with sda and sdb, and then excludes them from the rest of the installation process. There doesn't appear to be an option for disassembling the raid as part of the install process. I think there should be. Any tricks to removing/by-passing

I was playing a bit with multipathed devices (over two FC HBAs on SAN) last week (I had some hardware for limited time to play with). The support for multipathing in device mapper seems to be a bit newer thing, and I was left with couple of questions (things I haven't managed to try out while I had the hardware)... Is it possible to have root file system on multipathed device? I guess in

I am attempting to get multipath working with device-mapper (CentOS 4.2 and 4.3). It works on EVERY install of mine from RH (also v4.2, 4.3), but the same multipath.conf imported to all my installs of CentOS do not work. Note that I have tested a working 4.2 configuration file from RH on CentOS 4.2 and a working 4.3 configuration (it changed slightly) on CentOS 4.3. Neither worked. Our production

On 11/4/2015 11:36 AM, Boris Epstein wrote: > Absolutely, I see your point. This was the starting point - you add the > device on the ESXi server, you reboot the VM, the VM sees the device, no > problem. Now, I ask - do I have to reboot the VM? Logically I hope there > ought to be a way for me not to have to do that - but I have yet to figure > out how to get there. > vmware

I suppose it would help if I posted relevant version info (sorry about that...) CentOS Linux release 7.4.1708 (Core) @ 3.10.0-693.11.6.el7.x86_64 systemd-219-42.el7_4.4.x86_64 $ modinfo virtio_scsi filename: /lib/modules/3.10.0-693.11.6.el7.x86_64/kernel/drivers/scsi/virtio_scsi.ko.xz license: GPL description: Virtio SCSI HBA driver rhelversion: 7.4 srcversion:

Hello all, I have 3 Supermicro 1u servers, each with dual 250gb SATA drives. I have a server with CentOS 5 64bit setup for pxebooting and kickstart installs. I have a kickstart install file that doesn't specify the disks specifically. It works like a champ, and the operating system installs and completes. I have a kickstart install file that specifies the disk devices (sda,

Hello, The following patches address issues when dealing with hives that have corrupted data in them but are otherwise readable/writable. Those were found on some rather rare Windows installations that seem to work fine but current hivex fails to even open. Those patches change hivex to simply log and ignore such "corrupted" regions instead of aborting because the caller might be

By default, a kickstart installation will spread the configured partitions over all disks that are found, and the only way around that is to use --ondisk or ignoredisk. But I was wondering how reliable this method is. E.g. if there are four SATA ports on the system board, can I blindly assume that port one will always correspond to sda, port two to sdb, and so on? Can I assume that a second

The following patches address issues when dealing with hives that have corrupted data in them but are otherwise readable/writable. Those were found on some rather rare Windows installations that seem to work fine but current hivex fails to even open. Those patches change hivex to simply log and ignore such "corrupted" regions instead of aborting because the caller might be looking at

[Forwarding to the proper list] We use hivex for one of our projects and I see the following diff committed to the hivex project (source link provided) that ignores trailing garbage. But this code has been reverted to no ignore this condition in later version of hivex - /* This error is seemingly common in uncorrupt registry files. */ - /* - fprintf (stderr, "hivex: %s:

Because of the size of an extended partition reported by Linux is always 1024 bytes, so it will always fail to copy to an extended partition. This patch fixes this problem by copying to the offset of an extended partition in the destination disk. Signed-off-by: Hu Tao <hutao@cn.fujitsu.com> --- resize/resize.ml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git

The following patches address issues when dealing with hives that have corrupted data in them but are otherwise readable/writable. Those were found on some rather rare Windows installations that seem to work fine but current hivex fails to even open. Those patches change hivex to simply log and ignore such "corrupted" regions instead of aborting because the caller might be looking at

The following patches address issues when dealing with hives that have corrupted data in them but are otherwise readable/writable. Those were found on some rather rare Windows installations that seem to work fine but current hivex fails to even open. Those patches change hivex to simply log and ignore such "corrupted" regions instead of aborting because the caller might be looking at

Hello everyone. I'm trying to install CentOS 8 with root and swap partitions on software raid. The plan is: - create md0 raid level 1 with 2 hard drives: /dev/sda and /dev/sdb, using Linux Rscue CD, - install CentOS 8 with Virtual Box on my laptop, - rsync CentOS 8 root partition on /dev/md0p1, - chroot in CentOS 8 root partition, - configure /etc/mdadm.conf, grub.cfg, initramfs, install

As described here previously: https://www.redhat.com/archives/libguestfs/2010-March/msg00129.html Here is the three part patch to reimplement virt-win-reg to support exporting and merging Windows Registry entries in the 'regedit' format. Tested by me on a local Windows VM. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top'