virt February 2010

virt@lists.fedoraproject.org

34 participants
53 discussions

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

16 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

Fedora 12 Xen guests (domU) and hosts (dom0)
by Pasi Kärkkäinen 30 Mar '10

30 Mar '10

Hello, I thought of writing some information about running Fedora 12 Xen guests and also Fedora 12 Xen hosts/dom0. Fedora 12 includes the upstream Linux pv_ops Xen domU support in the default kernel. By using virt-install or virt-manager you can install Fedora 12 Xen PV (paravirtual) guests directly from network, for example on RHEL 5.4, CentOS 5.4, or Fedora Xen dom0/host. If you want to run Fedora 12 Xen dom0 (host), there are some extra steps needed. Fedora 12 ships with Xen hypervisor and management tools (Xen 3.4.1, and Xen 3.4.2 in the F12 updates), but the required Xen dom0 capable host kernel is not included in Fedora atm/yet. General information about Xen dom0 status in Fedora: http://fedoraproject.org/wiki/Features/XenPvopsDom0 There are a couple of different ways to get and install a Xen dom0 capable kernel to Fedora 12 host: - By using pre-packaged pv_ops xendom0 kernel rpms by M A Young. his repository: http://fedorapeople.org/~myoung/dom0/ - Compiling and installing Xen dom0 capable kernel yourself/manually. There are many options to choose from, full list of the available Xen dom0 capable kernels is here: http://wiki.xensource.com/xenwiki/XenDom0Kernels The recommended dom0 kernel is the pv_ops kernel, which is in the process of being cleaned up for upstream/mainline Linux inclusion. More information about pv_ops dom0 kernel, including the status reports: http://wiki.xensource.com/xenwiki/XenParavirtOps Xen developers are interested of both the success and failure reports when using the Xen pv_ops dom0 kernel. Tips for running Xen with Fedora 12: - Make sure you install all the latest Fedora 12 updates, since they have an updated Xen version (3.4.2), and also fix a bug in python-virtinst tool to make Xen guest console keymaps work properly: https://bugzilla.redhat.com/show_bug.cgi?id=533707 - Recent versions of Xen pv_ops dom0 kernel renamed some xen backend driver modules to have "xen-" prefix in them, for example evtchn module became xen-evtchn. Fedora Xen 3.4.2 init scripts take care of this, and load the correct modules, but Xen 3.4.1 doesn't do this automatically, causing xend fail to start in dom0/host before the modules are loaded manually. - There are some upcoming apic-related changes coming in pv_ops dom0 kernel, which will require a patch to Xen hypervisor. This patch is not yet included in the Fedora Xen rpms. The patch will be added to Fedora Xen rpms when the upstream pv_ops kernel starts to require/use it. - pv_ops dom0 kernel currently lacks blktap2 support, so using tap:aio: backend disk image files is not yet possible. Xen file: backend image files work though. At the moment it's recommended to use LVM volumes for guest disks (Xen phy: backend). - virt-manager seems to work OK on Fedora 12 Xen dom0. - If you experience problems related to Fedora 12 guests (domU) kernel crashing (especially related to save/restore/migration), install the latest Fedora updates to the guest. There has been a lot of Xen guest related fixes in the upstream Linux recently. These fixes will appear in Fedora when the kernel gets updated to include the latest stable upstream fixes. Hopefully that helps :) -- Pasi

2 4

windows xp guest and iphone
by Daniel Sanabria 05 Mar '10

05 Mar '10

Hi, Has anyone been able to successfully have the iphone recognized by a windows xp guest? I have tried adding the iphone as a usb devide to the guest's virtual hardware details without any luck :( Daniel

3 7

F12 and ksm/ksmtuned: info required...
by Gianluca Cecchi 02 Mar '10

02 Mar '10

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

5 13

problems with customization before install and floppy
by Gianluca Cecchi 01 Mar '10

01 Mar '10

Hello, I have F12 x86_64 and I'm using rawvirt fedora-virt-preview repo. Downloaded F13 Alpha TC2 + updates.img floppy I create a vm and I select customize before install. I add a floppy drive as storage, pointing to the floppy img. I click on finish installing virtual hw window and I come back at the vm details window Then I check the top-left V to confirm creation: BTW not so intuitive in my opinion..... I think it would be better to have an "OK" button as usual at bottom-right. Anyway when I click the V I get this: Unable to complete install '<class 'libvirt.libvirtError'> internal error unable to start guest: can't parse: "isa-fdc,driveA=drive-fdc0-0-0" Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/create.py", line 1502, in do_install dom = guest.start_install(False, meter = meter) File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 795, in start_install return self._do_install(consolecb, meter, removeOld, wait) File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 896, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1098, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error unable to start guest: can't parse: "isa-fdc,driveA=drive-fdc0-0-0" ' After the error I'm put back where if I click "finish" again, I have again the option to customize. If I customize again, I again get the error. If I don't customize and click directly the big V to confirm vm creation, I'm put in boot phase correctly. Now with the vm on, if I add the floppy again I'm told that it will be effective next reboot --> ok. I force off vm and configure to boot from dvd. When it starts it gives this error: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 589, in run_domain vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 1208, in startup self._backend.create() File "/usr/lib64/python2.6/site-packages/libvirt.py", line 300, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error unable to start guest: can't parse: "isa-fdc,driveA=drive-fdc0-0-0" Any problems with floppy in general? My set of related packages' versions: [gcecchi@tekkaman ~]$ rpm -qa qemu\* \*virt\* qemu-spice-83-2.fc12.x86_64 qemu-kvm-tools-0.12.2-6.fc12.x86_64 libvirt-client-0.7.6-1.fc12.x86_64 qemu-common-0.12.2-6.fc12.x86_64 virt-manager-0.8.3-1.fc12.noarch libvirt-python-0.7.6-1.fc12.x86_64 qemu-kvm-0.12.2-6.fc12.x86_64 qemu-user-0.12.2-6.fc12.x86_64 qemu-system-x86-0.12.2-6.fc12.x86_64 libvirt-0.7.6-1.fc12.x86_64 qemu-img-0.12.2-6.fc12.x86_64 convirt-kvm_only-1.1-1.fedora.noarch python-virtinst-0.500.2-1.fc12.noarch

2 3

[PATCH 0/4] Add a F-13 machine type, virtio-serial fixes
by Amit Shah 25 Feb '10

25 Feb '10

Hello, This patch series adds a 'fedora-13' machine type to differentiate from the upstream 0.12 machine type. It also backports a few virtio-serial fixes from upstream: disabling MSI, disabling virtio-serial for older machine types. If there are no objections, I'll commit this to the F-13 repo. Amit Shah (3): pc: Add a Fedora-13 machine type that contains backports from upstream pc: Add backward compatibility options for virtio-serial virtio-serial: pci: Allow MSI to be disabled Michael S. Tsirkin (1): virtio-serial: don't set MULTIPORT for 1 port dev hw/pc.c | 47 +++++++++++++++++++++++++++++++++++++++++++++-- hw/virtio-pci.c | 6 +++--- hw/virtio-serial-bus.c | 6 ++++-- 3 files changed, 52 insertions(+), 7 deletions(-)

2 5

[PATCH 0/7] vhost-net: migration/restart fixes
by Michael S. Tsirkin 25 Feb '10

25 Feb '10

The following patches fix guest restart and migration issues with vhost, bringing it up to date with latest vhost bits. After applying these patches, I get seamless live migration while running netperf TCP stream. Please consider them for F-13. Michael S. Tsirkin (7): msix: migration fix vhost: logging thinko fix vhost: move vhost_set_vq_addr vhost: used addr migration fix vhost: fix used logging size math vhost: logging mistake enable, not disable log vhost: fix log base hw/msix.c | 16 +++++++++-- hw/vhost.c | 80 ++++++++++++++++++++++++++++++++++++++++------------------- 2 files changed, 67 insertions(+), 29 deletions(-)

2 8

How can we pass kernel arguments(e.g:ks=hd:/dev/..) to a cdrom-based guest install?
by Li Ming 25 Feb '10

25 Feb '10

Hi, How can I pass the ks argument to a guest during install? I am writing an auto install python script,I can use virt-install --location install_tree --extra-args ks=...., but this will active the network, we want to mirror a true DVD install. If use virt-install --cdrom will solve this issue, we have a bad way to pass ks argument,uncompress the ISO,update the syslinux kernel args,then build the ISO again,but this will consume big resource,not a good way. Does someone have good suggestion for me to pass ks arg to kernel while using virt-install --cdrom in python script? Thanks Liam

6 8

Re: [fedora-virt] febootstrap on fedora 12 ppc: updates don't work?
by Richard W.M. Jones 23 Feb '10

23 Feb '10

On Mon, Feb 22, 2010 at 08:48:32PM -0700, Anthony Foiani wrote: > Richard -- > > First, thanks for the excellent tool! I'm trying to use it to create a root > FS for doing development on an embedded PPC board. > > (Out of curiosity, just how much work do you think implementing a > "--foreign" capability is? I happened to have an old PPC machine with an > f12 install on it, so I dodged that bullet, but it would be fantastic to be > able to build this root on my modern x86-64 workstation hardware...) > > Anyway, I tried to use the "-u" flag to febootstrap (hoping / believing that > it would provide my new root with the most up-to-date packages in my root), > and it failed to find the update repo metadata. I tried it again, without > the "-u" flag, and it mostly succeeded; it failed to install the > "filesystem", and "nscd" (?, error has already scrolled off my terminal) was > throwing "must be root" errors. > > I can duplicate this to get you more info if it would help... > > Anyway, the error message and a uname: > > $ uname -a > Linux shiny.int.foiani.com 2.6.31.9-174.fc12.ppc #1 Mon Dec 21 04:59:46 UTC > 2009 ppc ppc ppc GNU/Linux > > $ febootstrap \ > > -i bash -i 'boost*' -i 'g++' -i 'httpd' -i httpd-tools \ > > -u fedora-released-f12 \ > > fedora-12 f12-ppc-root > febootstrap | 4.2 kB 00:00 > febootstrap/primary_db | 12 MB 00:11 > Error: Cannot retrieve repository metadata (repomd.xml) for repository: > febootstrap-updates. Please verify its path and try again It cannot find the fedora-released-f12 repository for whatever reason. You should probably find out what path yum is trying to access. > chroot: failed to run command `rm': No such file or directory > chroot: failed to run command `rm': No such file or directory These are just a consequence of yum failing. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen guests. http://et.redhat.com/~rjones/virt-p2v

1 0

add new volume suggestion whille creating vm
by Gianluca Cecchi 22 Feb '10

22 Feb '10

Hello, I have F12 x86_64 and I'm using rawvirt fedora-virt-preview repo. qemu-spice-83-2.fc12.x86_64 qemu-kvm-tools-0.12.2-6.fc12.x86_64 libvirt-client-0.7.6-1.fc12.x86_64 qemu-common-0.12.2-6.fc12.x86_64 virt-manager-0.8.3-1.fc12.noarch libvirt-python-0.7.6-1.fc12.x86_64 qemu-kvm-0.12.2-6.fc12.x86_64 qemu-user-0.12.2-6.fc12.x86_64 qemu-system-x86-0.12.2-6.fc12.x86_64 libvirt-0.7.6-1.fc12.x86_64 qemu-img-0.12.2-6.fc12.x86_64 python-virtinst-0.500.2-1.fc12.noarch When I create a VM and arrive at storage window (step 4 of 5), I select "Select managed or other existing storage" then "browse"; then in "locate or create storage volume" window I select "new volume" button and I'm put into "Add a storage volume" window, that used to directly work previously. Now instead, I seem not to be able to get the "Finish" button selectable (it remains grey), any value I use for name, format and capacity options. Note that this problem exists only with the steps above and I found the cause is that there is the proposed suggestion of "vmname.img" (where vmname is name I'm giving to my vm) inside the box, but also the ".img" extension is out of the "Name" box, at the right side .... as soon as I keep off the ".img" letters inside the box, the "Finish" button becomes selectable (black) probably the automatic suggestion is to kept without the .img part..... Note that instead, if I use the other method, going directly to select "details" for my host, then the "storage" label and select "New volume", the "name:" box is empty and not confusing..... HIH, Gianluca

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

virt February 2010