April 2015 - Users - libvirt List Archives

[libvirt-users] issue on fedora21 with libvirt-1.2.13 and 1.2.14 - containers won't start at all
by Thierry Parmentelat 11 Apr '15

11 Apr '15

Answering my own question, seems like my problem is very similar to what is reported below for redhat enterprise linux 7 https://bugzilla.redhat.com/show_bug.cgi?id=1209757

1 0

[libvirt-users] issue on fedora21 with libvirt-1.2.13 and 1.2.14 - containers won't start at all
by Thierry Parmentelat 11 Apr '15

11 Apr '15

Hi there I am using fedora21 for hosts and guests, using lxc containers, and was on vanilla 1.2.9 as exposed by the fedora yum repo The other day I was needing the ability to grant mknod capability to some guests, some chap on IRC kindly pointed me at the <capabilities> tag However I was told that needed 1.2.11 So I went and rebuilt from this download http://libvirt.org/sources/libvirt-1.2.14-1.fc21.src.rpm using plain rmbuild —rebuild Once I had upgraded my host with these new rpms it looked like everything was going fine, and my guests indeed were able to mknod However once I rebooted the host, virsh unpleasantly refused to start any of my containers, and complained like this after hanging for 5 to 10 seconds: 2015-04-11 07:44:10.295+0000: 37843: error : virLXCProcessStart:1263 : internal error: guest failed to start: libvirt: error : Failed to terminate process 37905 with SIGKILL: Device or resource busy — At that point I redid the same with 1.2.13, which gave me the same behaviour, and then 1.2.12 which seems to work for me right now — So it looks like 1.2.13 brings me a regression of some kind I am attaching the XML config for one sample domain, mostly they all look alike Should I file a bug report, and if so where should I do that ? thanks — root@buzzcocks ~ # virsh -c lxc:/// dumpxml testmaster setlocale: No such file or directory <domain type='lxc' id='1528'> <name>testmaster</name> <uuid>18989592-f964-4d51-90af-7ecf7719b758</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu placement='auto'>1</vcpu> <numatune> <memory mode='strict' placement='auto'/> </numatune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64'>exe</type> <init>/sbin/init</init> </os> <features> <acpi/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/libexec/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/vservers/testmaster'/> <target dir='/'/> </filesystem> <interface type='bridge'> <mac address='52:54:00:ae:8b:47'/> <source bridge='br0'/> <target dev='viftestmaster'/> <guest dev='eth0'/> </interface> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='lxc' port='0'/> <alias name='console0'/> </console> </devices> </domain>

1 0

[libvirt-users] Detecting that the VM is snapshoting
by Joaquín Rinaudo 10 Apr '15

10 Apr '15

While taking or reverting a snapshot, using virsh --connect qemu:///system dominfo, the state of a VM is paused. Is there a way to distinguish this state (snapshotting) with virsh or any other tools? Joaquín

2 2

[libvirt-users] LXC and syslog seperation (/dev/log)
by James Leu 10 Apr '15

10 Apr '15

Hello, I'm seeing syslog messages "bleed" from the host and other LXC into the messages, maillog, secure logs of other LXCs. I'm using libvirt 1.0.0 on a host with systemd and kernel 3.9.10. Each LXC is running an older non-systemd linux distribution Is this a known issue? Is there a work around? Thank you for you time, Jim -- James R. Leu | Director of Technology | INOC | Madison, WI, USA O: +1-608-204-0203 | F: +1-608-663-4558 | jleu(a)inoc.com | www.inoc.com Service. Not Software.®

3 3

[libvirt-users] raw disks used by guest unavailable to host - retrieve them?
by lejeczek 10 Apr '15

10 Apr '15

hi everybody my guests had drives passed though, like here: <disk type='block' device='lun'> <driver name='qemu' type='raw' cache='none'/> <source dev='/dev/sdv'/> <target dev='sda' bus='scsi'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> guests were Windows 8/2012, now after de-defining guests those disks are still unavailable to host's lvm, pvscan doesn't see. Is there a way to fix it? bw. P

1 1

[libvirt-users] How to get the real migrate speed (MB/s) in the libvirt.
by Edward Young 10 Apr '15

10 Apr '15

Hi all, I start to migrate a VM with its storage using "virsh migrate --live --copy-storage-all ..." command. I'm wondering whether we can get the migration report when the migration is done. For instance, how long it takes to migrate this VM, the total data transferred and etc.. Thanks! Ed

2 1

[libvirt-users] Centos 7.1.1503 + libvirt 1.2.14 = broken direct network mode
by mxs kolo 09 Apr '15

09 Apr '15

Hi all. I use LXC on Centos 7 x86-64, with libvirt version 1.2.6 and 1.2.12 My container has bridged network: # virsh dumpxml test1 <domain type='lxc'> <name>test1</name> <uuid>518539ab-7491-45ab-bb1d-3d7f11bfb0b1</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <memtune> <hard_limit unit='KiB'>1048576</hard_limit> <soft_limit unit='KiB'>1048576</soft_limit> <swap_hard_limit unit='KiB'>2097152</swap_hard_limit> </memtune> <vcpu placement='static'>2</vcpu> <os> <type arch='x86_64'>exe</type> <init>/sbin/init</init> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/libexec/libvirt_lxc</emulator> <filesystem type='block' accessmode='passthrough'> <source dev='/dev/data/test1'/> <target dir='/'/> </filesystem> <filesystem type='ram' accessmode='passthrough'> <source usage='524288' units='KiB'/> <target dir='/dev/shm'/> </filesystem> <interface type='direct'> <mac address='02:00:00:1a:a9:54'/> <source dev='br0' mode='bridge'/> </interface> <console type='pty'> <target type='lxc' port='0'/> </console> </devices> </domain> And all was fine, before I accidentally upgraded Centos to 7.1.1503 After upgrade LXC can't start with diagnostic: [root@node14 ~]# virsh start test1 error: Failed to start domain test1 error: internal error: guest failed to start: internal error: Child process (ip link set macvlan0 netns 25263) unexpected exit status 2: RTNETLINK answers: Invalid argument I reinstall libvirt 1.2.14, but catch same error. If someone will experience in solving this problem - it will be interesting to hear about. b.r. Maxim Kozin

2 4

[libvirt-users] XML vm configfile with Display using QEMU GTK interface
by Vinícius Ferrão 09 Apr '15

09 Apr '15

Hello guys, I'm trying to start a VM using the QEMU GTK Display Interface instead of a SDL window. But I'm failing. My actual setting is using SDL with this XML line: <graphics type='sdl' display=':0.0' xauth='/home/ploog/.Xauthority'/> I changed to: <graphics type='gtk'> But it fails to start the VM. Any ideias? Thanks in advance,

2 1

[libvirt-users] SIGTERM signal to qemu-kvm process
by Jatin Davey 09 Apr '15

09 Apr '15

Hi I am using QEMU 0.12.1 as the hypervisor in my RHEL installation of 6.5. I wanted to know if there are any side-effects with respect to VM image corruption when i use SIGTERM signal to kill a qemu-kvm process which effectively stops my VM running on the host. Appreciate if you can provide me some valuable information in this regard. Thanks Jatin

3 4

[libvirt-users] [Libvirt] [virsh] Transport Error during enumeration while connecting libvirt to Hyper-V Server
by Dhaval_Shah1＠dell.com 07 Apr '15

07 Apr '15

Hi all, I am using libvirt 1.1.1. I can successfully able to connect with Qemu driver but when I am trying to connect to the windows Hyper-V using virsh, I am getting failure. [root@localhost hyperv]# virsh version Compiled against library: libvirt 1.1.1 Using library: libvirt 1.1.1 Using API: QEMU 1.1.1 Running hypervisor: QEMU 1.5.3 When I am doing virsh to connect to hype-V I am getting failure that [root@localhost hyperv]# virsh -c hyperv://172.16.67.192 Enter username for 11.16.67.92 [administrator]: administrator Enter administrator's password for 11.16.67.92: error: failed to connect to the hypervisor error: internal error: Transport error during enumeration: Transport initialization failed (2) using gdb I came to know that from the function "hypervEnumAndPull()" it is calling "wsmc_action_enumerate()" and we are verifying the response using "hyperyVerifyResponse" and from there it fails and cleanup is being called. Code : response = wsmc_action_enumerate(priv->client, root, options, filter); if (hyperyVerifyResponse(priv->client, response, "enumeration") < 0) { goto cleanup; } I have correctly done the settings on my hyper-v Server using below commands: winrm set winrm/config/service/auth @{Basic="true"} winrm set winrm/config/service @{AllowUnencrypted="true"} Does anyone knows what could be wrong or I am missing something or can anyone help to solve this issue. Thanks & Regards, Dhaval Shah

2 3