- Users - oVirt List Archives

[Users] Node as guest - Nested KVM
by Douglas Landgraf 04 Aug '12

04 Aug '12

This is a multi-part message in MIME format. --------------030900080005030708090405 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, I remember someone asking about this topic few weeks ago, here the steps: http://wiki.ovirt.org/wiki/Vdsm_Developers#Running_Node_as_guest_-_Nested_K… Enjoy and fell free to improve it! -- Cheers Douglas --------------030900080005030708090405 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> Hi,<br> <br> I remember someone asking about this topic few weeks ago, here the steps:<br> <a href="http://wiki.ovirt.org/wiki/Vdsm_Developers#Running_Node_as_guest_-_Nested_K…">http://wiki.ovirt.org/wiki/Vdsm_Developers#Running_Node_as_guest_-_Nested_K…</a><br> <br> Enjoy and fell free to improve it!<br> <br> <pre class="moz-signature" cols="72">-- Cheers Douglas</pre> </body> </html> --------------030900080005030708090405--

3 2

[Users] User management broken in 3.0 ?
by Alex Leonhardt 03 Aug '12

03 Aug '12

This is a multi-part message in MIME format. --------------060207040707040004040507 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi there, I've been using 3.0 for some testing recently and was very confused by how to manage new users !? It doesnt seem to be possible to add more "local" users at all ? Or is there a document you can point me at ? Alex --------------060207040707040004040507 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> <font size="-1"><font face="Tahoma">Hi there,<br> <br> I've been using 3.0 for some testing recently and was very confused by how to manage new users !? It doesnt seem to be possible to add more "local" users at all ? Or is there a document you can point me at ? <br> <br> Alex<br> <br> </font></font> </body> </html> --------------060207040707040004040507--

3 3

Re: [Users] Failure to migrate from one host out of four
by Karli Sjöberg 03 Aug '12

03 Aug '12

3 aug 2012 kl. 09.55 skrev Karli Sjöberg: > > 3 aug 2012 kl. 09.30 skrev Martin Kletzander: > >> On 08/02/2012 04:20 PM, Karli Sjöberg wrote: >>> Sorry man, I spoke too soon. It´s back again:( >>> >>> I´ve got another guest "stuck". It´s all for testing at this point, so I >>> can basically do anything I want with it, so I just shut it down and put >>> the host back into maintenance. I guess something must still have the >>> old locale written in some conf somewhere, set after it was installed. >>> Do you know where to start looking? >>> >> >> No problem, but I don't think it will be the locale again. BTW I took >> this off-list when I replied to you last time. Try looking at >> libvirtd.log again. If you don't find anything, then you can try sending >> it to me or libvirt-users list (if it is libvirt that's doing the >> problem, but I don't think so). >> >> Martin > > Well, hasty as I am, I thought that maybe it would be good to remove glibc and glib-common, and then installing again... Turns out that don´t work out too well, haha:) So I´m reinstalling it right now, and was careful to choose us_EN this time. Will keep you posted on how it turns out. After a clean reinstall and us_EN locale it´s working again, just as expected. I´ll still keep an eye on it though, just in case. /Karli

1 0

[Users] Managing Remote Access to Physical Workstations
by Randall Wood 03 Aug '12

03 Aug '12

I have an environment where I would like to be able to provide users with a single web interface from which they would be able to open a console on either a virtual machine or on a physical machine. Playing with a clean install of oVirt 3.1 suggests that oVirt is not capable of doing this. Has anyone successfully configured oVirt to provide this capability, or know of a system that could integrate with oVirt to meet that requirement? -- Randall Wood Alexandria Software http://www.alexandriasoftware.com randall.h.wood(a)alexandriasoftware.com 202.683.8604

5 10

Re: [Users] Managing Remote Access to Physical Workstations
by Sigbjorn Lie 02 Aug '12

02 Aug '12

Hi, Then you should still have a look at the Leostream Connection Broker. (www.leostream.com) One of the latest features we're integration with Red Hat Enterprise Virtualization / (ovirt). And they support both Windows and Linux. They support a wide variety of protocols and flexible configurations as well. Regards, Siggi On Thu, August 2, 2012 15:13, Randall Wood wrote: > Yes, I have a few of those available. They are nice (when the > bandwidth is there to support them). > > I'm looking for a single broker interface for both physical and > virtual machines that supports both Windows and Linux. > > On Thu, Aug 2, 2012 at 9:03 AM, Sigbjorn Lie <sigbjorn(a)nixtra.com> wrote: > >> Hi, >> >> >> Have you looked at Teradici PCoIP? They have a hardware solution based on a PCIe card in the >> host machine, and a PCoIP thin client. The performance is stunning. You don't even notice that >> you're connected to a thin client. I'm using this on a daily basis myself. >> >> To get a broker you can use Leostream's Connection Broker which supports Teradici PCoIP both >> for Windows and Linux. >> >> >> You will be needing the thin client when connecting. I don't think you can use a software >> client to connect to the physical machines. You can ask Leostream about this. >> >> See the following youtube video for more info: >> http://www.youtube.com/watch?v=NWjhAHDQZ7E >> >> >> This solution is for physical machines, not virtual machines. >> >> >> >> Regards, >> Siggi >> >> >> >> >> >> On Thu, August 2, 2012 14:44, Randall Wood wrote: >> >>> Sorry for the delay in responding. >>> >>> >>> >>> I have a set of users (about 50) who have Linux workstations at their >>> desks. These users have root access to these workstations, and these workstations are >>> frequently host VMs or are used for hardware driver development and support. These users have >>> access to a pool of managed Windows 7 VMs (for MS Office applications) in oVirt, so they are >>> already using the oVirt user portal. I would like to give these users remote access to their >>> workstations (from thin clients in conference rooms, from home, from corporate laptops on the >>> road, etc) using the same User Portal that they already use for the Windows VMs. >>> >>> VMware View and Citrix XenDesktop support providing users access to a >>> mixed set of managed-virtual-machine or unmanaged-physical-or-virtual-machine through a single >>> broker, but neither of them support access to Linux desktops. >>> >>> On Sat, Jul 21, 2012 at 2:33 AM, Johan Kragsterman >>> <johan.kragsterman(a)capvert.se> wrote: >>> >>> >>>> Hi, Randall! >>>> >>>> >>>> >>>> What you need is a "broker", and a terminal server is working as a "broker". There are >>>> several solutions that will work, but first I would want to know why you need physical >>>> machines? Are there demanding graphical applications you're going to run, or...? >>>> >>>> Rgrds Johan >>>> >>>> >>>> >>>> -----users-bounces(a)ovirt.org skrev: ----- >>>> Till: Itamar Heim <iheim(a)redhat.com> >>>> Från: Randall Wood >>>> Sänt av: users-bounces(a)ovirt.org >>>> Datum: 2012.07.20 22:37 >>>> Kopia: "users(a)ovirt.org" <users(a)ovirt.org> >>>> Ärende: Re: [Users] Managing Remote Access to Physical Workstations >>>> >>>> >>>> >>>> On Jul 20, 2012, at 16:30, Itamar Heim <iheim(a)redhat.com> wrote: >>>> >>>> >>>> >>>>> On 07/20/2012 11:13 PM, Randall Wood wrote: >>>>> >>>>> >>>>>> >>>>>>> No. oVirt's focus is virtual machines so the user portal only lets you open up >>>>>>> consoles on VMs managed by oVirt engine. >>>>>> >>>>>> I thought so. >>>>>> >>>>>> >>>>>> >>>>>>> When you say physical machines - would they be Linux or could they be Windows? >>>>>>> I might have an idea ...... >>>>>>> >>>>>>> >>>>>> >>>>>> The physical machines would all be RHEL, CentOS, or Fedora. >>>>>> >>>>>> >>>>> >>>>> which protocol would you expect users to use to gain access to this physical machines? >>>> >>>> I would prefer SPICE, but could use SPICE, VNC, or RDP. >>>> _______________________________________________ >>>> Users mailing list >>>> Users(a)ovirt.org >>>> http://lists.ovirt.org/mailman/listinfo/users >>>> >>>> >>> >>> >>> >>> -- >>> Randall Wood >>> Alexandria Software >>> http://www.alexandriasoftware.com >>> randall.h.wood(a)alexandriasoftware.com 202.683.8604 >>> _______________________________________________ >>> Users mailing list >>> Users(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> >>> >>> >> >> > > > > -- > Randall Wood > Alexandria Software > http://www.alexandriasoftware.com > randall.h.wood(a)alexandriasoftware.com 202.683.8604 > >

1 0

Re: [Users] Host installation failed with error "Unable to set host time"
by Nicholas Kesick 02 Aug '12

02 Aug '12

--_5d15bdc1-d905-4034-ad4c-39e3fe255785_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0A= =0A= =0A= Daniel=2C It seems clear to me that for some reason Fedora 16 can't access the RTC (r= eal time clock - hardware clock) on your computer's motherboard. Odd that R= HEL 6.2 can but I forget what it is based on. Anyway can you try a Fedora 1= 7 live cd and see if the "hwclock --show" command works? If it doesn't=2C I= am thinking that you will want to file a bugzilla. If it does work=2C then= vdsm and ovirt-node-2.5.0 will work for you on Fedora 17. - Nick ---------------------------------------------------------------------------= ----------- From: DYeung(a)TrustedCS.com To: cybertimber2000(a)hotmail.com Subject: RE: [Users] Host installation failed with error "Unable to set hos= t time" Hi=2C Nicholas=2C=0A= I like to give you an update. I found that hwclock worked perfectly f= ine on RHEL 6.2 system. I am still=0A= puzzling why it failed in Fedora 16. I am thinking of installing oVirt 3.0= on RHEL 6.2 to see how it turns out. =0A= If you find anything=2C please let me know. =0A= Thanks a lot. =0A= =0A= Daniel =0A= =0A= =0A= =0A= From: DYeung(a)TrustedCS.com To: cybertimber2000(a)hotmail.com Subject: RE: [Users] Host installation failed with error "Unable to set hos= t time" Date: Wed=2C 1 Aug 2012 12:36:26 +0000 =0A= =0A= =0A= =0A= =0A= =0A= Here are the putput: =0A= =0A= #date =0A= Wed Aug 1 08:29:59 EDT 2012 =0A= =0A= # hwclock --show =0A= hwclock: Cannot access the Hardware Clock via any known method. =0A= hwclock: Use the --debug option to see the details of our search for an acc= ess method. =0A= =0A= # hwclock --debug =0A= hwclock from util-linux 2.20.1 =0A= hwclock: Open of /dev/rtc failed: Device or resource busy =0A= No usable clock interface found. =0A= hwclock: Cannot access the Hardware Clock via any known method. =0A= =0A= I am wondering if this is a bug in Fedora 16 or maybe I am missing the driv= er or related rpm.=0A= =0A= =0A= Let me know if you find anything. Thank you for your help.=20 =0A= =0A= DY =0A= =0A= =0A= =0A= =0A= From: Nicholas Kesick [cybertimber2000(a)hotmail.com] =0A= Sent: Tuesday=2C July 31=2C 2012 5:38 PM =0A= To: Daniel Yeung=3B oVirt Mailing List =0A= Subject: RE: [Users] Host installation failed with error "Unable to set hos= t time" =0A= =0A= =0A= =0A= =0A= =0A= =0A= From: DYeung(a)TrustedCS.com =0A= To: users(a)ovirt.org =0A= Date: Tue=2C 31 Jul 2012 20:12:31 +0000 =0A= Subject: [Users] Host installation failed with error "Unable to set host ti= me" =0A= =0A= =0A= =0A= =0A= I created a new host and the installation failed with the following message= s on the engine.log: =0A= =0A= <BSTRAP component=3D'SetSSHAccess' status=3D'OK' message=3D'SUCCESS'/> =0A= <BSTRAP component=3D'SET_SYSTEM_TIME' status=3D'FAIL' message=3D'Unable to = set host time.'/> =0A= <BSTRAP component=3D'RHEV_INSTALL' status=3D'FAIL'/> =0A= . Error occured. (Stage: Running first installation script on Host) =0A= 2012-07-31 15:28:06=2C530 INFO [org.ovirt.engine.core.utils.hostinstall.Mi= naInstallWrapper] (pool-5-thread-4) RunSSHCommand returns true =0A= 2012-07-31 15:28:06=2C530 INFO [org.ovirt.engine.core.bll.VdsInstaller] (p= ool-5-thread-4) RunScript ended:true =0A= 2012-07-31 15:28:06=2C530 ERROR [org.ovirt.engine.core.bll.VdsInstaller] (p= ool-5-thread-4) Installation of 192.168.4.125. Operation failure. (Stage: R= unning first installation script on Host) =0A= 2012-07-31 15:28:06=2C531 INFO [org.ovirt.engine.core.bll.InstallVdsComman= d] (pool-5-thread-4) After Installation pool-5-thread-4 =0A= 2012-07-31 15:28:06=2C532 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStat= usVDSCommand] (pool-5-thread-4) START=2C SetVdsStatusVDSCommand(vdsId =3D 1= 001e89e-db3f-11e1-99f0-bbd8c818bb29=2C status=3DInstallFailed=2C nonOperati= onalReason=3DNONE)=2C log id: 3b08378 =0A= 2012-07-31 15:28:06=2C544 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStat= usVDSCommand] (pool-5-thread-4) FINISH=2C SetVdsStatusVDSCommand=2C log id:= 3b08378 =0A= =0A= =0A= Here are the vdsm related rpms in my Fedora 16 system. =0A= =0A= vdsm-4.9.3.3-0.fc16.x86_64 =0A= vdsm-bootstrap-4.9.3.3-0.fc16.noarch =0A= vdsm-cli-4.9.3.3-0.fc16.noarch =0A= =0A= Does anyone encounter the same problem? Any hints?=20 =0A= =0A= Thank you. =0A= =0A= DY =0A= =0A= _______________________________________________ Users mailing list Users@ov= irt.org=0A= http://lists.ovirt.org/mailman/listinfo/users=0A= =0A= I'll take a stab at it. =0A= Can you post the output of these two commands? Exclude the #=20 =0A= #date =0A= #hwclock --show =0A= =0A= =0A= =0A= =0A= =0A= = --_5d15bdc1-d905-4034-ad4c-39e3fe255785_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <style></style></head> <body class=3D'hmmessage'><div dir=3D'ltr'><div id=3D"mps0_readMsgBodyConta= iner" class=3D"ReadMsgBody"><div class=3D"SandboxScopeClass ExternalClass" = id=3D"mps0_MsgContainer"><div>=0A= <div><span lang=3D"en-US">=0A= <div>=0A= <div style=3D""><span lang=3D"en-US">Daniel=2C<br><br>It seems clear to me = that for some reason Fedora 16 can't access the RTC (real time clock - hard= ware clock) on your computer's motherboard. Odd that RHEL 6.2 can but I for= get what it is based on. Anyway can you try a Fedora 17 live cd and see if = the "hwclock --show" command works? If it doesn't=2C I am thinking that you= will want to file a bugzilla. If it does work=2C then vdsm and ovirt-node-= 2.5.0 will work for you on Fedora 17.<br><br>- Nick<br><br></span><font sty= le=3D"font-size: 12pt=3B" face=3D"Times New Roman" size=3D"3"><span style= =3D"font-size:12pt"><font style=3D"font-size: 16pt=3B" face=3D"Arial" size= =3D"4"><span style=3D"font-size:14pt">-------------------------------------= -------------------------------------------------<br></span></font></span><= /font>From: DYeung(a)TrustedCS.com<br>To: cybertimber2000(a)hotmail.com<br>Subj= ect: RE: [Users] Host installation failed with error "Unable to set host ti= me"<br><br><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-si= ze:12pt"><font face=3D"Arial" size=3D"4"><span style=3D"font-size:14pt">Hi= =2C Nicholas=2C</span></font></span></font></div>=0A= <div style=3D""><font face=3D"Times New Roman" size=3D"3"><span style=3D"fo= nt-size:12pt"><font face=3D"Arial" size=3D"4"><span style=3D"font-size:14pt= ">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B I like to give you an update. I = found that hwclock worked perfectly fine on RHEL 6.2 system. I am still=0A= puzzling why it failed in Fedora 16. &nbsp=3BI am thinking of installing oV= irt 3.0 on RHEL 6.2 to see how it turns out. </span></font></span></font></= div>=0A= <div style=3D""><font face=3D"Times New Roman" size=3D"3"><span style=3D"fo= nt-size:12pt"><font face=3D"Arial" size=3D"4"><span style=3D"font-size:14pt= ">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B If you find anything=2C please l= et me know. </span></font></span></font></div>=0A= <div style=3D""><font face=3D"Times New Roman" size=3D"3"><span style=3D"fo= nt-size:12pt"><font face=3D"Arial" size=3D"4"><span style=3D"font-size:14pt= ">&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Thanks a lot. </span></font></sp= an></font></div>=0A= <div style=3D""><font face=3D"Times New Roman" size=3D"3"><span style=3D"fo= nt-size:12pt"><font face=3D"Arial" size=3D"4"><span style=3D"font-size:14pt= ">&nbsp=3B</span></font></span></font></div>=0A= <div style=3D""><font face=3D"Times New Roman" size=3D"3"><span style=3D"fo= nt-size:12pt"><font face=3D"Arial" size=3D"4"><span style=3D"font-size:14pt= ">Daniel </span></font></span></font></div>=0A= </div>=0A= </span></div>=0A= </div>=0A= </div></div><br><br><div><div id=3D"SkyDrivePlaceholder"></div><hr id=3D"st= opSpelling">From: DYeung(a)TrustedCS.com<br>To: cybertimber2000(a)hotmail.com<b= r>Subject: RE: [Users] Host installation failed with error "Unable to set h= ost time"<br>Date: Wed=2C 1 Aug 2012 12:36:26 +0000<br><br>=0A= =0A= =0A= <style></style><style id=3D"ecxowaParaStyle">=0A= </style>=0A= =0A= =0A= <div style=3D"direction:ltr=3Bfont-family:Tahoma=3Bcolor:#000000=3Bfont-siz= e:10pt">Here are the putput:<br>=0A= <br>=0A= #date<br>=0A= Wed Aug&nbsp=3B 1 08:29:59 EDT 2012<br>=0A= <br>=0A= # hwclock --show<br>=0A= hwclock: Cannot access the Hardware Clock via any known method.<br>=0A= hwclock: Use the --debug option to see the details of our search for an acc= ess method.<br>=0A= <br>=0A= # hwclock --debug<br>=0A= hwclock from util-linux 2.20.1<br>=0A= hwclock: Open of /dev/rtc failed: Device or resource busy<br>=0A= No usable clock interface found.<br>=0A= hwclock: Cannot access the Hardware Clock via any known method.<br>=0A= <br>=0A= I am wondering if this is a bug in Fedora 16 or maybe I am missing the driv= er or related rpm.=0A= <br>=0A= <br>=0A= Let me know if you find anything. Thank you for your help. <br>=0A= <br>=0A= DY<br>=0A= <br>=0A= <br>=0A= <div style=3D"font-family:Times New Roman=3Bcolor:#000000=3Bfont-size:16px"= >=0A= <hr tabindex=3D"-1">=0A= <div style=3D"direction:ltr" id=3D"ecxdivRpF58378"><font color=3D"#000000" = face=3D"Tahoma" size=3D"2"><b>From:</b> Nicholas Kesick [cybertimber2000@ho= tmail.com]<br>=0A= <b>Sent:</b> Tuesday=2C July 31=2C 2012 5:38 PM<br>=0A= <b>To:</b> Daniel Yeung=3B oVirt Mailing List<br>=0A= <b>Subject:</b> RE: [Users] Host installation failed with error "Unable to = set host time"<br>=0A= </font><br>=0A= </div>=0A= <div></div>=0A= <div>=0A= <div dir=3D"ltr">=0A= <hr id=3D"ecxstopSpelling">=0A= From: DYeung(a)TrustedCS.com<br>=0A= To: users(a)ovirt.org<br>=0A= Date: Tue=2C 31 Jul 2012 20:12:31 +0000<br>=0A= Subject: [Users] Host installation failed with error "Unable to set host ti= me"<br>=0A= <br>=0A= <style id=3D"ecxowaParaStyle">=0A= .ExternalClass p=0A= {margin-bottom:0=3B}=0A= =0A= .ExternalClass=0A= {direction:ltr=3Bfont-family:Tahoma=3Bcolor:#000000=3Bfont-size:10pt=3B}=0A= .ExternalClass P=0A= {margin-bottom:0=3B}=0A= .ExternalClass=0A= {scrollbar-base-color:undefined=3Bscrollbar-highlight-color:undefined=3Bscr= ollbar-darkshadow-color:undefined=3Bscrollbar-track-color:undefined=3Bscrol= lbar-arrow-color:undefined=3B}=0A= </style><br>=0A= <div>=0A= <div style=3D"color:rgb(0=2C0=2C0)=3Bfont-family:Tahoma=3Bfont-size:10pt=3B= direction:ltr">=0A= I created a new host and the installation failed with the following message= s on the engine.log:<br>=0A= <br>=0A= &lt=3BBSTRAP component=3D'SetSSHAccess' status=3D'OK' message=3D'SUCCESS'/&= gt=3B<br>=0A= &lt=3BBSTRAP component=3D'SET_SYSTEM_TIME' status=3D'FAIL' message=3D'Unabl= e to set host time.'/&gt=3B<br>=0A= &lt=3BBSTRAP component=3D'RHEV_INSTALL' status=3D'FAIL'/&gt=3B<br>=0A= . Error occured. (Stage: Running first installation script on Host)<br>=0A= 2012-07-31 15:28:06=2C530 INFO&nbsp=3B [org.ovirt.engine.core.utils.hostins= tall.MinaInstallWrapper] (pool-5-thread-4) RunSSHCommand returns true<br>= =0A= 2012-07-31 15:28:06=2C530 INFO&nbsp=3B [org.ovirt.engine.core.bll.VdsInstal= ler] (pool-5-thread-4)&nbsp=3B RunScript ended:true<br>=0A= 2012-07-31 15:28:06=2C530 ERROR [org.ovirt.engine.core.bll.VdsInstaller] (p= ool-5-thread-4) Installation of 192.168.4.125. Operation failure. (Stage: R= unning first installation script on Host)<br>=0A= 2012-07-31 15:28:06=2C531 INFO&nbsp=3B [org.ovirt.engine.core.bll.InstallVd= sCommand] (pool-5-thread-4) After Installation pool-5-thread-4<br>=0A= 2012-07-31 15:28:06=2C532 INFO&nbsp=3B [org.ovirt.engine.core.vdsbroker.Set= VdsStatusVDSCommand] (pool-5-thread-4) START=2C SetVdsStatusVDSCommand(vdsI= d =3D 1001e89e-db3f-11e1-99f0-bbd8c818bb29=2C status=3DInstallFailed=2C non= OperationalReason=3DNONE)=2C log id: 3b08378<br>=0A= 2012-07-31 15:28:06=2C544 INFO&nbsp=3B [org.ovirt.engine.core.vdsbroker.Set= VdsStatusVDSCommand] (pool-5-thread-4) FINISH=2C SetVdsStatusVDSCommand=2C = log id: 3b08378<br>=0A= <br>=0A= <br>=0A= Here are the vdsm related rpms in my Fedora 16 system.<br>=0A= <br>=0A= vdsm-4.9.3.3-0.fc16.x86_64<br>=0A= vdsm-bootstrap-4.9.3.3-0.fc16.noarch<br>=0A= vdsm-cli-4.9.3.3-0.fc16.noarch<br>=0A= <br>=0A= Does anyone encounter the same problem?&nbsp=3B Any hints? <br>=0A= <br>=0A= Thank you.<br>=0A= <br>=0A= DY<br>=0A= <br>=0A= _______________________________________________ Users mailing list Users@ov= irt.org=0A= <a href=3D"http://lists.ovirt.org/mailman/listinfo/users" target=3D"_blank"= >http://lists.ovirt.org/mailman/listinfo/users</a></div>=0A= <div style=3D"color:rgb(0=2C0=2C0)=3Bfont-family:Tahoma=3Bfont-size:10pt=3B= direction:ltr">=0A= I'll take a stab at it.<br>=0A= Can you post the output of these two commands? Exclude the # <br>=0A= #date<br>=0A= #hwclock --show<br>=0A= </div>=0A= </div>=0A= </div>=0A= </div>=0A= </div>=0A= </div></div> </div></body> </html>= --_5d15bdc1-d905-4034-ad4c-39e3fe255785_--

1 0

[Users] Failure to migrate from one host out of four
by Karli Sjöberg 02 Aug '12

02 Aug '12

--_000_0CBBF9E4118E4C0C82215A5FE4D6D522sluse_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Wondering if anyone has encountered the same issue as me. On one host in my= cluster, if I migrate in a guest, I cannot migrate it out to another host?= The get "stuck" there, so to speak. Same when a guest is started on that = particular host, it is impossible to migrate them out again. iptables are flushed, for excluding purposes. vdsmd, libvirtd and sanlock a= re all running. This is what I caught from libvirtd.log: 2012-08-02 11:44:07.542+0000: 4231: debug : qemuMonitorUnref:248 : QEMU_MON= ITOR_UNREF: mon=3D0x7fe7e40c8410 refs=3D3 2012-08-02 11:44:07.542+0000: 4232: debug : qemuMonitorUnref:248 : QEMU_MON= ITOR_UNREF: mon=3D0x7fe7e40c8410 refs=3D2 2012-08-02 11:44:07.542+0000: 4232: debug : virConnectIsAlive:18395 : conn= =3D0x7fe7e00c4e50 2012-08-02 11:44:07.562+0000: 4236: debug : virDomainMigrateSetMaxDowntime:= 16565 : dom=3D0x7fe7d8000cc0, (VM: name=3Dmilli, uuid=3D2291f0d8-6341-4821-= 8774-2ed84b8bccc1), downtime=3D50, flags=3D0 2012-08-02 11:44:07.562+0000: 4236: debug : qemuDomainObjBeginJobInternal:7= 53 : Starting job: migration operation (async=3Dmigration out) 2012-08-02 11:44:07.562+0000: 4236: debug : qemuDomainMigrateSetMaxDowntime= :9500 : Setting migration downtime to 50ms 2012-08-02 11:44:07.562+0000: 4236: debug : qemuMonitorRef:239 : QEMU_MONIT= OR_REF: mon=3D0x7fe7e40c8410 refs=3D3 2012-08-02 11:44:07.562+0000: 4236: debug : qemuMonitorSetMigrationDowntime= :1753 : mon=3D0x7fe7e40c8410 downtime=3D50 2012-08-02 11:44:07.562+0000: 4236: debug : qemuMonitorSend:861 : QEMU_MONI= TOR_SEND_MSG: mon=3D0x7fe7e40c8410 msg=3D{"execute":"migrate_set_downtime",= "arguments":{"value":0,050000},"id":"libvirt-261"} fd=3D-1 2012-08-02 11:44:07.563+0000: 4231: debug : qemuMonitorRef:239 : QEMU_MONIT= OR_REF: mon=3D0x7fe7e40c8410 refs=3D4 2012-08-02 11:44:07.563+0000: 4231: debug : qemuMonitorIOWrite:470 : QEMU_M= ONITOR_IO_WRITE: mon=3D0x7fe7e40c8410 buf=3D{"execute":"migrate_set_downtim= e","arguments":{"value":0,050000},"id":"libvirt-261"} len=3D86 ret=3D86 errno=3D11 2012-08-02 11:44:07.563+0000: 4231: debug : qemuMonitorUnref:248 : QEMU_MON= ITOR_UNREF: mon=3D0x7fe7e40c8410 refs=3D3 2012-08-02 11:44:07.564+0000: 4231: debug : qemuMonitorRef:239 : QEMU_MONIT= OR_REF: mon=3D0x7fe7e40c8410 refs=3D4 2012-08-02 11:44:07.564+0000: 4231: debug : qemuMonitorIOProcess:365 : QEMU= _MONITOR_IO_PROCESS: mon=3D0x7fe7e40c8410 buf=3D{"error": {"class": "JSONPa= rsing", "desc": "Invalid JSON syntax", "data": {}}} len=3D80 2012-08-02 11:44:07.564+0000: 4231: debug : qemuMonitorUnref:248 : QEMU_MON= ITOR_UNREF: mon=3D0x7fe7e40c8410 refs=3D3 2012-08-02 11:44:07.564+0000: 4236: error : qemuMonitorJSONCheckError:331 := internal error unable to execute QEMU command 'migrate_set_downtime': Inva= lid JSON syntax 2012-08-02 11:44:07.564+0000: 4236: debug : qemuMonitorUnref:248 : QEMU_MON= ITOR_UNREF: mon=3D0x7fe7e40c8410 refs=3D2 2012-08-02 11:44:07.564+0000: 4236: debug : qemuDomainObjEndJob:870 : Stopp= ing job: migration operation (async=3Dmigration out) 2012-08-02 11:44:07.564+0000: 4231: debug : qemuMonitorRef:239 : QEMU_MONIT= OR_REF: mon=3D0x7fe7e40c8410 refs=3D3 2012-08-02 11:44:07.564+0000: 4231: debug : qemuMonitorIOProcess:365 : QEMU= _MONITOR_IO_PROCESS: mon=3D0x7fe7e40c8410 buf=3D{"error": {"class": "JSONPa= rsing", "desc": "Invalid JSON syntax", "data": {}}} len=3D80 2012-08-02 11:44:07.564+0000: 4236: debug : virDomainFree:2345 : dom=3D0x7f= e7d8000cc0, (VM: name=3Dmilli, uuid=3D2291f0d8-6341-4821-8774-2ed84b8bccc1) 2012-08-02 11:44:07.564+0000: 4231: error : qemuMonitorJSONIOProcessLine:15= 6 : internal error Unexpected JSON reply '{"error": {"class": "JSONParsing"= , "desc": "Invalid JSON syntax", "data": {}}}' 2012-08-02 11:44:07.564+0000: 4231: debug : qemuMonitorIO:645 : Error on mo= nitor internal error Unexpected JSON reply '{"error": {"class": "JSONParsin= g", "desc": "Invalid JSON syntax", "data": {}}}' 2012-08-02 11:44:07.564+0000: 4231: debug : qemuMonitorUnref:248 : QEMU_MON= ITOR_UNREF: mon=3D0x7fe7e40c8410 refs=3D2 2012-08-02 11:44:07.564+0000: 4231: debug : qemuMonitorIO:679 : Triggering = error callback 2012-08-02 11:44:07.564+0000: 4231: debug : qemuProcessHandleMonitorError:3= 45 : Received error on 0x7fe7e4000e50 'milli' 2012-08-02 11:44:07.592+0000: 4232: debug : qemuDomainObjBeginJobInternal:7= 53 : Starting job: async nested (async=3Dmigration out) 2012-08-02 11:44:07.593+0000: 4232: debug : qemuMonitorRef:239 : QEMU_MONIT= OR_REF: mon=3D0x7fe7e40c8410 refs=3D3 2012-08-02 11:44:07.593+0000: 4232: debug : qemuMonitorGetMigrationStatus:1= 776 : mon=3D0x7fe7e40c8410 2012-08-02 11:44:07.593+0000: 4232: debug : qemuMonitorSend:851 : Attempt t= o send command while error is set internal error Unexpected JSON reply '{"e= rror": {"class": "JSONParsing", "desc": "Invalid JSON syntax", "data": {}}}= ' 2012-08-02 11:44:07.593+0000: 4232: debug : qemuMonitorUnref:248 : QEMU_MON= ITOR_UNREF: mon=3D0x7fe7e40c8410 refs=3D2 2012-08-02 11:44:07.593+0000: 4232: debug : doPeer2PeerMigrate3:2425 : Fini= sh3 0x7fe7e00c4e50 ret=3D-1 2012-08-02 11:44:08.798+0000: 4233: debug : virDomainInterfaceStats:7299 : = dom=3D0x7fe7e40c72d0, (VM: name=3Dmilli, uuid=3D2291f0d8-6341-4821-8774-2ed= 84b8bccc1), path=3Dvnet0, stats=3D0x7fe803e45b10, size=3D64 2012-08-02 11:44:08.802+0000: 4233: debug : virDomainFree:2345 : dom=3D0x7f= e7e40c72d0, (VM: name=3Dmilli, uuid=3D2291f0d8-6341-4821-8774-2ed84b8bccc1) 2012-08-02 11:44:12.564+0000: 4234: debug : virDomainGetJobInfo:16465 : dom= =3D0x7fe7dc000e00, (VM: name=3Dmilli, uuid=3D2291f0d8-6341-4821-8774-2ed84b= 8bccc1), info=3D0x7fe803644af0 2012-08-02 11:44:12.564+0000: 4234: debug : virDomainFree:2345 : dom=3D0x7f= e7dc000e00, (VM: name=3Dmilli, uuid=3D2291f0d8-6341-4821-8774-2ed84b8bccc1) 2012-08-02 11:44:13.804+0000: 4235: debug : virDomainGetInfo:4298 : dom=3D0= x7fe7e8001bd0, (VM: name=3Dmilli, uuid=3D2291f0d8-6341-4821-8774-2ed84b8bcc= c1), info=3D0x7fe802e43b20 2012-08-02 11:44:13.805+0000: 4235: debug : qemudGetProcessInfo:1156 : Got = status for 5448/0 user=3D1770 sys=3D1445 cpu=3D0 rss=3D185496 2012-08-02 11:44:13.805+0000: 4235: debug : virDomainFree:2345 : dom=3D0x7f= e7e8001bd0, (VM: name=3Dmilli, uuid=3D2291f0d8-6341-4821-8774-2ed84b8bccc1) 2012-08-02 11:44:13.806+0000: 4238: debug : virDomainInterfaceStats:7299 : = dom=3D0x7fe7f0002520, (VM: name=3Dmilli, uuid=3D2291f0d8-6341-4821-8774-2ed= 84b8bccc1), path=3Dvnet0, stats=3D0x7fe801640b10, size=3D64 2012-08-02 11:44:13.807+0000: 4238: debug : virDomainFree:2345 : dom=3D0x7f= e7f0002520, (VM: name=3Dmilli, uuid=3D2291f0d8-6341-4821-8774-2ed84b8bccc1) 2012-08-02 11:44:16.474+0000: 4232: error : virNetClientProgramDispatchErro= r:174 : An error occurred, but the cause is unknown 2012-08-02 11:44:16.474+0000: 4232: debug : doPeer2PeerMigrate3:2458 : Conf= irm3 0x7fe7e40029c0 ret=3D-1 vm=3D0x7fe7e4000e50 2012-08-02 11:44:16.474+0000: 4232: debug : qemuMigrationConfirm:3109 : dri= ver=3D0x7fe7f80bd9c0, conn=3D0x7fe7e40029c0, vm=3D0x7fe7e4000e50, cookiein= =3D(null), cookieinlen=3D0, flags=3D3, retcode=3D1 2012-08-02 11:44:16.474+0000: 4232: debug : qemuMigrationEatCookie:752 : co= okielen=3D0 cookie=3D'(null)' 2012-08-02 11:44:16.475+0000: 4232: debug : qemuProcessStartCPUs:2644 : Usi= ng lock state '(null)' 2012-08-02 11:44:16.475+0000: 4232: debug : qemuDomainObjBeginJobInternal:7= 53 : Starting job: async nested (async=3Dmigration out) And this is from a migration gone well: 2012-08-02 11:41:28.386+0000: 618: debug : qemuProcessStop:3872 : Shutting = down VM 'milli' pid=3D3776 flags=3D1 2012-08-02 11:41:28.386+0000: 618: debug : qemuMonitorClose:797 : QEMU_MONI= TOR_CLOSE: mon=3D0x7f49dc000d50 refs=3D2 2012-08-02 11:41:28.386+0000: 618: debug : qemuMonitorUnref:248 : QEMU_MONI= TOR_UNREF: mon=3D0x7f49dc000d50 refs=3D1 2012-08-02 11:41:28.386+0000: 606: debug : qemuMonitorUnref:248 : QEMU_MONI= TOR_UNREF: mon=3D0x7f49dc000d50 refs=3D0 2012-08-02 11:41:28.386+0000: 606: debug : qemuMonitorFree:225 : mon=3D0x7f= 49dc000d50 2012-08-02 11:41:28.386+0000: 618: debug : qemuProcessKill:3769 : vm=3Dmill= i pid=3D3776 flags=3D5 2012-08-02 11:41:28.586+0000: 618: debug : qemuDomainCleanupRun:1921 : driv= er=3D0x7f49e806f1b0, vm=3Dmilli 2012-08-02 11:41:28.586+0000: 618: debug : qemuProcessAutoDestroyRemove:432= 0 : vm=3Dmilli 2012-08-02 11:41:28.586+0000: 618: debug : qemuDriverCloseCallbackUnset:578= : vm=3Dmilli, uuid=3D2291f0d8-6341-4821-8774-2ed84b8bccc1, cb=3D0x4900d0 2012-08-02 11:41:28.586+0000: 618: debug : virCgroupNew:603 : New group /li= bvirt/qemu/milli 2012-08-02 11:41:28.587+0000: 618: debug : virCgroupDetect:262 : Detected m= ount/mapping 0:cpu at /sys/fs/cgroup/cpu,cpuacct in /system/libvirtd.servic= e 2012-08-02 11:41:28.587+0000: 618: debug : virCgroupDetect:262 : Detected m= ount/mapping 1:cpuacct at /sys/fs/cgroup/cpu,cpuacct in /system/libvirtd.se= rvice 2012-08-02 11:41:28.587+0000: 618: debug : virCgroupDetect:262 : Detected m= ount/mapping 2:cpuset at /sys/fs/cgroup/cpuset in 2012-08-02 11:41:28.587+0000: 618: debug : virCgroupDetect:262 : Detected m= ount/mapping 3:memory at /sys/fs/cgroup/memory in 2012-08-02 11:41:28.587+0000: 618: debug : virCgroupDetect:262 : Detected m= ount/mapping 4:devices at /sys/fs/cgroup/devices in 2012-08-02 11:41:28.587+0000: 618: debug : virCgroupDetect:262 : Detected m= ount/mapping 5:freezer at /sys/fs/cgroup/freezer in 2012-08-02 11:41:28.587+0000: 618: debug : virCgroupDetect:262 : Detected m= ount/mapping 6:blkio at /sys/fs/cgroup/blkio in 2012-08-02 11:41:28.587+0000: 618: debug : virCgroupMakeGroup:524 : Make gr= oup /libvirt/qemu/milli 2012-08-02 11:41:28.587+0000: 618: debug : virCgroupMakeGroup:546 : Make co= ntroller /sys/fs/cgroup/cpu,cpuacct/system/libvirtd.service/libvirt/qemu/mi= lli/ 2012-08-02 11:41:28.587+0000: 618: debug : virCgroupMakeGroup:546 : Make co= ntroller /sys/fs/cgroup/cpu,cpuacct/system/libvirtd.service/libvirt/qemu/mi= lli/ 2012-08-02 11:41:28.587+0000: 618: debug : virCgroupMakeGroup:546 : Make co= ntroller /sys/fs/cgroup/cpuset/libvirt/qemu/milli/ 2012-08-02 11:41:28.587+0000: 618: debug : virCgroupMakeGroup:546 : Make co= ntroller /sys/fs/cgroup/memory/libvirt/qemu/milli/ 2012-08-02 11:41:28.587+0000: 618: debug : virCgroupMakeGroup:546 : Make co= ntroller /sys/fs/cgroup/devices/libvirt/qemu/milli/ 2012-08-02 11:41:28.587+0000: 618: debug : virCgroupMakeGroup:546 : Make co= ntroller /sys/fs/cgroup/freezer/libvirt/qemu/milli/ 2012-08-02 11:41:28.587+0000: 618: debug : virCgroupMakeGroup:546 : Make co= ntroller /sys/fs/cgroup/blkio/libvirt/qemu/milli/ 2012-08-02 11:41:28.587+0000: 618: debug : virCgroupRemove:758 : Removing c= group /sys/fs/cgroup/cpu,cpuacct/system/libvirtd.service/libvirt/qemu/milli= / and all child cgroups 2012-08-02 11:41:28.588+0000: 618: debug : virCgroupRemoveRecursively:713 := Removing cgroup /sys/fs/cgroup/cpu,cpuacct/system/libvirtd.service/libvirt= /qemu/milli//vcpu1 2012-08-02 11:41:28.595+0000: 618: debug : virCgroupRemoveRecursively:713 := Removing cgroup /sys/fs/cgroup/cpu,cpuacct/system/libvirtd.service/libvirt= /qemu/milli//vcpu0 2012-08-02 11:41:28.603+0000: 618: debug : virCgroupRemoveRecursively:713 := Removing cgroup /sys/fs/cgroup/cpu,cpuacct/system/libvirtd.service/libvirt= /qemu/milli/ 2012-08-02 11:41:28.611+0000: 618: debug : virCgroupRemove:758 : Removing c= group /sys/fs/cgroup/cpu,cpuacct/system/libvirtd.service/libvirt/qemu/milli= / and all child cgroups 2012-08-02 11:41:28.611+0000: 618: debug : virCgroupRemove:758 : Removing c= group /sys/fs/cgroup/cpuset/libvirt/qemu/milli/ and all child cgroups 2012-08-02 11:41:28.611+0000: 618: debug : virCgroupRemoveRecursively:713 := Removing cgroup /sys/fs/cgroup/cpuset/libvirt/qemu/milli/ 2012-08-02 11:41:28.620+0000: 618: debug : virCgroupRemove:758 : Removing c= group /sys/fs/cgroup/memory/libvirt/qemu/milli/ and all child cgroups 2012-08-02 11:41:28.620+0000: 618: debug : virCgroupRemoveRecursively:713 := Removing cgroup /sys/fs/cgroup/memory/libvirt/qemu/milli/ 2012-08-02 11:41:28.633+0000: 618: debug : virCgroupRemove:758 : Removing c= group /sys/fs/cgroup/devices/libvirt/qemu/milli/ and all child cgroups 2012-08-02 11:41:28.679+0000: 618: debug : virCgroupRemoveRecursively:713 := Removing cgroup /sys/fs/cgroup/devices/libvirt/qemu/milli/ 2012-08-02 11:41:28.684+0000: 618: debug : virCgroupRemove:758 : Removing c= group /sys/fs/cgroup/freezer/libvirt/qemu/milli/ and all child cgroups 2012-08-02 11:41:28.684+0000: 618: debug : virCgroupRemoveRecursively:713 := Removing cgroup /sys/fs/cgroup/freezer/libvirt/qemu/milli/ 2012-08-02 11:41:28.689+0000: 618: debug : virCgroupRemove:758 : Removing c= group /sys/fs/cgroup/blkio/libvirt/qemu/milli/ and all child cgroups 2012-08-02 11:41:28.689+0000: 618: debug : virCgroupRemoveRecursively:713 := Removing cgroup /sys/fs/cgroup/blkio/libvirt/qemu/milli/ 2012-08-02 11:41:28.697+0000: 618: debug : virConnectClose:1496 : conn=3D0x= 7f49dc10fac0 2012-08-02 11:41:28.698+0000: 606: debug : virDomainFree:2345 : dom=3D0xaa0= ea0, (VM: name=3Dmilli, uuid=3D2291f0d8-6341-4821-8774-2ed84b8bccc1) 2012-08-02 11:41:28.700+0000: 618: debug : qemuDomainObjEndAsyncJob:887 : S= topping async job: migration out # rpm -qa | egrep '(vdsm|libvirt|sanlock|json)' | sort -d json-c-0.9-4.fc17.x86_64 json-glib-0.14.2-2.fc17.x86_64 libvirt-0.9.11.4-3.fc17.x86_64 libvirt-client-0.9.11.4-3.fc17.x86_64 libvirt-daemon-0.9.11.4-3.fc17.x86_64 libvirt-daemon-config-network-0.9.11.4-3.fc17.x86_64 libvirt-daemon-config-nwfilter-0.9.11.4-3.fc17.x86_64 libvirt-lock-sanlock-0.9.11.4-3.fc17.x86_64 libvirt-python-0.9.11.4-3.fc17.x86_64 python-simplejson-2.5.2-1.fc17.x86_64 sanlock-2.3-3.fc17.x86_64 sanlock-lib-2.3-3.fc17.x86_64 sanlock-python-2.3-3.fc17.x86_64 vdsm-4.10.0-5.fc17.x86_64 vdsm-cli-4.10.0-5.fc17.noarch vdsm-python-4.10.0-5.fc17.x86_64 vdsm-xmlrpc-4.10.0-5.fc17.noarch Best Regards ---------------------------------------------------------------------------= ---- Karli Sj=F6berg Swedish University of Agricultural Sciences Box 7079 (Visiting Address Kron=E5sv=E4gen 8) S-750 07 Uppsala, Sweden Phone: +46-(0)18-67 15 66 karli.sjoberg(a)slu.se<mailto:karli.sjoberg@adm.slu.se> --_000_0CBBF9E4118E4C0C82215A5FE4D6D522sluse_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:= space; -webkit-line-break: after-white-space; ">Hi,<div><br></div><div><di= v>Wondering if anyone has encountered the same issue as me. On one host in = my cluster, if I migrate in a guest, I cannot migrate it out to another hos= t?  The get "stuck" there, so to speak. Same when a guest is started o= n that particular host, it is impossible to migrate them out again.</d= iv><div><br></div><div>iptables are flushed, for excluding purposes. v= dsmd, libvirtd and sanlock are all running.</div><div><br></div><div>This i= s what I caught from libvirtd.log:</div><div>2012-08-02 11:44:07.542+0000: = 4231: debug : qemuMonitorUnref:248 : QEMU_MONITOR_UNREF: mon=3D0x7fe7e40c84= 10 refs=3D3</div><div><div>2012-08-02 11:44:07.542+0000: 4232: debug : qemu= MonitorUnref:248 : QEMU_MONITOR_UNREF: mon=3D0x7fe7e40c8410 refs=3D2</div><= div>2012-08-02 11:44:07.542+0000: 4232: debug : virConnectIsAlive:18395 : c= onn=3D0x7fe7e00c4e50</div><div>2012-08-02 11:44:07.562+0000: 4236: debug : = virDomainMigrateSetMaxDowntime:16565 : dom=3D0x7fe7d8000cc0, (VM: name=3Dmi= lli, uuid=3D2291f0d8-6341-4821-8774-2ed84b8bccc1), downtime=3D50, flags=3D0= </div><div>2012-08-02 11:44:07.562+0000: 4236: debug : qemuDomainObjBeginJo= bInternal:753 : Starting job: migration operation (async=3Dmigration out)</= div><div>2012-08-02 11:44:07.562+0000: 4236: debug : qemuDomainMigrateSetMa= xDowntime:9500 : Setting migration downtime to 50ms</div><div>2012-08-02 11= :44:07.562+0000: 4236: debug : qemuMonitorRef:239 : QEMU_MONITOR_REF: mon= =3D0x7fe7e40c8410 refs=3D3</div><div>2012-08-02 11:44:07.562+0000: 4236: de= bug : qemuMonitorSetMigrationDowntime:1753 : mon=3D0x7fe7e40c8410 downtime= =3D50</div><div>2012-08-02 11:44:07.562+0000: 4236: debug : qemuMonitorSend= :861 : QEMU_MONITOR_SEND_MSG: mon=3D0x7fe7e40c8410 msg=3D{"execute":"migrat= e_set_downtime","arguments":{"value":0,050000},"id":"libvirt-261"}</div><di= v> fd=3D-1</div><div>2012-08-02 11:44:07.563+0000: 4231: debug : qemuM= onitorRef:239 : QEMU_MONITOR_REF: mon=3D0x7fe7e40c8410 refs=3D4</div><div>2= 012-08-02 11:44:07.563+0000: 4231: debug : qemuMonitorIOWrite:470 : QEMU_MO= NITOR_IO_WRITE: mon=3D0x7fe7e40c8410 buf=3D{"execute":"migrate_set_downtime= ","arguments":{"value":0,050000},"id":"libvirt-261"}</div><div> len=3D= 86 ret=3D86 errno=3D11</div><div>2012-08-02 11:44:07.563+0000: 4231: debug = : qemuMonitorUnref:248 : QEMU_MONITOR_UNREF: mon=3D0x7fe7e40c8410 refs=3D3<= /div><div>2012-08-02 11:44:07.564+0000: 4231: debug : qemuMonitorRef:239 : = QEMU_MONITOR_REF: mon=3D0x7fe7e40c8410 refs=3D4</div><div>2012-08-02 11:44:= 07.564+0000: 4231: debug : qemuMonitorIOProcess:365 : QEMU_MONITOR_IO_PROCE= SS: mon=3D0x7fe7e40c8410 buf=3D{"error": {"class": "JSONParsing", "desc": "= Invalid JSON syntax", "data": {}}}</div><div> len=3D80</div><div>2012-= 08-02 11:44:07.564+0000: 4231: debug : qemuMonitorUnref:248 : QEMU_MONITOR_= UNREF: mon=3D0x7fe7e40c8410 refs=3D3</div><div>2012-08-02 11:44:07.564+0000= : 4236: error : qemuMonitorJSONCheckError:331 : internal error unable to ex= ecute QEMU command 'migrate_set_downtime': Invalid JSON syntax</div><div>20= 12-08-02 11:44:07.564+0000: 4236: debug : qemuMonitorUnref:248 : QEMU_MONIT= OR_UNREF: mon=3D0x7fe7e40c8410 refs=3D2</div><div>2012-08-02 11:44:07.564+0= 000: 4236: debug : qemuDomainObjEndJob:870 : Stopping job: migration operat= ion (async=3Dmigration out)</div><div>2012-08-02 11:44:07.564+0000: 4231: d= ebug : qemuMonitorRef:239 : QEMU_MONITOR_REF: mon=3D0x7fe7e40c8410 refs=3D3= </div><div>2012-08-02 11:44:07.564+0000: 4231: debug : qemuMonitorIOProcess= :365 : QEMU_MONITOR_IO_PROCESS: mon=3D0x7fe7e40c8410 buf=3D{"error": {"clas= s": "JSONParsing", "desc": "Invalid JSON syntax", "data": {}}}</div><div>&n= bsp;len=3D80</div><div>2012-08-02 11:44:07.564+0000: 4236: debug : virDomai= nFree:2345 : dom=3D0x7fe7d8000cc0, (VM: name=3Dmilli, uuid=3D2291f0d8-6341-= 4821-8774-2ed84b8bccc1)</div><div>2012-08-02 11:44:07.564+0000: 4231: error= : qemuMonitorJSONIOProcessLine:156 : internal error Unexpected JSON reply = '{"error": {"class": "JSONParsing", "desc": "Invalid JSON syntax", "data": = {}}}'</div><div>2012-08-02 11:44:07.564+0000: 4231: debug : qemuMonitorIO:6= 45 : Error on monitor internal error Unexpected JSON reply '{"error": {"cla= ss": "JSONParsing", "desc": "Invalid JSON syntax", "data": {}}}'</div><div>= 2012-08-02 11:44:07.564+0000: 4231: debug : qemuMonitorUnref:248 : QEMU_MON= ITOR_UNREF: mon=3D0x7fe7e40c8410 refs=3D2</div><div>2012-08-02 11:44:07.564= +0000: 4231: debug : qemuMonitorIO:679 : Triggering error callback</div><di= v>2012-08-02 11:44:07.564+0000: 4231: debug : qemuProcessHandleMonitorError= :345 : Received error on 0x7fe7e4000e50 'milli'</div><div>2012-08-02 11:44:= 07.592+0000: 4232: debug : qemuDomainObjBeginJobInternal:753 : Starting job= : async nested (async=3Dmigration out)</div><div>2012-08-02 11:44:07.593+00= 00: 4232: debug : qemuMonitorRef:239 : QEMU_MONITOR_REF: mon=3D0x7fe7e40c84= 10 refs=3D3</div><div>2012-08-02 11:44:07.593+0000: 4232: debug : qemuMonit= orGetMigrationStatus:1776 : mon=3D0x7fe7e40c8410</div><div>2012-08-02 11:44= :07.593+0000: 4232: debug : qemuMonitorSend:851 : Attempt to send command w= hile error is set internal error Unexpected JSON reply '{"error": {"class":= "JSONParsing", "desc": "Invalid JSON syntax", "data": {}}}'</div><div>2012= -08-02 11:44:07.593+0000: 4232: debug : qemuMonitorUnref:248 : QEMU_MONITOR= _UNREF: mon=3D0x7fe7e40c8410 refs=3D2</div><div>2012-08-02 11:44:07.593+000= 0: 4232: debug : doPeer2PeerMigrate3:2425 : Finish3 0x7fe7e00c4e50 ret=3D-1= </div><div>2012-08-02 11:44:08.798+0000: 4233: debug : virDomainInterfaceSt= ats:7299 : dom=3D0x7fe7e40c72d0, (VM: name=3Dmilli, uuid=3D2291f0d8-6341-48= 21-8774-2ed84b8bccc1), path=3Dvnet0, stats=3D0x7fe803e45b10, size=3D64</div= ><div>2012-08-02 11:44:08.802+0000: 4233: debug : virDomainFree:2345 : dom= =3D0x7fe7e40c72d0, (VM: name=3Dmilli, uuid=3D2291f0d8-6341-4821-8774-2ed84b= 8bccc1)</div><div>2012-08-02 11:44:12.564+0000: 4234: debug : virDomainGetJ= obInfo:16465 : dom=3D0x7fe7dc000e00, (VM: name=3Dmilli, uuid=3D2291f0d8-634= 1-4821-8774-2ed84b8bccc1), info=3D0x7fe803644af0</div><div>2012-08-02 11:44= :12.564+0000: 4234: debug : virDomainFree:2345 : dom=3D0x7fe7dc000e00, (VM:= name=3Dmilli, uuid=3D2291f0d8-6341-4821-8774-2ed84b8bccc1)</div><div>2012-= 08-02 11:44:13.804+0000: 4235: debug : virDomainGetInfo:4298 : dom=3D0x7fe7= e8001bd0, (VM: name=3Dmilli, uuid=3D2291f0d8-6341-4821-8774-2ed84b8bccc1), = info=3D0x7fe802e43b20</div><div>2012-08-02 11:44:13.805+0000: 4235: debug := qemudGetProcessInfo:1156 : Got status for 5448/0 user=3D1770 sys=3D1445 cp= u=3D0 rss=3D185496</div><div>2012-08-02 11:44:13.805+0000: 4235: debug : vi= rDomainFree:2345 : dom=3D0x7fe7e8001bd0, (VM: name=3Dmilli, uuid=3D2291f0d8= -6341-4821-8774-2ed84b8bccc1)</div><div>2012-08-02 11:44:13.806+0000: 4238:= debug : virDomainInterfaceStats:7299 : dom=3D0x7fe7f0002520, (VM: name=3Dm= illi, uuid=3D2291f0d8-6341-4821-8774-2ed84b8bccc1), path=3Dvnet0, stats=3D0= x7fe801640b10, size=3D64</div><div>2012-08-02 11:44:13.807+0000: 4238: debu= g : virDomainFree:2345 : dom=3D0x7fe7f0002520, (VM: name=3Dmilli, uuid=3D22= 91f0d8-6341-4821-8774-2ed84b8bccc1)</div><div>2012-08-02 11:44:16.474+0000:= 4232: error : virNetClientProgramDispatchError:174 : An error occurred, bu= t the cause is unknown</div><div>2012-08-02 11:44:16.474+0000: 4232: debug = : doPeer2PeerMigrate3:2458 : Confirm3 0x7fe7e40029c0 ret=3D-1 vm=3D0x7fe7e4= 000e50</div><div>2012-08-02 11:44:16.474+0000: 4232: debug : qemuMigrationC= onfirm:3109 : driver=3D0x7fe7f80bd9c0, conn=3D0x7fe7e40029c0, vm=3D0x7fe7e4= 000e50, cookiein=3D(null), cookieinlen=3D0, flags=3D3, retcode=3D1</div><di= v>2012-08-02 11:44:16.474+0000: 4232: debug : qemuMigrationEatCookie:752 : = cookielen=3D0 cookie=3D'(null)'</div><div>2012-08-02 11:44:16.475+0000: 423= 2: debug : qemuProcessStartCPUs:2644 : Using lock state '(null)'</div><div>= 2012-08-02 11:44:16.475+0000: 4232: debug : qemuDomainObjBeginJobInternal:7= 53 : Starting job: async nested (async=3Dmigration out)</div></div><div><br= ></div><div>And this is from a migration gone well:</div><div><div>2012-08-= 02 11:41:28.386+0000: 618: debug : qemuProcessStop:3872 : Shutting down VM = 'milli' pid=3D3776 flags=3D1</div><div>2012-08-02 11:41:28.386+0000: 618: d= ebug : qemuMonitorClose:797 : QEMU_MONITOR_CLOSE: mon=3D0x7f49dc000d50 refs= =3D2</div><div>2012-08-02 11:41:28.386+0000: 618: debug : qemuMonitorUnref:= 248 : QEMU_MONITOR_UNREF: mon=3D0x7f49dc000d50 refs=3D1</div><div>2012-08-0= 2 11:41:28.386+0000: 606: debug : qemuMonitorUnref:248 : QEMU_MONITOR_UNREF= : mon=3D0x7f49dc000d50 refs=3D0</div><div>2012-08-02 11:41:28.386+0000: 606= : debug : qemuMonitorFree:225 : mon=3D0x7f49dc000d50</div><div>2012-08-02 1= 1:41:28.386+0000: 618: debug : qemuProcessKill:3769 : vm=3Dmilli pid=3D3776= flags=3D5</div><div>2012-08-02 11:41:28.586+0000: 618: debug : qemuDomainC= leanupRun:1921 : driver=3D0x7f49e806f1b0, vm=3Dmilli</div><div>2012-08-02 1= 1:41:28.586+0000: 618: debug : qemuProcessAutoDestroyRemove:4320 : vm=3Dmil= li</div><div>2012-08-02 11:41:28.586+0000: 618: debug : qemuDriverCloseCall= backUnset:578 : vm=3Dmilli, uuid=3D2291f0d8-6341-4821-8774-2ed84b8bccc1, cb= =3D0x4900d0</div><div>2012-08-02 11:41:28.586+0000: 618: debug : virCgroupN= ew:603 : New group /libvirt/qemu/milli</div><div>2012-08-02 11:41:28.587+00= 00: 618: debug : virCgroupDetect:262 : Detected mount/mapping 0:cpu at /sys= /fs/cgroup/cpu,cpuacct in /system/libvirtd.service</div><div>2012-08-02 11:= 41:28.587+0000: 618: debug : virCgroupDetect:262 : Detected mount/mapping 1= :cpuacct at /sys/fs/cgroup/cpu,cpuacct in /system/libvirtd.service</div><di= v>2012-08-02 11:41:28.587+0000: 618: debug : virCgroupDetect:262 : Detected= mount/mapping 2:cpuset at /sys/fs/cgroup/cpuset in</div><div>2012-08-02 11= :41:28.587+0000: 618: debug : virCgroupDetect:262 : Detected mount/mapping = 3:memory at /sys/fs/cgroup/memory in</div><div>2012-08-02 11:41:28.587+0000= : 618: debug : virCgroupDetect:262 : Detected mount/mapping 4:devices at /s= ys/fs/cgroup/devices in</div><div>2012-08-02 11:41:28.587+0000: 618: debug = : virCgroupDetect:262 : Detected mount/mapping 5:freezer at /sys/fs/cgroup/= freezer in</div><div>2012-08-02 11:41:28.587+0000: 618: debug : virCgroupDe= tect:262 : Detected mount/mapping 6:blkio at /sys/fs/cgroup/blkio in</div><= div>2012-08-02 11:41:28.587+0000: 618: debug : virCgroupMakeGroup:524 : Mak= e group /libvirt/qemu/milli</div><div>2012-08-02 11:41:28.587+0000: 618: de= bug : virCgroupMakeGroup:546 : Make controller /sys/fs/cgroup/cpu,cpuacct/s= ystem/libvirtd.service/libvirt/qemu/milli/</div><div>2012-08-02 11:41:28.58= 7+0000: 618: debug : virCgroupMakeGroup:546 : Make controller /sys/fs/cgrou= p/cpu,cpuacct/system/libvirtd.service/libvirt/qemu/milli/</div><div>2012-08= -02 11:41:28.587+0000: 618: debug : virCgroupMakeGroup:546 : Make controlle= r /sys/fs/cgroup/cpuset/libvirt/qemu/milli/</div><div>2012-08-02 11:41:28.5= 87+0000: 618: debug : virCgroupMakeGroup:546 : Make controller /sys/fs/cgro= up/memory/libvirt/qemu/milli/</div><div>2012-08-02 11:41:28.587+0000: 618: = debug : virCgroupMakeGroup:546 : Make controller /sys/fs/cgroup/devices/lib= virt/qemu/milli/</div><div>2012-08-02 11:41:28.587+0000: 618: debug : virCg= roupMakeGroup:546 : Make controller /sys/fs/cgroup/freezer/libvirt/qemu/mil= li/</div><div>2012-08-02 11:41:28.587+0000: 618: debug : virCgroupMakeGroup= :546 : Make controller /sys/fs/cgroup/blkio/libvirt/qemu/milli/</div><div>2= 012-08-02 11:41:28.587+0000: 618: debug : virCgroupRemove:758 : Removing cg= roup /sys/fs/cgroup/cpu,cpuacct/system/libvirtd.service/libvirt/qemu/milli/= and all child cgroups</div><div>2012-08-02 11:41:28.588+0000: 618: debug := virCgroupRemoveRecursively:713 : Removing cgroup /sys/fs/cgroup/cpu,cpuacc= t/system/libvirtd.service/libvirt/qemu/milli//vcpu1</div><div>2012-08-02 11= :41:28.595+0000: 618: debug : virCgroupRemoveRecursively:713 : Removing cgr= oup /sys/fs/cgroup/cpu,cpuacct/system/libvirtd.service/libvirt/qemu/milli//= vcpu0</div><div>2012-08-02 11:41:28.603+0000: 618: debug : virCgroupRemoveR= ecursively:713 : Removing cgroup /sys/fs/cgroup/cpu,cpuacct/system/libvirtd= .service/libvirt/qemu/milli/</div><div>2012-08-02 11:41:28.611+0000: 618: d= ebug : virCgroupRemove:758 : Removing cgroup /sys/fs/cgroup/cpu,cpuacct/sys= tem/libvirtd.service/libvirt/qemu/milli/ and all child cgroups</div><div>20= 12-08-02 11:41:28.611+0000: 618: debug : virCgroupRemove:758 : Removing cgr= oup /sys/fs/cgroup/cpuset/libvirt/qemu/milli/ and all child cgroups</div><d= iv>2012-08-02 11:41:28.611+0000: 618: debug : virCgroupRemoveRecursively:71= 3 : Removing cgroup /sys/fs/cgroup/cpuset/libvirt/qemu/milli/</div><div>201= 2-08-02 11:41:28.620+0000: 618: debug : virCgroupRemove:758 : Removing cgro= up /sys/fs/cgroup/memory/libvirt/qemu/milli/ and all child cgroups</div><di= v>2012-08-02 11:41:28.620+0000: 618: debug : virCgroupRemoveRecursively:713= : Removing cgroup /sys/fs/cgroup/memory/libvirt/qemu/milli/</div><div>2012= -08-02 11:41:28.633+0000: 618: debug : virCgroupRemove:758 : Removing cgrou= p /sys/fs/cgroup/devices/libvirt/qemu/milli/ and all child cgroups</div><di= v>2012-08-02 11:41:28.679+0000: 618: debug : virCgroupRemoveRecursively:713= : Removing cgroup /sys/fs/cgroup/devices/libvirt/qemu/milli/</div><div>201= 2-08-02 11:41:28.684+0000: 618: debug : virCgroupRemove:758 : Removing cgro= up /sys/fs/cgroup/freezer/libvirt/qemu/milli/ and all child cgroups</div><d= iv>2012-08-02 11:41:28.684+0000: 618: debug : virCgroupRemoveRecursively:71= 3 : Removing cgroup /sys/fs/cgroup/freezer/libvirt/qemu/milli/</div><div>20= 12-08-02 11:41:28.689+0000: 618: debug : virCgroupRemove:758 : Removing cgr= oup /sys/fs/cgroup/blkio/libvirt/qemu/milli/ and all child cgroups</div><di= v>2012-08-02 11:41:28.689+0000: 618: debug : virCgroupRemoveRecursively:713= : Removing cgroup /sys/fs/cgroup/blkio/libvirt/qemu/milli/</div><div>2012-= 08-02 11:41:28.697+0000: 618: debug : virConnectClose:1496 : conn=3D0x7f49d= c10fac0</div><div>2012-08-02 11:41:28.698+0000: 606: debug : virDomainFree:= 2345 : dom=3D0xaa0ea0, (VM: name=3Dmilli, uuid=3D2291f0d8-6341-4821-8774-2e= d84b8bccc1)</div><div>2012-08-02 11:41:28.700+0000: 618: debug : qemuDomain= ObjEndAsyncJob:887 : Stopping async job: migration out</div></div><div><br>= </div><div><div><div># rpm -qa | egrep '(vdsm|libvirt|sanlock|json)' | sort= -d</div><div>json-c-0.9-4.fc17.x86_64</div><div>json-glib-0.14.2-2.fc17.x8= 6_64</div><div>libvirt-0.9.11.4-3.fc17.x86_64</div><div>libvirt-client-0.9.= 11.4-3.fc17.x86_64</div><div>libvirt-daemon-0.9.11.4-3.fc17.x86_64</div><di= v>libvirt-daemon-config-network-0.9.11.4-3.fc17.x86_64</div><div>libvirt-da= emon-config-nwfilter-0.9.11.4-3.fc17.x86_64</div><div>libvirt-lock-sanlock-= 0.9.11.4-3.fc17.x86_64</div><div>libvirt-python-0.9.11.4-3.fc17.x86_64</div= ><div>python-simplejson-2.5.2-1.fc17.x86_64</div><div>sanlock-2.3-3.fc17.x8= 6_64</div><div>sanlock-lib-2.3-3.fc17.x86_64</div><div>sanlock-python-2.3-3= .fc17.x86_64</div><div>vdsm-4.10.0-5.fc17.x86_64</div><div>vdsm-cli-4.10.0-= 5.fc17.noarch</div><div>vdsm-python-4.10.0-5.fc17.x86_64</div><div>vdsm-xml= rpc-4.10.0-5.fc17.noarch</div></div></div><div> <div><br class=3D"Apple-interchange-newline"><br></div><div>Best Regards<br= >--------------------------------------------------------------------------= -----<br>Karli Sj=F6berg<br>Swedish University of Agricultural Sciences<br>= Box 7079 (Visiting Address Kron=E5sv=E4gen 8)<br>S-750 07 Uppsala, Sweden<b= r>Phone:  +46-(0)18-67 15 66</div><div><a href=3D"mailto:karli.sjoberg= @adm.slu.se">karli.sjoberg(a)slu.se</a></div> </div> <br></div></body></html>= --_000_0CBBF9E4118E4C0C82215A5FE4D6D522sluse_--

3 6

[Users] Fwd: [jboss-rpm] New jboss-as update (7.1.1-6)
by Itamar Heim 02 Aug '12

02 Aug '12

fyi -------- Original Message -------- Subject: [jboss-rpm] New jboss-as update (7.1.1-6) Date: Thu, 02 Aug 2012 10:47:28 +0200 From: Marek Goldmann <mgoldman(a)redhat.com> To: jboss-rpm(a)lists.jboss.org <jboss-rpm(a)lists.jboss.org> Hi all, I just submitted a new update (7.1.1-6) to Fedora. This is a bugfix release which fixes issues with oVirt: - https://bugzilla.redhat.com/show_bug.cgi?id=843285 - https://bugzilla.redhat.com/show_bug.cgi?id=844554 - https://bugzilla.redhat.com/show_bug.cgi?id=842997 - https://bugzilla.redhat.com/show_bug.cgi?id=842996 (All above issues are talking about the same thing) Additionally a fix preventing the package from building from source was applied. Once it hits testing, please give it a try and bump the karma: https://admin.fedoraproject.org/updates/jboss-as-7.1.1-6.fc17 Thanks! --Marek _______________________________________________ jboss-rpm mailing list jboss-rpm(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-rpm

1 0

[Users] oVirt has been approved for inclusion in Fedora 18
by Yaniv Kaul 02 Aug '12

02 Aug '12

This is a multi-part message in MIME format. --------------030707040702020007010301 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit >From http://lists.fedoraproject.org/pipermail/devel/2012-July/170410.html : * #913 F18 Feature: oVirt engine 3.1 - https://fedoraproject.org/wiki/Features/oVirtEngine_3.1 (mmaslano, 17:20:45) * AGREED: oVirt is approved as a feature (+7,-0) (mmaslano, 17:23:49) --------------030707040702020007010301 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> From <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <a href="http://lists.fedoraproject.org/pipermail/devel/2012-July/170410.html">http://lists.fedoraproject.org/pipermail/devel/2012-July/170410.html</a> :<br> <br> * #913 F18 Feature: oVirt engine 3.1 -<br>   <a class="moz-txt-link-freetext" href="https://fedoraproject.org/wiki/Features/oVirtEngine_3.1">https://fedoraproject.org/wiki/Features/oVirtEngine_3.1</a>  (mmaslano,<br>   17:20:45)<br>   * AGREED: oVirt is approved as a feature (+7,-0)  (mmaslano, 17:23:49)<br> </body> </html> --------------030707040702020007010301--

4 3

[Users] host raiding two LUN from different external storage
by Johan Kragsterman 02 Aug '12

02 Aug '12

Hi! In some setups, like when you got two datacenters that works like failover sites, you would like to have two external raid controllers(storage devices), one in each datacenter. You then send two identical LUN's, from each controller, to a cluster, let's say two hosts, for simplicity. What you normally do is to host raid these LUN's in mirror(raid 1), so the hosts write the same to both LUN's, and both controllers. Question for me here is if I can accomplish this in oVirt management? Because if I can't, it will be a problem, because if I host raid at the host level, then the storage would be local storage for oVirt, wouldn't it? And then I suppose it can't be used for live migration, can it? Regrds Johan

3 6