> From: Philip Rhoades
> I can ssh from/to the host/guest OK but how do I set up a route (or
> whatever is necessary) so that another machine:
> eth0: 192.168.0.12
> can ssh to the guest? - "ssh 192.168.122.68" gives "no route to host" -
> http://docs.fedoraproject.org/virtualization-guide/f12/en-US/html/ but
> the problem does not seem to be covered there.
Alexander is correct in saying that bridging would allow you to do that.
There are two networking discussed in the guide.
The first is a NAT (network address translation), in which the guests are
given "private" ip addresses and any outbound traffic appears to be coming
from the host machine's IP address. This is the same as the setup on your
ADSL router where the internal network machines get addresses of
192.168.x.x but the internet sees your requests as coming from the IP
address of your router.
There should be lots of documentation in linux firewalling guides under
sections on NAT (or possibly called IP Masquerading in some). Have a look
at these for information on port forwarding to reveal services
inside the virtual (such as ssh).
The other option is bridging. This shares the physical network interface
of the host with the guest. In this case the VM acts as though it's a
machine plugged into the same subnet as the host, its services are
accessible like those of the host and it's as vulnerable to attack as the
I am trying to work out whether it is practical to propose Dom0 xen
support as a feature for Fedora 15.
The kernel situation is that Domain 0 has been accepted upstream for
2.6.37. Assuming a 3 month kernel release cycle, F15 will most likely ship
with a 2.6.37.x kernel, with 2.6.38 coming out either after the F15
release or just before but too late to be included. If the plan to get key
xen drivers into 2.6.38 succeeds, then F15 may be become usable as a
Domain 0 system at some point during its lifetime as the kernel package in
a Fedora version typically has one major update.
If the kernel team accept backported patches then it might just be
possible to ship F15 with usable Domain 0 support but the timescale for
that would be very tight.
The other thing we would need to consider is what needs to be done to make
xen friendly enough to be usable by an ordinary user. The page
https://fedoraproject.org/wiki/Features/XenPvopsDom0 contains plans from
when dom0 xen support was expected to make a quick return to Fedora, but
they are a couple of years old now so probably need updating.
I think as a minimum we would need a way to add a dom0 enabled grub entry
for a kernel, rather than requiring the user to hand edit the grub file.
We should also make sure that xen works with the other Fedora
What do others think about this? For example is it achievable as a
feature, is it too early and better to wait for F16, and what else should
we aim to do to make xen usable in Fedora?
On 10-11-12 09:57 AM, Todd Deshane wrote:
> There is also an ongoing discussion about Xen vs. KVM performance on
> the CentOS virt list
There are some interesting ideas and insightful comments there. I am
tempted to abort my own benchmarking, as it seems others are doing the
same. I think I will proceed though, until and unless someone there
releases numbers first.
As I mentioned before, I've hit a snag with my in-progress benchmarks.
I've filed a bug but I doubt I will wait for resolution. I'll need a bit
more time now to setup a RHEL 6 based platform (host and guests). I'm
still hoping to get most done this weekend, but I make no promises. If
not, I'll aim for the weekend after to finish.
Node Assassin: http://nodeassassin.org
I'm trying spice with a w2k3 guest.
I set up the emulator wrapper to change video adapter when starting the vm.
But with w2k3 I get a ctrl+alt+del window at boot...
How do I send the key?
>From virt-manager screen it doesn' work (I think expected as vnc is
I saw something about a monitor command to add in startup command to
be able to send keys via tcp... but if I insert it into my wrapper I
get a duplicate error in startup:
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 333, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error Process exited while reading console log
output: qemu-kvm: -monitor telnet:10.4.5.39:4444,server,nowait:
Duplicate ID 'monitor' for chardev
parse error: telnet:10.4.5.39:4444,server,nowait
In fact I see there is already something like this in my command line:
Does this mean that the monitor is already enabled? In this case how
do I use it?
Thanks in advance,
I have a test rh el 6 server where I have 6 network adapters, but I
think my idea could also cover for example an F13 server with
eth0 and eth1 are dedicated for bond0 and main ip for kvm host
eth4 and eth5 are dedicated as multipath iSCSI initiators for
configuring storage pools on disks presented by an iSCSI SAN array
I would like to dedicate eth2 and eth3 to network for my guests, but I
want to cover multiple vlans.
Suppose I want to cover vlanid=1 and vlanid=2
Here is my planned approach
1) configure bond1 with eth1 and eth2 as slaves
# cat ifcfg-eth2
--> is it ok to put MTU line here or do I have to put it at bond
interface definition level?
2) bond1 is without ip/netmask information; something like
3) create bond1.1 script something like this:
4) create bond1.2 script something like this:
5) create brvlan1 script
6) create brvlan2 script
QUESTION: is it necessary to put BOOTPROTO=dhcp for bridge interfaces?
Can I put a static ip or better no ip at all?
7) service network restart with eventually adjustments fro iptables
8) service libvirtd reload
If the steps above make sense
9) If I want a guest on vlan1 I have to assign it
shared physical device --> brvlan1
QUESTION: in guest do I have to tag the lan or should it be
transparent with the guest?
Otherwise: waht would be a correct different way of proceeding?
If my approach is correct, would it make sense to have similar
approache for bond0, so that I can use this bond interface for guests
Thanks in advance.
on weekend I upgrade my Fedora from version 13 to 14. Yesterday I try
boot my virtuell machines thats I have configured under fedora 13
virt-manager, but no machine boot, for example Fedora, Ubuntu and
If start a virtual machine, I see the BIOS screen and than it switch
to a prompt. The cpu graph in virtmanager show a constant line by
round 30% but the harddisk io graph show nothing.
I try something: reinstall the virt packages, erase the libvirtd
configuration and create a new virtual machine, with different hd
options, virtio, ide, scsi. I disable selinux and reenable selinux
with wrote the selinux flags new on filesystem. If I create a new
machine, I see the boot screen from cd-image but if it switch to the
normal boot, it shows only the prompt.
What can I do to run machines under f14? Or which information can I
send to you to locate the problem. I'm desperate and have no idea.
My hardware are an AMD Phenom X2 (, with enable virtuallisation option
in BIOS) and under f13 the kvm machines run and run .....
Beat me, whip me, make me use Windows!
On 11/17/2010 08:01 PM, Kenneth Armstrong wrote:
> I saw this bug update today for the SPICE client:
> It mentions giving the spicec the ability to work with the spice-xpi
> package for RHEV. I did a yum search for spice-xpi which is
> apparently available for RHEL, but couldn't find it in Fedora. Is
> there a particular repo to use to try this, or is it not in Fedora
In my fedora 13 system, watching boot messages go past,
I'd see libvirtd start then immediately say [OK] and
go to the next service.
In fedora 14, I see the starting libvirtd message then
it sits for 10 or 20 seconds and finally says [OK].
Has anyone else noticed this?
Weirdly, if I say service libvirtd stop after the
system is fully up and running followed by service
libvirtd start, it starts up near instantaneously
the second time. Is there some cache it builds the
first time it starts after a boot?