- Users - libvirt List Archives

[libvirt-users] Sharing a host directory with a Windows guest
by Peter Steele 11 Aug '16

11 Aug '16

I'm running libvirt un a CentOS 7.2 host and have created a Windows 10 VM under that. I've been researching how to share a folder on my host with the Windows guest VM but can't figure out if it's possible. I've added the code <filesystem type='mount' accessmode='passthrough'> <driver type='path' wrpolicy='immediate'/> <source dir='var/lib/mydata`'/> <target dir='/mydata'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </filesystem> to the xml definition of my Windows VM but I assume something needs to be configured on the VM side as well. Is there a way to accomplish this? Peter

2 1

[libvirt-users] Proper XML for compareCPU method
by David Ashley 10 Aug '16

10 Aug '16

All - What is the proper XML to supply to the Python Connections compareCPU method? I have looked at the cpu_map.xml file and I believe I have the proper XML configured but the method always throws an exception with a missing CPU architecture error. Here is the code. from __future__ import print_function import sys import libvirt conn = libvirt.open('qemu:///system') if conn == None: print('Failed to open connection to qemu:///system', file=sys.stderr) exit(1) retc = conn.compareCPU('<cpu><arch name="x86"><model name="kvm64"/></arch></cpu>') if retc == -1: print("CPUs are not the same.") else: print("CPUs are the same.") conn.close() exit(0) This probably just a simple error on my part but I have tried more that a few permutations of the XML with no success. So I guess I need some help with this. Thanks, David Ashley

2 1

[libvirt-users] Cannot guestmount a Fedora 24 XFS disk.
by Andre Goree 10 Aug '16

10 Aug '16

I seem to be having trouble using guestmount to mount a Fedora 24 disk that is using XFS. This is the error messings I get when I try: root@cpdev-cn5:/var/lib/libvirt/images/base# guestmount --rw -a ${disk_path}/${disk_name} -m /dev/${target}1 /tmp/fedora-master/ libguestfs: error: mount_options: /dev/vda1 on /: mount: wrong fs type, bad option, bad superblock on /dev/vda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so guestmount: '/dev/sda1' could not be mounted. Did you mean one of these? /dev/sda1 (xfs) Verbose output shows: libguestfs: recv_from_daemon: received GUESTFS_LAUNCH_FLAG libguestfs: [03647ms] appliance is up libguestfs: send_to_daemon: 72 bytes: 00 00 00 44 | 20 00 f5 f5 | 00 00 00 04 | 00 00 00 4a | 00 00 00 00 | ... guestfsd: main_loop: new request, len 0x44 /dev/sda1: No such file or directory mount -o /dev/vda1 /sysroot/ [ 1.759120] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 1.762869] XFS (vda1): Version 5 superblock detected. This kernel has EXPERIMENTAL support enabled! [ 1.762869] Use of these features in this kernel is at your own risk! [ 1.764819] XFS (vda1): Superblock has unknown read-only compatible features (0x1) enabled. [ 1.765834] XFS (vda1): Attempted to mount read-only compatible filesystem read-write. [ 1.765834] Filesystem can only be safely mounted read only. [ 1.767472] XFS (vda1): SB validate failed with error 22. mount: wrong fs type, bad option, bad superblock on /dev/vda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so guestfsd: error: /dev/vda1 on /: mount: wrong fs type, bad option, bad superblock on /dev/vda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so guestfsd: main_loop: proc 74 (mount_options) took 0.09 seconds libguestfs: recv_from_daemon: 272 bytes: 20 00 f5 f5 | 00 00 00 04 | 00 00 00 4a | 00 00 00 01 | 00 12 34 00 | ... libguestfs: error: mount_options: /dev/vda1 on /: mount: wrong fs type, bad option, bad superblock on /dev/vda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so I've tried with both /dev/sda1 and /dev/vda1 but no luck. Interestingly enough, a CentOS 7.2 image with XFS and the same setup (i.e., a single partition formatted with XFS) mounts without issue. Any ideas? Andre Goree Senior Engineer, Atlantic.Net CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information. Any unauthorized disclosure or use without Atlantic.Net's express written consent is strictly prohibited. If you received this email in error, please notify the sender and delete this email from your system.

2 3

[libvirt-users] Mounting VM filesystem on host while VM running
by Patrick PICHON 09 Aug '16

09 Aug '16

Hello, All my VMs are using LVs created on the host side. I'm using collectd to monitor some of the ressources of my host as well as the libvirt pluging to monitor my VMs. Collectd has an interesting plugin ( df ) which can monitor the filesystem usage. I would like to use it to monitor the VMs filesytsem usage. As it is obvious that if I mount the VM filesystem on the host while the VM is running, I'm wondering if I could mount it in READONLY without expecting any panic/corruption problem. Any advices ? Patrick

4 8

[libvirt-users] Libvirt: dynamic ownership did not work
by Jonatan Schlag 05 Aug '16

05 Aug '16

Hi, I have a very strange problem with libvirt. I work on some machines with libvirt (Debian/ Arch Linux) and libvirt set the ownership of images file automatically to the qemu user / group for example on Arch Linux to nobody:kvm. So when I copy an image file with root and use I then with qemu, libvirt change the owner/ group to nobody:kvm. But I also compiled libvirt for a machine (gcc 4.9.4 glibc 2.12) and on this machine libvirt did not change the ownership of the image files which results in this error: libvirtError: internal error: process exited while connecting to monitor: able-ticketing,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on 2016-08-03T18:19:47.494512Z qemu-system-x86_64: -drive file=/data/hdd1/libvirt/images/test.img,format=raw,if=none,id=drive-virtio-disk0: Could not open '/data/hdd1/libvirt/images/test.img': Permission denied When I set the ownership manually to nobody:kvm everything is fine, but I could not work out why libvirt is unable to set the ownership automatically. Can anybody give me a hint where I could search further to work out the problem? My libvirt version is 1.3.3.2 and the settings dynamic_ownership = 1 in /etc/libvirt/qemu.conf is set. I also created a bug report where I described the problem a little bit more detailed. https://bugzilla.redhat.com/show_bug.cgi?id=1363864 Thanks for every help. Regards Jonatan

3 9

[libvirt-users] NPIV storage pools do not map to same LUN units across hosts.
by Nitesh Konkar 04 Aug '16

04 Aug '16

Link: http://wiki.libvirt.org/page/NPIV_in_libvirt Topic: Virtual machine configuration change to use vHBA LUN There is a NPIV storage pool defined on two hosts and pool contains a total of 8 volumes, allocated from a storage device. Source: # virsh vol-list poolvhba0 Name Path ------------------------------------------------------------------------------ unit:0:0:0 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000366 unit:0:0:1 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000367 unit:0:0:2 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000368 unit:0:0:3 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000369 unit:0:0:4 /dev/disk/by-id/wwn-0x6005076802818bda300000000000036a unit:0:0:5 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000380 unit:0:0:6 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000381 unit:0:0:7 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000382 -------------------------------------------------------------------- Destination: -------------------------------------------------------------------- # virsh vol-list poolvhba0 Name Path ------------------------------------------------------------------------------ unit:0:0:0 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000380 unit:0:0:1 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000381 unit:0:0:2 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000382 unit:0:0:3 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000367 unit:0:0:4 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000368 unit:0:0:5 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000366 unit:0:0:6 /dev/disk/by-id/wwn-0x6005076802818bda300000000000036a unit:0:0:7 /dev/disk/by-id/wwn-0x6005076802818bda3000000000000369 -------------------------------------------------------------------- As you can see in the above output,the same set of eight LUNs from the storage server have been mapped, but the order that the LUNs are probed on each host is different, resulting in different unit names on the two different hosts . If the the guest XMLs is referencing its storage by "unit" number then is it safe to migrate such guests because the "unit number" is assigned by the driver according to the specific way it probes the storage and hence when you migrate these guests , it results in different unit names on the destination hosts. Thus the migrated guest gets mapped to the wrong LUNs and is given the wrong disks. The problem is that the LUN numbers on the destination host and source host do not agree. Example, LUN 0 on source_host, for example, may be LUN 5 on destination_host. When the guest is given the wrong disk, it suffers a fatal I/O error. (This is manifested as fatal I/O errors since the guest has no idea that its disks just changed out under it.)The migration does not take into account that the unit numbers do match on on the source and destination sides. So, should libvirt make sure that the guest domains reference NPIV pool volumes by their globally-unique wwn instead of by "unit" numbers? The guest XML references its storage by "unit" number. Eg:- <disk type='volume' device='lun'> <driver name='qemu' type='raw' cache='none'/> <source pool='poolvhba0' volume='unit:0:0:0'/> <backingStore/> <target dev='vdb' bus='virtio'/> <alias name='virtio-disk1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> I am planning to write a patch for it. Any comments on the above observation/approach would be appreciated. Thanks, Nitesh.

1 1

[libvirt-users] Error with OpenStack starting an instance
by Silvia Fichera 04 Aug '16

04 Aug '16

Hi all, I have installed OpenStack using devstack, when I try to launch an instance I have an error related to libvirt: libvirtError: Cannot get interface MTU on 'br-int' and this don't allow to create a VM. Any hint to solve it? Thanks -- Silvia Fichera

2 1

[libvirt-users] Assigning static ip address in libvirt
by harish.shastry＠gmail.com 04 Aug '16

04 Aug '16

Hello Is there way to assign static ip address to lxc and KVM guests with libvirt? I saw some snippets here https://libvirt.org/formatdomain.html#ipconfig but unable to get it to work. Regards Harish Regards Harish

2 1

[libvirt-users] Crash after connection close when callback is in progress
by Vincent Bernat 03 Aug '16

03 Aug '16

Hey! It seems that if I close a connection while a domain event callback is in progress, I can easily have a crash. Here is a backtrace: #v+ #0 virFree (ptrptr=0x0) at ../../../src/util/viralloc.c:582 save_errno = <optimized out> #1 0x00007fc8328a4ad2 in virObjectEventCallbackListPurgeMarked (cbList=0xadfc30) at ../../../src/conf/object_event.c:282 freecb = <optimized out> n = 0 #2 virObjectEventStateFlush (state=0xaf5380) at ../../../src/conf/object_event.c:819 tempQueue = { count = 0, events = 0x0 } #3 virObjectEventTimer (timer=<optimized out>, opaque=0xaf5380) at ../../../src/conf/object_event.c:560 state = 0xaf5380 #4 0x00007fc83280b7aa in virEventPollDispatchTimeouts () at ../../../src/util/vireventpoll.c:457 cb = 0x7fc8328a48d0 <virObjectEventTimer> timer = 1 opaque = 0xaf5380 now = 1470212691501 i = 0 ntimeouts = 1 #5 virEventPollRunOnce () at ../../../src/util/vireventpoll.c:653 fds = 0x7fc824000920 ret = <optimized out> timeout = <optimized out> nfds = 1 __func__ = "virEventPollRunOnce" __FUNCTION__ = "virEventPollRunOnce" #6 0x00007fc83280a141 in virEventRunDefaultImpl () at ../../../src/util/virevent.c:314 __func__ = "virEventRunDefaultImpl" #7 0x0000000000400b37 in loop (arg=0x0) at crash.c:8 __PRETTY_FUNCTION__ = "loop" #v- And the state of cbList: #v+ >>> print *cbList $2 = { nextID = 11419456, count = 1, callbacks = 0x0 } #v- I have another thread, but it is just sleeping when the crash happens. Here is the source code: #+begin_src c #include <stdio.h> #include <unistd.h> #include <assert.h> #include <pthread.h> #include <libvirt/libvirt.h> void* loop(void *arg) { while (1) { assert (virEventRunDefaultImpl() >= 0); } return NULL; } void callback(virConnectPtr conn, virDomainPtr dom, void *opaque) { // Do nothing. } void freecb(void *opaque) { // Do nothing. } int main() { assert(virInitialize() >= 0); assert(virEventRegisterDefaultImpl() >= 0); pthread_t event_loop; assert(pthread_create(&event_loop, NULL, loop, NULL) == 0); virConnectPtr conn = virConnectOpen("test:///default"); assert(conn != NULL); int cbid = virConnectDomainEventRegisterAny(conn, NULL, VIR_DOMAIN_EVENT_ID_LIFECYCLE, callback, NULL, freecb); assert(cbid != -1); virDomainPtr dom = virDomainDefineXML(conn, "<domain type=\"test\">" "<name>new VM</name>" "<memory unit=\"KiB\">8192</memory>" "<os><type>hvm</type> </os>" "</domain>"); assert(dom != NULL); assert(virDomainCreate(dom) != -1); virDomainFree(dom); assert(virConnectDomainEventDeregisterAny(conn, cbid) != -1); if (virConnectClose(conn) > 0 ) { printf("leak...\n"); } usleep(100000); return 0; } #+end_src Running this program in an infinite loop triggers the bug in less than 1 second (most of the time, just after displaying "leak..."). I am using libvirt 2.0.0 (in Debian). I have also file the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1363628 -- Write clearly - don't sacrifice clarity for "efficiency". - The Elements of Programming Style (Kernighan & Plauger)

1 0

[libvirt-users] systemd restarts libvirt
by Ishmael Tsoaela 02 Aug '16

02 Aug '16

Hi All, Can anyone please assist with this issue I am facing. There is continuous restart of libvirt, this causes virt-manager to disconnect. syslogs: systemd[1]: libvirt-bin.service: Start operation timed out. Terminating. systemd[1]: Failed to start Virtualization daemon. systemd[1]: libvirt-bin.service: Unit entered failed state. systemd[1]: libvirt-bin.service: Failed with result 'timeout'. systemd[1]: libvirt-bin.service: Service hold-off time over, scheduling restart. systemd[1]: Stopped Virtualization daemon. systemd[1]: Starting Virtualization daemon... dnsmasq[1296]: read /etc/hosts - 7 addresses libvirtd (libvirt) 1.3.4 QEMU emulator version 2.3.0 vir-manager 1.4.0

2 2