Re: [fedora-virt] Routing to guests
by Robert Thiem
> 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
host.
Robert
12 years, 3 months
F12 and ksm/ksmtuned: info required...
by Gianluca Cecchi
Hello,
F12 x86_64 with Qemu/KVM booted yesterday evening.
It has two guests with CentOS 5.3 x86_64 configured to auto-start and
now they are running...
I see this morning, some minutes ago:
[root@virtfed ~]# service ksm status
ksm is not running
My config:
[root@virtfed ~]# chkconfig --list|grep ksm
ksm 0:off 1:off 2:on 3:on 4:on 5:on 6:off
ksmtuned 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@virtfed ~]# cat /sys/kernel/mm/ksm/pages_shared
3786
Then I start two other guests, both with CentOS 5.4 x86_64.
After a while:
[root@virtfed ~]# cat /sys/kernel/mm/ksm/pages_shared
4752
[root@virtfed ~]# cat /sys/kernel/mm/ksm/pages_shared
5219
...
[root@virtfed ~]# cat /sys/kernel/mm/ksm/pages_shared
90895
and now, without any action at my side:
[root@virtfed ~]# service ksm status
ksm is running
Is this normal/expected?
Any deeper doc/link about ksm/ksmtuned logic?
Is it ksmtuned that spins ksm as it is needed? Any log file to check/configure?
I read https://fedoraproject.org/wiki/Features/KSM but probably I'm
missing something...
Thanks,
Gianluca
14 years, 1 month
Fedora 12 host and windowsXP guest - No Sound from guest
by Daniel Sanabria
Hi all,
I can't get any sound out of a windows xp guest. I've tried <sound
model='es1370'/> and <sound model='ac97'/> and windows seems to recognize
them ok but no sound at all.
My audio setup in the host is fairly simple, fedora12 and an integrated
sound card + a USB headset, both are successfully detected by fedora and I
can switch between the 2 without problems.
I feel like something is missing here, the host_sound and guest_sound
doesn't seem to be integrated properly. What setting can I change to get
sound out of the guest?
Thanks in advance,
Daniel
14 years, 3 months
libvirtd crashes host when autostarting
by Rich Mahn
Summary:
My host crashes when I use the autostart function in
libvirtd.
This command sequence works fine:
service libvirtd stop
virsh autostart mydomain --disable
service lib virtd start
virsh start mydomain
This command sequence will crash the host:
service libvirtd stop
virsh autostart mydomain
service libvirtd start
I can't find any error messages related to this. The host system
freezes, the keyboard starts blinking the caps-lock and scroll-lock,
and as best I can tell, the kernel has stopped running.
If I starting up the host system with the VM autostarted, I sometimes
get messages that look like kernel errors on the screen, but I don't
find them in any log files so far. They seem to be related to networking.
Here's some configuration information--I don't know really what all is
needed, but this, I guess is a start:
Host and VM both Fedora 11 with the lastest updates.
Host machine in Intel based with the virtual support turned on.
In the /var/log/libvirtd/qemu directory, the command line to start
the virtual machine is different when started from autostart. The
difference is in this portion:
-net tap,fd=11,vlan=0 for failure (autostart) and
-net tap,fd=18,vlan=0 for success
I am using a bridged connection.
Here's the command line that's used, split over
lines for some degree of readability:
LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/bin/qemu-kvm -S -M pc
-m 1024 -smp 1 -name mydomain
-uuid 5cde5a23-2abe-fcdd-04dc-5ae3a46ab51c
-monitor pty -pidfile /var/run/libvirt/qemu//mydomain.pid
-boot c -drive file=,if=ide,media=cdrom,index=2
-drive file=/dev/mapper/vg_host-lv_mydomain,if=virtio,index=0,boot=on
-drive file=/dev/mapper/vg_host-lv_mydomain_data,if=virtio,index=1
-net nic,macaddr=54:52:00:67:91:e9,vlan=0,model=virtio
-net tap,fd=11,vlan=0 -serial pty -parallel none
-usb -usbdevice tablet -vnc 127.0.0.1:0
14 years, 3 months
how to active XEN on Fedora 12
by Dario Lesca
hi, I have 'yum install xen*' on fedora 12 64 bit and reboot.
But the service xen* not start, the folder /proc/xen is missing.
What should I do now?
How to start and Use XEN?
Many thanks
--
Dario Lesca <d.lesca(a)solinos.it>
14 years, 3 months
virt for dummies?
by Robert P. J. Day
i've been asked to give a presentation on basic virtualization, and
i'd like to find something online that i might be able to hand out
along the lines of "virtualization for dummies." *very* basic intro,
talking about the underlying technology, Xen vs KVM, what that means,
etc. pointers? thanks.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
14 years, 3 months
Fedora 11 on XEN Host
by sungsoo khim
Excuse if this was already discussed. (few hours of searching didn't
really help out)
We have some server running Cent OS 5.4 as Dom0, and a few more fedora
11 running on top of them using XEN.
From time to time, one or two of our fedora VM's Load Index will rise
up to 100+ over 8 hour period. (In a very linear fashion)
When we see the trend starting (regardless of the Load index number at
the moment) we are not able to login using SSH or even console (xm
console [VMNAME]).
Only way to deal with it is to reboot the VM, and there is no
significant log entry at all. to indicate any system specific errors.
(As if nothing has happened) However, no log message are present during
the high load period.
When it happens however, active running process will reply back - such
as web proxy process. All socket open requests work as should (SSH,
HTTP, etc), but will not go further than opening the socket with a
greeting message.
Has anyone had similar experience, and fund a resolution to?
14 years, 4 months
trying to test qemu-spice on F12
by Gianluca Cecchi
hello,
I'm testing qemu-spice for some windows guests..
I installed repo files and sw components as I read on
www.linux-kvm.com web site
Now I would like to try this on my host that is a F12 x86_64 where I
already have virt-manager / livirtd set up for other pre-existing vm.
So some sort of questions arise:
1) Can I manually start a VM from command line taking advantage of
libvirtd setup already in place?
For example I have virbr0 as default enabled and I tried something like:
/usr/libexec/qemu-spice -hda disc0.img -m 512 -localtime -qxl 1
-spice port=5930,disable-ticketing -cdrom spice-windows.iso -net nic
-net user,net=192.168.122.0/24,host=192.168.122.1
but it seems the guest takes the default 10.0.2.15 ip and it is not
able to exit to the internet as I would like to see and verify
graphical improvements in my guest....
what would be the manual command to attach to virbr0?
I also tried to mimic start line of a vm started from virt-manager using
"-net nic,vlan=0,name=nic.0 -net tap,fd=24,vlan=0,name=tap.0"
but then I'm not able to connect via spice to the guest....
2) doing some tests with the client, run with the command:
/usr/bin/spicec -h localhost -p 5930
I saw previous posts telling to hit Ctrl+F12 to exit its window, but
it seems it is not working for me.
tried severale key combinations but the only chance to come back with
the pointer to the host is to shutdown the VM....
any hint on this?
Thanks,
Gianluca
14 years, 4 months
windows 7 ACPI issue
by Emmett Culley
I attempted to upgrade one of my XP virtual machines images to win 7 and got the following error:
-----------------
The following issues are preventing Windows from upgrading. Cancel the upgrade, complete each task, and then restart the upgrade to continue.
This computer is not compliant with the Advanced Configuration and Power Interface (ACPI) standard. Windows must be installed onto a computer that supports ACPI. Contact your computer manufacturer for a BIOS update or install Windows on an ACPI-compliant computer.
-----------------
Has else anybody seen this?
The only reference I found in google was that ACPI isn't available on 32 VMs.. So I reinstalled xp on an x86_VM and got the same error when attempting to upgrade to win 7.
Emmett
14 years, 4 months
Another weird KVM glitch
by Tom Horsley
I've been looking at a few days worth of testbed results,
and rarely (but more than once) a fantastically weird failure
happens:
Some random process (bash, gcc, etc) will die with a
Trace/Breakpoint trap reported as the reason for the abort.
I am running tests of debugging on most of the virtual
machines, but I'm not debugging these apps, I'm debugging
other stuff on other virtual machines.
It is almost like the emulation code is looking at stale
register values when reporting a breakpoint or address
trap and directing it to the wrong process. So far, I've
never seen this on my Xeon based host, only on my Opteron
based host.
There are 8 CPUs on this thing. I wonder if there is
a missing lock somewhere in some infrequently executed
code path.
14 years, 4 months
