- Users - libvirt List Archives

[libvirt-users] How can I open a libvirt remote connection with ssh
by Wangkai (Kevin,C) 11 Apr '13

11 Apr '13

Hi, When I use 'virConnectOpenAuth' function to connect to '192.168.1.102' libvirtd with ssh, Code below, the screen print the dialog "root(a)192.168.1.102's password:" , and only After I type the password, the connection can be created. How can I connect to libvirtd with ssh automatically? No need to type the password manually. char *au[2] = {"root", "xxxx"}; virConnectAuth auth = { credTypes, sizeof(credTypes) / sizeof(int), virConnCb,/* callback function, actually was not be called after connect*/ au /* user and password */ }; conn = virConnectOpenAuth("qemu+ssh://192.168.1.102/system", &auth, 0); Thanks, Kevin

3 3

Re: [libvirt-users] fail to convert qemu xml to args with libvirt-1.0.4: An error occurred, but the cause is unknown
by Yin Olivia-R63875 11 Apr '13

11 Apr '13

Hi Daniel, Just Ping. Did you ever successfully convert QEMU xml file to argv on other platforms? Best Regards, Olivia > -----Original Message----- > From: Yin Olivia-R63875 > Sent: Tuesday, April 09, 2013 1:22 PM > To: 'libvir-list(a)redhat.com' > Cc: 'libvirt-users(a)redhat.com' > Subject: fail to convert qemu xml to args with libvirt-1.0.4: An error > occurred, but the cause is unknown > > Hi, > > I used to convert qemu XML to args with libvirt-1.0.3. > But it failed to convert with libvirt-1.0.4. > > # virsh domxml-to-native qemu-argv test.xml >test.sh > error: An error occurred, but the cause is unknown > > > Comparing the debug file as below: > 1) lbvirt-1.0.3 > <cut> > 2013-04-09 03:23:47.296+0000: 2669: debug : > virEventPollInterruptLocked:716 : Interrupting > 2013-04-09 03:23:47.296+0000: 2669: debug : virNetClientIO:1807 : All done > with our call head=(nil) call=0x100871c0 rv=0 > 2013-04-09 03:23:47.297+0000: 2670: debug : virEventPollRunOnce:640 : Poll > got 1 event(s) > 2013-04-09 03:23:47.297+0000: 2670: debug : > virEventPollDispatchTimeouts:425 : Dispatch 0 > 2013-04-09 03:23:47.297+0000: 2669: debug : virNetMessageFree:73 : > msg=0x10087500 nfds=0 cb=(nil) > 2013-04-09 03:23:47.297+0000: 2670: debug : > virEventPollDispatchHandles:470 : Dispatch 1 > 2013-04-09 03:23:47.297+0000: 2670: debug : > virEventPollDispatchHandles:484 : i=0 w=1 > 2013-04-09 03:23:47.297+0000: 2669: debug : virConnectClose:1483 : > conn=0x100878b8 <cut> > > 2) libvirt-1.0.4 > <cut> > 2013-04-09 03:07:58.012+0000: 2834: debug : > virEventPollInterruptLocked:716 : Interrupting > 2013-04-09 03:07:58.012+0000: 2834: debug : virNetClientIO:1810 : All done > with our call head=(nil) call=0x10089db8 rv=0 > 2013-04-09 03:07:58.012+0000: 2835: debug : virEventPollRunOnce:640 : Poll > got 1 event(s) > 2013-04-09 03:07:58.012+0000: 2835: debug : > virEventPollDispatchTimeouts:425 : Dispatch 0 > 2013-04-09 03:07:58.012+0000: 2834: error : > virNetClientProgramDispatchError:175 : An error occurred, but the cause is > unknown > 2013-04-09 03:07:58.012+0000: 2835: debug : > virEventPollDispatchHandles:470 : Dispatch 1 > 2013-04-09 03:07:58.012+0000: 2834: debug : virNetMessageFree:73 : > msg=0x1008a0f8 nfds=0 cb=(nil) > 2013-04-09 03:07:58.012+0000: 2835: debug : > virEventPollDispatchHandles:484 : i=0 w=1 > 2013-04-09 03:07:58.012+0000: 2835: debug : > virEventPollDispatchHandles:498 : EVENT_POLL_DISPATCH_HANDLE: watch=1 > events=1 > 2013-04-09 03:07:58.012+0000: 2835: debug : > virEventPollCleanupTimeouts:516 : Cleanup 0 > 2013-04-09 03:07:58.013+0000: 2835: debug : > virEventPollCleanupTimeouts:552 : Found 0 out of 0 timeout slots used, > releasing 0 > 2013-04-09 03:07:58.013+0000: 2835: debug : virEventPollCleanupHandles:564 : > Cleanup 2 > 2013-04-09 03:07:58.013+0000: 2834: debug : virConnectClose:1483 : > conn=0x1008a4b0 <cut> > > > How can I debug this cause unknown error? > > Best Regards, > Olivia

1 0

Re: [libvirt-users] [virt-tools-list] Debugging TLS connection between virt-viewer and libvirt running on separate hosts
by Cole Robinson 11 Apr '13

11 Apr '13

On 04/10/2013 10:47 AM, Will Dennis wrote: > Hi all, > > I’m running libvirt 1.0.4 on one host (Ubuntu 12.04), and > virt-manager/virt-viewer on another (FC18), and using TLS to secure the comm’s > between the hosts. I was able to get virt-manager to connect the the > hypervisor host via qemu+tls method, but virt-viewer will not connect (either > invoked from the “Show the graphical console” option on virt-manager’s VM > window, or by invoking virt-viewer directly.) Both fail with a generic error > (virt-manager’s view console says “viewer connection to hypervisor host got > refused or disconnected”) but does not give a more explicit error. I did a > tcpdump, and the trace does show the client machine connecting to TCP port > 16514 on the hypervisor host, which is owned by the libvirtd daemon. From what > I can see in the packets from that dump, it looks like the endpoints are > exchanging certificate info, but of course the session is encrypted, so can’t > really see what else is going on… Is there a way someone can give me to debug > the communications for either the client or server side? (There’s nothing > being written to logs as far as I can see.) CCing libvirt-users - Cole

1 0

[libvirt-users] performance tradeoffs/penalty
by lejeczek 10 Apr '13

10 Apr '13

hi everybody a newbie here, hoping some experienced users/expert can honestly answer this one question, and I think I realize all other advantages libvirtoffer but simply performance, does libvirt make a user pay penalty, even if only a small amount, for using it when compared to raw qemu-kvm command line? if it does where the overhead goes? quest or host, or maybe both? lastly if overall performance is slower then how small it is comparing to all the advantages it offers? many thanks and apologies if this subject was answered already in the past

2 1

[libvirt-users] when save the domain, the following errors occured
by Wangkai (Kevin,C) 10 Apr '13

10 Apr '13

Hi, I have create one vm by libvirt api, And I goto virsh, when I doing save the domain, the following errors occurred: virsh # save demo2 /home/wk/libvirt/demo2.save error: Failed to save domain demo2 to /home/wk/libvirt/demo2.save error: internal error unable to send file handle 'migrate': No file descriptor supplied via SCM_RIGHTS virsh # list Id Name State ---------------------------------------------------- 18 demo2 running What was the problem? I cannot find it. Thanks, Kevin.

2 3

[libvirt-users] Faulty manual?
by Daniele Testa 10 Apr '13

10 Apr '13

Hi, Look under examples: http://builder.virt-tools.org/artifacts/libvirt-virshcmdref/html/sect-attac… (root@h2)-(/)# virsh attach-disk vps_99 /dev/nbd2 vdb --address pci:0000.00.11.0 --persistent *error: command 'attach-disk' doesn't support option --address* (root@h2)-(/)# virsh --version 0.7.5 Is someone playing a trick on me? Regards, Daniele

2 2

[libvirt-users] can remote libvirt applications make non-blocking API calls
by arvind viswanathan 10 Apr '13

10 Apr '13

Hi, I wanted to check if event loop integration was supported even for remote applications using libvirt. My application would like to make non-blocking calls and also recv asynchronous notification remotely. Can some one point out if its supported. thanks Arvind

2 1

[libvirt-users] (no subject)
by arvind viswanathan 10 Apr '13

10 Apr '13

I wanted to check if event loop integration was supported even for remote applications using libvirt. My application would like to make non-blocking calls and also recv asynchronous notification remotely. Can some one point out if its supported. thanks

2 1

[libvirt-users] Filesystem passthrough of a Lustre mounted directory
by Tatiana Kichkaylo 10 Apr '13

10 Apr '13

Hi, I am trying to pass a Lustre directory mounted on the host to the guest. I can pass a local directory in just fine when starting an instance via virsh. I can execute the qemu command from libvirt's logs (dropping –S flag) directly, and passing the Lustre mounted directory also works (but the network complains about different MAC address). However, when I start an instance using virsh, the mount inside the guest succeeds, and ls works sometimes, but everything else (cat, touch, actual edit) on any file in the mounted directory gives "Identifier removed" after some delay. Is libvirt doing something beyond just calling qemu that can cause this problem? And how do I get around it? The host is RedHat 6.1, libvirt 1.0.3, qemu 1.4.50. Thanks, Tatiana The command pulled out from the libvirt's log: LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none \ /usr/local/bin/qemu-system-x86_64 \ -name i3e -M pc-0.14 -S \ -cpu SandyBridge,+pdpe1gb,+osxsave,+dca,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme \ -enable-kvm -m 2048 -smp 1,sockets=1,cores=1,threads=1 \ -uuid ccc66436-8535-472e-8397-eee52d01cffe -no-user-config -nodefaults \ -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/i3e.monitor,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew \ -no-kvm-pit-reinjection -no-shutdown -kernel /var/lib/nova/instances/instance-0000003d/kernel \ -initrd /var/lib/nova/instances/instance-0000003d/ramdisk \ -append root=/dev/vda \ -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ -drive file=/var/lib/nova/instances/instance-0000003d/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none \ -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 \ -fsdev local,security_model=passthrough,id=fsdev-fs0,path=/mnt/lustre/ \ -device virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=testfs,bus=pci.0,addr=0x3 \ -chardev file,id=charserial0,path=/var/lib/nova/instances/instance-0000003d/console.log \ -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 \ -device isa-serial,chardev=charserial1,id=serial1 -device usb-tablet,id=input0 \ -netdev tap,fd=30,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=fa:16:3e:39:23:6f,bus=pci.0,addr=0x4 \ -vnc 127.0.0.1:3 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6

1 0

[libvirt-users] Problem with net-define using Open vSwitch bridge
by Will Dennis 10 Apr '13

10 Apr '13

Hi all, I used "net-define" to create a network to use to attach VMs to an Open vSwitch bridge. The net-define worked fine, I can see the network in "net-list" (I set it to started and to autostart) but when I try to attach a new VM's NIC to this network (via virt-manager), I'm getting the following traceback: Unable to complete install: 'Unable to add bridge vl10-ovsbr0 port vnet0: Operation not supported' 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/create.py", line 1943, in do_install guest.start_install(False, meter=meter) File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1249, in start_install noboot) File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1317, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2606, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: Unable to add bridge vl10-ovsbr0 port vnet0: Operation not supported I'm going to assume the problem is that the bridge is not a linux bridge, but an Open vSwitch bridge. But I did have a line in the XML file that I used for net-define as follows: <virtualport type='openvswitch'/> But when I ran net-define, it failed to create the network with the error: XML error: unexpected virtualport type -1 Removing that line and re-running the net-define worked, as I have stated above. How do I tell libvirt that this bridge is an Open vSwitch bridge and not a regular Linux bridge? Thanks, Will

2 7