[CentOS-virt] CentOS 6 Xen virt* issues

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

I just upgraded some of my el6xen boxes to latest CentOS 6.7, Xen 4.4.3 and 
dom0 3.18.17 rpms, and noticed these new problems:


1) virt-manager fails to start with an error: "D-Bus library appears to be 
incorrectly set up; failed to read machine uuid: Failed to open 
"/var/lib/dbus/machine-id": No such file or directory"

And indeed.. there was no such file. Running command "dbus-uuidgen --ensure" 
fixed it, and virt-manager starts OK after that. So this was more for the 
mailinglist archives, if someone else meets the same issue.


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

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

2015-09-26 Thread Pasi Kärkkäinen 
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.. 


Thanks,

-- Pasi


>  -George


___
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-26 Thread Pasi Kärkkäinen 
On Sat, Sep 26, 2015 at 09:04:23PM +0300, Pasi Kärkkäinen wrote:
> Hello,
> 
> I just upgraded some of my el6xen boxes to latest CentOS 6.7, Xen 4.4.3 and 
> dom0 3.18.17 rpms, and noticed these new problems:
> 

And third issue aswell:

3) Creating an HVM guest using virt-manager with file-based storage uses 
loopback-mount, not blktap

When I manually create a new Xen HVM guest using virt-manager, and choose 
file-based image for storage of the VM, it seems to be set up to use file: 
backend/driver with loopback-mounted image file:


  
  
  
  


# losetup -a
/dev/loop0: [fd00]:1709109 (/var/lib/libvirt/images/testvm2.img)

With earlier versions of rpms similar setup used blktap2 backend.. (and yes, I 
do have blktap module loaded in dom0 kernel).


Thanks,

-- Pasi

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