Displaying 20 results from an estimated 2000 matches similar to: "exception looking up device number for sda1"
2009 Jan 19
0
Migration with ubuntu 8.0.4.1 fails
hi,
I have 2 servers running xen 3.2 on ubuntu 8.0.4.1 (64-bit) installed
from the repositories (2.6.24-22-xen) with Intel-Quadcore CPU''s. The
setup is based on
http://www.asplund.nu/xencluster/xen-cluster-howto.html. I can start the
domU (ubuntu 8.0.4.1 (64-bit)) on each server without problems. But when
I start the live-migration with xm migrate dummy xen2 --live the
migration
2008 Mar 07
2
domU paused in booting
Hi all,
my domU guests stop booting in my new 3.2 (kernel 2.6.18.8) xen
installation when run perfectly in my other 3.0.2 (2.6.16) xen server.
whe i start the domU with "xm create" i get these messages:
Using config file "./debian.4-0.xen3.cfg".
Started domain debian.4-0
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table
2006 Jan 26
0
Loop Mounted Device Issue?
Hi. We are running xen-3.0-testing. We use loop back mounted file
systems. The server we are running restarts itself/crashes. This seems
to happen around setting up loop back devices. (>63 loop back devices
seems to trigger a crash, but we have seen then with fewer devices
mounted as well).
We have swapped all hardware (bar the disks) to a new server. Same
issue. I see no disk
2006 Jan 21
4
Xen Starting DomainU:Error: Device 0 (vif) could not be connected. Hotplug scripts not working
hi,
I am trying to start a new domainU but got the error:
Error: Device 0 (vif) could not be connected. Hotplug scripts not working
I have struggled with it for a long time. I found somebody else report this
but can not find a solution.
The xen version is xen-3.0 latest version.
I do not have a initrd.
Domain0 works fine but when I create a new domain, it always gives an error
as above.
Thanks,
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:
2011 Aug 04
3
[Q] VmError: Disk isn''t accessible with tap2:tapdisk:vhd
I''m newbie Xen-4.1.1
I''m trying to boot DomU with the following configuration.
Sometime DomU boot, but sometime boot failed
I''m not sure what is the problem.
I can attach that image with tap-ctl on Dom0.
Does anybody advice me about this problem??
Sincerely
* Environment
OS : Scientific Linux 6.1 x86_64
Kernel : 2.6.32.43
2012 Oct 17
0
vhd format support failed on suse11 x86_64 sp2
Hi all,
I had met with a question about vhd format when i install xen 4.2.0 source code on suse11_x86_64_sp2.
execute steps:
1)Install fully suse 11 sp2 to host pc
2)Boot from Xen kernel menu
3)Download xen 4.2.0 source code from http://xen.org/download/index_4.2.0.html
4)Download bin86-0.16.19.tar.gz cmake-2.8.9.tar.gz Dev86src-0.16.19.tar.gz gettext-0.18.1.1.tar.gz
2011 Jan 30
0
Stub domains broken in Xen 4.0?
When I try to use stubdom-dm in lieu of qemu-dm, the guest domain crashes
almost immediately if I specify an emulated NIC (''vif='') in the guest
configuration file. If I don''t specify a vif, it works fine. If I use the
same configuration with qemu-dm instead of sutbdom-dm, it works fine. Is
there some reason QEMU emulated networking doesn''t work with stub domains
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
2011 May 24
0
XEN 4.1 performance issue
Hi,
I migrate Xen4.0 to XEN4.1, and found XEN4.1 performance is not as good as 4.0.2. xm shutdown takes longer time, control thru libvirt take longer time, and since I''m testing PCI/VGA passthru, the "createdevice: pci" also take around 5~8 seconds comparing to 1 second in XEN4.0.2. below is my configuration, do you have any suggestions to make the performance better?
2010 Jul 22
1
HVM domain can not boot up with Qcow incremental image
Dear,Beg for your help. I am really puzzled with this problem.HVM domain can not boot up with Qcow incremental image(using command: qcow-create size incremental_file original_Qcow_img_file), but it can boot up with the original Qcow disk image file. When using Qcow incremental image, the guest qemu window would disappear before loading grub, and `xm list` can not find this guest domain.The VM
2011 Oct 28
0
"reset requested in cpu_handle_ioreq" causes the wirtual machine crashed when using "xm create xp.hvm"
the contexts are as follows, looking forward to your reply, thanks
[1]enviromention : xen3.4.2+CentOS-5.5
[2]config file: xp.hvm, as follows
_s_name = 'xp-101'
_s_vnc_display = 5310
_s_vm_id = 101
_s_vm_mac = '00:16:3e:eb:ca:65'
_s_memory = 512
_s_allow_destroy = False
_s_use_vnc = True
# -*- mode: python; -*-
2009 Jun 25
0
Error creating vm xen3.4
Hi all, when i try to create a new virtual machine in a new instalation of
xen3.4 ( compiled from source) i get this error:
xm create windows2.hvm
Using config file "./windows2.hvm".
Error: Domain ''y'' does not exist.
And this is the log:
[2009-06-25 17:59:42 13862] TRACE (XendDomainInfo:291) domain_getinfo(2)
failed, ignoring: (3, ''No such process'')
2008 Apr 14
0
full virtualisation on centos5.1 with a F7 guest
Hi
I m trying to install a full virtualized guest on my dell poweredge 1950
with centos 5.1 64 bits.
I just launched the following command
virt-install -n elaphe -r 4096 -f /var/lib/xen/images/elaphe -s 40 -b
vlanbr15 --hvm
Would you like to enable graphics support? (yes or no) yes
What is the virtual CD image, CD device or install location?
/var/lib/xen/F-7-i386-DVD.iso
Starting
2011 Jan 17
0
Xen 4.0.1 + 2.6.18-194.32.1.el5xen CentOS Dom0
I am running Xen 4.0.1 with a 2.6.18-194.32.1.el5xen CentOS Dom0. I built
and installed the Xen binaries from source. The systems boot successfully
however I am having issues bring up DomUs. Here is config:
name = ''xyz''
memory = 256
vcpus = 1
pae = 1
vnc = 1
vncunused = 1
disk = [ ''phy:/dev/vg1/xyz,hda,w'' ]
vif = [
2012 Aug 24
1
Problems with create VM
Hi,
I installed the xen in server with CentOS 6, but not create vm.
[root@localhost oracleteste]# xm create oracleteste.cfg
Using config file "./oracleteste.cfg".
Started domain oracleteste (id=9)
[root@localhost oracleteste]# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 1024 1 r-----
2011 Jan 23
1
DRBD VBD script not working in squeeze ?
Hi,
since I upgraded from Lenny, DRBD VBD scripts not works at all.
This config works :
disk = [ 'phy:/dev/drbd/by-res/ads-disk,xvda,w' ]
But his one doesn't work at all :
disk = [ 'drbd:ads-disk,xvda,w' ]
I obtain this error :
# xm create ads.cfg
Using config file "/etc/xen/ads.cfg".
Error: Device 51712 (vbd) could not be connected. Hotplug scripts
2010 Jun 06
3
Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1
Hi!
Please help me.
# xm create win7.hvm
Using config file "./win7.hvm".
Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1
grep -v ^# /etc/xen/win7.hvm | grep -vx ''''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 2048
name = "win7"
vif = [
2006 Nov 02
0
Install WinXP on FC6 - no graphic window display
I have loaded FC6 with the virtualizations kernel, and I am attempting
to load WinXP. I searched all the logs and docs and configured what I
think is correct based on these. When I do an xm create dfw11286lv1.hvm,
I get the following messages:
Using config file "dfw11286lv1.hvm".
Started domain dfw1128glv1
However, I never get a window with the installer. Also, when I open the