- Users - libvirt List Archives

[libvirt-users] Whether Virsh migrate VM works with xen hypervisor??
by Ajitha Robert 20 Nov '14

20 Nov '14

Hi all By referring https://libvirt.org/migration.html.. I tried VM migration between two libvirt machines I tried instance migration with ssh, tls and tcp. In all three I got the same error as " this function is not supported by the connection driver" *Eg* migrate --live domuname xen+tls://desthostname/system error: this function is not supported by the connection driver: virDomainMigrate3 My question is Whether live migration is supported with Xen hypervisor. -- *Regards,Ajitha R*

1 0

[libvirt-users] Connecting libvirt remotely using tls: TLS handshake failed : packet with unexpected length +gnutls_handhsake Error
by Ajitha Robert 19 Nov '14

19 Nov '14

Hi all, I am facing an error while connecting libvirt remotely using tls.. I have created CA, client and server certificates with RSA 1024 bit using Openssl. I am using debian linux flavor in both client and server. *Original Error:* (When trying to connect remote libvirt) virsh -c xen+tls://destinationipaddr/system error: failed to connect to the hypervisor error: authentication failed: TLS handshake failed A TLS packet with unexpected length was received. In source code i found the error line. the return value is 21 ./src/rpc/virnettlscontext.c: ret = gnutls_handshake(sess->session); *Below are log details* *client(Initiator of ssl connection ) :* virNetTLSSessionHandshake:1351 : Ret=-21 error: authentication failed: TLS handshake failed A TLS packet with unexpected length was received. *In the server side, * virNetTLSSessionHandshake:1369 : authentication failed: TLS handshake failed Could not negotiate a supported cipher suite. Please guide me for solving this error -- *Regards,Ajitha R*

2 2

[libvirt-users] Unable to start container after OS upgrade
by mallu mallu 18 Nov '14

18 Nov '14

I upgraded my container from CentOS 6.4 to CentOS 6.5. Everything looks good after upgrade until reboot. When rebooted to container I'm getting the following errors.. Any help would be greatly appreciated /bin/mknod: `/dev/lp2': Operation not permitted /bin/chown: cannot access `/dev/lp2': No such file or directory /bin/mknod: `/dev/lp3': Operation not permitted /bin/chown: cannot access `/dev/lp3': No such file or directory /bin/mknod: `/dev/net/tun': Operation not permitted /bin/mknod: `/dev/ppp': Operation not permitted /bin/mknod: `/dev/fuse': Operation not permitted /sbin/start_udev: line 269: /proc/sys/kernel/hotplug: Read-only file system udevd[71]: file_contexts: invalid context system_u:object_r:device_t:s0 udevd[71]: file_contexts: invalid context system_u:object_r:device_t:s0 udevd[71]: matchpathcon(/dev/.udev/rules.d) failed udevd[71]: matchpathcon(/dev/.udev/rules.d) failed [ OK ] Setting hostname vm1292ussac1-goagent1.cust.aops-eds.com: [ OK ] Checking filesystems [ OK ] mount: can't find / in /etc/fstab or /etc/mtab Mounting local filesystems: [ OK ] /etc/rc.d/rc.sysinit: line 606: plymouth: command not found Enabling /etc/fstab swaps: [ OK ] init: kexec-disable main process (139) terminated with status 1

2 2

[libvirt-users] Changing 'source file' on running VM.
by mathew.moon＠vipaar.com 18 Nov '14

18 Nov '14

2 1

[libvirt-users] Problem with the use of domfsfreeze mountpoint option
by Payes Anand 17 Nov '14

17 Nov '14

Hi everybody, I am having a problem with the use of domfsfreeze command. It is freezing all the filesystems present on the domain, instead of freezing just the mountpoints provided. I am issuing the command-- # virsh domfsfreeze <domain> --mountpoint <mountpoint> Output was-- Froze 3 filesystem(s) I want to freeze a particular mount point on the VM, so that i can take a snapshot using my own snapshot feature. Using library: libvirt 1.2.5 Using API: QEMU 1.2.5 Running hypervisor: QEMU 2.0.0 --Upgraded libvirt to 1.2.10, but that also didn't solve the problem. Am i missing something over here? Any help would be greatly appreciated. Best Regards, Payes

5 8

[libvirt-users] Do not attempt to add physical NIC to virbr0
by Sagar Shedge 17 Nov '14

17 Nov '14

Hi, I got this NOTE on most of the link. But I am not getting reason for this. Why someone should not add physical NIC to virbr0. I tried to add my eth1 to virbr0 and it get added. So whether it affects to some functionality of NAT network? -- Sagar Dilip Shedge, Pune. With Regards.

2 2

[libvirt-users] Suspend Domain (virsh suspend) or Freeze Filesystems (virsh domfsfreze) to take Snapshot of ISCSI volume
by Payes Anand 16 Nov '14

16 Nov '14

Hi everybody, I am trying to take snapshot of a particular iscsi disk mounted inside the guest operating system. I have created my own snapshot feature for that. Could someone please suggest the better choice for stopping read/write operations on disk out of the two to take snapshots, or if you have any better solution, 1) freeze filesystems ( using domfsfreeze ) and then take the snapshot or, 2) suspend the VM ( using virsh suspend ) and then take the snapshot And, before taking the snapshots what other operations should i perform ( like sync or flush buffer ) for a consistent snapshot. Any help would be greatly appreciated. Best Regards, Payes

1 0

[libvirt-users] Trouble creating virtio-serial device
by David Richardson 14 Nov '14

14 Nov '14

Hello, I've running Ubuntu-14.04 as my host and my guest. I've been trying to get guest to host communication set up by configuring a virtio-serial device. My xml file contains: <channel type='unix'> <source mode='bind' path='/home/dave/vm1.agent'/> <target type='virtio' name='vm1'/> </channel> When I start up the VM, I get the following error: error: Failed to create domain from vm1.xml error: internal error: process exited while connecting to monitor: qemu-system-x86_64: -chardev socket,id=charchannel0,path=/home/dave/vm1.agent,server,nowait: Failed to bind socket: Permission denied qemu-system-x86_64: -chardev socket,id=charchannel0,path=/home/dave/vm1.agent,server,nowait: chardev: opening backend "socket" failed dmesg shows what appears to be an apparmor denial for mknod: [250108.632450] type=1400 audit(1415994657.679:152): apparmor="DENIED" operation="mknod" profile="libvirt-2fd2ec54-f644-228e-08ba-297c8b304153" name="/home/dave/vm1.agent" pid=21856 comm="qemu-system-x86" requested_mask="c" denied_mask="c" fsuid=112 ouid=112 I can add a line to /etc/apparmor.d/abstractions/libvirt-qemu similar to: owner /home/dave/vm1.agent rw, After restarting apparmor, this gets rid of the apparmor complaint, but I still get the same error from 'virsh create vm1.xml' when trying to create the VM. Any suggestions for how to fix this? Thanks, ~Dave

1 0

[libvirt-users] hostdev a Xeon Phi
by lejeczek 14 Nov '14

14 Nov '14

hi everybody I'd like to ask around if Xeon Phis are any good for passthrough? Are there any plans for near future or maybe there are already some success stories using this product? many thanks, P.

1 0

[libvirt-users] Is there a way to disable libvirt qemu monitor while creating kvm vm using virsh?
by Min Du 12 Nov '14

12 Nov '14

Hi, Now for some reason, I need to add “ -qmp tcp:127.0.0.1:1235” when creating a KVM VM using libvirt. This command meaning in “qemu-kvm --help” is: -qmp dev like -monitor but opens in 'control' mode. I added command-line equivalent options into the xml file, like below format: <qemu:commandline> <qemu:arg value="-s"/> <qemu:arg value="-qmp"/> <qemu:arg value="tcp:127.0.0.1:1235"/> </qemu:commandline> However when I create VM using this xml file, I got the error: # virsh create instance-libvirt.xml error: Failed to create domain from instance-libvirt.xml error: internal error process exited while connecting to monitor: qemu-kvm: -qmp tcp:127.0.0.1:1235: Duplicate ID 'monitor' for mon duplicate chardev: monitor The VM I created, without “—qmp” option, has below options showing in “ps aux | grep qemu-kvm”: -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/vmifs_test.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control Looks like libvirt automatically adds the monitor options upon VM creation. Is there a way to disable this and use “—qmp” instead when creating VM? Thanks for your help. Best Regards, Min

4 6