- Users - libvirt List Archives

[libvirt-users] libvirtError: internal error Domain mytest didn't show up
by Chun Tat David Chu 02 Jun '11

02 Jun '11

Hi All, I am new using libvirt. I kept on getting the following error when I try to start my VM. Can anyone give me any suggestion on what could went wrong? Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 498, in run_domain vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 573, in startup self.vm.create() File "/usr/lib64/python2.4/site-packages/libvirt.py", line 287, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error Domain mytest didn't show up Thanks, David

2 3

[libvirt-users] io=native
by Troels Arvin 02 Jun '11

02 Jun '11

Hello, Regarding KVM - in particular RHEL 6.1 x86_64: I just did a set of benchmarks comparing the effect of <driver name='qemu' type='raw' cache='none' io='native'/> versus <driver name='qemu' type='raw' cache='none'/> Using Oracle's "orion" tool with an XIV backend, I got: With io='native': Maximum Large MBPS=964.41 Maximum Small IOPS=11797 Minimum Small Latency=7.57 WithOUT io='native': Maximum Large MBPS=727.42 Maximum Small IOPS=7793 Minimum Small Latency=7.56 In other words, setting the io-attribute to 'native' yields a significant performance improvement. I wonder why KVM doesn't simply default to using io='native'. If that can't happen, then I wonder why libvirt doesn't set io='native' for storage attached to a guest after creation. (virt-manager sets io='native' for the first storage, attached during guest setup, but seems to forget for subsequent block-device additions). -- Regards, Troels Arvin <troels(a)arvin.dk> http://troels.arvin.dk/

1 0

[libvirt-users] unable to migrate guests
by PREETHI RAMESH 31 May '11

31 May '11

I'm new to libvirt and I'm facing a problem while migrating the guest domain. Both guest and host are of the same config(checked it with uname -a) Migrating using virsh, I get: virsh # migrate hda2 --desturi qemu+ssh://root@10.129.54.254/system root(a)10.129.54.254's password: error: operation failed: migration to 'tcp:kvm-lab:49168' failed: migration failed. The details of the problem are shown by the Virtual machine manger are: Unable to migrate guest: operation failed: migration to 'tcp:kvm-lab:49165' failed: migration failed Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/migrate.py", line 523, in _async_migrate vm.migrate(dstconn, migrate_uri, rate, live, secure, meter=meter) File "/usr/share/virt-manager/virtManager/domain.py", line 1141, in migrate self._backend.migrate(destconn.vmm, flags, newname, interface, rate) File "/usr/lib/python2.7/dist-packages/libvirt.py", line 521, in migrate if ret is None:raise libvirtError('virDomainMigrate() failed', dom=self) libvirtError: operation failed: migration to 'tcp:kvm-lab:49165' failed: migration failed I've tried disabling apparmor and then migrating by- pre@pre-Inspiron-N4010:~$ sudo invoke-rc.d apparmor kill .: 35: Can't open /lib/apparmor/functions invoke-rc.d: initscript apparmor, action "kill" failed. and stopping iptables- pre@pre-Inspiron-N4010:~$ sudo /etc/init.d/iptables stop [sudo] password for pre: sudo: /etc/init.d/iptables: command not found Thank you.

1 0

[libvirt-users] no virtio in virt-manager
by Konstantin Svist 30 May '11

30 May '11

Hi, For some reason, I don't have virtio as an option in virt-manager on one of my computers. I'm using Fedora 14 with virt-preview repo, x64 architecture. It must be some package that I missed, does anyone know what it might be? Thanks

1 0

[libvirt-users] Forward routed network bridge on system's vlan
by RaSca 30 May '11

30 May '11

Hi all, I created a two node cluster that manages virtual machines with two servers connected via a cross cable on the network 10.0.0.0/24. I want that machines that runs on different servers in the network 172.16.0.0/24 can see all the others. To make this possible I've configured a vlan on each server: ... ... 5: eth1.111@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP link/ether 5c:d9:98:b1:4c:4d brd ff:ff:ff:ff:ff:ff inet 172.16.0.0/24 brd 172.16.0.255 scope global eth1.111 inet6 fe80::5ed9:98ff:feb1:4c4d/64 scope link valid_lft forever preferred_lft forever ... ... And created a "lan" network, via virsh: <network> <name>lan</name> <uuid>8ac034c8-553d-b995-5a80-c1c711cb088c</uuid> <forward dev='eth1.111' mode='route'/> <bridge name='virbr1' stp='on' delay='0' /> <ip address='172.16.0.2' netmask='255.255.255.0'> </ip> </network> but with this setup "lan" never comes up because, for some reason, the network is locked: # virsh net-start lan error: Failed to start network lan error: internal error Network 172.16.0.1/255.255.255.0 is already in use by interface eth1.111 What is not clear to me is why, if I turn down the eth1.111 device, start the lan network, turn eth1.111 up and then force the brctl addif command, everything works: # ifdown eth1.111 Removed VLAN -:eth1.111:- # virsh net-start lan Network lan started # ifup eth1.111 Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config Added VLAN with VID == 111 to IF -:eth1:- # brctl addif virbr1 eth1.111 # brctl show bridge name bridge id STP enabled interfaces br0 8000.6c626dd7518e no eth0 virbr0 8000.000000000000 yes virbr1 8000.5cd998b14c4d yes eth1.111 Why manually is possible to make things work? What am I ignoring? Thanks a lot, -- RaSca Mia Mamma Usa Linux: Niente è impossibile da capire, se lo spieghi bene! rasca(a)miamammausalinux.org http://www.miamammausalinux.org

1 0

[libvirt-users] libvirt boots from Knoppix-CD but not Debian-CD
by Christian Brandt 29 May '11

29 May '11

Debian Squeeze, libvirt 0.8.3, qemu-kvm 0.15.5 After configuring the cd image the bios screen shows: (tested with virsh, virt-install and virt-manager) Starting SeaBIOS (version 0.5.1-20110523_174945-brahms) Booting from CD-Rom 65MB medium found (bzw. whatever size) Boot failed: Could not read from CDROM (code 000c) ... the cd images (debian6-cd1, debian6-netinst, debian6-buisnesscard) have the correct md5sum an can be mounted, they simply do not boot. On the other hand, a recent knoppix ISO works well. Tested countless times. All access rights are 777. Only special feature: the host is a minimal installation done with debootstrap and contains not much else than libvirt, virt-manager and lxterminal. I am out of wit. Any ideas? -- Christian Brandt life is short and in most cases it ends with death but my tombstone will carry the hiscore

1 2

[libvirt-users] kvm.h not found
by --[ UxBoD ]-- 27 May '11

27 May '11

Hello all, Am attempting to compile the latest version of libvirt against a custom kernel 2.6.32.40 under CentOS 5.6 and see this in the configure output: checking linux/kvm.h usability... no checking linux/kvm.h presence... no checking for linux/kvm.h... no I have tried to change where it is looking using: CPPFLAGS="-I /home/compuser/linux-2.6.32.40/include" ./configure but end up with the same result. What am I doing wrong ? -- Thanks, Phil

2 1

[libvirt-users] polkit error when starting virt-manager on fedora14
by Alex 26 May '11

26 May '11

Hi, I have the following error in syslog when starting virt-manager and trying to connect: May 25 16:39:33 sage libvirtd: 16:39:33.525: error : remoteDispatchAuthPolkit:3846 : Policy kit denied action org.libvirt.unix.manage from pid 27509, uid 500, result: 512 I can manually start the kvm guest using virsh, but why can't virt-manager start them? This is on fedora14 x86_64: # rpm -qva|egrep 'virt|polkit|qemu' polkit-qt-0.99.0-2.fc14.x86_64 qemu-img-0.13.0-1.fc14.x86_64 python-virtkey-0.50-8.fc14.x86_64 qemu-kvm-0.13.0-1.fc14.x86_64 polkit-0.98-5.fc14.x86_64 polkit-gnome-0.97-4.fc14.x86_64 libvirt-python-0.8.3-9.fc14.x86_64 virt-viewer-0.2.1-1.fc13.x86_64 gpxe-roms-qemu-1.0.1-3.fc14.noarch virt-top-1.0.4-3.fc13.x86_64 libvirt-client-0.8.3-9.fc14.x86_64 virtuoso-opensource-6.1.2-1.fc14.x86_64 qemu-common-0.13.0-1.fc14.x86_64 polkit-desktop-policy-0.98-5.fc14.noarch redland-virtuoso-1.0.12-1.fc14.x86_64 python-virtinst-0.500.6-1.fc14.noarch libvirt-0.8.3-9.fc14.x86_64 qemu-system-x86-0.13.0-1.fc14.x86_64 virt-manager-0.8.7-2.fc14.noarch Please let me know what other information I can provide to fix this problem. I haven't rebooted yet, but I suspect at least that would fix it? Thanks, Alex

1 1

[libvirt-users] Failed to connect to Xen 4.1 using virsh
by YAO 26 May '11

26 May '11

Hi, I installed xen 4.1 and libvirt 0.9.1 on ubuntu 10.04 x86 when I tried "*virsh -c xen:/// list*", the terminal give me error: *error: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd may need to be started: No such file or directory* *error: failed to connect to the hypervisor* But when I tried "*sudo virsh -c xen:/// list*", there's different error: *error: unable to connect to 'localhost:8000': Connection refused* *error: failed to connect to the hypervisor* That really confused me. Do I need to start libvirtd like "*sudo libvirtd*"? cause "*virsh -c test:///default list*" is OK without it. I have started xencommons and xend, so I really don't know what I missed... Thanks, Yao

1 0

[libvirt-users] Replace library WinXPs by virtual WinXPs as on a linux Fedora system?
by Rob 25 May '11

25 May '11

Hi, The current situation: * About 500 university library PCs run WinXP as the main OS. I would like to achieve the following: * Replace the WinXP by a linux system (Fedora?) with virtualizationsoftware (KVM?) and have WinXP as a guest OS, in such a way that the users immediately boot into WinXP without noticing the virtualization. * Over the network I should still be able to access the host Fedora OS. Is this a feasible idea? If yes, can you give me some clues how to start? Thank you! Rob.

1 0