- Users - libvirt List Archives

[libvirt-users] Making remote access to qemu://session easier?
by Lars Kellogg-Stedman 03 May '16

03 May '16

This is frustrating: $ export LIBVIRT_DEFAULT_URI=qemu+ssh://remotehost/session $ virsh list error: failed to connect to the hypervisor error: no valid connection error: Operation not supported: Connecting to session instance without socket path is not supported by the ssh connection driver Has there been any thought given to making this easier? It seems that having a simple helper script on the remote host that could make the same "use $XDG_RUNTIME_DIR or use $HOME/.confg" decision as libvirtd would be able determine the socket path automatically. Would that be a reasonable solution? I see that right now, even support for qemu://remotehost/system requires that "virsh" knows that path to the remote socket, so having a remote helper that can read the libvirt configuration might simplify things in general. That is, I am envisioning that for .../session connections, virsh would do something like: ssh remotehost libvirt-socket-helper --user And for .../system connections, virsh would do something like: ssh remotehost libvirt-socket-helper --system Rather than: ssh remotehost sh -c 'if nc -q 2>&1 | grep \"requires an argument\" >/dev/null 2>&1; then ARG=-q0;else ARG=;fi;nc $ARG -U /var/run/libvirt/libvirt-sock' And in either of the above cases, "libvirt-socket-helper" would parse the environment and the libvirtd configuration as necessary and ultimately act like "nc -U /path/to/some/socket". -- Lars Kellogg-Stedman <lars(a)redhat.com> | larsks @ {freenode,twitter,github} Cloud Engineering / OpenStack | http://blog.oddbit.com/

3 3

[libvirt-users] I have ping through bridge , net has been started , But IPs they're not equivalent.
by Mohsen Pahlevanzadeh 29 Apr '16

29 Apr '16

Dear All, I have the following configuration and I have ping from bridge : ///////////////////////////////////////////////////// iface eth0 inet static address 192.168.1.4 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.1 auto ivbr0 iface ivbr0 inet static address 192.168.1.4 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.1 bridge_ports eth0 bridge_stp on bridge_maxwait 0 bridge_fd 0 ///////////////////////////////////////////// # brctl show bridge name bridge id STP enabled interfaces ivbr0 8000.18037360b44e yes eth0 ///////////////////////////////////////////// my network xml file : <network> <name>myintranet</name> <uuid>465ce6cb-0a69-4f89-92ba-629349741e73</uuid> <forward mode='nat'> <interface dev="eth0" /> </forward> <bridge name='ivbr0' stp='on' delay='0' /> <mac address='52:54:00:0f:f4:f0'/> <ip address='192.168.1.4' netmask='255.255.255.0'> <dhcp> <range start='192.168.1.3' end='192.168.122.254'/> </dhcp> </ip> </network> //////////////////////////////////////////// Now , I have ping of my modem and internet. Then I did the following command : # ip l set dev ivbr0 down # brctl delbr ivbr0 # virsh net-start myintranet Network myintranet started According to above , myintranet network has been started. But with the following IP address : # ip a show dev ivbr0 17: ivbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 52:54:00:0f:f4:f0 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global ivbr0 valid_lft forever preferred_lft forever //////// 192.168.122.1 ? Question is , Where I change this address?(I set in myxml file.) --best regards Mohsen

2 1

[libvirt-users] virsh and disable interface
by Mohsen Pahlevanzadeh 29 Apr '16

29 Apr '16

Dear All, According to http://wiki.libvirt.org/page/Networking#Debian.2FUbuntu_Bridging May be I have to do "ifdown eth0" How can I define, edit or other task live? ---mohsen

2 1

[libvirt-users] vhost-user libvirt 1.2.18 issue
by chintu hetam 28 Apr '16

28 Apr '16

Hello there, i am trying to start my VM with 2 virtio interfaces as a vhost-user interface Following is my relevant xml network configuration " <interface type='vhostuser'> <mac address='52:54:00:c7:ac:38'/> <source type='unix' path='/tmp/vhost1.sock' mode='server'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </interface> <interface type='vhostuser'> <mac address='52:54:00:9d:ea:73'/> <source type='unix' path='/tmp/vhost2.sock' mode='server'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' function='0x0'/> </interface>" when i execute virsh start domain_name command it starts and gets paused log shows it's stuck at n-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on QEMU waiting for connection on: disconnected:unix:/tmp/vhost1.sock,server is there anything i am missing? thank you in advance. -hardik-

1 0

[libvirt-users] Use virt-* tools from within container?
by Ken D'Ambrosio 28 Apr '16

28 Apr '16

Hi, all. I've set up an LXC container for various Openstack admin chores, and now I'm being asked to have it used for importing qcow2 images -- on which we want to run utilities like virt-sparsify and virt-sysprep, first. Sadly, when I do that, it dies horribly, e.g., root@openstack-cli:/tmp# virt-sysprep -a cloud-image.qcow2 Examining the guest ... libguestfs: warning: supermin-helper -f checksum returned a short string Fatal error: exception Guestfs.Error("cannot find any suitable libguestfs supermin, fixed or old-style appliance on LIBGUESTFS_PATH (search path: /usr/lib/guestfs)") Is there a way around this? Or is the answer, "Don't do that in a container"? Thanks! -Ken P.S. /usr/lib/guestfs -- the only part of the error I can easily look into -- has more stuff in it than the system that does process virt-* commands properly. Here's what's there: excludelist make.sh packagelist supermin.d

2 1

[libvirt-users] Networking issues with lxc containers in AWS EC2
by Peter Steele 27 Apr '16

27 Apr '16

I've created an EC2 AMI for AWS that essentially represents a CentOS 7 "hypervisor" image. I deploy instances of these in AWS and create an number of libvirt based lxc containers on each of these instances. The containers run fine within a single host and have no problem communicating with themselves as well as with their host, and vice versa. However, containers hosted in one EC2 instance cannot communicate with containers hosted in another EC2 instance. We've tried various tweaks with our Amazon VPC but have been unable to find a way to solve this networking issue. If I use something like VMware or KVM and create VMs using this same hypervisor image, the containers running under these VMs can communicate with with each other, even across different hosts. My real question is has anyone tried deploying EC2 images that host containers and have figured out how to successfully communicate between containers on different hosts? Peter

2 8

[libvirt-users] /proc/meminfo
by Peter Steele 26 Apr '16

26 Apr '16

Has anyone seen this issue? We're running containers under CentOS 7.2 and some of these containers are reporting incorrect memory allocation in /proc/meminfo. The output below comes from a system with 32G of memory and 84GB of swap. The values reported are completely wrong. # cat /proc/meminfo MemTotal: 9007199254740991 kB MemFree: 9007199224543267 kB MemAvailable: 12985680 kB Buffers: 0 kB Cached: 119744 kB SwapCached: 10804 kB Active: 110228 kB Inactive: 111716 kB Active(anon): 53840 kB Inactive(anon): 57568 kB Active(file): 56388 kB Inactive(file): 54148 kB Unevictable: 0 kB Mlocked: 15347728 kB SwapTotal: 0 kB SwapFree: 18446744073709524600 kB Dirty: 20304 kB Writeback: 99596 kB AnonPages: 18963368 kB Mapped: 231472 kB Shmem: 51852 kB Slab: 1891324 kB SReclaimable: 1805244 kB SUnreclaim: 86080 kB KernelStack: 60656 kB PageTables: 81948 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 104487760 kB Committed_AS: 31507444 kB VmallocTotal: 34359738367 kB VmallocUsed: 354796 kB VmallocChunk: 34359380456 kAnonHugePages: 15630336 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB DirectMap4k: 81684 kB DirectMap2M: 3031040 kB DirectMap1G: 32505856 kB

4 16

[libvirt-users] Managing VMs across multiple physical hosts
by Daniel Corbe 25 Apr '16

25 Apr '16

Hello List, We’re currently managing VMs across approximately 26 physical hosts. We tend to migrate VMs around a lot to do things like spread load and keep VMs running when physical hosts are in need of package updates. Suffice it to say sometimes finding out which physical host a VM is currently running on can be a pain. Anyone know of an open source tool that will give me a snapshot of what’s running where across a list of physical hosts? Doesn’t have to be anything fancy. A command-line utility will do. Best, Daniel

3 4

[libvirt-users] VM crash : Failed to terminate process X with SIGKILL: Device or resource busy
by Michel Villeneuve 22 Apr '16

22 Apr '16

Hello since I changed my hypervisor from centos 6.3 to Fedora-23 I had many problems with differents VMs. Very often once by day ( I have about 150 VM ), some VMs crash or freeze indifferently and I got messages like this on console. [<fffffffff8000a08bd>] wake_bit_funtion +0w0/0x23..... [<fffffffff8800a0ead>] :jbd:journal_get_write_access+0x22/0x33 ;;;; [<fffffffff800013ccd>] :ext3:ext3_dirty_inode+0x63/0x7b And so the VM is crashed and can't be accessed but often the ping command can respond Before my migration I never meet these problems, It 's strictly the same VMs between the 6.3 and fedora23 release. I just changed the parameter : <type arch='x86_64' machine='rhel-6.0.0'>hvm</type> to <type arch='x86_64' machine='pc-i440fx-2.4'>hvm</type> and do a virsh define I tried some other version of the parameters without success. and I also added a lockd manager in fedora23. Before and I used libvirt.0.9.5 or 1.0.2 on centos 6.03 without lockd A major problem with these crashs is that the VMs couldn't be destroyed by the virsh command, the qemu process is notified as defunct by the ps command If I try a virsh destroy I get in log file 2016-04-20 20:32:47.318+0000: 5541: info : virEventPollRunOnce:641 : EVENT_POLL_RUN: nhandles=11 timeout=-1 2016-04-20 20:32:55.028+0000: 5567: debug : virProcessKillPainfully:368 : Timed out waiting after SIGTERM to process 8720, sending SIGKILL 2016-04-20 20:33:00.032+0000: 5567: error : virProcessKillPainfully:398 : Failed to terminate process 8720 with SIGKILL: Périphérique ou ressource occupé or on console Failed to terminate process xxx with SIGTERM: Device or resource busy and the VM is still in the list in a "Stopping" state Result of ps ps on the the qemu process attached to the VM qemu 8720 1 0 avril20 ? 00:07:16 [qemu-system-x86] <defunct> root 8733 2 0 avril20 ? 00:00:01 [vhost-8720] root 8735 2 0 avril20 ? 00:00:00 [kvm-pit/8720] libvirtd seems to be in an anormal state. If I restart the libvirtd the virsh command just hang and never remove the VM from the list. The only seems to reboot the hypervisor but all the VMs in production too. Is there a way to remove the process qemu in defunct state without reboot the hypervisor. Perhaps the probleme come from the VM parameters which have been created on 6.3 Centos and libvirt <1.0 version. Do I need to convert some other parameters ? I 'am trying to put a new hypervisor in aFailed to terminate process X with SIGKILL: Device or resource busy version level less than fedora23 perhaps a Centos 7.2 to see what 's happen and if there is a problem like mine. Thanks PS: I put the log_level to 1 ----------------------information in logfile [root@kvmserver6 ~]# ls -al /var/lib/libvirt/qemu/domain-1-TEST-VM-A total 8 drwxr-x--- 2 qemu qemu 4096 20 avril 22:01 . drwxr-x--x. 18 qemu qemu 4096 20 avril 22:01 .. srwxrwxr-x 1 qemu qemu 0 20 avril 22:01 monitor.sock /var/lib/libvirt/qemu/channel/target/domain-1-TEST-VM-A/ [root@kvmserver6 ~]# cat /var/log/libvirt/qemu/TEST-VM-A.log 2016-04-20 20:01:36.714+0000: starting up libvirt version: 1.3.3, package: 1.fc23 (Unknown, 2016-04-06-15:17:39, thinkpad2), qemu version: 2.4.1 (qemu-2.4.1-8.fc23), hostname: kvmserver6.univ-brest.fr LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm -name TEST-VM-A,debug-threads=on -S -machine pc-i440fx-2.4,accel=kvm,usb=off -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 1e4c27e4-123e-719a-9fdf-f783d34cbb40 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-TEST-VM-A/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/libvirt/images/POOL_PROD4/TEST-VM-A.img,format=raw,if=none,id=drive-virtio-disk0 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-ide0-1-0,readonly=on -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=28 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:11:11,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 0.0.0.0:0,password -k fr -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device ES1370,id=sound0,bus=pci.0,addr=0x4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on char device redirected to /dev/pts/1 (label charserial0) qemu: terminating on signal 15 from pid 5541 -- Michel Villeneuve Tel 02 98 01 71 61

1 1

[libvirt-users] Mapping physical interface to a container
by Peter Steele 22 Apr '16

22 Apr '16

In the "other" LXC project (linuxcontainers.org) you can map a host's physical ethernet interface to a container, e.g. lxc.network.type = phys lxc.network.flags = up lxc.network.link = eth1 lxc.network.name = eth1 Is there an equivalent option for doing this with libvirt lxc? Peter

1 1