- Users - libvirt List Archives

[libvirt-users] Accessing libvirtd from multiple agents
by arvind viswanathan 12 Apr '13

12 Apr '13

Hi, I was wondering if multiple remote agents can access the same libvirtd. How do we prevent conflicting commands from the different agents. Can different access permission be set for the agents? (The documentation usually goes over the case where one agent can access multiple libvirtd and not this case) Thanks Arvind

4 4

[libvirt-users] virtio_ioport_write: unexpected address
by denghuancong 12 Apr '13

12 Apr '13

the guest is normally running, but the qemu log is printing the following message: what happen? thanks a lot. virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0

1 0

[libvirt-users] virtio_ioport_write: unexpected address
by denghuancong 12 Apr '13

12 Apr '13

the guest is normally running, but the qemu log is printing the following message: what happen? thanks a lot. virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0 virtio_ioport_write: unexpected address 0x13 value 0x0

1 0

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 12 Apr '13

12 Apr '13

Hi Daniel, I also tried libvirt-1.0.4 on my X86 machine. user@x86:~ $ uname -a Linux 2.6.32-33-server #70-Ubuntu SMP Thu Jul 7 22:28:30 UTC 2011 x86_64 GNU/Linux user@x86:~ $ which virsh /usr/local/bin/virsh user@x86:~ $ /usr/local/bin/virsh --version 1.0.4 user@x86:~ $ cd libvirt-1.0.4/tests/qemuxml2argvdata user@x86:~/libvirt-1.0.4/tests/qemuxml2argvdata $ virsh domxml-to-native qemu-argv qemuxml2argv-disk-virtio.xml >1.dom error：An error occurred, but the cause is unknown Best Regards, Olivia > -----Original Message----- > From: Yin Olivia-R63875 > Sent: Thursday, April 11, 2013 10:18 AM > To: 'Daniel P. Berrange' > Cc: 'libvirt-users(a)redhat.com'; 'libvir-list(a)redhat.com' > Subject: RE: fail to convert qemu xml to args with libvirt-1.0.4: An error > occurred, but the cause is unknown > > 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

[libvirt-users] reboot command lost
by 邓焕聪 12 Apr '13

12 Apr '13

when i send a reboot command to libvirtd to reboot a domain, it does not receive and print the following warn:2013-04-10 06:01:39.080+0000: 2908: warning : qemuDomainObjTaint:1311 : Domain id=56 name='69751ca7-3198-4f3c-8265-cb8cb70ad750' uuid=69751ca7-3198-4f3c-8265-cb8cb70ad750 is tainted: high-privileges what's the problem??? thanks a lot. > From: libvirt-users-request(a)redhat.com > Subject: libvirt-users Digest, Vol 40, Issue 24 > To: libvirt-users(a)redhat.com > Date: Wed, 10 Apr 2013 12:00:18 -0400 > > Send libvirt-users mailing list submissions to > libvirt-users(a)redhat.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/libvirt-users > or, via email, send a message with subject or body 'help' to > libvirt-users-request(a)redhat.com > > You can reach the person managing the list at > libvirt-users-owner(a)redhat.com > When replying, please edit your Subject line so it is more specific > than "Re: Contents of libvirt-users digest..." > > > Today's Topics: > > 1. performance tradeoffs/penalty (lejeczek) > 2. Re: performance tradeoffs/penalty (Felicitus) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 10 Apr 2013 13:02:19 +0100 > From: lejeczek <peljasz(a)yahoo.co.uk> > To: libvirt-users(a)redhat.com > Subject: [libvirt-users] performance tradeoffs/penalty > Message-ID: <516554CB.2000703(a)yahoo.co.uk> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > 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 > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <https://www.redhat.com/archives/libvirt-users/attachments/20130410/6183c314…> > > ------------------------------ > > Message: 2 > Date: Wed, 10 Apr 2013 14:45:02 +0200 > From: Felicitus <felicitus(a)felicitus.org> > To: libvirt-users(a)redhat.com > Subject: Re: [libvirt-users] performance tradeoffs/penalty > Message-ID: <51655ECE.20503(a)felicitus.org> > Content-Type: text/plain; charset=ISO-8859-1 > > > does libvirt make a user pay penalty, even if only a small amount, for > > using it when compared to raw qemu-kvm command line? > > Not that I know of, except that the libvirt daemon uses a few additional > CPU cycles. Technically yes, in the spirit of the question no. Have a > look at your process tree; you'll see command lines in the same way as > you'd expect them to be when you start machines manually. > > > if it does where the overhead goes? quest or host, or maybe both? > > No additional CPU cycles for the guest, a few additional CPU cycles for > the host to get status information and expose it via the daemon. > > > if overall performance is slower then how small it is comparing to all > > the advantages it offers? > > It is completely negligible. > > Felicitus > > > > ------------------------------ > > _______________________________________________ > libvirt-users mailing list > libvirt-users(a)redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users > > End of libvirt-users Digest, Vol 40, Issue 24 > *********************************************

3 2

Re: [libvirt-users] reboot command lost?
by denghuancong 12 Apr '13

12 Apr '13

how do i check the mode of my system used, and how do i change it?how do i check whether to install the acpid?thanks. > From: libvirt-users-request(a)redhat.com > Subject: libvirt-users Digest, Vol 40, Issue 26 > To: libvirt-users(a)redhat.com > Date: Thu, 11 Apr 2013 07:34:17 -0400 > > Send libvirt-users mailing list submissions to > libvirt-users(a)redhat.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/libvirt-users > or, via email, send a message with subject or body 'help' to > libvirt-users-request(a)redhat.com > > You can reach the person managing the list at > libvirt-users-owner(a)redhat.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of libvirt-users digest..." > > > Today's Topics: > > 1. How can I open a libvirt remote connection with ssh > (Wangkai (Kevin,C)) > 2. Re: How can I open a libvirt remote connection with ssh > (Daniel P. Berrange) > 3. Re: How can I open a libvirt remote connection with ssh > (Wangkai (Kevin,C)) > 4. Re: How can I open a libvirt remote connection with ssh > (Henrik Ahlgren) > 5. Re: reboot command lost? (Michal Privoznik) > 6. Re: virt-install on powerpc64 issues (Martin Kletzander) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 11 Apr 2013 09:45:18 +0000 > From: "Wangkai (Kevin,C)" <wangkai86(a)huawei.com> > To: "libvirt-users(a)redhat.com" <libvirt-users(a)redhat.com> > Subject: [libvirt-users] How can I open a libvirt remote connection > with ssh > Message-ID: > <87B246BB5ED53A4C98E4F9A35839EDE128F1136D(a)nkgeml506-mbs.china.huawei.com> > > Content-Type: text/plain; charset="us-ascii" > > 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 > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <https://www.redhat.com/archives/libvirt-users/attachments/20130411/10a9246b…> > > ------------------------------ > > Message: 2 > Date: Thu, 11 Apr 2013 10:54:36 +0100 > From: "Daniel P. Berrange" <berrange(a)redhat.com> > To: "Wangkai (Kevin,C)" <wangkai86(a)huawei.com> > Cc: "libvirt-users(a)redhat.com" <libvirt-users(a)redhat.com> > Subject: Re: [libvirt-users] How can I open a libvirt remote > connection with ssh > Message-ID: <20130411095436.GF29791(a)redhat.com> > Content-Type: text/plain; charset=utf-8 > > On Thu, Apr 11, 2013 at 09:45:18AM +0000, Wangkai (Kevin,C) wrote: > > 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. > > Libvirt has to spawn an external SSH process for +ssh URIs, so we can't hook > it up into our auth callbacks. > > > How can I connect to libvirtd with ssh automatically? No need to type the password manually. > > You need to setup SSH public keys + SSH agent > > > > > 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); > > virConnectOpenAuth() doesn't do anything useful for '+ssh' URIs. > > There is however a alternative 'libssh2' URI that does use the > callbacks. eg qemu+libssh2://hostname/system > > This is less tested & potentially buggy, but it might be ok for your needs > > Regards, > Daniel > -- > |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| > |: http://libvirt.org -o- http://virt-manager.org :| > |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| > |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| > > > > ------------------------------ > > Message: 3 > Date: Thu, 11 Apr 2013 09:59:46 +0000 > From: "Wangkai (Kevin,C)" <wangkai86(a)huawei.com> > To: "Daniel P. Berrange" <berrange(a)redhat.com> > Cc: "libvirt-users(a)redhat.com" <libvirt-users(a)redhat.com> > Subject: Re: [libvirt-users] How can I open a libvirt remote > connection with ssh > Message-ID: > <87B246BB5ED53A4C98E4F9A35839EDE128F11384(a)nkgeml506-mbs.china.huawei.com> > > Content-Type: text/plain; charset="utf-8" > > > > > -----Original Message----- > > From: Daniel P. Berrange [mailto:berrange@redhat.com] > > Sent: Thursday, April 11, 2013 5:55 PM > > To: Wangkai (Kevin,C) > > Cc: libvirt-users(a)redhat.com > > Subject: Re: [libvirt-users] How can I open a libvirt remote connection > > with ssh > > > > On Thu, Apr 11, 2013 at 09:45:18AM +0000, Wangkai (Kevin,C) wrote: > > > 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. > > > > Libvirt has to spawn an external SSH process for +ssh URIs, so we can't > > hook > > it up into our auth callbacks. > > [Wangkai (Kevin,C)] > Which type of URI can be hooked by auth callback? Qemu+tls? > > > > > > How can I connect to libvirtd with ssh automatically? No need to type > > the password manually. > > > > You need to setup SSH public keys + SSH agent > [Wangkai (Kevin,C)] > Maybe I will try this later. > > > > > > > > > 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); > > > > virConnectOpenAuth() doesn't do anything useful for '+ssh' URIs. > > > > There is however a alternative 'libssh2' URI that does use the > > callbacks. eg qemu+libssh2://hostname/system > > > > This is less tested & potentially buggy, but it might be ok for your > > needs > > > > Regards, > > Daniel > > -- > > |: http://berrange.com -o- > > http://www.flickr.com/photos/dberrange/ :| > > |: http://libvirt.org -o- http://virt- > > manager.org :| > > |: http://autobuild.org -o- > > http://search.cpan.org/~danberr/ :| > > |: http://entangle-photo.org -o- http://live.gnome.org/gtk- > > vnc :| > > > > ------------------------------ > > Message: 4 > Date: Thu, 11 Apr 2013 13:01:45 +0300 > From: Henrik Ahlgren <pablo(a)seestieto.com> > To: "Wangkai (Kevin,C)" <wangkai86(a)huawei.com> > Cc: "libvirt-users(a)redhat.com" <libvirt-users(a)redhat.com> > Subject: Re: [libvirt-users] How can I open a libvirt remote > connection with ssh > Message-ID: <20130411100144.GL17558(a)seestieto.com> > Content-Type: text/plain; charset=us-ascii > > On Thu, Apr 11, 2013 at 09:45:18AM +0000, Wangkai (Kevin,C) wrote: > > > > How can I connect to libvirtd with ssh automatically? No need to type the password manually. > > Just use SSH public key authentication with an empty passphrase, just > as you would with any other automated SSH connection. > > > > ------------------------------ > > Message: 5 > Date: Thu, 11 Apr 2013 13:06:06 +0200 > From: Michal Privoznik <mprivozn(a)redhat.com> > To: ??? <dhc3(a)hotmail.com> > Cc: "libvirt-users(a)redhat.com" <libvirt-users(a)redhat.com> > Subject: Re: [libvirt-users] reboot command lost? > Message-ID: <5166991E.1020300(a)redhat.com> > Content-Type: text/plain; charset=UTF-8 > > On 11.04.2013 10:04, ??? wrote: > > when i send a reboot command to libvirtd to reboot a domain, it does not > > receive and print the following warn: > > > > 2013-04-10 06:01:39.080+0000: 2908: warning : qemuDomainObjTaint:1311 : > > Domain id=56 name='69751ca7-3198-4f3c-8265-cb8cb70ad750' > > uuid=69751ca7-3198-4f3c-8265-cb8cb70ad750 is tainted: high-privileges > > > > with reboot you may choose what mode do you want to use: > 'acpi', 'agent', 'initctl' or 'signal' > > By default, ACPI is used, meaning an ACPI event is send to the guest. > However, when there is no acpid running, this event is silently ignored. > So you have two options: > > 1) install acpid into the guest > > 2) use a different method. > > Michal > > > > ------------------------------ > > Message: 6 > Date: Thu, 11 Apr 2013 13:34:13 +0200 > From: Martin Kletzander <mkletzan(a)redhat.com> > To: Alexey Kardashevskiy <aik(a)ozlabs.ru> > Cc: libvirt-users(a)redhat.com > Subject: Re: [libvirt-users] virt-install on powerpc64 issues > Message-ID: <51669FB5.4030600(a)redhat.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On 04/10/2013 07:15 AM, Alexey Kardashevskiy wrote: > > Hi! > > > > I am trying to setup a guest using virt-install script: > > > > /usr/bin/virt-install -n fc18guest5 -r 1024 \ > > --disk path=/home/aik/virtimg/fc18guest,size=8 \ > > -c /home/aik/virtimg/Fedora-18-ppc64-DVD.iso \ > > --video vga --arch=ppc64 -d --machine=pseries > > > > And it fails. I could not find any relevant log in /var/log/libvirt/ so > > It should be stored in '/var/log/libvirt/qemu/fc18guest5.log'. If > there's nothing related, look for errors in '/var/log/libvirt/libvirtd.log'. > > > I simply hacked /usr/local/bin/qemu-system-ppc64 to print all the > > parameters passed into it. So I got the command line (below, after the > > second question) where the "-device scsi-cd" parameter is cut in a > > middle so QEMU fails to start. 788 chars long - is there a limit? > > > > I don't think it has anything to do with the fact that there is a > newline between '-device' and 'scsi-cd'. That's just debug output of > virt-install. > > > The second question is - where does virt-install store those xmls? I > > have to choose a new name for a machine even if virt-install failed, in > > the example it is "fc18guest5" (5 at the end). "virsh -c qemu:///system > > list" prints an empty list with no domains. > > > > Command 'virsh list' (by default) lists only running domains, try adding > '--all' as a parameter. > > > > > Thanks! > > > > > > > > > > /usr/local/bin/qemu-system-ppc64 -name fc18guest5 -S -M pseries > > -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -uuid > > 71f8b17f-ca48-80fe-db58-4d933c66fe2d -no-user-config -nodefaults > > -chardev > > socket,id=charmonitor,path=/home/aik/.config/libvirt/qemu/lib/fc18guest5.monitor,server,nowait > > -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc > > -no-reboot -no-shutdown -device pci-ohci,id=usb,bus=pci,addr=0x1.0x2 > > -device spapr-vscsi,id=scsi0,reg=0x2000 -drive > > file=/home/aik/virtimg/fc18guest,if=none,id=drive-scsi0-0-0-0,format=raw > > -device > > scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2 > > -drive > > file=/home/aik/virtimg/Fedora-18-ppc64-DVD.iso,if=none,id=drive-scsi0-0-0-1,readonly=on,format=raw > > -device scsi-cd,bus=scsi0.0,ch > > > > > > > > The full log is here: > > > > > > [aik@vpl2 ~]$ ./start_installation.sh > > ++ /usr/bin/virt-install -n fc18guest5 -r 1024 --disk > > path=/home/aik/virtimg/fc18guest,size=8 -c > > /home/aik/virtimg/Fedora-18-ppc64-DVD.iso --video vga --arch=ppc64 -d > > --machine=pseries > > [Wed, 10 Apr 2013 15:06:10 virt-install 9880] DEBUG (cli:221) Launched > > with command line: > > /usr/bin/virt-install -n fc18guest5 -r 1024 --disk > > path=/home/aik/virtimg/fc18guest,size=8 -c > > /home/aik/virtimg/Fedora-18-ppc64-DVD.iso --video vga --arch=ppc64 -d > > --machine=pseries > > [Wed, 10 Apr 2013 15:06:10 virt-install 9880] DEBUG (cli:326) Requesting > > libvirt URI default > > [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (cli:328) Received > > libvirt URI qemu:///session > > [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (virt-install:259) > > Requesting virt method 'default', hv type 'default'. > > [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (virt-install:469) > > Received virt method 'hvm' > > [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (virt-install:470) > > Hypervisor name is 'kvm' > > [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (cli:935) DISPLAY is > > set: graphics defaulting to VNC. > > [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (cli:953) --graphics > > compat generated: vnc > > [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG > > (DistroInstaller:209) DistroInstaller location is a local file/path: > > /home/aik/virtimg/Fedora-18-ppc64-DVD.iso > > [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (virt-install:626) > > Guest.has_install_phase: True > > > > Starting install... > > [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (Guest:1296) > > Generated install XML: > > <domain type='kvm'> > > <name>fc18guest5</name> > > <uuid>56b64ac6-9596-6e8e-5321-4fc583960065</uuid> > > <memory>1048576</memory> > > <currentMemory>1048576</currentMemory> > > <vcpu>1</vcpu> > > <os> > > <type arch='ppc64' machine='pseries'>hvm</type> > > <boot dev='cdrom'/> > > <boot dev='hd'/> > > </os> > > <features> > > <acpi/><apic/><pae/> > > </features> > > <clock offset="utc"/> > > <on_poweroff>destroy</on_poweroff> > > <on_reboot>destroy</on_reboot> > > <on_crash>destroy</on_crash> > > <devices> > > <emulator>/usr/local/bin/qemu-system-ppc64</emulator> > > <disk type='file' device='disk'> > > <driver name='qemu'/> > > <source file='/home/aik/virtimg/fc18guest'/> > > <target dev='sda' bus='scsi'/> > > </disk> > > <disk type='file' device='cdrom'> > > <driver name='qemu'/> > > <source file='/home/aik/virtimg/Fedora-18-ppc64-DVD.iso'/> > > <target dev='sdb' bus='scsi'/> > > <readonly/> > > </disk> > > <interface type='user'> > > <mac address='52:54:00:ca:ed:7a'/> > > </interface> > > <input type='mouse' bus='ps2'/> > > <graphics type='vnc' port='-1'/> > > <console type='pty'/> > > <video> > > <model type='vga'/> > > </video> > > </devices> > > </domain> > > > > [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (Guest:1297) > > Generated boot XML: > > <domain type='kvm'> > > <name>fc18guest5</name> > > <uuid>56b64ac6-9596-6e8e-5321-4fc583960065</uuid> > > <memory>1048576</memory> > > <currentMemory>1048576</currentMemory> > > <vcpu>1</vcpu> > > <os> > > <type arch='ppc64' machine='pseries'>hvm</type> > > <boot dev='hd'/> > > </os> > > <features> > > <acpi/><apic/><pae/> > > </features> > > <clock offset="utc"/> > > <on_poweroff>destroy</on_poweroff> > > <on_reboot>restart</on_reboot> > > <on_crash>restart</on_crash> > > <devices> > > <emulator>/usr/local/bin/qemu-system-ppc64</emulator> > > <disk type='file' device='disk'> > > <driver name='qemu'/> > > <source file='/home/aik/virtimg/fc18guest'/> > > <target dev='sda' bus='scsi'/> > > </disk> > > <disk type='block' device='cdrom'> > > <target dev='sdb' bus='scsi'/> > > <readonly/> > > </disk> > > <interface type='user'> > > <mac address='52:54:00:ca:ed:7a'/> > > </interface> > > <input type='mouse' bus='ps2'/> > > <graphics type='vnc' port='-1'/> > > <console type='pty'/> > > <video> > > <model type='vga'/> > > </video> > > </devices> > > </domain> > > > > [Wed, 10 Apr 2013 15:06:12 virt-install 9880] ERROR (cli:439) internal > > error process exited while connecting to monitor: char device redirected > > to /dev/pts/4 (label charserial0) > > > > > > > > [0]/usr/local/bin/qemu-system-ppc64 [1]-name [2]fc18guest5 [3]-S [4]-M > > [5]pseries [6]-enable-kvm [7]-m [8]1024 [9]-smp > > [10]1,sockets=1,cores=1,threads=1 [11]-uuid > > [12]56b64ac6-9596-6e8e-5321-4fc583960065 [13]-no-user-config > > [14]-nodefaults [15]-chardev > > [16]socket,id=charmonitor,path=/home/aik/.config/libvirt/qemu/lib/fc18guest5.monitor,server,nowait > > [17]-mon [18]chardev=charmonitor,id=monitor,mode=control [19]-rtc > > [20]base=utc [21]-no-reboot [22]-no-shutdown [23]-device > > [24]pci-ohci,id=usb,bus=pci,addr=0x1.0x2 [25]-device > > [26]spapr-vscsi,id=scsi0,reg=0x2000 [27]-drive > > [28]file=/home/aik/virtimg/fc18guest,if=none,id=drive-scsi0-0-0-0,format=raw > > [29]-device > > [30]scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2 > > [31]-drive > > [32]file=/home/aik/virtimg/Fedora-18-ppc64-DVD.iso,if=none,id=drive-scsi0-0-0-1,readonly=on,format=raw > > [33]-device [34]scsi-cd,bus=scsi0.0,ch > > [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (cli:442) > > Traceback (most recent call last): > > File "/usr/bin/virt-install", line 636, in start_install > > noboot=options.noreboot) > > 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 2775, in > > createLinux > > if ret is None:raise libvirtError('virDomainCreateLinux() failed', > > conn=self) > > libvirtError: internal error process exited while connecting to monitor: > > char device redirected to /dev/pts/4 (label charserial0) > > > > > > > > [0]/usr/local/bin/qemu-system-ppc64 [1]-name [2]fc18guest5 [3]-S [4]-M > > [5]pseries [6]-enable-kvm [7]-m [8]1024 [9]-smp > > [10]1,sockets=1,cores=1,threads=1 [11]-uuid > > [12]56b64ac6-9596-6e8e-5321-4fc583960065 [13]-no-user-config > > [14]-nodefaults [15]-chardev > > [16]socket,id=charmonitor,path=/home/aik/.config/libvirt/qemu/lib/fc18guest5.monitor,server,nowait > > [17]-mon [18]chardev=charmonitor,id=monitor,mode=control [19]-rtc > > [20]base=utc [21]-no-reboot [22]-no-shutdown [23]-device > > [24]pci-ohci,id=usb,bus=pci,addr=0x1.0x2 [25]-device > > [26]spapr-vscsi,id=scsi0,reg=0x2000 [27]-drive > > [28]file=/home/aik/virtimg/fc18guest,if=none,id=drive-scsi0-0-0-0,format=raw > > [29]-device > > [30]scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2 > > [31]-drive > > [32]file=/home/aik/virtimg/Fedora-18-ppc64-DVD.iso,if=none,id=drive-scsi0-0-0-1,readonly=on,format=raw > > [33]-device [34]scsi-cd,bus=scsi0.0,ch > > [Wed, 10 Apr 2013 15:06:12 virt-install 9880] DEBUG (cli:451) Domain > > installation does not appear to have been successful. > > If it was, you can restart your domain by running: > > virsh --connect qemu:///session start fc18guest5 > > otherwise, please restart your installation. > > Domain installation does not appear to have been successful. > > If it was, you can restart your domain by running: > > virsh --connect qemu:///session start fc18guest5 > > otherwise, please restart your installation. > > > > [aik@vpl2 ~]$ virsh -c qemu:///system list > > Id Name State > > ---------------------------------------------------- > > > > [aik@vpl2 ~]$ > > > > > > > > ------------------------------ > > _______________________________________________ > libvirt-users mailing list > libvirt-users(a)redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users > > End of libvirt-users Digest, Vol 40, Issue 26 > *********************************************

1 0

[libvirt-users] FW: rpc error‏
by 邓焕聪 12 Apr '13

12 Apr '13

From: dhc3(a)hotmail.com To: eblake(a)redhat.com Subject: RE: [libvirt-users] rpc error‏ Date: Thu, 11 Apr 2013 16:07:28 +0000 the infomation of libvirt package in my centos 6.3 is show as follow:Name : libvirt Relocations: (not relocatable)Version : 0.9.10 Vendor: CentOSRelease : 21.el6_3.8 Build Date: Tue Jan 29 03:28:31 2013Install Date: Mon Apr 8 13:00:12 2013 Build Host: c6b10.bsys.dev.centos.orgGroup : Development/Libraries Source RPM: libvirt-0.9.10-21.el6_3.8.src.rpmSize : 4950064 License: LGPLv2+Signature : RSA/SHA1, Tue Jan 29 03:43:07 2013, Key ID 0946fca2c105b9dePackager : CentOS BuildSystem <http://bugs.centos.org>URL : http://libvirt.org/Summary : Library providing a simple virtualization APIDescription :Libvirt is a C toolkit to interact with the virtualization capabilitiesof recent versions of Linux (and other OSes). The main package includesthe libvirtd server exporting the virtualization support. when i meet that message, i restart the libvirtd deamon, and it run normally. > Date: Thu, 11 Apr 2013 06:45:48 -0600 > From: eblake(a)redhat.com > To: dhc3(a)hotmail.com > CC: libvirt-users(a)redhat.com > Subject: Re: [libvirt-users] rpc error‏ > > On 04/11/2013 02:08 AM, 邓焕聪 wrote: > > > > > > > > libvritd offten print the following message: > > libvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peer > > when i restart the service libvirtd , it runs nomally, but after a while, it print the that messages again. > > Which version of libvirt? You might try upgrading to a newer version > (latest is 1.0.4); there have been patches to cut down on spurious > messages when a connection is shut down normally. > > -- > Eric Blake eblake redhat com +1-919-301-3266 > Libvirt virtualization library http://libvirt.org >

1 0

[libvirt-users] rpc error‏
by 邓焕聪 11 Apr '13

11 Apr '13

libvritd offten print the following message: libvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peerlibvir: RPC error : Cannot recv data: Connection reset by peer when i restart the service libvirtd , it runs nomally, but after a while, it print the that messages again. how could i fix it right? thanks a lot. :)

2 1

[libvirt-users] Reg: Initialization of secure memory. Problem with libvirt-0.10.2
by Anusha K 11 Apr '13

11 Apr '13

Dear All, Please find few minutes from your time and guide us with some pointers if possible. We are facing a libvirtd crash when we are trying to connect to qemu by default TLS transport. i.e libvirt crash when trying to inquiry libvirt version using curl with TLS # virsh -c qemu+tls://localhost/system version error: authentication failed: TLS handshake failed A TLS packet with unexpected length was received. error: failed to connect to the hypervisor We used our own CA and certificates on both Kontron PC and our board. Libvirtd.conf was modified so that libvirt is listening all IPs using default IP These directories and files created and used. /etc/pki/CA/cacert.pem /etc/pki/libvirt/private/serverkey.pem /etc/pki/libvirt/servercert.pem /etc/pki/libvirt/private/clientkey.pem /etc/pki/libvirt/clientcert.pem TLS connection worked fine with Kontron PC # virsh -c qemu+tls://localhost/system version Compiled against library: libvir 0.9.5 Using library: libvir 0.9.5 Using API: QEMU 0.9.5 Running hypervisor: QEMU 0.12.1 But libvirt crashed on our board (using libvirt 0.10.2, gnutls-2.10.5-1_WR4.3.x86_64 and libudev-161-4 rpms, libgcrypt-1.4.0-3_WR4.3.x86_64 ) # virsh -c qemu+tls://localhost/system version error: authentication failed: TLS handshake failed A TLS packet with unexpected length was received. error: failed to connect to the hypervisor GDB: Breakpoint 3, 0x00007f555bb07410 in gnutls_handshake () from /usr/lib64/libgnutls.so.26 (gdb) c Continuing. Program received signal SIGABRT, Aborted. 0x00007f555a096005 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x00007f555a096005 in raise () from /lib64/libc.so.6 #1 0x00007f555a098e40 in abort () from /lib64/libc.so.6 #2 0x00007f555b87fdc5 in _gcry_logv (level=50, fmt=0x7f555b8c6170 "*operation is not possible without initialized secure memory\n*", arg_ptr=0x7fff546e1130) at misc.c:136 #3 0x00007f555b8803d5 in _gcry_log_bug (fmt=0x48e0 <Address 0x48e0 out of bounds>) at misc.c:220 #4 0x00007f555b885697 in _gcry_secmem_malloc_internal (size=<value optimized out>) at secmem.c:497 #5 0x00007f555b88579c in _gcry_secmem_malloc (size=136) at secmem.c:522 #6 0x00007f555b880a65 in do_malloc (n=18656, flags=<value optimized out>, mem=0x7fff546e1290) at global.c:553 #7 0x00007f555b880aa9 in _gcry_malloc_secure (n=18656) at global.c:592 #8 0x00007f555b880b19 in _gcry_xmalloc_secure (n=136) at global.c:746 #9 0x00007f555b8c35df in _gcry_mpi_alloc_limb_space (nlimbs=17, secure=18656) at mpiutil.c:92 #10 0x00007f555b8c365f in _gcry_mpi_alloc_secure (nlimbs=17) at mpiutil.c:75 #11 0x00007f555b8b025a in secret (output=0x17cfa20, input=0x17d0480, skey=0x6) at rsa.c:365 #12 0x00007f555b8b045a in _gcry_rsa_sign (algo=<value optimized out>, resarr=0x17d0660, data=0x17d0480, skey=<value optimized out>) at rsa.c:608 #13 0x00007f555b88c1ef in pubkey_sign (r_sig=0x7fff546e1488, s_hash=<value optimized out>, s_skey=<value optimized out>) at pubkey.c:692 #14 _gcry_pk_sign (r_sig=0x7fff546e1488, s_hash=<value optimized out>, s_skey=<value optimized out>) at pubkey.c:1807 ---Type <return> to continue, or q <return> to quit--- #15 0x00007f555bb29d8c in ?? () from /usr/lib64/libgnutls.so.26 #16 0x00007f555bb15e7a in ?? () from /usr/lib64/libgnutls.so.26 #17 0x00007f555bb1ddd6 in ?? () from /usr/lib64/libgnutls.so.26 #18 0x00007f555bb1e67f in ?? () from /usr/lib64/libgnutls.so.26 #19 0x00007f555bb1edaf in ?? () from /usr/lib64/libgnutls.so.26 #20 0x00007f555bb0af85 in ?? () from /usr/lib64/libgnutls.so.26 #21 0x00007f555bb06c55 in ?? () from /usr/lib64/libgnutls.so.26 #22 0x00007f555bb07437 in gnutls_handshake () from /usr/lib64/libgnutls.so.26 #23 0x00007f555c8a961b in virNetTLSSessionHandshake () from /usr/lib64/libvirt.so.0 #24 0x00007f555c89ea2b in virNetServerClientInit () from /usr/lib64/libvirt.so.0 #25 0x00007f555c89c821 in ?? () from /usr/lib64/libvirt.so.0 #26 0x00007f555c8a012a in ?? () from /usr/lib64/libvirt.so.0 #27 0x00007f555c79fbf5 in virEventPollRunOnce () from /usr/lib64/libvirt.so.0 #28 0x00007f555c79e825 in virEventRunDefaultImpl () from /usr/lib64/libvirt.so.0 #29 0x00007f555c89c20d in virNetServerRun () from /usr/lib64/libvirt.so.0 #30 0x000000000040c830 in ?? () It seems that virsh does not make proper use of libgcrypt or gnutls. In fact, Libgcrypt informs us what actually is going wrong. Please let us know if it is a known issue. Please go through the below link for more details: http://lists.gnupg.org/pipermail/gcrypt-devel/2008-December/001420.html Thanking you in anticipation. Thanks and Regards, Anusha K.

1 0

[libvirt-users] reboot command lost‏
by 邓焕聪 11 Apr '13

11 Apr '13

when i send a reboot command to libvirtd to reboot a domain, it does not receive and print the following warn: 2013-04-10 06:01:39.080+0000: 2908: warning : qemuDomainObjTaint:1311 : Domain id=56 name='69751ca7-3198-4f3c-8265-cb8cb70ad750' uuid=69751ca7-3198-4f3c-8265-cb8cb70ad750 is tainted: high-privileges what's the problem??? thanks a lot.:)

2 1