I've found this issue in several other threads and haven't been able to solve it in my case yet. I've repaired permissions and removed any culprits of theiving major device numbers I can think of offhand. Don't have virtual box or any other vm software installed. Virtual machine won't resume - starts with the dev/vmmon missing issue and ends up at 'cannot find peer process to connect to'
I've attached the support bundle. Any help would be much appreciated!
Thanks,
Erich
That did it, can't believe it was that simple of a fix. Thank you so much.
Is there any mechanism to check the data that is replicated in recovery site is consistent or not? - Yes, see below.
It does change block tracking evey time (Subsequent Replications) by using block by block comparison of source and target disk or it just refers .psf file? - it doesn't use CBT. It uses a LWD (which is similar to but not the same as CBT). It doesn't do a block by block comparison on an ongoing basis. The vSCSI filter tracks writes as the VM writes to it's disk.
See below for details:
A lightweight snapshot is a consistency group across all virtual disks in a VM. When a snapshot is created, all writes are “synchronized” across all virtual disks using a Two-Phase-Commit protocol in the vSCSI filter. This provides write order consistency across all virtual disks. The replica data is not written to the shadow VMDK until entire block group has been received
vSphere Replication creates a redo-log on the disk at the target location. When a replication takes place the vSphere Replication Appliance receives the changed blocks from the source host and immediately writes them to the redo log on the target disk. When the complete replication bundle (the “light weight delta”) had been received, it then commits the redo log to the target VMDK file.
VR then retains the redo log in the form of a snapshot, which is automatically committed during failover. This snapshot is always retained in case of error during the commit; during crash or corruption it ensures there is always a ‘last known good’ snapshot ready to be committed.
It is supported. The issue is with the boot loader. SLES 11 used to install GRUB on BIOS and ELILO on UEFI. Converter doesn't support (E)LILO. However SLES 12 switched to GRUB2 which is now used for both firmwares.
Hi Ulli
You were absolutely right. I had powered on the VM while trying to make it work with the wrong settings in WMX.
And you where right again in your instructions above.
The VM is now fully functional again and I am in the process of backing up everything and checking in all code.
The VM was my SharePoint 2013 dev mashine and there were some code on it that wasn't checked in to TFS so you just saved me a lot of hours recreating...
Thank a lot for taking your time to get me out of this mess.
You are the man.
Best regards and thanks again
Søren
Thanks for help!!
Now i can configure vcenter server!
REgards!
In profile.xml we use ${app.ip} to show the ip address of the VM. However, this is showing the IP from eth0, we need it to show for eth1.
Please share the steps in getting this .
Hi,
Even while some of the other threads show similarities, it doesn't have to mean it is the same issue.
I had a quick look at some of your logs and I notice that your VMware Fusion version is from 2014 (Fusion 5.0.5)
That wouldn't be a problem, but your system log has this snippet:
Sep 28 14:16:36 D25MH1HUF8JC com.apple.kextd[51]: Untrusted kexts are not allowed
Sep 28 14:16:36 D25MH1HUF8JC com.apple.kextd[51]: ERROR: invalid signature for com.vmware.kext.vmci, will not load
Sep 28 14:16:36 D25MH1HUF8JC com.apple.kextd[51]: Untrusted kexts are not allowed
Sep 28 14:16:36 D25MH1HUF8JC com.apple.kextd[51]: ERROR: invalid signature for com.vmware.kext.vsockets, will not load
Sep 28 14:16:36 D25MH1HUF8JC com.apple.kextd[51]: Untrusted kexts are not allowed
Sep 28 14:16:36 D25MH1HUF8JC com.apple.kextd[51]: ERROR: invalid signature for com.vmware.kext.vmnet, will not load
Sep 28 14:16:36 D25MH1HUF8JC com.apple.kextd[51]: Untrusted kexts are not allowed
Sep 28 14:16:36 D25MH1HUF8JC com.apple.kextd[51]: ERROR: invalid signature for com.vmware.kext.vmx86, will not load
Sep 28 14:16:39 D25MH1HUF8JC com.apple.kextd[51]: Untrusted kexts are not allowed
Sep 28 14:16:39 D25MH1HUF8JC com.apple.kextd[51]: ERROR: invalid signature for com.vmware.kext.vmci, will not load
Sep 28 14:16:40 D25MH1HUF8JC com.apple.kextd[51]: Untrusted kexts are not allowed
Sep 28 14:16:40 D25MH1HUF8JC com.apple.kextd[51]: ERROR: invalid signature for com.vmware.kext.vsockets, will not load
Sep 28 14:16:40 D25MH1HUF8JC com.apple.kextd[51]: Untrusted kexts are not allowed
Sep 28 14:16:40 D25MH1HUF8JC com.apple.kextd[51]: ERROR: invalid signature for com.vmware.kext.vmnet, will not load
Sep 28 14:16:40 D25MH1HUF8JC com.apple.kextd[51]: Untrusted kexts are not allowed
Sep 28 14:16:40 D25MH1HUF8JC com.apple.kextd[51]: ERROR: invalid signature for com.vmware.kext.vmx86, will not load
IOW, if this is the last version of the VMware Fusion app that you are running then it appears that you do need a newer version that has properly signed kernel extensions.
From memory the signing of kernel extensions was changed/fixed in Fusion 6.
So far I've not heard about anyone who was able to run VMware Fusion 6 on macOS Sierra (not sure if your are on Sierra, didn't see the OS version), with Fusion 5 your chances are even less.
It does not mean it isn't possible, but at least it is not easy to get it to work.
edit: Most likely your solution is to install Fusion 8.5, you can download that from here:
Try VMware Fusion or Fusion Pro.
You can try for 30 days if that resolves the issue and then change the license on that "trial" into a permanent one by buying the upgrade.
Which btw is the only lucky part, before Fusion 8.5 you could only buy an upgrade from one version earlier and now you still can upgrade from Fusion 4 and do not have to pay the full amount.
--
Wil
Wow! So I could use an high-end server without hard disk, raid, etc etc and use only one USB stick? I never would have thought it.
In this scenario my high availability seems not so high...
Last question:
I've read that it's not a good idea to store SQL Server VM on a NAS due to poor performance, many people raccomend to use a local storage or a SAN.
But, If I want create a cluster I can't use local storage, and a SAN would be expensive and useless for my purposes.
What would you recommend me?
thank you
thank you
thank you
ds
When I realized I was still on v5 I thought this might be the issue although it had been running just fine and I hadn't upgraded OS'es since the last time I successfully booted the VM as far as I can remember. I'm running 10.11. I've purchased the upgrade to 8.5 and we'll see if that fixes the problem. Thanks!
I'm on Kubuntu 4.4.0-38-generic.
I downloaded VMware Workstation Player.
I don't have a proxy, VPN or anything, it's flat connection that works perfectly on anything, except your software.
Guest OS is Microsoft Windows 10 Pro x64.
After successful installation I clicked on "Virtual Machine > Install VMware Tools".
It told me that my VMware Tools was outdated and is it time to update to "VMware Tools for Windows 2000 and later 10.0.10".
But it does not connect it gets stuck on this only screen, this is the only thing I see:
http://oi63.tinypic.com/2e5sdxx.jpg
It hasn't changed this year. So what do I do to get this to work?
I have manually downloaded "VMware-Player-12.5.0-4352439.x86_64.bundle.tar" from your servers.
Is it possible to install it, and will it be sufficient for all the latest features in your player?
Problem solved. Thanks! Must have run an update since I last ran the VM and didn't realize it.
So after we run a SRM Test we are expected to provide the History HTML report. Generally we export that from the web client and that works great but when we have 4 histories per recovery plan and 15+ recovery plans we now start to look at automating this export.
Unfortunately I am not able to find out how to get the XML data of the history report like we get from the web client. I get this far:
$SRMExtensionData = $SRMConnection.ExtensionData;
$Recovery = $SRMExtensionData.Recovery;
$RecoveryPlans = $SRMExtensionData.Recovery.ListPlans();
foreach ($RecoveryPlan in $RecoveryPlans) {
$RPHistory = $Recovery.GetHistory($RecoveryPlan.MoRef);
$RPHistoryCount = $RPHistory.GetResultCount();
$RPHistoryResults = $RPHistory.GetRecoveryResult($RPHistoryCount);
}
Each history result only gives me :
Key :
Plan :
Name :
Description :
StartTime :
StopTime :
ExecutionTimeInSeconds :
TotalPausedTimeInSeconds :
ResultState :
RunMode :
WarningCount :
ErrorCount :
Am I missing someplace else to get this information from or a method to export?
Hi,
I'm new to Vrealize so if this is the wrong place to post I appologize.
I've been searching for a tutorial or examples for creating Custom Resources/Dynamic Types in VRA 7.0.
I've currently created a namespace, type and find workflows in VRO but don't see the inventory items returned by the Find All workflow. At this point I'm not sure what I'm doing wrong.
Any help finding comprehensive documentation of these features would be really helpful.
Thanks,
-Tony
Hi,
Yeah, those are the instructions I followed. The only difference between what I did and what is written in the instructions is that I did not have the "Install VMWare tools" option, instead it said "Reinstall VMWare tools". No error message was displayed so I believe it was successful.
When I go to VM Display setting, it is set to auto detect and I am unable to change the display settings.
Thanks,
Ben
On Red Hat Enterprise Linux 6 or 7, in a guest OS in the VMWare environment, not using multipaths, is there a danger to specify a simple udev rule as follows?
KERNEL=="sdb1", OWNER="oracle", GROUP="dba",...
Currently we use this rule:
KERNEL=="sd?1", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent", RESULT=="<UUID returned by scsi_id>", OWNER="oracle", GROUP="dba",...
(We set disk.enableUUID=true in vSphere to get the UUID.)
The concern is that the label sdb for this specific disk may change under certain conditions, maybe after inserting a new hard disk which happens to be scanned earlier than this one on next reboot. I think that would be true if this was not a VM guest. How about on a VM? Thanks.
Hi DarcyzDarcyz
I tried to uninstall and reinstall according to the knowledgebase. This did NOT solve the problem. In the latest version i had, 8.2(I think) was extremely energy efficient, and the fan was never running. I was actually surprised how energy efficient this version was compared to 6.0, 7.0 and the other 8.x version.
Now with 8.5, the enrgy levels are up, and fan is running constantly like the 6.0 version. I hope the Development team will take a look at this.
Anybody have other experiences???
Thanks,
Per
This works great and fast. This is the ticket for me. Thanks!
Right as I saw your response I was toying with this. It takes a lot longer and it does not have the much better formatting of yours.
$vms = gc .\_VMs.txt
foreach($vm in $vms) {
get-vm $VM | get-vmhost | select name
}
I'm rolling out AppVol 2.11 and UEM 9 in a non-persistent Win 10 desktop environment.
Is there a recommended way to handle the user profiles i this type of configuration?
I can use a writablevolume for everything, but they are seem challenging to backup on a regular basis and I would rather not keep user files in the writablevolume. Standard Windows Roaming User Profiles and UEM redirection for the user files (my Documents, etc.) would work, but there is the whole "delay at login until the whole Roaming profile is loaded" thing I would rather avoid if possible. I unsuccessfully tried to use a writablevolume to store the user profile settings (absent a MS Roaming-Profile) but it breaks UEM redirect of the user folders (My Documents, etc) and places these files in the writable volume.
How are others configuring their systems?
super
