I'm having a problem about suspend/resume instance. Theoretically, as I suspend a vm, it will save the vm's state at that time, and upon resumption, vm is exactly as it was before entering suspending. However, in OpenStack (Juno verrsion), when I resume, it does not return to previous state, which looks like the vm boot from start and requires login username/password. So it make me confused and I don't know why!.
I'm using OpenStack (Juno version), hypervisor is KVM/QEMU.
Thanks all!
Related
is it increasing your internet security in terms of privacy/tracking/fingerprinting, if you are surfing with your web browser in a virtual machine enviroinment (virtual box + vpn)? Instead of surfing from your normal windows operating system...
Or is a virtual machine not helping you in fingerprinting cases? I just want to understand if you can use a virtual machine as a additional privacy tool and if yes, on what aspects would it have an impact (ip address, virus infections, fingerprinting, etc.)?
Thanks
When you're hosting a VM on your local machine, it may share the same IP as your host, as far as the outside world is concerned. Most hypervisors allow you to change how it obtains an IP address, but in typical configs it will only change on your local network, which is probably NATed behind a single address provided by your ISP. A VPN is a good way to change that, and you can configure that either inside or outside the VM, though ideally you'd no want to be sharing an IP with your host system.
Using a VM can help against fingerprinting because you can be running a different browser in a different OS in your VM than on your host system - but that instance itself can be tracked/fingerprinted, so it may be a good idea to rotate through a series of different configurations (or use a browser plugin that randomises some settings, such as reported browser version, OS, installed fonts, etc), and to throw away changes in your VM each time you use it, which will eliminate even the hardest of "supercookies" that might try to track you.
Unless your hypervisor is compromised (this has happened in the past, but it's rare), the VM itself will provide good protection from malware - for example Windows malware will have no effect on a Linux VM, and vice versa - and any malware that does infect your VM is contained by the sandbox that the VM provides - and you can simply reset it to return to a known-clean state, or throw it away and start again.
JProfiler is not able to detect any local running jvm. Thinking of user access issue, I have started the java services with the same logged-in user on server but still no luck. Some help here would be really appreciated.
I am trying to deploy a cent-os 7 VM on a vcenetr from pyvmomi python library and then before powering on the VM I am trying to setup static IP and DNS for the VM.
VM creation goes fine , but guest customization fails, givimg following error:
**Customization of the guest operating system 'rhel6_64Guest' is not sup
ported in this configuration. Microsoft Vista (TM) and Linux guests with Logical
Volume Manager are supported only for recent ESX host and VMware Tools versions
. Refer to vCenter documentation for supported configurations."
faultCause =
faultMessage = (vmodl.LocalizableMessage) []
uncustomizableGuestOS = 'rhel6_64Guest'
Now this customization problem goes away if the VM is just rebooted once. After that we can do the guest customization.
But this reboot takes around 30 seconds of time and for our case , we need to get VMs up and running faster than this time.
Any body who faces similar problem and has some context on it will be very helpful.
Also I don't understand how rebooting the VM solves this problem.
Please share your thoughts even if you don't have exact solutions .
On further Investigation I found that open-vm-tools does not work until the VM is powered on atleast once.
When Machine is powered on , the HOST system detects the open-vm-tools running on guest OS , and from there on open-vm-tools works.
So open-vm-tools can not be used for initial provisioning as it will just not work at the start up.
Cloud-init is the alternative solution which should be used for initial provisioning.
I am wondering if there is any way to get VMware Player to blink or show a message in the window title or perform some similar notifying action whenever there is some activity inside the guest operating system.
I run a Windows VM on a Linux box. If I am working on the host OS and an email or IM or any notification appears on a window inside the Windows VM, there is no way for me to be notified of that in the host OS. I am wondering if there is any practical solution to this or if this is an intrinsic limitation of virtualization. Any thoughts? Thanks.
This is an intrinsic limitation of type 2 virtualization, if you're able to get out the virtual machine it means something went wrong in terms of security.
BUT, you can still solve your problem. Both the host and the VM are connected to the Internet (and sometimes connected on the same internal network). You have a common resource, so they can communicate. The easiest solution in your example is to use an external notification service like pushbullet (if you don't mind it to be hosted elsewhere) or pushjet (if you want to self host).
On Windows machines that we own it's possible to change a MAC address to a pre-assigned value. But is it possible to set the MAC address on EC2 Windows machines to a pre-assigned value?
Here is the problem:
We provide a virtual lab/training/evaluation environment that runs off Amazon EC2. Every so often a customer wants to run licensed software (that they own!) in the cloud, but the licensing component requires a fixed MAC address to exist.
But it's unclear what happens in EC2 if we tweak with the MAC address, especially after a reboot or snapshot of the machine. One big issue I see is that if we take a snapshot of a machine with a fixed MAC, and then launch multiple copies of it, then each copy will, in theory, have the same MAC address. Obviously a routing issue.
But still, it's unclear what happens or if the underlying virtualization stack simply generates random MACs every time a machine is launched.
Of-course, I would love to hear about other workarounds if you have ideas..
You can use an EC2 instance in a VPC and attach an Elastic Network Interface to it.
ENI is like an additional network card that have fixed IP address (internal and external) and fixed MAC address.
More about ENI in AWS site.
Unfortunately there's no good workaround here. EC2 does not allow any manipulation of the MAC address on an instance.