March 2013 - Users - Libvirt List Archives

[libvirt-users] unssafe operation with virt-manager

by digvijay chauhan

I tried to migrate with virt-manager's GUI but when i invoke migrate command it gives me error that "unable to migrate vm unsafe operation"

11 years, 4 months

2
1
0 / 0

[libvirt-users] How to pass USB device to the guest VM

by Marc Haber

Hi, I am trying to access my Galaxy Tab from Samsung KIES running on Windows 7 inside a KVM VM. This unfortunately does not seem to work as expected. My Distribution is debian unstable. I therefore have qemu-system-x86 version 1.4.0+dfsg-1exp, libvirt 1.0.3-1 and virt-manager 0.9.4-2. lsusb shows the Tab as follows: Bus 001 Device 016: ID 04e8:6877 Samsung Electronics Co., Ltd Galaxy S in Virt Manager, I can add a USB Host Device 001:016 SAMSUNG SAMSUNG_Android. This ends up in the VM as "USB 04e8:6877" and shows up in XML as <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x04e8'/> <product id='0x6877'/> </source> </hostdev> However, when I start Windows 7, the Galaxy Tab is not detected and also does not show up in Device Manager. The KVM process is called as: qemu-system-x86 -machine accel=kvm:tcg -name mywindows -S -M pc-1.1 -m 4096 -smp 2,sockets=2,cores=1,threads=1 -uuid 8e6e01e8-2191-9dcc-e2e4-5eb7ae55c450 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/snsvw001.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/dev/luksdev/mywindows,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=23,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:c4:16:65,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on -vga qxl -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=67108864 -device usb-host,hostbus=1,hostaddr=16,id=hostdev0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 This looks correct to me as a layman. Also, when I boot up the same VM with Linux as guest OS, the Galaxy Tablet does not show up in lsusb. What is happening on my system so that the USB device is not detected in Windows and Linux? Any ideas how to fix that? Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 31958061 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 31958062

11 years, 4 months

1
0
0 / 0

Re: [libvirt-users] [virt-tools-list] C'ant migrate with virt-manager or virsh

by Cole Robinson

On 03/14/2013 03:17 AM, Digvijay wrote: > [root@node0 ~]# virsh migrate --live try1 qemu+ssh://root@100.100.102.106/system > --unsafe > root(a)100.100.102.106's password: > error: operation failed: migration job: unexpectedly failed > error: Reconnected to the hypervisor > CC-ing libvirt-users I think that virsh command should work. Look at /var/log/libvirt/qemu/$vmname.log on both the source host and the destination host. > > I tried to run the migration but it is not doing profitably.I also used virtual > machine manager but it is giving me " unsafe operation" > > Unable to migrate guest: Unsafe migration: Migration may lead to data corruption > if disks use cache != none > > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/asyncjob.py", line 96, in cb_wrapper > callback(asyncjob, *args, **kwargs) > File "/usr/share/virt-manager/virtManager/migrate.py", line 553, in _async_migrate > vm.migrate(dstconn, migrate_uri, rate, live, secure, meter=meter) > File "/usr/share/virt-manager/virtManager/domain.py", line 1163, in migrate > self._backend.migrate(destconn.vmm, flags, newname, interface, rate) > File "/usr/lib64/python2.7/site-packages/libvirt.py", line 822, in migrate > if ret is None:raise libvirtError('virDomainMigrate() failed', dom=self) > libvirtError: Unsafe migration: Migration may lead to data corruption if disks > use cache != none Like the error says, your disks need to have cache=None or libvirt won't allow the migration. You can change that setting per disk in the VM details UI in virt-manager. - Cole

11 years, 4 months

2
2
0 / 0

[libvirt-users] Check memory inside a container

by Saurabh Deochake

Hi all, I'm new to LXC and libvirt. I have created a LXC container using libvirt. In domain XML file I have mentioned "memory" and "current memory" as 256 MB. Now I want to check the memory inside the container, but whenever I run top command or try to cat /proc/meminfo, it shows host machine's memory which is 3GB. So is there any command by which I can check containers memory? Regards, Saurabh Deochake.

11 years, 4 months

2
2
0 / 0

[libvirt-users] backup disk/state

by Evaggelos Balaskas

Hi there, i am trying to understand something that bothering me for some time now. A running domain has two things that someone needs to take backup. So there is the disk and the state. Using snapshots as checkpoint someone can take the disk snapshot but i cant understand how to "transfer" the saved state from "backup ed" disk. Reading through Kashyap's and Eric's posts (mostly) i can now understand a lot about backing up and snapshotting but i cant figure out (perhaps i need to read more) how to boot up the snapshot disk with the saved (?) state. Thanks in advance -- Evaggelos Balaskas - Unix System Engineer http://gr.linkedin.com/in/evaggelosbalaskas

11 years, 4 months

2
1
0 / 0

[libvirt-users] RHEL 5 libvirt client - QEMU+SSH fails with "login authentication type 2" problem

by Saravanan Shanmugham (sarvi)

Hi, I have RHEL5 libvirt client compiled at ${BSPACE}/usrcisco This client when connecting to a libvirtd/server fails to connect as follows -bash-3.2$ ${BSPACE}/usrcisco/bin/virsh -c qemu+ssh://sarvi@cnh-nehalem-1/system?socket=/var//run/libvirt/libvirt-sock error: failed to connect to the hypervisor error: authentication failed: unsupported authentication type 2 I have the libvirt client compiled and installed as follows PYTHON=${BSPACE}/usrcisco/bin/python LDFLAGS="-L${BSPACE}/libnl-1.1.2/lib/ -L${BSPACE}/device-mapper.1.02.28/lib/ioctl/" CFLAGS="-I${BSPACE}/libnl-1.1.2/include -I${BSPACE}/device-mapper.1.02.28/include/" CPPFLAGS="-I${BSPACE}/device-mapper.1.02.28/include/ -I${BSPACE}/libnl-1.1.2/include" ./configure --prefix=${BSPACE}/usrcisco --enable-static --with-libvirtd=no --with-hal=no --with-python --with-PACKAGE=yes --with-packager=no --with-packager-version=no --with-gnu-ld=no --with-apparmor=no --with-apparmor-mount=no--with-attr=no --with-audit=no --with-avahi=no --with-blkid=no --with-capng=no --with-curl=no --with-dbus=no --with-fuse=no --with-hal=no --with-netcf=no --with-numactl=no --with-openwsman=no --with-pciaccess=no --with-sanlock=no --with-sasl=no --with-selinux=no --with-selinux-mount=no --with-udev=no --with-yajl=no --with-xen=no --with-xen-inotify=no --with-qemu=no --with-uml=no --with-openvz=no--with-vmware=no --with-phyp=no --with-xenapi=no --with-libxl=no --with-vbox=no --with-gnutls=no --without-ssh2 --with-rhel5-api=yes The same library sources when compiled on RHEL6 as above, without specifying the "--with-rhel5-api=yes" compiles AND connect to the same server fine I am looking for pointers as to what the problem could be OR how to trouble shoot the problem. Thanks, Sarvi

11 years, 4 months

1
2
0 / 0

[libvirt-users] update qemu-kvm with running guests?

by Jamie Fargen

Good Afternoon, I was curious to know what happens to running guests when the qemu-kvm rpm is update via yum. I assume that the current qemu processes would be running the old binary, but the new processes would be started using the new binary. Please let me know if this assumption is correct. Regards, Jamie Ian Fargen

11 years, 4 months

2
1
0 / 0

[libvirt-users] QEMU+SSH login issue on RHEL 4

by Shantan Marepally (shanredd)

Hi All, I am trying to compile libvirt tools from source on RHEL 4. I could get the sources compiled, but when I try to connect to libvirtd using QEMU+SSH I get the following error: error: failed to connect to the hypervisor error: authentication failed: unsupported authentication type 2 With root as the user, I could login, rest other users get the error. All authentication related settings are setup fine. When I try the login using QEMU+SSH to the same libvirtd, compiled on RHEL 5, with any other user things seem to be working fine. The thing that was different in the build is that I am trying to build a minimal virsh client on RHEL 4. The following are the configure parameters I used: ./configure --enable-static --with-libvirtd=no --with-hal=no --with-python --with-PACKAGE=yes --with-packager=no --with-packager-version=no --with-gnu-ld=no --with-apparmor=no --with-apparmor-mount=no--with-attr=no --with-audit=no --with-avahi=no --with-blkid=no --with-capng=no --with-curl=no --with-dbus=no --with-fuse=no --with-hal=no --with-netcf=no --with-numactl=no --with-openwsman=no --with-pciaccess=no --with-sanlock=no --with-sasl=no --with-selinux=no --with-selinux-mount=no --with-udev=no --with-yajl=no --with-xen=no --with-xen-inotify=no --with-qemu=no --with-uml=no --with-openvz=no --with-vmware=no --with-phyp=no --with-xenapi=no --with-libxl=no --with-vbox=no --with-gnutls=no Are there any specific options that are needed for QEMU+SSH to work? any other ideas what could go wrong? Thanks, Shantan Ps: The following are the debug logs with the error message: 2013-03-11 20:13:21.887+0000: 19285: debug : virNetClientIOEventLoopPassTheBuck:1423 : Giving up the buck (nil) 2013-03-11 20:13:21.887+0000: 19285: debug : virNetClientIOEventLoopPassTheBuck:1437 : No thread to pass the buck to 2013-03-11 20:13:21.887+0000: 19285: debug : virNetClientCloseLocked:644 : client=0x2a98c0d9c0, sock=0x2a98c0d6c0, reason=3 2013-03-11 20:13:21.887+0000: 19285: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c0d6c0 2013-03-11 20:13:21.887+0000: 19285: debug : virObjectRef:295 : OBJECT_REF: obj=0x2a98c0d9c0 2013-03-11 20:13:21.887+0000: 19285: debug : virKeepAliveStop:299 : RPC_KEEPALIVE_STOP: ka=0x2a98c0dae0 client=0x2a98c0d9c0 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollRunOnce:640 : Poll got 1 event(s) 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollDispatchTimeouts:425 : Dispatch 0 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollDispatchHandles:470 : Dispatch 2 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollDispatchHandles:484 : i=0 w=1 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollDispatchHandles:498 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollDispatchHandles:484 : i=1 w=2 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollDispatchHandles:487 : Skip deleted n=1 w=2 f=7 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollCleanupTimeouts:516 : Cleanup 0 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollCleanupTimeouts:552 : Found 0 out of 0 timeout slots used, releasing 0 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollCleanupHandles:564 : Cleanup 2 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollCleanupHandles:577 : EVENT_POLL_PURGE_HANDLE: watch=2 2013-03-11 20:13:21.887+0000: 19286: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c0d9c0 2013-03-11 20:13:21.887+0000: 19286: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c0d6c0 2013-03-11 20:13:21.887+0000: 19286: debug : virObjectUnref:260 : OBJECT_DISPOSE: obj=0x2a98c0d6c0 2013-03-11 20:13:21.887+0000: 19286: debug : virNetSocketDispose:998 : sock=0x2a98c0d6c0 fd=7 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollRemoveHandle:180 : EVENT_POLL_REMOVE_HANDLE: watch=2 2013-03-11 20:13:21.887+0000: 19285: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c0dae0 2013-03-11 20:13:21.887+0000: 19285: debug : virObjectUnref:260 : OBJECT_DISPOSE: obj=0x2a98c0dae0 2013-03-11 20:13:21.887+0000: 19285: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c0d9c0 2013-03-11 20:13:21.887+0000: 19286: debug : virFileClose:73 : Closed fd 7 2013-03-11 20:13:21.887+0000: 19285: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c0d9c0 2013-03-11 20:13:21.887+0000: 19285: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c0d9c0 2013-03-11 20:13:21.888+0000: 19285: debug : virObjectUnref:260 : OBJECT_DISPOSE: obj=0x2a98c0d9c0 2013-03-11 20:13:21.888+0000: 19285: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c20650 2013-03-11 20:13:21.888+0000: 19285: debug : virObjectUnref:260 : OBJECT_DISPOSE: obj=0x2a98c20650 2013-03-11 20:13:21.887+0000: 19286: debug : virFileClose:73 : Closed fd 9 2013-03-11 20:13:21.889+0000: 19285: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c205e0 2013-03-11 20:13:21.889+0000: 19285: debug : virObjectUnref:260 : OBJECT_DISPOSE: obj=0x2a98c205e0 2013-03-11 20:13:21.889+0000: 19286: debug : virProcessAbort:92 : aborting child process 19287 2013-03-11 20:13:21.889+0000: 19285: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c09e80 2013-03-11 20:13:21.889+0000: 19285: debug : virObjectUnref:260 : OBJECT_DISPOSE: obj=0x2a98c09e80 2013-03-11 20:13:21.889+0000: 19286: debug : virProcessAbort:100 : trying SIGTERM to child process 19287 2013-03-11 20:13:21.889+0000: 19285: debug : virFileClose:73 : Closed fd 10 2013-03-11 20:13:21.889+0000: 19285: debug : virFileClose:73 : Closed fd 8 2013-03-11 20:13:21.889+0000: 19285: debug : virNetMessageClear:56 : msg=0x2a98c0da20 nfds=0 2013-03-11 20:13:21.889+0000: 19285: debug : do_open:1206 : driver 1 remote returned ERROR 2013-03-11 20:13:21.889+0000: 19285: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x571630 2013-03-11 20:13:21.889+0000: 19285: debug : virObjectUnref:260 : OBJECT_DISPOSE: obj=0x571630 error: failed to connect to the hypervisor error: authentication failed: unsupported authentication type 2 2013-03-11 20:13:21.889+0000: 19285: debug : virEventPollAddTimeout:225 : Used 0 timeout slots, adding at least 10 more 2013-03-11 20:13:21.889+0000: 19285: debug : virEventPollInterruptLocked:716 : Interrupting 2013-03-11 20:13:21.889+0000: 19285: debug : virEventPollAddTimeout:248 : EVENT_POLL_ADD_TIMEOUT: timer=1 frequency=0 cb=0x411e39 opaque=(nil) ff=(nil) 2013-03-11 20:13:21.909+0000: 19286: debug : virProcessAbort:107 : process has ended: exit status 255 2013-03-11 20:13:21.909+0000: 19285: debug : virEventPollRemoveTimeout:300 : EVENT_POLL_REMOVE_TIMEOUT: timer=1 2013-03-11 20:13:21.909+0000: 19285: debug : virEventPollInterruptLocked:712 : Skip interrupt, 0 1084229984

11 years, 4 months

2
2
0 / 0

[libvirt-users] snapshot-create fails with "error: Failed to open file '(null)': Bad address"

by Thomas Stein

Hello. I'm not able to create a snapshot for none of my vm's running on a particular node. And i have absolut no idea where to look to solve this. Someone can point me to the right direction? hn images # qemu-x86_64 -version qemu-x86_64 version 1.2.2 (qemu-kvm-1.2.0), Copyright (c) 2003-2008 Fabrice Bellard hn images # libvirtd --version libvirtd (libvirt) 1.0.3 hn images # qemu-img info gentoo-template.qcow2 image: gentoo-template.qcow2 file format: qcow2 virtual size: 130G (139586437120 bytes) disk size: 30G cluster_size: 65536 hn images # virsh snapshot-create gentoo-template error: Failed to open file '(null)': Bad address hn images # hn images # uname -a Linux hn 3.8.2 #1 SMP Sat Mar 9 12:17:41 CET 2013 x86_64 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz GenuineIntel GNU/Linux hn images # thank you t.

11 years, 4 months

2
2
0 / 0

[libvirt-users] ANNOUNCE: Oz 0.10.0 Release

by Chris Lalancette

All, I'm pleased to announce release 0.10.0 of Oz. Oz is a program for doing automated installation of guest operating systems with limited input from the user. Release 0.10.0 is a bugfix and feature release for Oz. Some of the highlights between Oz 0.9.0 and 0.10.0 are: * Support for installing OpenSUSE 12.1 and 12.2 * Support for python3 * Support for Ubuntu 12.04.1, 12.04.2, and 12.10 * Fix up <command> ordering so that commands are run in the order they are specified in the XML * Updates and fixes to the documentation * Increase the shutdown timeout to support slower qemu guests * Add a default screenshot directory as /var/lib/oz/screenshots * Support for RHEL 5.9 * Support for Fedora 18 * Switch over to pycurl for header information; this allows http authentication to work * Switch to using the libvirt built-in screenshot mechanism. This removes the gvnc dependency and makes screenshots more reliable, but requires libvirt 0.9.7 or newer * Delete auto-generated ssh keys after customization A tarball of this release is available, as well as packages for Fedora-17. Instructions on how to get and use Oz are available at http://github.com/clalancette/oz/wiki . If you have questions or comments about Oz, please feel free to contact me at clalancette(a)gmail.com, or open up an issue on the github page: http://github.com/clalancette/oz/issues . Thanks to everyone who contributed to this release through bug reports, patches, and suggestions for improvement. Chris Lalancette

11 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Users March 2013