Re: [CentOS-virt] CentOS 7 Xen 4.4.3 packages available for in virt7-xen-44-testing

2015-09-27 Thread Pasi Kärkkäinen 
On Sat, Sep 26, 2015 at 08:51:37PM +0300, Pasi Kärkkäinen wrote:
> On Tue, Sep 22, 2015 at 12:08:12PM +0100, George Dunlap wrote:
> > 
> > > Anyway, here's something I noticed while testing xend bits:
> > >
> > > # systemctl enable xend.service
> > > xend.service is not a native service, redirecting to /sbin/chkconfig.
> > > Executing /sbin/chkconfig xend on
> > > The unit files have no [Install] section. They are not meant to be enabled
> > > using systemctl.
> > > Possible reasons for having this kind of units are:
> > > 1) A unit may be statically enabled by being symlinked from another unit's
> > >.wants/ or .requires/ directory.
> > > 2) A unit's purpose may be to act as a helper for some other unit which 
> > > has
> > >a requirement dependency on it.
> > > 3) A unit may be started when needed via activation (socket, path, timer,
> > >D-Bus, udev, scripted systemctl call, ...).
> > >
> > >
> > > "systemctl start xend.service" works OK though.. and after that xm works 
> > > too.
> > 
> > Right -- I haven't tried xend under systemd.  Given that xend is gone
> > in 4.6, I'm considering whether to say "patches welcome" re fixing
> > xend in 4.4 for C7...
> > 
> 
> I'll try to investigate.. 
> 

Actually it seems those were "warnings" only.. xend does start automatically 
now on centos7. 
So it's not a problem really.


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] xen and centos7

2015-09-27 Thread Christoph 

Am 2015-09-25 17:25, schrieb George Dunlap:

The code is from the XenProject, which is developed by a number of
different companies, not just Citrix.

The XenProject has greatly expanded our automated testing over the
last few years; additionally, a number of different companies have
their own automated test suites (Oracle, XenServer), and test the
development branches regularly.

The bugs we've found since RC1 have been almost entirely in niche
cases -- enabling this feature broke that bit of hardware; switching
this caused that obscure configuration not to work quite right; adding
this build option breaks things with that particular compiler.

All that to say, RC3 is pretty close to what the final release will
be.  The main thing that needs testing is actually the packaging
effort -- is it easy to install? Does it upgrade properly? 

And the main thing holding up the official C7 release (for either of
them) is just testing.  The more people install, test it, and say
"this works for me" (or report bugs when it doesnt' work), the sooner
the release will come. :-)

 -George


it works for me since 2 days without issues... only one thing what I 
needed to change was the path of pvgrub :) (from /usr/lib... to 
/usr/lib64...)


--
--
Greetz
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 6 Xen virt* issues

2015-09-27 Thread Pasi Kärkkäinen 
Hello,

Replying to myself.. see below for more details about the problem.

On Sat, Sep 26, 2015 at 09:04:23PM +0300, Pasi Kärkkäinen wrote:
> 
> 2) virt-viewer doesn't work anymore. 
> 
> It seems in el6.6 virt-viewer was version 0.6.0-11, but now in el6.7 it's 
> 2.0-7, with a lot of changes..
> 
> If I try to use virt-viewer and run "virt-viewer " command, I get an 
> error popup dialog saying "Failed to connect: Display can only be attached 
> through libvirt with --attach".
> 
> verbose debug output:
> 
> 
> # virt-viewer -v --debug -c "xen://" testvm
> 
> (virt-viewer:9420): virt-viewer-DEBUG: Set connect info: 
> (null),(null),(null),-1,(null),(null),(null),0
> [root@fdell01 rpm]# less testvm01.txt 
> (virt-viewer:9374): virt-viewer-DEBUG: connecting ...
> (virt-viewer:9374): virt-viewer-DEBUG: Opening connection to libvirt with URI 
> xen://
> Opening connection to libvirt with URI xen://
> (virt-viewer:9374): virt-viewer-DEBUG: Add handle 7 1 0x865520
> (virt-viewer:9374): virt-viewer-DEBUG: initial connect
> (virt-viewer:9374): virt-viewer-DEBUG: notebook show status 0x7f
> (virt-viewer:9374): virt-viewer-DEBUG: virt_viewer_app_set_uuid_string: UUID 
> changed to 587eb1bf-2427-a4d3-9113-d8bfb9911212
> (virt-viewer:9374): virt-viewer-DEBUG: No guest-specific fullscreen config, 
> using fallback
> (virt-viewer:9374): virt-viewer-DEBUG: notebook show status 0x7f
> (virt-viewer:9374): virt-viewer-DEBUG: Guest testvm is running, determining 
> display
> Guest testvm is running, determining display
> (virt-viewer:9374): virt-viewer-DEBUG: Set connect info: 
> (null),(null),(null),-1,(null),(null),(null),0
> (virt-viewer:9374): virt-viewer-DEBUG: Guest testvm has a vnc display
> Guest testvm has a vnc display
> (virt-viewer:9374): virt-viewer-DEBUG: Using direct libvirt connection
> (virt-viewer:9374): virt-viewer-DEBUG: Error operation forbidden: read only 
> access prevents virDomainOpenGraphics
> (virt-viewer:9374): virt-viewer-DEBUG: After open connection callback fd=-1
> (virt-viewer:9374): virt-viewer-DEBUG: Remove handle 1 7
> (virt-viewer:9374): virt-viewer-DEBUG: Disposing window 0x7e1820
> 
> (virt-viewer:9374): virt-viewer-DEBUG: Set connect info: 
> (null),(null),(null),-1,(null),(null),(null),0
> 
> 
> And trying with the "attach" option:
> 
> # virt-viewer -v --debug -c "xen://" -a testvm
> 
> (virt-viewer:9374): virt-viewer-DEBUG: Set connect info: 
> (null),(null),(null),-1,(null),(null),(null),0
> [root@fdell01 rpm]# less testvm02.txt 
> (virt-viewer:9389): virt-viewer-DEBUG: connecting ...
> (virt-viewer:9389): virt-viewer-DEBUG: Opening connection to libvirt with URI 
> xen://
> Opening connection to libvirt with URI xen://
> (virt-viewer:9389): virt-viewer-DEBUG: Add handle 7 1 0x13ef580
> (virt-viewer:9389): virt-viewer-DEBUG: initial connect
> (virt-viewer:9389): virt-viewer-DEBUG: notebook show status 0x137a000
> (virt-viewer:9389): virt-viewer-DEBUG: virt_viewer_app_set_uuid_string: UUID 
> changed to 587eb1bf-2427-a4d3-9113-d8bfb9911212
> (virt-viewer:9389): virt-viewer-DEBUG: No guest-specific fullscreen config, 
> using fallback
> (virt-viewer:9389): virt-viewer-DEBUG: notebook show status 0x137a000
> (virt-viewer:9389): virt-viewer-DEBUG: Guest testvm is running, determining 
> display
> Guest testvm is running, determining display
> (virt-viewer:9389): virt-viewer-DEBUG: Set connect info: 
> (null),(null),(null),-1,(null),(null),(null),0
> (virt-viewer:9389): virt-viewer-DEBUG: Guest testvm has a vnc display
> Guest testvm has a vnc display
> (virt-viewer:9389): virt-viewer-DEBUG: Using direct libvirt connection
> (virt-viewer:9389): virt-viewer-DEBUG: Error argument unsupported: fd passing 
> is not supported by this connection
> (virt-viewer:9389): virt-viewer-DEBUG: After open connection callback fd=-1
> (virt-viewer:9389): virt-viewer-DEBUG: Remove handle 1 7
> (virt-viewer:9389): virt-viewer-DEBUG: Disposing window 0x136b820
> 
> (virt-viewer:9389): virt-viewer-DEBUG: Set connect info: 
> (null),(null),(null),-1,(null),(null),(null),0
> 
> 
> 
> So it seems both connection types/methods now fail.. I'm not sure if the 
> issue is in our custom libvirt build, or in Xen's qemu.. (googling for those 
> errors reveals some related patches which also have patches for qemu: 
> http://comments.gmane.org/gmane.comp.emulators.virt-tools/9185)
> 
> Error from the first attempt:
> 
> (virt-viewer:9374): virt-viewer-DEBUG: Using direct libvirt connection
> (virt-viewer:9374): virt-viewer-DEBUG: Error operation forbidden: read only 
> access prevents virDomainOpenGraphics
> 
> Error from the second attempt:
> (virt-viewer:9389): virt-viewer-DEBUG: Using direct libvirt connection
> (virt-viewer:9389): virt-viewer-DEBUG: Error argument unsupported: fd passing 
> is not supported by this connection
> 

It seems CentOS 7.1 is still using virt-viewer version 0.6.0-12, and on centos7 
virt-viewer works OK for me with xen/libvirt! So it seems only the newer 
virt-viewer 2.0 on