Displaying 20 results from an estimated 3000 matches similar to: "Bug in xen-utils-unstable"
2008 Aug 26
0
[PATCH] xend: fix LinuxImageHandler debugging output
xend: fix LinuxImageHandler debugging output
Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com>
diff -r c2472ded5c7c tools/python/xen/xend/image.py
--- a/tools/python/xen/xend/image.py Tue Aug 26 15:16:57 2008 +0100
+++ b/tools/python/xen/xend/image.py Tue Aug 26 17:06:09 2008 +0100
@@ -637,8 +637,9 @@ class LinuxImageHandler(ImageHandler):
log.debug("ramdisk
2007 Feb 27
3
freebsd domu 14, bad address
Hello,
I''m trying to get a freebsd virtual machine running following :
http://www.yuanjue.net/xen/howto.html
But I get :
# xm create freebsd_xen_INSTALL -c
Using config file "./freebsd_xen_INSTALL".
Error: (14, ''Bad address'')
Am I missing something?
I am using xen 3.0.4.
Thanks and regards,
Sergi
....
log output from xend.log:
[2007-02-27 12:46:59
2011 Jan 23
1
SETVCPUCONTEXT failed
Hi guys,
I cannot get my domU''s to boot. My current setup is as follows:
Xen: 4.0.1
Dom0: Debian with custom linux 2.6.32.27 Xen kernel
DomU: Same kernel as Dom0
When I try to start the VM, I just get:
Error: (1, ''Internal error'', ''launch_vm: SETVCPUCONTEXT failed (rc=-1)\n'')
And /var/log/xend.log says:
[2011-01-23 15:36:01 3201] DEBUG
2011 Jan 23
1
SETVCPUCONTEXT failed
Hi guys,
I cannot get my domU''s to boot. My current setup is as follows:
Xen: 4.0.1
Dom0: Debian with custom linux 2.6.32.27 Xen kernel
DomU: Same kernel as Dom0
When I try to start the VM, I just get:
Error: (1, ''Internal error'', ''launch_vm: SETVCPUCONTEXT failed (rc=-1)\n'')
And /var/log/xend.log says:
[2011-01-23 15:36:01 3201] DEBUG
2005 Aug 30
4
Re: [Xen-changelog] New console transport and update xenconsoled.
Xen patchbot -unstable wrote:
># HG changeset patch
># User cl349@firebug.cl.cam.ac.uk
># Node ID 8fe8a99b1c2a6ea88624546ab625eaa0758e3a17
># Parent e69cbfee4011da1648718f1f5cbe8dabb956e72a
>New console transport and update xenconsoled.
>Add a new console interface using a seperate shared page and event channel
>instead of passing the console input/output over control
2009 Jan 26
1
Xen+drbd VmError: Block device must have "phy", "file" or "tap" specified to type
Hello List,
i am trying to get xen 3.3.1+ linux kernel 2.6.18 +drbd 8.3.0 working.
Here is my config:
----------------------------------------------
kernel = ''/boot/vmlinuz-2.6.18.8-xenU''
memory = ''128''
root = ''/dev/sda2 ro''
disk = [
''drbd:pgone-disk,sda2,w''
]
name
2008 Oct 23
0
XEN 3.3: xend chrashes beim Start der DomU
Hi,
I try to start a DomU with
xm create endian -c
and got the following error message
Xend has probably crashed! Invalid or missing HTTP status code.
I''ve tested the DomU with nearly the same system at VMWare (Windows) and it works normaly, but on my server I get this error message.
I useing gentoo as Dom0. I tried also a gentoo DomU with the same result.
Thanks.
2006 Aug 08
11
architecture-specific stuff in xend
Hi Ewan, I''m almost ready to integrate some PPC-specific stuff into
xend, and I was wondering if you had a plan for how that should work.
First example: the device tree data structure we talked about a few
weeks ago. We will need to pass the config data to PPC code, probably in
XendDomainInfo.initDomain(), and then pass the resulting data structure
into libxc''s xc_linux_load()
2007 Jan 11
0
[PATCH 6/8] HVM save restore: guest memory handling
[PATCH 6/8] HVM save restore: guest memory handling
Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
add support for save/restore HVM guest memory
diff -r bb1c450b2739 tools/libxc/xc_hvm_restore.c
--- a/tools/libxc/xc_hvm_restore.c Thu Jan 11 21:03:11 2007 +0800
+++ b/tools/libxc/xc_hvm_restore.c Thu Jan 11 21:05:45 2007 +0800
@@ -31,6 +31,40 @@
#include <xen/hvm/ioreq.h>
2007 Nov 28
0
[Xen-ia64-devel] [PATCH] Add guest_os_type domain config option
On ia64 we have a desire to know the guest OS the user plans to run
in an HVM domain. With this information we can make certain
optimizations, for instance knowing if a guest identity maps a memory
region can change how we handle page faults. In the past we''ve tried to
do this via the guest firmware detecting the guest type, but this is
error prone and doesn''t allow the user to
2006 May 31
0
Bug#368417: xen-hypervisor-3.0-i386: cannot start NetBSD-HEAD
Package: xen-hypervisor-3.0-i386
Version: 3.0.2+hg9681-1
Severity: important
Have been trying to get NetBSD to run under debian unstable
with the debian supplied hypervisor.
Using the 3.0.2-2 hypervisor supplied by XenSource, it works just fine.
Because the install process overrides other things, reverified with
debian hypervisor afterwards and symptom continues.
Attaching the netbsd.cfg and the
2006 May 31
0
[pakrat@private.neotoma.org: xen-hypervisor-3.0-i386: cannot start NetBSD-HEAD]
----- Forwarded message from pakrat <pakrat@private.neotoma.org> -----
Forwarding to list without attachments.
From: pakrat <pakrat@private.neotoma.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: xen-hypervisor-3.0-i386: cannot start NetBSD-HEAD
X-Neotoma-Consulting-MailScanner: Found to be clean
X-Neotoma-Consulting-MailScanner-From:
2005 Nov 12
0
NFS root on problem on Xen Debian
Hi,
I have Xen (unstable) on two Debian Sarge 2.4.27
systems, one of which is an nfs server and the other
the nfs client. I am trying to set up NFS root so that
I can live migrate my domains from one to another.
My /etc/exports on N1(10.5.144.29)
/myfs1/foo 10.5.144.27(rw,sync,no_root_squash)
10.5.144.29(rw,sync,no_root_squash)
10.5.144.30(rw,sync,no_root_squash)
My /hosts.allow on N1
2008 Mar 25
0
domU doesn''t start | Error
Hi Guys,
my domUs won''t start and i do not know why.
i use the acutal version of xen (3.2) from mercurial on a debian etch
64 system. Thanks for any help
here the config of a domU:
==================================
name = "vadmin89"
kernel = "/boot/vmlinuz-2.6-xen"
root = "/dev/hda1"
memory = 75
disk = [
2010 Jun 07
1
111b virt-install failure
Hi,
I''ve been using xVM with no problems since 2009.06 release (centos4/5, rhel4/5, sol10 as guests). This was using the 111a version. Just installed a new server with the 111b version
and ....
virt-install --nographics -p -r 8192 -n CentOS_48_64_92 -f /dev/zvol/dsk/zm0/vm/CentOS_48_64_92 -l ftp://192.168.101.120/pub/CentOS-48 -w bridge=aggr0 --os-type=linux --os-variant=rhel4
2008 Jul 03
3
xm create fails with ''elf_xen_note_check: ERROR:''
Hi --
I''m getting this error even though I have correct DVD ISO image for snv_92.
bash-3.2# uname -a
SunOS stoakly2 5.11 snv_92 i86pc i386 i86xpv
bash-3.2# xm create snv.py
Using config file "./snv.py".
Error: (2, ''Invalid kernel'', ''elf_xen_note_check: ERROR: Will only load
images built for the generic loader or Linux images'')
bash-3.2#
2006 May 02
0
Mini-OS and Xend issue
I am seeing a strange issue while running Mini-OS on the changeset
9906:a95e677073c1. This is on both i386 and x86_64. The only difference
being on i386 if I stop printing to the console, this issue is not
manifested. But with x86_64 it happens all the time.
Bringing up Mini-OS for the first time causes xm to hang on certain
commands like "list, destroy". Other commands like
2006 Apr 28
0
Can''t connect to domain
Hi again :)
OK we''re making good progress. Dom0 booted with 2.6.16-xen kernel,
Steve''s wonderful xen-create-image has done the biz for me with
debootstrap and created a sid disk image+swap, and I can start the
created ''joltpg1'' OK.. but when I go to connect to the console, I see this:
jolt:/dev# xm console joltpg1
xenconsole: Could not read tty from store:
2006 Aug 31
1
error creating domain
Hello all;
I am trying to create SuSE10 guest under my FC5 host, this configuration has
worked before but due to abnormal shutdown of my server i get the following
error while trying to create the guest OS;
** the same configuration *used to* work just fine
*#xm create -c /etc/xen/suse.cfg*
-------------------------------------------------------------------------------------
Using config file
2011 Jun 29
1
no Disk drive detected when provisioning new vms or after restarting a vm
Hi All
I have xen 4.0 in centos dom0
the machine was working fine for months and yesterday out of sudden I
can no longer provision new vms and to make things worst If any vm
shutdown I cannot re run it again .
the vm stop at the process of detecting the (ubuntu and debian all versions)
[!] Detect Disks "No disk drive was detected. If you know the name of
the driver needed by your disk