I am running FreeNAS 11.1-U5 at home. I have everything configured and have created VM's for Windows Server, Ubuntu, pfSense, FreePBX. I was able to install Windows and Ubuntu, but shortly after (a few hours after installing them), and after turning them off through the FreeNAS GUI, they have stopped turning on. FreeNAS reports at the top of the GUI that the start was successful, but the VM details still read "stopped".
I have run the VM's before and have the required settings in my CMOS configured for the Host (FreeNAS machine). Restarting the host will fix the problem for a while and it will let me work with the VM's, but I cannot keep restarting FreeNAS. Can anyone tell me why this happens and how to fix it please?
Related
I have Redhat 6.10 Synchronizer Server and xen client device setup. I am able to download updates via a manager software which run on xen client device.
But each time I want to download the update.tar
I restart the apache and then client xen device.
or I have to reboot the xen client device which I want to update then it downloads.
But sometimes even on xen client device reboot the update.tar wont download.
xen-client: downloading ....and it just keeps downloading without downloading it. It times out. I believe that for the update to download on the xen client device just restarting the xen client or invoking the client service should be enough. There should be no need to restart apache and then restart the xen-vm-client.
I am not able to download without restarting the httpd server. ie I have to run 'service httpd restart' and then immediately 'xen-vm-client reboot' . But without this I am not able to download the update.tar by just firing 'xen-vm-client reboot' on Xen. I have to restart httpd and then xen client device for it to download.
I had an issue with Redhat 6.10. After 'yum install httpd' and rebooting redhat it wont boot up. And then after debugging through the boot process, I figure out that httpd service running at different runlevels on boot stops redhat from booting up. So had to
chkconfig httpd off
chkconfig httpd --del
This fixed the issue of httpd at runlevels hanging the redhat bootup. But I think this could be the reason why I have to restart httpd to get the update to download. Otherwise if I reboot the xen client device it downloads without a httpd restart. So any hints/ideas are really appreciated.
Please give me some understanding about why this is happening and how this can be solved if you know.
Once again grateful for all the help.
Regards
Shraddha
Next what I ll try is 'chkconfig httpd on' this might again cause the redhat to hangup on booting. And thus I may have to reinstall the entire Synchronizer redhat 6.10 setup. Or still trying to investigate about the issue.
The Issue: I have disabled SELinux entirely. We have Apache running on a CentOS 8 VM. We have a simple information page running on the server. It displays great when we are on that VM in Gnome using either 127.0.0.1, locahost, or it's actual IP address. However, we cannot view this page from the same subnet or any subnet. The message we get in our browsers when off that server is "server took too long to respond". I am thinking there is some small little thing we must be missing in the Apache config. We even have Webmin on there to make the administration easier. I have never had this problem with CentOS 5/6/7 previously. I know that CentOS 8 is the last release as RHEL has bought it, and they want to see CentOS killed off.
Actions Taken:
Disabled SE Linux entirely to eliminate it being a firewall issue.
Installed Webmin to have access to the Apache administration module making looking for any issue easier.
Tested from the server itself in Gnome which the page comes up.
Tested from other computers on the same subnet, off the same switch.
Tested from other subnet computers.
On my computer, I created a Hyper-V VM and virtual switch from the Microsoft documentation using all the defaults a few months ago, everything was fine, I could see the real computer in the Network list and connect to the Internet. I tried adding a second VM using the same virtual switch and now the original VM won't connect. I've removed the second VM, uninstalled and reinstalled Hyper-V, deleted all the VMs and virtual switches and started again, all with no luck.
The closest I've got to it working again is ticking "Enable virtual LAN identification for management operating systems" under the virtual switch which lets the VM see the real computer in the Network list, but the real computers network connection no longer works. I untick the box and the network connection comes back and the real computer is removed from the Network list.
When I uninstalled Hyper-V and reinstalled, the VM was in the list, so I don't know if there are some settings that don't get removed on uninstall, I ran CCleaner to try clearing it all out with no change.
Any ideas how to completely uninstall Hyper-V with all it's hidden settings and details or how to fix the virtual switch issues?
I am using Ubuntu 14.04 on VmWare-Player 10. My host system is Windows 7. It worked fine, but since I restarted my host system (I have done this often and it was working without any problems) it stucks at the ubuntu boot up:
I have restarted my host system and it locked again:
Do I have to change something in the log files or how can I fix this?
Thanks in advance,
clax
Ok so I was working fine with the WP8 emulator but suddenly after going into Hyper-V manager it stopped working, didn't make any change and even deleted the virtual machine to be created again on debug but no luck
I have tried with the various emulator images but none of them seems to work anymore, event viewer shows no errors on Hyper-V.
What I have noticed is that the virtual machine starts in Hyper-V goes to Windows logo, then hangs for a few minutes in a black screen and turns off afterwards automatically, tried starting it without debuging, directly from hyper-v but nothing works, should I reinstall the SDK? seems to me this is not install related since it worked before
Thanks
Taken from the connect forums, I don't know if it will fix your problem:
I had issues with the emulator and tried several things, including the below solutions and on a few occasions couldn't figure out what the problem was so I restored a previous image since that was quick.
From Discussion "RTW - Can't debug - IP Address Issue"
Uninstall the SDK
Uninstall and reinstall the virtual switches using:
C:> netcfg –u vms_pp
C:> netcfg –c p –i vms_pp
Reboot
Reinstall the SDK
From Discussion "Emulator and wireless adapter issues"
Problem solved! Hyper-V uses same MAC address for guest VMs (virtual
machine) and Host. If the router configured to give the host always
same ip address it will conflict with the emulator. Solution - on the
router remove the host from known PCs and let it give you some new ip
address (not fixed). After you start the emulator it will get the
correct ip address from router. Router will show you two PCs (host and
vm) with the same MAC, but different ip addresses.
Remove the instances in Hyper-V, and then run XdeCleanup.