Displaying 20 results from an estimated 500 matches similar to: "XenDomainInfo.py: Can hang in _releaseDevices."
2007 Nov 06
3
Problem while installing XEN 3.1 on Fedora 6
Hi,
I downloaded XEN 3.1 source code on a fedora 6 machine.
I did
# make world
# make install
It did not give me an error then when I restarted the machine the Grub
did not have 2 options. It had only one option that was the kernel.
On loading the OS, when i gave
# xend
it gives the following errors:
[root@localhost sbin]# xend
ERROR Internal error: Could not obtain handle on privileged command
2014 Apr 10
0
Bug#744163: xenstore problems
Package: xen-utils-4.1
Version: 4.1.4-3+deb7u1
Severity: important
When starting (or migrating in) a domain, sometimes I get the following exception:
[2014-04-01 10:58:08 4821] ERROR (XendDomainInfo:2927) XendDomainInfo.initDomain: exception occurred
Traceback (most recent call last):
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 2914, in _initDomain
2006 Sep 20
15
[PATCH] [XEND] Remove hard tabs
# HG changeset patch
# User Hollis Blanchard <hollisb@us.ibm.com>
# Date 1158780052 18000
# Node ID f7d90f962967a5a94fce0c04f8fcac449f36344f
# Parent 041be3f6b38e05f904d240630c18cadb1259317b
[XEND] Remove hard tabs.
Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
diff -r 041be3f6b38e -r f7d90f962967 tools/python/xen/xend/XendDomainInfo.py
---
2011 Feb 04
5
[PATCH] kdump: introduce "reset_devices" command line option
upstream commit 7e96287ddc4f42081e18248b6167041c0908004c
Author: Vivek Goyal <vgoyal@in.ibm.com>
[PATCH] kdump: introduce "reset_devices" command line option
Resetting the devices during driver initialization can be a costly
operation in terms of time (especially scsi devices). This option can be
used by drivers to know that user forcibly wants the devices to
2007 Apr 11
2
Error: Device 0 (vkbd) is already connected.
Hi,
Is vfb working well lately? I thought I''d test it out on ia64 and it
works great, but only once per boot. If I stop the domain and restart
it, I get the following:
Error: Device 0 (vkbd) is already connected.
To make sure this isn''t an ia64 anomaly, I tried it on an x86_64 system.
Same thing, works the first time, reboot the domain and it''s broken. I
see
2013 Apr 17
10
xl network-attach SEGV in 4.2 and 4.1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
4.2 and 4.1 suffers from SEGV during xl network-attach in
libxl__device_nic_add. In 4.3-unstable it is fixed by:
5420f2650 libxl: Set vfb and vkb devid if not done so by the caller
So either the patch need to be backported to 4.1 and 4.2, or fixed by this one:
- ------
libxl: Fix SEGV in network-attach
When "device/vif" directory
2011 Apr 12
1
Xen migration fails
Hi,
I have been getting the following error (logged in /var/log/xen/xend.log)
when I try to migrate a VM from one particular host to the other (the
reverse migration works fine). My system was working fine for a long time (i
did several migrations in both the directions). I am using Xen-3.4.3
(installed from source code) with CentOS 5.4. I am using drbd to replicate
the disks.
2009 Feb 26
4
SXCE104, Cannot boot HVM domain
Hi,
I cannot boot Windows XP domU on SXCE104 dom0.
It was running for weeks..
Is it a known bug?
# virsh start wxpp01 &
# virsh dumpxml wxpp01
<domain type=''xen'' id=''-1''>
<name>wxpp01</name>
<uuid>fb96e8c9-940d-7e0a-12ef-f167a7f1102c</uuid>
<os>
<type>hvm</type>
2012 Nov 08
0
Sometimes unable to reboot VM
Xen Version: 4.2.0
Linux Kernel Version: 3.2.30
OS: Debian 6.0
Sometimes when trying to reboot a VM, the reboot fails with the following
message in xend.log: Has anyone experienced this issue before, know the
cause and/or fix? This is an HVM VM. Device model is set in the
configuration file
device_model = ''/usr/lib/xen/bin/qemu-dm''
We use the same configuration file with
2009 Dec 02
7
san suport
Hi,
i''m having problems attaching disks from a fc-san to a solaris 10 guest.
xen host ist a opensolaris box "SunOS node1 5.11 snv_127 i86pc i386 i86xpv".
my xen guest is named pg4.
this command works fine.
virsh attach-disk pg4 /dev/dsk/c8t600A0B800029D69A000013CA4B00E1ABd0 hdb
and before i was able to import this volume as a zpool on the xen host - so
connection to this
2014 Jul 18
0
NUT + devd + FreeBSD
On Mon, Oct 29, 2007 at 9:45 PM, Daniel O'Connor <doconnor at gsoft.com.au> wrote:
> I made the following devd script..
>
> sh
> cd /tmp
> fetch
> mkdir /usr/local/etc/devd
> sed -Ene 's/SYSFS\{idVendor\}==\"(.*)\", SYSFS\{idProduct\}==\"(.*)\", MODE=.*/attach 100 {\
> device-name "ugen[0-9]+";\
> match
2007 Jul 15
0
virtman breaks after installing XEN 3.1 on SELS 10.1
I have an installation of 32bit SLES 10.1 on 2 servers in my lab that I just
rebuilt. I applied the files from xen-3.1.0-install-x86_32.tgz and broke all
the virtman functions. The errors I got indicate some missing python
classes, specifically xen.install. I''m not sure why. This is what I get when
I try to run virtman from the command line. If I try to run it from yast i
get nothing.
2010 May 07
9
[PATCH] xl: Update memory info in xenstore when use ''xl mem-set''
''xl mem-set'' should update memory info in xenstore''s vm info.
Signed-off-by: Yu Zhiguo <yuzg@cn.fujitsu.com>
diff -r ccae861f52f7 -r 5847ce53f5dc tools/libxl/libxl.c
--- a/tools/libxl/libxl.c Thu May 06 11:59:55 2010 +0100
+++ b/tools/libxl/libxl.c Sat May 08 01:38:51 2010 +0800
@@ -2290,11 +2290,22 @@
uint32_t videoram;
char *videoram_s = NULL;
2007 Jul 09
0
[PATCH] Fix xm sysrq command for inactive managed domain
Hi,
I tried to test a wrong operation on purpose again. When I tried
xm sysrq command to a inactive managed domain, I saw the following
error message. The error message did not have a message text
behind "Error:". And I found an AssertionError message in xend.log.
# xm list PVdomain.1
Name ID Mem VCPUs State Time(s)
PVdomain.1
2011 Nov 13
0
Bug#648670: xm was unable determine an actual domU state under some conditions
Package: xen-utils-4.1
Version: 4.1.1-3
I have an HVM domU which was created with xen-utils-4.0 (and Xen 4.0 hypervisor of course). Recently I've upgraded to Xen 4.1 and xen-utils-4.1, but after a reboot I was unable to do anything with it: "xm start" caused "Domain is already running" error, while "xm shutdown" simply hadn't printed any error messages, only
2007 Oct 30
5
NUT + devd + FreeBSD
I made the following devd script..
sh
cd /tmp
fetch
mkdir /usr/local/etc/devd
sed -Ene 's/SYSFS\{idVendor\}==\"(.*)\", SYSFS\{idProduct\}==\"(.*)\", MODE=.*/attach 100 {\
device-name "ugen[0-9]+";\
match "vendor" "0x\1";\
match "product" "0x\2";\
action "chown @RUN_AS_GROUP@
2007 Oct 31
3
Error: (9, ''Bad file descriptor'')
Dom0 = centos 5 (32bit), 4GB Ram
DomU = centos 5 (PV) (32bit)
xen 3.1.2 rc1, compiled using XEN_TARGET_X86_PAE=Y
kernel 2.6.18, modified to load areca card drivers
initrd image created using the following command
mkinitrd -v -f --with=aacraid --with=arcmsr --with=sd_mod --with=scsi_mod
initrd-2.6.18-xen.img 2.6.18-xen
When i issue xm create for a domU which was working earlier i get the
2008 Sep 23
1
non-page-aligned MMIO BAR found since 3.3
Hello,
I''ve done an update from xen 3.2 to 3.3. Since 3.3 I can not use my
TV-Card anymore. The error message is "Error: pci: 0000:10:0a.0:
non-page-aligned MMIO BAR found."
lspci shows the card as 10:0a.0 Multimedia controller: Philips
Semiconductors SAA7146 (rev 01)
Any hints ?
Thanks in advance
Christoph
xm dmesg:
(XEN) Xen version 3.3.1-rc1-pre (root@artus.own) (gcc
2008 Oct 07
0
xend accesses wrong pci slot while enabling pci pass-through on xen3.3.0
Hi all,
I am trying the pci-passthrough on xen 3.3.0. I binded the pci slot to
pciback using late binding.
But xend fails to allocate this slot to domU.
linux-242:/home/xen-3.3.0 # xm create -c pci=08:01.0
/etc/xen/xen3.3_guest1
Using config file "/etc/xen/xen3.3_guest1".
Error: [Errno 2] No such file or directory:
''/sys/bus/pci/devices/0000:06:00.0/config''
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