Displaying 15 results from an estimated 15 matches similar to: "[PATCH] [Xm-TEST] Fix XAPI test case 02"
2012 Jan 24
1
[PATCH 0/5] Get rid of get_driver() and put_driver()
Greg:
This patch series removes the get_driver() and put_driver() routines
from the kernel.
Those routines don''t do anything useful. Their comments say that they
increment and decrement the driver''s reference count, just like
get_device()/put_device() and a lot of other utility routines. But a
struct driver is _not_ like a struct device! It resembles a piece of
code more
2013 Jan 17
0
XCP 1.1 SR_BACKEND_FAILURE_46 The VDI is not available [opterr=VDI already attached RW] issue
Hello
I have a problem with VDI already attached RW in the "adding tag" in
blktap2. This issue is on all hosts in pool with attached lvmoiscsi SR.
Is there any solution to this problem?
/var/log/SMlog:
[32484] 2013-01-17 14:59:44.200883 vdi_activate {''sr_uuid'':
''e33281eb-ba4c-3829-9b61-7c64764dff9c'', ''subtask_of'':
2012 Feb 22
0
Announce: Puppet Dashboard 1.2.6 Available
This is a maintenance release of Puppet Dashboard.
It includes contributions from Adrien Thebo, Chad Metcalf, Chris W,
Daniel Pittman, Daniel Sauble, Devon Harless, Michael Stahnke, Moses
Mendoza, Randall Hansen, Josh Lifton, and Nick Fagerlund.
This release is available for download at:
http://downloads.puppetlabs.com/dashboard/
We have included Debian and RPM packages as well as a tarball
2012 May 23
2
Bug#674088: xcp-xapi: vbd-plug to dom0 does not creates /dev/xvd* devices in dom0
Package: xcp-xapi
Version: 1.3.2-6
Severity: normal
Tags: upstream
Normally (in 'iso-based' XCP) is possible to attach VDI to dom0.
That operation usually looks like:
xe vbd-create vdi-uuid=... vm-uuid=(dom0 uuid) device=N
xe vbd-plug
I done those steps in xcp-xapi and got success (no error), but no xvd* device found.
Here operations log:
# xe vbd-create
2017 Jul 14
0
[PATCH 07/27] daemon: Reimplement ‘is_dir’, ‘is_file’ and ‘is_symlink’ APIs in OCaml.
This also demonstrates usage of optional arguments.
---
daemon/Makefile.am | 2 ++
daemon/is.c | 41 -----------------------------------------
daemon/is.ml | 44 ++++++++++++++++++++++++++++++++++++++++++++
daemon/is.mli | 21 +++++++++++++++++++++
generator/actions_core.ml | 3 +++
generator/daemon.ml | 7 ++++---
6 files changed, 74
2007 Apr 13
0
[958] branches/wxruby2/wxwidgets_282: Additions to UpdateUIEvent API 2.6->2.8
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!--
#msg dl { border: 1px #006 solid; background: #369; padding:
2010 May 19
0
Hi - Regarding xend - xm create Error
Hi,
I am able to get Xend running on Fedora 8 but when I try to create any
VM it fails.
The xm create osc.cfg throws following error -
[root@asds174 vm_images]# xm create osc.cfg
Modified
arg=osc.cfg
stop3
Using config file "./osc.cfg".
group_id=None
[''create'', ''osc.cfg'']
Stop 1
None
[''vm'', [''name'',
2009 Jul 28
0
Xen 3.2 @ Debian 5.0 / Debian 4.0 DomU crashes daily
Hello,
on my xen host, Debian 5.0 I have few domU''s running, most of them are Lenny''s, a couple is running at Etch (Debian 4.0). All domU''s are running stable except of one (Etch / Debian 4.0). This one crashes almost daily and I wasn''t able figure out the reason why.
Inside the domU there is nothing installed except of base system and Zimbra ZCS 5.0 and its
2010 Oct 24
1
Bug#601271: xen-utils-4.0: domain fails to reboot (AttributeError: 'NoneType' object has no attribute 'getBitSize')
Package: xen-utils-4.0
Version: 4.0.1-1
Severity: important
I'm running a 32-bit Ubuntu 10.04 domU on a 32-bit Debian squeeze dom0.
xm create works fine, but whenever I try to reboot this domU it fails with
the following traceback in xend.log:
[2010-10-23 17:48:58 1679] INFO (XendDomainInfo:2088) Domain has shutdown: name=
onini id=2 reason=reboot.
[2010-10-23 17:48:58 1679] DEBUG
2008 Nov 27
6
Bug#507020: xen-utils-3.2-1: Pygrub says "Error: Boot loader didn't return any data!"
Package: xen-utils-3.2-1
Version: 3.2.1-2
Severity: normal
When my domU uses this configuration:
---
root = '/dev/sda2 ro'
disk = [
'phy:/dev/volume0/lenny.vandervlis.nl-swap,sda1,w',
'phy:/dev/volume0/lenny.vandervlis.nl-disk,sda2,w',
]
---
Pygrub gives the error "Error: Boot loader didn't return
2011 Oct 29
0
Bug#644100: Boot loader didn't return any data! if reboot domU with disk DRBD
Package: xen-utils-4.0
Version: 4.0.1-2
If you reboot with the DomU disk DRBD domain destroy.
pygrub error when trying to run a image on DRBD device
My config DomU
------------------------------------------------------
bootloader = '/usr/lib/xen-default/bin/pygrub'
vcpus = '1'
memory = '256'
cpus="8-15"
root = '/dev/xvda2 ro'
#disk
2008 Mar 25
1
Xen3.1 Etch-backports | VE already running
Hi guys,
actually i use the following packages from etch-backports:
===========================
ii linux-headers-2.6.18-6-xen-vserver 2.6.18.dfsg.1-18etch1
Common header files for Linux 2.6.18
ii linux-headers-2.6.18-6-xen-vserver-amd64 2.6.18.dfsg.1-18etch1
Header files for Linux 2.6.18 on AMD64
ii linux-image-2.6.18-6-xen-vserver-amd64
2008 Aug 09
4
Upgrade 3.0.3 to 3.2.1
Hi,
i''m prepering to upgrade my servers from xen 3.0.3 32-bit to 3.2.1 64-bit.
The old system:
Debian 4.0 i386 with included hypervisor 3.0.3 (pae) and dom0 kernel.
The new systen:
Debian lenny amd64 with the included hypervisor 3.2.1 and dom0 kernel from
Debian 4.0 amd64.
My domUs have a self compiled kernel out of the dom0 kernel of the old system
(mainly the dom0 kernel but
2013 Jul 28
4
Fedora 19 installation with virt-install
Hello,
I want to install a DomU with Fedora 19 in a Debian Host Dom0 with the
following versions...
ii libc6-xen:i386 2.13-38
i386 Embedded GNU C Library: Shared libraries [Xen version]
ii libxen-4.1 4.1.4-3+deb7u1
i386 Public libs for Xen
ii libxenstore3.0 4.1.4-3+deb7u1
i386
2010 Jun 25
1
[SPAM] The Infamous "Device 0 (vif) could not be connected. Hotplug scripts not working."
When I start my domU, I get the infamous and UNINFORMATIVE! error message:
"Device 0 (vif) could not be connected. Hotplug scripts not working."
What could be the cause?
There are strange things occuring. When I boot the host, I can start
zero, one or two VM before it happens (most often zero), and then no
other VM may be started successfully.
It fails the same whether I try to boot