similar to: Processed (with 1 errors): xen-utils-common: should allow local unix connections for virt-manager by default

Your message dated Fri, 29 Aug 2014 13:33:00 +0000 with message-id <20140829133300.GB4246 at shell.waldi.eu.org> and subject line xend support gone has caused the Debian Bug report #491660, regarding xen-utils-common: should allow local unix connections to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility

Processing commands for control at bugs.debian.org: > retitle 655301 xend shouldn't start if TOOLSTACK is not xm Bug #655301 [xcp-xapi] xcp-xapi fails to start Changed Bug title to 'xend shouldn't start if TOOLSTACK is not xm' from 'xcp-xapi fails to start' > reassign 655301 xen-utils-common Bug #655301 [xcp-xapi] xend shouldn't start if TOOLSTACK is not xm Bug

Hello i'm setting up a debian system, with no root acount, i manage it with the sudo command, and installed the new xen 3.3.0 on it than i installed fluxbox and vnc4server on this machine, to get remote access to the debian/xen system i use ssh and xvnc4viewer, ssh for the console and xvnc4viewer for the windowmanager, until than everything works fine. than i installed virt-manager from the

Processing commands for control at bugs.debian.org: > reassign 489323 xen-utils-common Bug #489323 [xen-3] [xen-utils-common] XenAPI authentification needs python-pam to work Warning: Unknown package 'xen-3' Bug reassigned from package 'xen-3' to 'xen-utils-common'. Ignoring request to alter found versions of bug #489323 to the same values previously set Ignoring

Hi, I am trying to operate the remote KVM host's virt-manager thru Terminal Server Client. This KVM hosts is CentOS6.0 and running KVM guest and xrdp is installed from "epel" repo. And I'm using fedora 14's Terminal Server Client. After I started Virtual Machine Manager and try to connect to the hypervisor, following error happened. Is there any way to resolve this error?

Hi, I install xen 4.1.2 on centos 6 with linux kernel 3.0.4 as dom0 kernel. When I launch virt-manager on the command line ,a window pop up which show the following error: Unable to open a connection to the Xen hypervisor/daemon. Verify that: - A Xen host kernel was booted - The Xen service has been started Details: Unable to open connection to hypervisor URI ''xen:///'': no

Hi, Wanting to test some recent features of libvirt, I installed 0.9.3 on a couple of systems. It works fine on those, but since upgrading neither of them can successfully connect with virt-manager or virsh to a couple of other systems running libvirt 0.8.3. Even after upgrading virt-manager and virtinst to the latest versions on the 0.9.3 systems, they fail like this in virt-manager: Unable

I get “Unable to connect to libvirt” when using virt-manager in combination with the XL toolstack and Xen 4.2.1. (No problems when using virt-manager in combination with the XM toolstack.) More details of the situation can be found in a bug-report that I filed on launchpad. Please see: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1180281 Judging from the information that I provided

Hello, I posted this yesterday to the Xen-devel list, posting it additionally to the fedoraproject list too. My problem is Virt-manager is unable to connect to the hypervisor (explained below). However, xm list, xm info work fine. So I followed the guide http://wiki.xen.org/wiki/Xen_4.2_Build_From_Source_On_RHEL_CentOS_Fedora and built/installed Xen from source, using grub2-mkconfig to rebuild

On Wed, Nov 11, 2015 at 01:02:34PM +0200, Shahar Havivi wrote: > On 03.11.15 15:37, Daniel P. Berrange wrote: > > On Tue, Nov 03, 2015 at 10:14:00AM +0200, Shahar Havivi wrote: > > > Hi, > > > > > > I am trying to connect to remote libvirt via script, > > > and I get password prompt from the shell. > > > > > > > > >

Control: retitle -1 max grant frames problem (domu freeze with linux-image-4.9.0-4-amd64) Control: severity -1 important Control: reassign -1 src:xen 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9 Just gardening here. (i) Bug title should mention grant frames. (ii) This does not affect all use cases and is not, IMO, RC. Although we should certainly see if we can improve it. (iii) Britney is confused

On 03.11.15 15:37, Daniel P. Berrange wrote: > On Tue, Nov 03, 2015 at 10:14:00AM +0200, Shahar Havivi wrote: > > Hi, > > > > I am trying to connect to remote libvirt via script, > > and I get password prompt from the shell. > > > > > > ============================================================================ > >

tags 660882 +upstream severity 660882 wishlist retitle 660882 pv network device does not support multicast thanks Hi Simon, I'm afraid the Xen PV drivers (on Linux at least) do not support multicast. There has historically been some support for multicast, IIRC the old Solaris front and backends did support it so there is some support defined but not implemented. e.g. see

Processing commands for control at bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.9.26 > package xen-utils-common Ignoring bugs not assigned to: xen-utils-common > reassign 489323 xen-3 Bug#489323: [xen-utils-common] XenAPI authentification needs python-pam to work Bug reassigned from package `xen-utils-common' to `xen-3'. > reassign 489325

retitle 593741 xen-utils-common: python-xml is not marked as a dependency and xm errors without it reassign 593741 xen-utils-common kthxbye Hi, Tyler wrote: > Package: xen-tools > Version: 3.9-4 > Severity: important > > When you start building a basic xen box: > > apt-get install xen-linux-system-2.6.26-2-xen-amd64 xen-tools > > You eventually get to: > >

When I run the python test code I got the SASL error. But it's ok if I run the C sample code. Do you know the reason?? Here is the message: libvir: RPC error : authentication failed: Failed to start SASL negotiation: -4 (SASL(-4): no mechanism available: No worthy mechs found) Traceback (most recent call last): ? File "esxList.py", line 101, in ? ? ? conn = libvirt.openAuth(uri,

Processing commands for control at bugs.debian.org: > severity 588406 important Bug #588406 [xen-utils-common] xen-utils-common: /etc/xen/scripts/block not driving helper scripts; XEN_SCRIPT_DIR not properly set Severity set to 'important' from 'normal' > tags 588406 patch Bug #588406 [xen-utils-common] xen-utils-common: /etc/xen/scripts/block not driving helper scripts;

Processing commands for control at bugs.debian.org: > reassign 555902 xen-utils-common 3.3.1-2 Bug #555902 {Done: Bastian Blank <waldi at debian.org>} [xen-utils-3.4] xen-utils-3.4: /etc/init.d/xend - $DAEMON variable at xend_stop() Bug reassigned from package 'xen-utils-3.4' to 'xen-utils-common'. Bug No longer marked as found in versions xen-3/3.4.0-2. Bug No longer

Processing commands for control at bugs.debian.org: > reassign 628912 xen-utils-common 4.0.1-2 Bug #628912 [xen-utils-4.0] xenconsoled and xenstored stopping unhandled by init script Bug reassigned from package 'xen-utils-4.0' to 'xen-utils-common'. No longer marked as found in versions xen/4.0.1-2. Ignoring request to alter fixed versions of bug #628912 to the same values

Processing commands for control at bugs.debian.org: > reassign 596765 xen-utils-common Bug #596765 [xen] xen: can't create a VM : no module named xmlproc Bug reassigned from package 'xen' to 'xen-utils-common'. No longer marked as found in versions xen/4.0.1-2 and xen/4.0.1-1. Ignoring request to alter fixed versions of bug #596765 to the same values previously set >