virt May 2010

virt@lists.fedoraproject.org

22 participants
16 discussions

Re: [fedora-virt] Routing to guests
by Robert Thiem 15 Jan '12

15 Jan '12

> 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

9 13

Allow everyone access to kvm virtual machines
by Ask Bjørn Hansen 01 Jun '10

01 Jun '10

Hi, We have a Fedora box with a couple of virtualized windows boxes (under KVM) for testing. With Fedora 11 everyone seemed to have access by default to run/see the machines under virt-manager. Since upgrading to Fedora 12 a few days ago until root has access -- I tried editing libvirtd.conf as described in http://libvirt.org/auth.html (setting none for the sockets and such), but I'm having no luck. Any hints? - ask

2 1

performance regressions in Fedora 13?
by Kenneth Armstrong 01 Jun '10

01 Jun '10

I used kvm/virt-manager heavily in Fedora 11 (helped me a GREAT deal in getting my RHCT). Now, I'm trying to use it again in Fedora 13 to prepare for my RHCE, but I'm finding it a LOT slower. I can't install with an ISO image on my external driver (using ntfs-3g), it keeps failing with a permissions error. However, if I copy my ISO over to my home folder, and it picks it up. I also tried using the actual RHEL 5.5 and 5.4 CD's that I have to install from, but even though it's mounted and I can view the contents in Nautilus, virt-manager says that /dev/sr0 has no media present. So I tried to store the (preallocated raw) VM image on my external driver, but that fails too. So I have to have my VM virtio disk file on the same hard drive that the ISO is on trying to do the install, which takes nearly 20 hours installing RHEL 5.4. I did manage to get 5.5 installed before on this (by leaving it running overnight), but the performance was terrible. Also, I thought Fedora 13 was supposed to automagically set up virtual bridges for the VMs to use, but the only option I have is NAT, it says that there are no bridges configured, even though I have a virbr0 interface when I run ifconfig. Any help would be appreciated, as I have no desire to install VritualBox. -Kenny

4 10

[Xen-devel] [ANNOUNCE] Xen 3.4.3 released
by Pasi Kärkkäinen 28 May '10

28 May '10

----- Forwarded message from Keir Fraser <keir.fraser(a)eu.citrix.com> ----- From: Keir Fraser <keir.fraser(a)eu.citrix.com> To: "xen-devel(a)lists.xensource.com" <xen-devel(a)lists.xensource.com>, xen-users(a)lists.xensource.com Cc: Date: Fri, 28 May 2010 08:08:21 +0100 Subject: [Xen-devel] [ANNOUNCE] Xen 3.4.3 released Folks, 'RELEASE-3.4.3' is now tagged in repository http://xenbits.xensource.com/xen-3.4-testing.hg Lots of bug fixes: we recommend users of 3.4 branch upgrade their hypervisor and tools. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel(a)lists.xensource.com http://lists.xensource.com/xen-devel ----- End forwarded message -----

1 0

qemu-kvm nic gone after upgrade to F13
by Dr. Michael J. Chudobiak 27 May '10

27 May '10

Hi all, I had an instance of WindowsXP running just fine in F12, with "vanilla" settings (standard networking). After upgrading to F13, no NIC is shown in XP any more. I can run my VM manually, with working networking, if I use: qemu-kvm -hda /var/lib/libvirt/images/MikeWindows.img -net nic -net user If I try to run this image via virt-manager, the NIC vanishes. Oddly, the qemu-kvm process does not show a "-net nic" parameter - just a "-device rtl8139" flag: [root@xena mjc]# ps ax | grep qemu 4778 ? Sl 0:30 /usr/bin/qemu-kvm -S -M pc-0.11 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name MikeWindows -uuid 5586f5ac-e12b-301c-7feb-cfbccf77e424 -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/MikeWindows.monitor,server,nowait -mon chardev=monitor,mode=readline -rtc base=utc -boot c -drive file=/var/lib/libvirt/images/MikeWindows.img,if=none,id=drive-ide0-0-0,boot=on -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -device rtl8139,vlan=0,id=net0,mac=52:54:00:20:ee:f2,bus=pci.0,addr=0x4 -net tap,fd=35,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -vga std -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 What's gone wrong? Config files are below. - Mike networks/default.xml: <network> <name>default</name> <uuid>152fda9b-581e-4e29-b906-4b72fa858cc8</uuid> <bridge name="virbr0" /> <forward/> <ip address="192.168.122.1" netmask="255.255.255.0"> <dhcp> <range start="192.168.122.2" end="192.168.122.254" /> </dhcp> </ip> </network> MikeWindows.xml: <domain type='kvm'> <name>MikeWindows</name> <uuid>5586f5ac-e12b-301c-7feb-cfbccf77e424</uuid> <memory>1048576</memory> <currentMemory>1048576</currentMemory> <vcpu>1</vcpu> <os> <type arch='x86_64' machine='pc-0.11'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu'/> <source file='/var/lib/libvirt/images/MikeWindows.img'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' unit='0'/> </disk> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='network'> <mac address='52:54:00:20:ee:f2'/> <source network='default'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target port='0'/> </console> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes'/> <video> <model type='vga' vram='16384' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> </devices> </domain>

1 0

Fedora Virt Status
by Justin Forbes 27 May '10

27 May '10

Fedora 13 ========= Fedora 13 is released and in the wild. Thanks to everyone for all of your hard work. Now it is time to start looking forward to Fedora 14. It is a good time to start looking at the feature process and planning. Fedora 14 ========= 2010-07-13 Feature Submission Deadline (47 Days) 2010-07-27 Feature Freeze (61 Days) 2010-08-03 Alpha Freeze (68 Days) 2010-09-07 Beta Freeze (103 Days) 2010-10-12 Final Freeze (138 Days) 2010-10-26 Fedora 14 Release (152 Days) Fedora Cloud SIG ================ Progress is being made towards updated Fedora in the EC2 cloud, and There is some interest in supporting other cloude nvironemnets. More details can be found at https://fedoraproject.org/wiki/Cloud_SIG Virt Preview ================ As was announced before, the virt-preview repository for F12 users wishing to test out the latest F13 virtualization bits is available. Additionally we have created a virt-preview repository for F13 users wishing to test out packages destined for F14 virtualization. Instructions for using these repositories can be found at: https://fedoraproject.org/wiki/Virtualization_Preview_Repository Recent updates in this repository include: F-12: ==== libvirt-0.7.7-4: - Fix nodedev XML conversion errors (bz 591262) - Fix PCI xml decimal parsing (bz 582752) - Fix CDROM media connect/eject (bz 582005) - Always report qemu startup output on error (bz 581381) - Fix crash from 'virsh dominfo' if secdriver disabled (bz 581166) - Fix slow storage volume allocation (bz 582356) F13 Bugs ======== DOOM-O-METER: 83 bugs are open against F13 virtualization packages, 65 are not fixed with pending releases. The final release has brought a larger audience to Fedora 13 and we need to spend some time focusing on these bugs before directing all of our attention to Fedora 14. If you would like to help out, you can find more information at: http://fedoraproject.org/wiki/Virtualization_bugs = Important = == kvm == https://bugzilla.redhat.com/show_bug.cgi?id=478317 almost 9 thousand syscalls per second while idle A patch has been posted which may resolve the issue. Look for an update after further testing. https://bugzilla.redhat.com/show_bug.cgi?id=544940 reattach virtio to rhel{5,6} guests will cause qemu-kvm crash https://bugzilla.redhat.com/show_bug.cgi?id=583850 qemu-kvm often crashes crashes when connecting vnc The real bug is that vnc_refresh_server_surface assumes that the display width is a multiple of 16. If it's not, then it accesses beyond the end of the row by a few bytes. On all but the last row, this is mostly harmless (it can result in unnecessarily marking the end of the row dirty), but on the last row, it copies over heap metadata. Patch is pending for this.

1 0

Re: [fedora-virt] portablexdr
by Richard W.M. Jones 25 May '10

25 May '10

On Tue, May 25, 2010 at 02:17:51PM +0100, Tomasz Koziara wrote: > Thanks for portablexdr - I am using it in a windows port of my software. > I have one remark and one question: > > Remark: In the version 4.9.1 downloadable from your site at the > beginning of the xdr_float.c you #define vax for MINGW32. This is surely > wrong (and it does not work). Hence perhaps it would be worth updating > the archive. If you send me patches, I'll put them in the git repo. > Question: portablexdr looks like work in progress and it has no been > updated for quite some time now. Are you planning to release a "clean" > version at some point soon? I mean - is this still alive? portablexdr is in limbo. Sun changed the license for the XDR code so that portablexdr is not longer really necessary as a separate free implementation. However some sort of separate XDR implementation is still useful on platforms that lack XDR or lack good quality XDR (ie. *BSD and Windows). Since there is no other Sun-based project fulfilling this need, I'm still offering portablexdr. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top

1 0

Routed networking in libvirt
by Kenni Lund 25 May '10

25 May '10

Hello I just bought a new hosted server in a data center, which I'm going to run a few virtual machines on with libvirt/KVM. The server have 4 public IP addresses, but due to the data center, bridges are not an option. Luckily, I discovered that libvirt had an option for a routed network as an alternative to full NAT or bridging. With some help from a blogpost of Daniel P. Berrangé [1], I managed to get it working. I have 4 IP-addresses: x.y.z.215 / 255.255.255.255 (the host) x.y.z.251 / 255.255.255.192 (additional IP) x.y.z.252 / 255.255.255.192 (additional IP) x.y.z.253 / 255.255.255.192 (additional IP) I've then created the following network in libvirt: <network> <name>name</name> <forward mode='route'/> <bridge name='name' /> <ip address='x.y.z.251' netmask='255.255.255.192'> <dhcp> <range start='x.y.z.252' end='x.y.z.253' /> </dhcp> </ip> </network> This works, but I can only utilize 2 IP addresses for virtual machines and not 3, since the third IP address is used for the routed network. I'm wondering if it's possible to do something to workaround this? Both .215 and .251 binds to the host, eg. I can access all the services on the host through both IP-addresses, which I really don't need. Is it just the way it is, or can I do something about it? Looking at the routing tables, I don't see the .251 address mentioned anywhere as a gateway, the routing tables seems to just use the Iface of the routed libvirt network and not the IP address. Why is this address needed at all? [1] http://berrange.com/posts/2009/12/13/routed-subnets-without-nat-for-libvirt… Best Regards Kenni

3 5

[mst@redhat.com: [PATCH master+0.12] pci: irq_state vmstate breakage]
by Michael S. Tsirkin 17 May '10

17 May '10

This is needed for F13 as well. ----- Forwarded message from "Michael S. Tsirkin" <mst(a)redhat.com> ----- Date: Sun, 9 May 2010 19:15:16 +0300 From: "Michael S. Tsirkin" <mst(a)redhat.com> To: quintela(a)redhat.com, qemu-devel(a)nongnu.org, Anthony Liguori <anthony(a)codemonkey.ws> Subject: [PATCH master+0.12] pci: irq_state vmstate breakage Message-ID: <20100509161503.GA20492(a)redhat.com> Code for saving irq_state got vm_state macros wrong, passing in the wrong parameter. As a result, we both saved a wrong value and restored it to a wrong offset. This leads to device and bus irq counts getting out of sync, which in turn leads to interrupts getting lost or never cleared, such as https://bugzilla.redhat.com/show_bug.cgi?id=588133 Signed-off-by: Michael S. Tsirkin <mst(a)redhat.com> --- Juan, could you please take a look at this patch? I managed to catch this bug by looking at a savevm image which already has a wrong value, but I could not reproduce it locally so I don't know for sure whether patch is enough, or there are other bugs. Anthony, this is a regression introduced in eea4acfa5c1ef26439a718375475fe468b7f2fba so we need the fix on 0.12 branch as well. hw/pci.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/hw/pci.c b/hw/pci.c index 95bfa3d..5452b86 100644 --- a/hw/pci.c +++ b/hw/pci.c @@ -325,7 +325,7 @@ static VMStateInfo vmstate_info_pci_config = { static int get_pci_irq_state(QEMUFile *f, void *pv, size_t size) { - PCIDevice *s = container_of(pv, PCIDevice, config); + PCIDevice *s = container_of(pv, PCIDevice, irq_state); uint32_t irq_state[PCI_NUM_PINS]; int i; for (i = 0; i < PCI_NUM_PINS; ++i) { @@ -347,7 +347,7 @@ static int get_pci_irq_state(QEMUFile *f, void *pv, size_t size) static void put_pci_irq_state(QEMUFile *f, void *pv, size_t size) { int i; - PCIDevice *s = container_of(pv, PCIDevice, config); + PCIDevice *s = container_of(pv, PCIDevice, irq_state); for (i = 0; i < PCI_NUM_PINS; ++i) { qemu_put_be32(f, pci_irq_state(s, i)); -- 1.7.1.12.g42b7f ----- End forwarded message -----

2 2

[PATCH] typo: MemCached -> Cached
by Dan Kenigsberg 17 May '10

17 May '10

Thanks to Dave Hansen. --- ksmtuned | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/ksmtuned b/ksmtuned index 205ff84..4e0414f 100644 --- a/ksmtuned +++ b/ksmtuned @@ -76,7 +76,7 @@ committed_memory () { } free_memory () { - awk '/^(MemFree|Buffers|MemCached):/ {free += $2}; END {print free}' \ + awk '/^(MemFree|Buffers|Cached):/ {free += $2}; END {print free}' \ /proc/meminfo } -- 1.6.6.1

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

virt May 2010