I have a physical address in my host (its a pci bar address), and I want a driver in my kvm guest to access that address.
Whats the best way i can do such a thing?
If it was a linux process and not a kvm guest, I would just open and mmap /sys/bus/pci/devices/*/resource0 in my process, is there something equivalent I can do in a kvm guest?
All operations in the guest use Guest Virtual Addresses or Guest Physical Addresses. The translation to Host Physical Address may be done with Shadow Page Tables or Second Level Address Translation (like EPT) depending on your hardware and configuration. This implies that Host Physical Addresses have no meaning in the VM, or at least they can't be used directly without some work involving the cooperation of the hypervisor.
I don't know much about it, but you may want to look into the implementation of PCI Passthrough for network devices.
Related
I understand that it is running some kind of local DHCP server but specifically what is the Pocket Beagle/Beagle Bone Black running that allows it to allocate the address 192.168.7.2 to itself and 192.168.7.1 to the computer which it is connected to? And if I wanted to change those addresses to something else how would I be able to do it?
This is from BeagleBoard.org:
If connected via USB, a network adapter should show up on your
computer. Your Beagle should be running a DHCP server that will
provide your computer with an IP address of either 192.168.7.1 or
192.168.6.1, depending on the type of USB network adapter supported by your computer's operating system. Your Beagle will reserve 192.168.7.2
or 192.168.6.2 for itself.
If your Beagle includes WiFi, an access point called "BeagleBone-XXXX"
where "XXXX" varies between boards. The access point password defaults
to "BeagleBone". Your Beagle should be running a DHCP server that will
provide your computer with an IP address in the 192.168.8.x range and
reserve 192.168.8.1 for itself.
On my BeagleBone Blue with Debian Buster I found the configurations in the /etc/dnsmasq.d/SoftAp0 file:
And this is the service:
I have a setup with a few Linux devices and one windows device connected to a switch. I would like a way to tell the windows machine which IPs the Linux machines get when booting. I have tried to populate the arp table on the windows machine by pinging broadcast but I have not succeeded because windows doesn't reply to broadcast.
I have tried also nmap but that is not an option because it takes really long to scan (the net mask is 255.255.0.0)
You could set up a static IP and other network settings on all the Linux machines.
then on your Windows system edit your HOST file with the names and ip addresses.
This should bypass the need for a DHCP or DNS.
However other systems on the network will not be able to find your systems.
Regardless you still need to speak to the guys who administer the network to add your linux systems in.
It is rather impolite and/or against policy and somewhat bordering on illegal; to simply plug in your systems into the network not owned by yourself.
So if you have a right or need, the administrators will listen and should help you.
For sake of automation I need to be able to manually set the IP address of my Virtualbox guest (which is an OS X) to a fixed IP.
Can this be done using VBoxManage? I need to avoid the GUI.
Thanks
in your virtual machine setting, you can find networking adapters. You have some choice :
Network Address Translation (NAT): Used to share the host's IP address
If all you want is to browse the Web, download files and view e-mail inside the guest, then this default mode should be sufficient for you, and you can safely skip the rest of this section.
Bridged networking
This is for more advanced networking needs such as network simulations and running servers in a guest. When enabled, VirtualBox connects to one of your installed network cards and exchanges network packets directly, circumventing your host operating system's network stack.
Host-only networking
This can be used to create a network containing the host and a set of virtual machines, without the need for the host's physical network interface. Instead, a virtual network interface (similar to a loopback interface) is created on the host, providing connectivity among virtual machines and the host.
if you want specific IP for your virtual machine you can set in your guest vm ( ifconfig in linux & ipconfig in windows) and choose NAT in network adapter setting .
https://www.virtualbox.org/manual/ch06.html
I am developing an application related to networking . Its prerequisite is that the machine must have an ip address to function properly.
When i am on my home network , my machine gets the IP address through DHCP present on my network. However, when my machine is in stand alone mode e.g. while travelling i can not have an ip address and the status is LAN DISCONNECTED.
Is there a workaround so that i can get an ip address or virtual ip address in standalone mode?
I have already tried configuring with loopback address and other ip address.
Can I do it by installing a dhcp server on my machine? My system uses WINXP?
Network card: BroadcomNetxtreme 57XX gigabit ethernet.
I strongly feel that the application details have nothing to do with it. Since, when the machine has an ip address it starts working properly.
Still i am open to ideas.
I advise you to work inside a virtual machine, and then assign a virtual IP and vitual MAC of your convenience. You can use Virtual Box or VMWare.
I am using a Macbook running 10.6. I am using VMware Fusion to run an Ubuntu Server minimal virtual machine. Ubuntu Server is running your basic LAMP stack.
I do my development in Mac OS. I have VMware share a directory from Mac OS to the Ubuntu Server. Ubuntu Server uses that directory for apache.
I access my server is Mac OS in firefox using the ip address of my virtual machine. This is a pain because I have to find out what the ip address is of my virtual machine each time I boot it up. I could set a static ip address but this causes problems if I move my Macbook from network to network.
Is there any configuration (NAT or Bridged or something) that would let me access my virtual machine from the Mac OS using localhost or something similar?
Thanks
NAT should be OK. Your VM is on a different subnet that way, you can give it the static IP you like, and it won't interfere with the (dynamic) IP on your real network.
What you are looking for is the host-only networking adapter as opposed to the NAT or bridged adapters. This creates a network interface on the virtual machine that only connects the actual host. It is perfectly safe to set an IP address for this interface that does not change, and there will be no tricky NAT getting in the way. It's a little network that only exists for communication between the real host and the virtual host. It's exact purpose is so you can do development like this. I use the same feature on VirtualBox all the time, but VMWare has it as well.
Now, with a host-only adapter you might be worried that your VM now has no access to the Internet. The answer is simple. Just make two adapters. eth0, eth1. Make one of them a bridged or NAT adapter for Internet access. Make the other one the host-only adapter for your development. Most modern Linux distros will automatically route accordingly. I know for a fact that Ubuntu does, because I do it all the time. Again, this is with VirtualBox. Your mileage may vary with VMWare, but I can't imagine it's that different.
I'm using Virtual Box and typing in the computer local address (for instance 192.168.1.100) instead of localhost did the trick.
Maybe I'm misunderstanding your question but why not just add an entry in your hosts file for the virtual machine? That way you can access it with some arbitrarily assigned name (like testmachine) instead of the IP.
This is the first tutorial I found through google: http://decoding.wordpress.com/2009/04/06/how-to-edit-the-hosts-file-in-mac-os-x-leopard/
This would work best if your VM has a static IP, BTW (either no DHCP or configure the DHCP server to give that MAC the same IP every time). That way you don't have to worry about changing the hosts entry every time the DHCP server gives the VM a different IP.