P2V a Citrix Virtual machine (offline)
I am wanting to P2V a virtual machine. If you are wondering why not do a V2V I can't add the Xenserver hosts to SCVMM 2012 since the Xenserver I am running is 6.2 (which isn't supported with SCVMM 2012 SP1).
There are a couple that I would prefer to do an offline conversion (such as a domain controller) but it complains that it can't find the drivers for the NIC.
I have tried copying the folders under the XenTools directory on the VM to the "Driver Import" folder (I created a folder within that folder) but it still complains that it can't find the drivers.
Does anyone know the correct way to get this to work and get the Citrix PV Drivers in SCVMM so I can attempt an offline convert? The VM's are all 2008 R2
Did you find a solution to this? The drivers I am having an issue with are the SCSI drivers and the Ethernet PV drivers. I am trying to convert a domain controller.
Similar Messages
-
Trying p2v import of virtual machine image, server pool not chooseable
I'm trying to import a virtual machine image via p2v from an OEL 5 bare metal image. I go to resources, virtual machine images, Import, choose p2v, and then on the General Information page, it asks for Server Pool Name. The name of my one and only server pool is not in the dropdown. The dropdown only contains "Select Server Pool". I tried to fill in the rest and hit Next but it failed me on the Server Pool name.
How can I get the server pool name to show up in that dropdown?
There is one server pool, one server, and one vm already on that server.
thanks,
PeterIt's a bug, I had the same problem. I used this and it worked (copying and pasting from an old thread with the solution):
Workaround:
VM Manager -> Server Pools -> Select Server Pool Name -> EDIT -> Check the box of “Enable High Availability” -> Apply -> Ignore the “Shared storage is not mounted, or the file system is invalid. The file system should be OCFS2 or NFS.” error message. Leave unchecked the box of ”Enable High Availability” -> Apply again:
“The server pool updated successfully.”
Now you can retry the import. -
How to convert offline ESXi 5.5U1 virtual machines to Hyper-V?
Following on from my
earlier question, I am having trouble working out how to convert my ESXi VMs to Hyper-V. Am I doing something really unusual?
I have a ESXi 5.5U1 server at home for my home test lab. I want to convert this to Hyper-V Core 2012 R2. Target storage layout will look like this:
Currently under ESXi 5.5, I don't have the C drive (using a USB flash to boot), and the RAID-5 and RAID-0 arrays are two separate VMFS volumes.
I don't have swing kit to migrate, I have to repurpose existing hardware. I do have my Windows 8.1 workstation but that only has 900 GB free space.
Some of my VMs have vmdks greater than 2TB.
My plan was to
In ESXi before rebuilding, move my VMs from the RAID-5 vol to the RAID-0 vol and then delete anything that wouldn't fit that's not strictly necessary from the RAID-5 volume.
Shutdown ESXi and remove the USB flash drive.
Install Hyper-V onto the System disk as C drive.
Format the RAID-5 volume as NTFS (64k) and create a mount point into the C drive as C:\RAID-5. Put my VM disks in C:\RAID-5\VirtualDisks and the VMs in C:\RAID-5\VirtualMachines.
Somehow convert the VMs from the RAID-0 VMFS volume to Hyper-V VMs on the RAID-5 NTFS volume.
My confidence is low because I have tried to convert a new test machine created in ESXi 5.5 to a spare test Hyper-V 2012 R2 with the MVMC 3.1 converter and it failed. I also tried with the free 5nine converter and that failed too. I tried with and without
the Guest Additions installed. Both conversions failed. I should mention I am in a workgroup, not a windows domain.
Please help!May i inquire on why those two products failed? I had some struggles with both of them but eventually got things worked.
Also you should try this one
Starwind V2V convertor, it has worked for pure offline conversions for me as well. That was years ago, so hopefully it still works.
Sure, here is the log from an attempt to convert a brand new VMware virtual machine which has Windows Server 2012 R2 Standard in it with no VM tools. http://pastebin.com/xdhzZ7tx
Here is the log from an attempt to convert a Lubuntu linux VM: http://pastebin.com/Nc0E8Bip
Both conversions attempted with MVMC3.1. Common error between them is
12/24/2014 08:25:36 +00:00 [7] VERBOSE: Microsoft.Accelerators.Mvmc.Engine.DiskCopyFailureException: The virtual disk(s) attached to the source virtual machine were not successfully converted to VHD(s) and copied to the
workspace folder path. ---> System.AggregateException: One or more errors occurred. ---> System.AggregateException: One or more errors occurred. ---> System.Security.Principal.IdentityNotMappedException: Some or all identity references could not be
translated.
I retried using 5nine converter and it worked this time, not sure why. Will not try a test with a BSD based distro (pfSense) and Linux. -
Microsoft Virtual Machine Converter VMware To Hyper-V Cluster
I'm not sure if this should technically be in the clustering section but I have just moved from SCVMM 2012 SP1 to 2012 R2 and I kinda miss the built-in converter tool. What I used to do when converting VMware to Hyper-V was uninstall VMware Tools and then
I would do a physical to virtual conversion on the VMware virtual machine and SCVMM would handle copying the virtual machine while it was online and register it in our Hyper-V cluster. Now, the only thing I could come up with is the Microsoft Virtual Machine
Converter but it seems rather limited and doesn't seem to have an option to import to a cluster. So is the only option to convert it over to Hyper-V as if it were a local machine and then run another export/import process to get it in the cluster? I tried
to point it to a CSV and while it copied the disk over, it registered the virtual machine in ProgramData (the default location). This obviously causes issues when trying to make the VM highly available. Any one have a suggested process of the best way to go
about this? Thank you in advance for your time!So no matter what option I choose, V2V always shuts down the source VM during the conversion process. On the other hand, if I use the old method of uninstalling VMware tools manually and then doing a P2V instead, the source VM has to stay online for
that type of process. Then I just have to migrate it to become highly available and that seems to accomplish what I want. The only annoying part is that I couldn't run it on my Win 8.1 Pro workstation as it requires the BITS feature to be installed
and that only appears to be available on server editions (correct me if there is a way to get it on 8.1). I guess the documentation (I think) says that it should run on server editions only but V2V runs fine from 8.1 since it doesn't need BITS since it's
an offline process. -
Hi I have a current XP SP3 setup have been using in a dual boot with Windows 8.1(on separate partitions on different hard drives - I think these are SATA drives) but now am thinking of migrating my XP partition preferably as a live virtual machine
to be run as a guest via Windows 8.1 as host so I don't have to do the rebooting. Also prefer this to making a VHD of my XP so can use the existing partition allocated for it rather than taking up extra space as VHD on my windows 8 (and don't want yet
to replace my xp dual boot in case it does not work so well as vhd, as I have a lot of old educational programs my kids still use on it that I don't really want to put onto my W8.1). Will also save time if I don't have to convert it to VHD first. I
also do not want to reinstall a new XP Sp3 virtual machine from scratch for same reason - will take too long to resetup -just use existing as is.
I have used VMWare player and Virtual Box in past with an old 98SE system as a virtual VHD/VPC file but VMWare workstation is paid which may be the one I need to use a physical partition but I prefer to try freeware options first.
Will Hyper-V in Windows 8.1 (I have retail PRO version of both my XP and Windows 8.1) be able to do the same as VMWare workstation? OR is there another option to run the physical XP?
The other thing with my XP setup is that the user profiles that people login with are located on a different partition E (80GB) to my XP which is on J (100GB) and most of the programs for it run from partition D (over 120GB) and the XP boot loader resides
on a partition C (2GB) (which is not the Windows8.1 partition which becomes C only when it boots, but this C drive for XP may also be having the Windows 8 boot loader and files for that -using EasyBCD to handle boot menu of W7 type boot loader).
So I need a system that can mount these other physical partitions also alongside with my XP partition when it boots up.
So what are my options for running this XP SP3 setup via Windows 8 as a guest operating system?
Also will doing this be likely to require reactivation of my existing windows XP (retail) which means I cannot then use it again if I go back to the XP dual boot at times or in case the VM setup does not work?
Also do I need to change my XP first so that it boots off its own drive rather than the C partition - and how do I set this up then using EasyBCD or windows boot repair?HI I found I had to make physical disk offline to use in Hyper-V which I cannot do and do not want to do with all partitions - cannot choose just ones want.
So now am trying to make VM of my physical XP -and other partitions neeeded but D partition is over 127Gb so cannot use Disk2VHD.
Here is what am trying now - any other suggestions for alternate software to vmware convertor/disk2VHD maybe to do partitions over 127GB? I have posted also at VMware forums but no answer as yet.
Advice on doing a physical XPSP3 conversion to a VM for Virtual box and hyper-v ultimately
Hi I need advice as to best way to convert an existing XP Sp3 install on a physical hard drive along with other related partitions to a Virtual box VM image with aim to convert that VM image to a Hyper-V VM for use with Windows 8.1 host.
I have several C (boot ini partition), D programs, E Data, etc partitions and a current dual boot with an extra XP install I use as a backup system.
My main XP is on J drive and other XP on I drive with C drive boot ini that switches btw 2 with J set as default.
I have a D partition that is over 127 Gb so cannot use Disk2VHD which would have been easier, and it seems there is not a way to make a direct Hyper-V VM from converter but only Vmware VM?
I do not have or want to purchase as yet VMware Workstation as have W8.1 Pro that can use Hyper-V to run my XP SP3.
I seem to also have an issue with COM+ corrupted on my machine XP J drive ( It tried to reinstall the COM+ but my es.dll file won't register and I did get a failed conversion with converter when tried earlier at 94% saying VSS snapshots have
reached their limit). I think this is related to my COM+ issue which I am not sure now how to fix apart from repair install of my Xp (as I have tried repairing COM with various articles searched on google to no avail) which I may do first before
retry conversion. However my ALT XP on I drive seems to be fine with being able to browse the COM+ applications ok. SO maybe I can use that instead but it is the J drive XP I want the most (not sure if will work at reboot if I do not
hot clone it?)
I have read also the manual for converter 5.5.1 ver standalone and am not sure of a few things so if someone can guide me it would be very much appreciated.
First of all which version VM should I make image of if I later want to convert it to a Hyper-V VM image (I only have free Virtual Box latest ver, VMware Player and Hyper-V on Windows 8.1 PRo) ie: VMware workstation 10 or Vmware Player 6 or lower
ver or other? OR is there another software I should install for the conversion or later conversion to Hyper-V? I prefer to use Hyper-V over Virtual Box and Vmware Player if possible, but should these others work just as well for my Xp Sp3 existing
system as a VM in Windows 8.1? Please advise which you think is best of these?
Should I leave all configuration options off while converting and even XP licence, workgroup etc or is it most likely that I will have to reactivate my XP (retail ver) once I reboot in the VM although I am putting to run on Windows 8.1 host on exact same
hardware as my current XP in dual boot (replacing my physical copies which I don't intend to use after conversion)? Can I enter licence etc later as well?
I currently have 8 GB ram total -should I leave Xp one at max it suggests of around 3Gb ram?
I have Quad core processor -but should I make Xp Vm one dual core for when it runs on W8.1 host to allow the host some processors so can run at same time or leaving my Xp at quad core will be ok?
Network - I want to use host one as I read it is safer for obsolete XP so do I set that at start or is it better to change this later too -allowing xp to have own internet access (maybe as may need to reactivate also - don't want to call Microsoft
if can avoid it)?
If I just want to convert resulting VM to Hyper-V VM -which software to use after for this that is freeware (Virtual Box or VMware Player or Hyper-V -not sure which can do it) and do I not then install Vmware tools?
SYSPprep should I do anyway regardless of what target VM will be when configuring later, even if on same hardware machine? OR can I just boot Vm and see if boots ok first?
Anything else I should set specifically for this future use of the VM image in hyper-v?
AU -
Error 10698 Virtual machine could not be live migrated to virtual machine host
Hi all,
I am running a fail over cluster of
Host:
2 x WS2008 R2 Data Centre
managed by VMM:
VMM 2008 R2
Virtual Host:
1x windows 2003 64bit guest host/virtual machine
I have attempted a live migration through VMM 2008 R2 and im presented withe the following error:
Error (10698)
Virtual machine XXXXX could not be live migrated to virtual machine host xxx-Host01 using this cluster configuration.
(Unspecified error (0x80004005))
What i have found when running the cluster validation:
1 out of the 2 hosts have an error with RPC related to network configuration:
An error occurred while executing the test.
Failed to connect to the service manager on 'xxx-Host02'.
The RPC server is unavailable
However there are no errors or events on host02 that are showing any probelms at all.
In fact the validation report goes on to showing the rest of the configuration information of both cluster hosts as ok.
See below:
List BIOS Information
List BIOS information from each node.
xxx-Host01
Gathering BIOS Information for xxx-Host01
Item Value
Name Phoenix ROM BIOS PLUS Version 1.10 1.1.6
Manufacturer Dell Inc.
SMBios Present True
SMBios Version 1.1.6
SMBios Major Version 2
SMBios Minor Version 5
Current Language en|US|iso8859-1
Release Date 3/23/2008 9:00:00 AM
Primary BIOS True
xxx-Host02
Gathering BIOS Information for xxx-Host02
Item Value
Name Phoenix ROM BIOS PLUS Version 1.10 1.1.6
Manufacturer Dell Inc.
SMBios Present True
SMBios Version 1.1.6
SMBios Major Version 2
SMBios Minor Version 5
Current Language en|US|iso8859-1
Release Date 3/23/2008 9:00:00 AM
Primary BIOS True
Back to Summary
Back to Top
List Cluster Core Groups
List information about the available storage group and the core group in the cluster.
Summary
Cluster Name: xxx-Cluster01
Total Groups: 2
Group Status Type
Cluster Group Online Core Cluster
Available Storage Offline Available Storage
Cluster Group
Description:
Status: Online
Current Owner: xxx-Host01
Preferred Owners: None
Failback Policy: No failback policy defined.
Resource Type Status Possible Owners
Cluster Disk 1 Physical Disk Online All Nodes
IP Address: 10.10.0.60 IP Address Online All Nodes
Name: xxx-Cluster01 Network Name Online All Nodes
Available Storage
Description:
Status: Offline
Current Owner: Per-Host02
Preferred Owners: None
Failback Policy: No failback policy defined.
Cluster Shared Volumes
Resource Type Status Possible Owners
Data Cluster Shared Volume Online All Nodes
Snapshots Cluster Shared Volume Online All Nodes
System Cluster Shared Volume Online All Nodes
Back to Summary
Back to Top
List Cluster Network Information
List cluster-specific network settings that are stored in the cluster configuration.
Network: Cluster Network 1
DHCP Enabled: False
Network Role: Internal and client use
Metric: 10000
Prefix Prefix Length
10.10.0.0 20
Network: Cluster Network 2
DHCP Enabled: False
Network Role: Internal use
Metric: 1000
Prefix Prefix Length
10.13.0.0 24
Subnet Delay
CrossSubnetDelay 1000
CrossSubnetThreshold 5
SameSubnetDelay 1000
SameSubnetThreshold 5
Validating that Network Load Balancing is not configured on node xxx-Host01.
Validating that Network Load Balancing is not configured on node xxx-Host02.
An error occurred while executing the test.
Failed to connect to the service manager on 'xxx-Host02'.
The RPC server is unavailable
Back to Summary
Back to Top
If it was an RPC connection issue, then i shouldnt be able to mstsc, explorer shares to host02. Well i can access them, which makes the report above is a bit misleading.
I have also checked the rpc service and it has started.
If there is anyone that can shed some light or advice me oany other option for trouble shooting this, that would be greatley appreciated.
Kind regards,
ChuckyHi all,
I am running a fail over cluster of
Host:
2 x WS2008 R2 Data Centre
managed by VMM:
VMM 2008 R2
Virtual Host:
1x windows 2003 64bit guest host/virtual machine
I have attempted a live migration through VMM 2008 R2 and im presented withe the following error:
Error (10698)
Virtual machine XXXXX could not be live migrated to virtual machine host xxx-Host01 using this cluster configuration.
(Unspecified error (0x80004005))
What i have found when running the cluster validation:
1 out of the 2 hosts have an error with RPC related to network configuration:
An error occurred while executing the test.
Failed to connect to the service manager on 'xxx-Host02'.
The RPC server is unavailable
However there are no errors or events on host02 that are showing any probelms at all.
In fact the validation report goes on to showing the rest of the configuration information of both cluster hosts as ok.
See below:
List BIOS Information
List BIOS information from each node.
xxx-Host01
Gathering BIOS Information for xxx-Host01
Item Value
Name Phoenix ROM BIOS PLUS Version 1.10 1.1.6
Manufacturer Dell Inc.
SMBios Present True
SMBios Version 1.1.6
SMBios Major Version 2
SMBios Minor Version 5
Current Language en|US|iso8859-1
Release Date 3/23/2008 9:00:00 AM
Primary BIOS True
xxx-Host02
Gathering BIOS Information for xxx-Host02
Item Value
Name Phoenix ROM BIOS PLUS Version 1.10 1.1.6
Manufacturer Dell Inc.
SMBios Present True
SMBios Version 1.1.6
SMBios Major Version 2
SMBios Minor Version 5
Current Language en|US|iso8859-1
Release Date 3/23/2008 9:00:00 AM
Primary BIOS True
Back to Summary
Back to Top
List Cluster Core Groups
List information about the available storage group and the core group in the cluster.
Summary
Cluster Name: xxx-Cluster01
Total Groups: 2
Group Status Type
Cluster Group Online Core Cluster
Available Storage Offline Available Storage
Cluster Group
Description:
Status: Online
Current Owner: xxx-Host01
Preferred Owners: None
Failback Policy: No failback policy defined.
Resource Type Status Possible Owners
Cluster Disk 1 Physical Disk Online All Nodes
IP Address: 10.10.0.60 IP Address Online All Nodes
Name: xxx-Cluster01 Network Name Online All Nodes
Available Storage
Description:
Status: Offline
Current Owner: Per-Host02
Preferred Owners: None
Failback Policy: No failback policy defined.
Cluster Shared Volumes
Resource Type Status Possible Owners
Data Cluster Shared Volume Online All Nodes
Snapshots Cluster Shared Volume Online All Nodes
System Cluster Shared Volume Online All Nodes
Back to Summary
Back to Top
List Cluster Network Information
List cluster-specific network settings that are stored in the cluster configuration.
Network: Cluster Network 1
DHCP Enabled: False
Network Role: Internal and client use
Metric: 10000
Prefix Prefix Length
10.10.0.0 20
Network: Cluster Network 2
DHCP Enabled: False
Network Role: Internal use
Metric: 1000
Prefix Prefix Length
10.13.0.0 24
Subnet Delay
CrossSubnetDelay 1000
CrossSubnetThreshold 5
SameSubnetDelay 1000
SameSubnetThreshold 5
Validating that Network Load Balancing is not configured on node xxx-Host01.
Validating that Network Load Balancing is not configured on node xxx-Host02.
An error occurred while executing the test.
Failed to connect to the service manager on 'xxx-Host02'.
The RPC server is unavailable
Back to Summary
Back to Top
If it was an RPC connection issue, then i shouldnt be able to mstsc, explorer shares to host02. Well i can access them, which makes the report above is a bit misleading.
I have also checked the rpc service and it has started.
If there is anyone that can shed some light or advice me oany other option for trouble shooting this, that would be greatley appreciated.
Kind regards,
Chucky
Raja. B -
[SOLVED] virtual machine or dual-boot for development
I'm about to setup a new machine and I am in need of some advice on whether to dual-boot or run a virtual box. Arch Linux is my primary OS, but I need Windows 7 (64-bit) for certain development work. Specifically, the tools I use are Visual Studio Express 10/11 and NI LabVIEW, and I almost always run them both at the same time. Would this type of situation be better suited for a dual-boot setup or could I run it in VirtualBox? I haven't done a lot of work with virtual machines, so I'm not sure of how they typically perform. I mostly care about seamless performance and I honestly don't mind rebooting between the OSes, but if I cat get seamless performance using VirtualBox, then why not go that route. Also, not having to setup up the dual-boot is a plus.
The hardware of this machine includes: 8 gigs of ram, AMD FX 8350, 128 GB SSD, and a 1 GB Radeon 4670 graphics card.
I know this question has been touched on in other posts, but most of the posts I've seen are more than a year or two old. Given advances in hardware, I'm interested in a current advice.
Last edited by tlawren (2013-03-11 16:22:53)Hi,
I have a similar setup for my work. My hardware is : Intel(R) Core(TM) i7-3667U CPU @ 2.00GHz, 16GB of ram, 256GB SSD SED. I run a Windows 8 VM inside Virtualbox with the guest addition + extension pack and use VS 2012 Pro on daily basis.
My VM is configured to have only 1 CPU with a 100% execution cap and 4GB of ram. Thing run just perfectly like this, fluent and eye candy. Depending on my need I increase the number of CPU or tweak the execution cap.
Cheers
Edit:
Sadly modifying the VM CPU number must be done offline. However the execution cap can be tweaked online.
Last edited by dna (2013-03-11 12:46:04) -
Hi there,
just wanted to share my experience with a manual P2V Migration. The VM became to ressource hungry and it was decided to move it off an ESX 5 Cluster to a dedicated physical Machine.
V2P Virtual Machine to physical Server IBM x3650 M4 and switch from BIOS to UEFI Boot environment
Task:
V2P Migrate a VMware virtual machine to a IBM x3650 M4 with a ServeRAID 5110e RAID Controller or any other LSI RAID Controller without 3rd Party tools.
This should also work with other RAID Controllers or Servers but be sure to pick the right drivers then.
Extra Task:
The VM's boot environment/virtual BIOS is BIOS, not UEFI (as per default VMware Setting). The physical Server is running in UEFI mode.
The Challenge:
After restore the Server won't boot or get into a BSOD (7B), because the RAID drivers are missing.
After restore the VM won't boot because the boot environment has changed from BIOS to UEFI
Preparations:
An existing physical Server of the same type and with the same RAID controller and same OS would be nice for troubleshooting and checking the registry.
An existing DHCP server will make networking things easier.
Connect the new physical server x3650 M4 to power and network
create a virtual drive that has at least the size of the existing VM plus the size of the full backup (.vhd). Should be about twice the size of the original vmdk.
Get a USB Flash stick (I used a 8GB modell so no problem with larger sticks)
Download and extract LSI MegaRAID Driver on that USB media (I used 6.705.05.00-MR_Windows_Driver directly from LSI website)
Download and extract INTEL Network Adapter Driver on that USB media (I used 12.11.97.0 of e1r62x64.inf from 19.5 driver release from 2014.09.26 directly from LSI website)
Step by Step:
if you have an other physical Server of the same type and same Controller and same OS:
1. open regedit and export everything related to SCSIAdapter and megasas2 to .reg files or skip this step and use my files below
some of this (sub)keys may not be accesible - you will then first take ownership and/or modify permissions to read them
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_1000&DEV_005B&SUBSYS_04121014&REV_05
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\megasas2
this one is more complicated:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase (only relevant are those devices where the service name is megasas2 - export the whole subkey and get the filtering done with tools like notepad++)
Make a copy of the following files/folders:
c:\programdata\LSI\
c:\windows\inf\megasas2.INF
c:\windows\inf\megasas2.PNF
c:\windows\system32\drivers\megasas2.SYS
on the existing VM:
1. create a full backup (image) with the built-in Windows Backup Utility and save it in an accessible network location (you will need this one, if anything goes wrong or you want to come back to this point.
Alternatively you could create a VMware snapshot.
2. import the .reg files you created earlier or import my files below.
Attention: This will make the VM unbootable!
But it is required to prepare the VM for the new RAID controller when it will be restored on the physical server.
Do NOT reboot now as this will make the VM unbootable!
4. Copy the LSI folder and the megasas2.INF/PNF/SYS files to the appropriate destination folders on the VM.
3. again create a full backup (image) with the built-in Windows Backup Utility and save it in an other accessible network location but not where you safed the first backup.
This will be the "golden" backup if you want, where the RAID controller is prepares. We will rebuild the new machine with this second backup.
4. Optional: you could use the Backuputility now to restore the Systemstate of the first backup and reboot or restore the VMware snapshot.
This will undo the changes we made to the VM.
on the new physical server:
1. boot the physical server from Windows Server 2008 R2 SP1 DVD
2. when it is ready to install, press shift+F10 to get command prompt and do not click to install Server 2008
3. check driveletter of the USB stick with diskpart list vol (was C: at my Server, so don't wonder about that letter)
3. load drivers for ServeRAID SAS controller (this is mandatory to see the volume in diskpart)
drvload c:\srv_2008_x64\megasas2.inf
4. load drivers for INTEL I350 Gigabit NIC's (you will need this to access the backup that is on the network)
drvload c:\PRO1000\NDIS62\e1r62x64.inf
5. wpeinit (will start network. wait ~15 sec to let it start and get IP address)
check if you have IP connectivity an address with ipconfig, if not, use an other NIC driver and repeat steps 4+5
6. create the EFI and BCD
diskpart
list disk
select disk x (where x is the number of the disk to convert)
clean
convert gpt
create partition EFI size=128
format fs=fat32 quick label=EFI
assign letter=i or any other free drive letter
create partition MSR size=128
6.1 Copy EFI bootloader to EFI partition
i: (where i is the letter of your EFI partition)
mkdir EFI\Boot
mkdir EFI\Microsoft\Boot
copy x:\Windows\Boot\EFI\bootmgfw.efi i:\EFI\Microsoft\Boot (where x ist the default letter of the current Windows PE environment)
copy x:\Windows\Boot\EFI\bootmgfw.efi i:\EFI\Boot\bootx64.efi (note that the file will be renamed to bootx64.efi)
7. create the new partitions
diskpart
create partition primary size=100000 (edit the size to your needs. this will later become the system drive of your server)
format fs=ntfs quick label=Windows
assign letter=Y or any other free drive letter
create partition primary size=990000 (this will temporarily store your backup and we need it for the restore process)
format fs=ntfs quick label=Backup
assign letter=B or any other free drive letter
exit
8. map network drive and copy the backup .vhd to the local disk
net use L: \\networklocation\where\you\saved\the\backup (enter the credentials when asked)
copy the .vhd file that contains the OS of your VM to the local Backup Partition B. The relevant vhd file is usually the largest file in that fileset.
Note that the names are very similarly - be sure to get the correct file!
copy "L:\WindowsImageBackup\VMNAME\Backup 2015-02-03 123456\00e767c6-xxxx-xxxx-xxxxxxxxxxxx.vhd" B:\
give it time, this is slow and will take some minutes/hours and you will not see any progress! Look at the disk-LED's to see if anything is still happening
9. mount the .vhd and copy it's contents to the new system partition
Note that you can only mount a locally stored .vhd. You cannot mount a .vhd in a network location.
diskpart
select vdisk file=B:\00e767c6-xxxx-xxxx-xxxxxxxxxxxx.vhd
attach vdisk
select vol 5 (where 5 is the number of the mounted vdisk)
assign letter=Z or any other free drive letter
exit
10. Restore the files from the image
z: (where z is the letter of your mounted .vhd)
xcopy * Y:\ /e /c /h /k /o /b /q /y (where Y: is the letter of your new partition with the label "Windows")
several "Access denied" messages appear, ignore them. Those are SystemVolumeInformation folders.
11. Create Boot Configuration Data (BCD)
bootrec /RebuildBcd
this will try to repair the missing BCD on the second of the two small partitions we created earlier in and should normally work, otherwise you'll have to create BCD manually (search google for that procedure)
Note that it may find more than one Windows installation and ask which sould be added to the boot list. Be sure to select only the one that is in the correct Volume (Y:\)
that's it - exit the DOS command box and close the "Install Windows" Window, after a prompt it will reboot.
Select "Start Windows Normally", if Windows Error Recovery appears.
12. Preparing Windows
When Windows boots for the first time, DO NOT reboot if you are asked, it won't come back at this stage!
Install Intel chipset drivers for the Server (I used "intc_dd_inteldp_9.4.0.1026_windows_32-64.exe" from IBM website)
Open Device Manager, uninstall the "RAID-Controller" with the exclamation mark. You cannot install the correct driver for this Device at this point, it will bring you the error: "Cannot create a stable subkey under a volatile
parent key"
Once again, DO NOT reboot!
In Device Manager select Action>Add Legacy Hardware
click Next
select Hardware manually
select Storage Controller as Type
LSI should be listed, select "LSI MegaRAID SAS 9281-8E"
click Next, ignore the error "Code 10" Message.
Click Done.
Rightclick the LSI MegaRAID SAS 9281-8E device with the exclamation mark in Device Manager
select Update driver
select Browse my computer for driver software
select let me pick from a list of device drivers on my computer
select "Have Disk"
browse to the folder where the extracted RAID driver 6.705.05.00-MR_Windows_Driver is located (e.g. USB Flash stick E:\6.705.05.00-MR_Windows_Driver\srv_2008_x64)
then unselect "Show Compatible Hardware"
on the right side, scroll up and select "IBM ServeRAID M5110e SAS/SSATA Controller"
ignore the Update Driver Warning and click Yes
click Next, ignore the error "Code 10" Message.
ignore the exclamation mark on "IBM ServeRAID M5110e SAS/SSATA Controller" in Device Manager but be sure that there is only this controller and no other RAID-Controller or LSI SAS Controller listed under "Other Devices"
or "Storage Controllers"
NOW you are safe to reboot
After reboot you will find two "IBM ServeRAID M5110e SAS/SSATA Controller" in Device Manager
Rightclick and uninstall the one with the exclamation mark. Do not tick the checkbox to remove the driver as well!
You're done!! (hopefully)Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C31115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C38015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C41115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C48015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C51115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C58015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C61115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C68015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C71115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C78015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C81115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C88015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C91115D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C98015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_D20219E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_D20319E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0071&SUBSYS_00721137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00011BD4]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00721137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00731137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_008F1137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B01137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B11137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B61137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B71137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00C21137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00C31137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_03B11014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_040015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_040D1014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_10541000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_11771734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_14581002]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_1F201462]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_30351054]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_350C8086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_350D8086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_822910F1]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_843B1043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_84711043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92211000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92401000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92408086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92411000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92418086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92421000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92431000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92441000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92A01000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92A11000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92501000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92511000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92701000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00011BAA]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00021BD4]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00791137]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_02001AE3]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03B21014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03B31014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03C71014]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_070015D9]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_11761734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_11B31734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_30361054]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_350B8086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_84731043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_84801043]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_8985152D]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92551000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92561000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92568086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92601000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92608086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92611000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92618086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92621000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92631000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92641000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92648086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92671000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92678086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92681000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92688086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92751000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92758086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92761000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92768086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92771000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92801000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92808086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92811000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92821000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92828086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92841000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92881000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92891000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92901000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92908086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_D20819E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_D20919E5]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0409&SUBSYS_10091000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10011000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10018086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10021000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10031000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10038086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10041000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10081000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10088086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_100C1000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_100D1000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10811734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10a31734]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_20041000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_20051000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_30161054]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_34908086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35008086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35018086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35048086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35078086]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_82871033]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0413&SUBSYS_10051000]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="megasas2"
"DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7" -
SAPB1 in virtual machine?
Hello!
Has anyone had a success story running SAP B1 in a virtual machine, particularly virtualbox? Here is our problem: sql or SAP installer is very inefficient and stalls the installation process at 100% cpu for hours.
Our setup. Host server:
2 x Intel(r) Xeon(r) CPU E5620 @ 2.40GHz (2 x 4 cores, 2 x 8 virtual processors)
24GB RAM
6 x 1TB SATA-3GB 7200 rpm in RAID5 (raidz1)
Software: Opensolaris, SunOS 5.11 snv_134b
Virtualbox 3.1.8
SAPB1 Virtual Machine (more details - at the bottom):
Hardware (virtual)
4 cores, 8GB RAM, 32MB video ram, 2 HDDs:
C:\ - host: VMDK 80GB, dynamically allocate storage, on RAID5/raidz1 volume, guest: NTFS
E:\ - host: VDI 200GB, dynamically allocate storage, on the same raidz1, guest: NTFS
Software:
Windows Server 2008 R2 64bit (180 days evaluation license)
SQL Server 2008 R2 (180 days evaluation license)
SAP B1 8.81
Situation:
SQL server is configured by SAP installer. When installing SAP Demo database the VMu2019s cpu usage stays at 100% with sqlserver process at 18%, RAM usage is at only 40% (60% free), the installation process takes 6-7 hours to complete. SQL data and log files are placed in the same C:\ drive as the guest operating system. Disk activity shown by the host system is on average 300KB/s writes. The load on the host machine is 10% cpu for the copy of VirtualBox running this VM but no other cpu- ram- or disk-intensive tasks running at all. Earlier tests showed 30MB/s sustained writes on raidz1 but significantly faster in bursts due to effective ZFS caching in hostu2019s RAM. For what I can tell, there is plenty of disk bandwidth, host cpu and ram and guest ram.
Thereu2019s also a weirdest thing: CPU figures on guest donu2019t add up: performance monitor shows 100% cpu used on all four cores but when you look at individual processes the biggest one is sqlserver at 18%, SAP setup is 0-3%, taskmanager itself is 6-12%, the rest is negligible including IDLE process at 0-2%. The machine is clearly very busy with slow screen updates etc. but the sum of all running processes plus idle process is at 40-50%. Once install of the demo database sucessfully finished many hours later cpu usage came back to normal - 95-97% idle.
Suspicions:
1. SAP installer and/or production executables are compiled so that they arenu2019t happy at all under a hypervisor or only under virtualbox in particular. Earlier trial installation of the an old, 2004, version of SAPB1 on the same VM didnu2019t show this problem although we didnu2019t specifically test performance, it was just an early test installation. Slow u201Cby designu201D?
1a. SAP is not happy with evaluation versions of Windows Server or SQL. Slow u201Cby designu201D?
2. Placing demo DB files and logs on a different virtual drive (E:\) or an iSCSI drive will dramatically improve performance of SQL - This is next thing we are going to try.
2a. VirtualBoxu2019es realisation of VMDK (VMware disk format) is affecting performance.
2b. The format of virtual disks was chosen to dynamically allocate storage which is, although it seems plenty of spare host disk performance is available is still inefficient. But then, why CPU usage is the problem? Is that caused by badly written .exe files that do not return spare cpu cycles while waiting for disk operations?
Many thanks for any tips!
More on VM:
Guest OS: Windows 2008 (64 bit)
Memory size: 8192MB
VRAM size: 32MB
Number of CPUs: 4
Synthetic Cpu: off
CPUID overrides: None
Boot menu mode: message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
ACPI: on
IOAPIC: on
PAE: on
Time offset: 0 ms
Hardw. virt.ext: on
Hardw. virt.ext exclusive: on
Nested Paging: on
VT-x VPID: on
Monitor count: 1
3D Acceleration: off
Storage Controller Name (0): SATA Controller
Storage Controller Type (0): IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 30
Storage Controller Port Count (0): 2
Storage Controller Name (1): IDE Controller
Storage Controller Type (1): PIIX4
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1): 2
Storage Controller Port Count (1): 2
SATA Controller (0, 0): /export/home/admin/.VirtualBox/HardDisks/RAID/disk1.vmdk
SATA Controller (1, 0): /export/home/admin/.VirtualBox/HardDisks/RAID/disk2.vdi
IDE Controller (0, 0): /opt/VirtualBox/amd64/additions/VBoxGuestAdditions.isoWhile the other suggestions here have merit, I wonder what can be done with your current solution...
Why are you running such an old version of VirtualBox? Version 4.1.4 is available for Solaris machines; I would think you could use that under OpenSolaris (although I am unfamiliar with the details of OpenSolaris, as I haven't run it).
The dynamically-allocated disk is the second most likely culprit in the performance issues, right behind the older version of VirtualBox... I have used the dynamic allocation many times for file servers and application servers, but a database server needs to have the highest disk I/O performance possible. I don't like to see my client application waiting on the database to allocate new disk space which is waiting on the hypervisor to provide additional disk... I think you see my point.
You might take a snapshot or clone the VM and test on another machine, even to the point of cloning the existing virtual hard drive to one which was created as a statically allocated disk.
Those would be the first two items I would try out. Let us know how successful you are; I'd love to hear what seems to be the bottleneck, as we are considering placing our B1 services inside a VM. We are considering VirtualBox, VMware, and Citrix Xen at the moment.
Rob -
How to connect USB external Harddisk to Hyper-v virtual machine
Hi,
We are running hyper-v server 2008 R2, we have external USB harddisk connected in hyper-v Manager, we are not able connect this USB to virtual machine.. is this option is available in hyper-v? if no is there any document from microsoft stating the same?
Regards
AshaHi,
Unfortunately, USB is not supported on a Hyper-V virtual machine. You can perform the following suggestions:
1. Offline the USB hard disk on the Hyper-V host machine and connect it to the virtual machine as a pass-through disk(if the USB hard disk is support)
For more information, you can refer to:
Configuring Pass-through Disks in Hyper-V
http://blogs.technet.com/b/askcore/archive/2008/10/24/configuring-pass-through-disks-in-hyper-v.aspx
2. You can also use some USB over Ethernet application.
Best Regards,
Vincent Hu -
Constantly "Cluster resource 'Virtual Machine' in clustered service or application 'SERVER' failed
Hi...
I have an IBM BladeCenter S with 3 blades and an IBM System Storage DS3300 (ISCSI).
In each blade is running Windows Server 2008 R2 with
HYPER-V,
Failover Clustering with Cluster Shared Volumes.
I have observed that many errors occur constantly in "Failover Cluster Manager" and some VM´s are relocated to another blade automatically, however thoses VM´s sometimes no longer responds to network activity.
The errors I have observed in the "Failover Cluster Manager" are:
Source: Microsoft-Windows-FailoverClusting
Event ID: 1069
Description:
Cluster resource 'Virtual Machine' in clustered service or application 'SERVER' failed.
Source: Microsoft-Windows-FailoverClusting
Event ID: 1205
Description:
The Cluster service failed to bring clustered service or application 'SV-DBURAS' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Another error (warning type) that is constantly generated in the SYSTEM events (Mirage is the storage name):
Source: ds4dsm
Event ID: 769
Description:
IO error being retried via alternate controller Mirage:1
Source: ds4dsm
Event ID: 10
Description:
Mirage:0 Failover command issued.
Source: ds4dsm
Event ID: 801
Description:
Failover succeeded to Mirage:0.
Thank you in advance any help!Hi,
I suggest referring to the following articles:
http://technet.microsoft.com/en-us/library/cc756225(WS.10).aspx
http://technet.microsoft.com/en-us/library/cc773525(WS.10).aspx
Tim Quan - MSFT -
SCVMM Default Virtual Machine Path - CSV
I am having an issue where SCVMM is dropping the default virtual machine path from the host leaving a blank setting (none).
Below is my setup:
3 Win2K8R2SP1 host clustered
CSV used mapped to C:\ClusterStorage\<lunname>\
I add in the default path C:\ClusterStorage\<lunname>\ when I add the host to SCVMM then turn off placement for all other local drives
The default path stays in the configuration and is listed for placement until the host are either refershed on a automated basis or I manually choose the refresh host job. After the refresh I see the change from vpaths to (none).
This is causing issue with a deployment wizard from Citrix for default virtual machine placement, any help would be greatly appreciated.
Thanks.
EDIT:
Sorry forgot to menito I am using SCVMM 2008 R2 SP1 as well.You can select option "Make this virtual machine highly available" will store VMs
in CSV,
If you are creating new VM from an Existing VM template , you have to choose the same option and in
"Select Destination" Wizard Choose - "Place the Virtual Machine on a Host"
This will help you to to save Your VMs in to CSV...
Cheers -
Powerbuilder with Virtual Machine / Build Machine environment
We are in the process of upgrading our from Powerbuilder 10.5 to Powerbuilder 12.5, and upgrading our virtual machines from Windows 2003 to Windows Server 2008.
We work in a virtual machine environment, connecting through Citrix -- multiple virtual developer desktops are set up, and we have one machine that serves as a formal "build" machine. The build machine uses Powergen to do a formal Powerbuilder build from within a controlled environment.
We have purchased one Powerbuilder 12.6 license per developer. But I can't figure out how to set up the licensing to let everyone work under the new platform. The other pieces seem to work fine (including version control licenses that use a license server and Powergen); not sure why Powerbuilder setup seems so complicated.
We have set up a served license model, per instructions. The server seems to serve up licenses fine, but they never seem to be released. It seems that one license is taken up for each developer, for each virtual machine. If there's no way to release it when you're done on a particular VM, we go through the licenses pretty quickly.
Under this scenario, even if a developer ONLY needs to connect into one VM for development, and needs to be able to do a formal build on a different non-developer machine, it seems that I'd have to purchase two licenses (when you multiply this by the # of developers involved, the cost adds up pretty quickly)? That can't be right, is it?
For our Source control licenses (which, I believe also use Sysam or something similar), it is also based on the # of developers. When a developer moves from one machine to another (closes the connection to source control), the license is "released", so that the same user can grab it from a different machine. We can set up the amount of time after which the license can be released. It's still based on a named user (registered in the server), and is not a floating point license; it just gives the developers some flexibility so that they can get their work done.
How can I set up Powerbuilder 12.6 and/or Sysam to be able to do something similar without having to buy one license per (developer, VM) combination?
Thanks in advance
Alok MehtaThank you to everyone that responded.
Based on the responses above, I just wanted to follow up with my own thoughts and my plan of action.
First, my current plan of action...
1) Each developer in our shop will run PB off of a single machine only (either virtual or desktop).
2) Following Paul Horan's suggestion,
> What we did at my company was setup a dedicated physical build machine - not
> a VM, but a physical box using a local unserved license.
we will allocate a single license for a physical box so that each developer, when they need to do a formal build, will walk over to that machine in order to do it.
Second, my thoughts...
This is still one more license than what I thought I would/should need, and it's really unfortunate that we even have to resort to this, but the alternative is worse -- I can't justify virtualizing our build machine if it means purchasing twice as many Powerbuilder licenses (one for each developer that may need to do a build).
The licensing constraints are impacting the way we do our work, which is not a good thing. As a long time Powerbuilder developer and manager (since PB 4.0), I find this trend very discouraging. I understand the concern about unlicensed / pirated products, but I believe there are better ways to handle this (without annoying and driving away existing customers).
Those who know Powerbuilder know of the strengths of the tool/platform. But I agree with other feedback on this thread that if a company makes it increasingly hard for existing customers to get their work done using their tool, the customers will look for alternate tools from other vendors that don't cripple the development infrastructure as much.
Thanks again to everyone for providing very valuable feedback and advice! This was very helpful! -
Around about 5 am GMT this morning one of my Virtual Machines went offline and never recovered. All endpoints became inaccessible (RDP, HTTP, HTTPS, SMTP etc). I'm using the VM to host a small (relatively low traffic) .NET web application so only realised
when a user reported the issue later on in the morning.
First thing I attempted to do is RDP into the VM but this wasn't possible. I suspect the outage was triggered by a routine maintenance update that Microsoft applied to the VM in the night (but can't be sure!). Why would this kill all the endpoints? or what
other reason would cause the endpoints to spontaneously fail like this? I haven't been near the server for 3 weeks.
I attempted a shutdown, restart and instance resize but none of these fixed the issue. The only thing that worked in the end was to STOP the server and manually START, this was far from ideal as the Virtual IP was regenerated and I had to change the A records
on the DNS server which has resulted in even more down time.
It's only a small web app but these kind of things really put me off moving some of our larger web properties into the Azure cloud. When things like this happen you really have limited options!
EDIT ---
When I say kill all the endpoints, they didn't actually disappear from the management portal, they just failed to work. VM server is running Windows 2012 on a small instance, no availability sets.
Hi,
I found a thread that was discuss Azure Virtual Machine can't access issue, the thread link is:
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/538a8f18-7c1f-4d6e-b81c-70c00e25c93d/troubleshooting-endpoint-connectivity-rdpsshhttp-etc-failures , it give several ways to fixed it, hope it helps.
Best Regards
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
Volfs in virtual machine doesn't come online
Hi,
I am running Solaris10 inside Virtual Box 2.1.0.
Even though I am mounting the ISO image for vol2 of Solaris10 installation, when the system reboots, the system doesn't recognize the cdrom and I have to skip installing the rest of Solaris cd's.
The volfs doesn't exist and svcadm enable says that it doesn't see "volfs" pattern ...
what the heck is going on?
Does anyone know on this forum?
Please help ...
Thanksmario_garcia wrote:
Hello
i have been trying to mount a cd in a virtual machine but volfs is disabled and it just doesn't come online.
i do svcadm enable volfs but it still remains offline
I try with this : svcadm enable -s volfs
svcadm: Instance "svc:/system/filesystem/volfs:default" has unsatisfied dependencies So what are the dependencies? What does svcs -xv show?
Darren
Maybe you are looking for
-
Fatal Error has occured and the application is being terminated
It seems that Captivate is eating my projects. I've started my second project (after completing my first without any errors) and I'm constintly getting corrupted files. It set me back at least a few hours worth of work. So I started creating backu
-
New Hard Drive-can't locate files
I just moved my library to my new external hard drive. I have switched my preferences to look in the new drive, but itunes gives me the little exclimation point next to my songs and says it can't locate the files. I can go through and locate them all
-
Yahoo account says off line. How to get online?
mac osx 10.8.5. I set up yahoo & hotmail accounts in apple mail. Sometimes they work & in the address bar to the right it says online. Then either or both switch to offline. How can I get them to stay online? I was told that this has nothing to
-
Java.lang.ClassNotFoundException: _MostrarPr
Hello everybody, I deploying an ear file in application server in Windows and work all right, but the same file I deploy in Linux, but when at last the deploy was successful, somo jsp pages doesn't work. In a page I insert a record in the database an
-
I have recently had to hand back my work computer having had my email account closed as well. I have opened a new account but having done this I cant open the books I have on my reader that were purchased through my old account. How can I open my boo