Displaying 20 results from an estimated 1200 matches similar to: "Cannot open root device xvda1 or unknown-block(0,0)"
2012 Jun 08
3
cannot boot guest VM
Hi,
I''m trying to boot a PV VM I just installed (following http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installer) without success.
My XEN installation is xen-unstable 54c8c9eaee92+ on a Debian unstable machine (x86_64), kernel 3.3.4+. The VM I installed is, again, a Debian unstable x86_64. The installation went smoothly; I used an 8GB file as a disk back-end. I went
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.
2012 Apr 24
21
no console when using xl toolstack xen 4.1.2
Hello!
I was asking for help on the Freenode channel, and I was pointed here.
I have a situation where, using xl, I can create a functional PV domU, with or without pv-grub, but I cannot access the console. Firing up xend and using xm works without trouble. Since xend and company is being deprecated, I would like to transition to using the xl toolstack.
The system is an Arch Linux system
2013 Oct 08
10
xl console regression on xen-unstable
I''m unable to start xl console on latest xen-unstable (build with commit
8e0da8c07f4f80e14314977a11f738bd74a5b62b).
> xl -vvv console sid
> xenconsole: Could not read tty from store: No such file or directory
I also tried "xl create -c", and it shows console from pygrub but when
the "xl create" reaches the end I got the same error:
> xenconsole: Could not
2008 Mar 02
0
error installing Xen guests on CentOS 5.1 x64 - could not read tty from store
Hi all
I keep on getting this error when I try and install a Xen guest on a
CentOS 5.1 x64 server with Xen installed from the repositories:
[root at gimbli ~]# virt-install sdl=0 vnc=0 nographic=0 -v
--location=http://intranet/kickstart/cPanel/centos/5.1/32/os/i386/
--ram=256 --file-size=10 --file=/home/vm/vps07.img --name=vps07
libvir: error : configuration file syntax error: expecting an
2015 Oct 01
0
xen and spice problem
On Thu, Oct 1, 2015 at 10:06 AM, Christoph <mangel at gmx.de> wrote:
> Hi
>
> it is possible to use xen and spice already? If yes is there any howto or
> doc how?
Fabio has been the one working on getting spice working. Fabio, any ideas?
>
> If I turn on spice in cfg of a hvm domU, I get this error:
>
> Parsing config from /etc/xen/marax.cfg
> libxl: detail:
2013 Jun 19
4
e008:[<ffff82c480122353>] check_lock+0x1b/0x45 [konrad.wilk@oracle.com: FAILURE 3.10.0-rc6upstream-00061-g752bf7d(x86_64) 3.10.0-rc6upstream-00061-g752bf7d(i386): 2013-06-19 (tst007)]
Hey,
It looks like one of the patches that went in Xen 4.1 blows up.
This used to work over the weekend, so I can only surmise
it is one the three patches. This is with a debug=y build
(which has been working nicely for the last month or more).
It looks like one of the patches that went in Xen 4.1 blows up.
This used to work a day ago - that is c/s 23551 worked nicely.
----- Forwarded message
2010 Jun 03
1
Xen 3.1.2 on CentOS 5.5 doesn't see all 4 CPUs
Hello all,
I've been digging around on this for a few days and I have not come up
with a solution.
I have a Compaq ProLiant DL580 (G1, the old tan Compaq) with 4 x 700MHz
P-III CPUs and 11GB of memory. I've loaded CentOS 5.5 with Virtualization
(Xen) + KVM and patched up to current (full KS packages file list at the
end).
When it boots, Xen only detects a single CPU as shown in the xm
2015 Oct 01
5
xen and spice problem
Hi
it is possible to use xen and spice already? If yes is there any howto
or doc how?
If I turn on spice in cfg of a hvm domU, I get this error:
Parsing config from /etc/xen/marax.cfg
libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: base group
enabled
libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: freq group
enabled
libxl: detail:
2008 Jun 14
14
Dom0 won''t come up, Fedora 9
Trying to get Xen going on Fedora 9. Xen was installed from the
distro RPMs. Xen version is 3.2.0 and the linux-xen version is
2.6.25.3.
Xen seems to come up fine, but the system just hangs at the
point where booting of Dom0 should start. There is absolutely
no output from Dom0.
I configured Xen to log to a serial port and captured the output
below. Any suggestions on how to continue
2011 Feb 22
6
how to optimize CentOS XEN dom0?
Hi,
I have a problematic CentOS XEN server and hope someone could point me
in the right direction to optimize it a bit.
The server runs on a Core2Quad 9300, with 8GB RAM (max motherboard can
take, 1U chassis) on an Intel motherboard with a 1TB SATA HDD.
dom0 is set to 512MB limit with a few small XEM VM's running:
root at zaxen01:[~]$ xm list
Name ID
2012 Jun 17
3
Possible bug, dom0 crash on ubuntu
When booting a recently compiled Xen 4.2 on Ubuntu 12.04, dom0
crashes. I''ve included a serial console log below.
I''ve used:
Xen 4.2 unstable rev. 25483, compiled on the same machine. I had to
apply the AT_EMPTY_PATH patch from
http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to
get it to compile.
Linux 3.2.0-25, which is the default kernel in Ubuntu''s
2011 Feb 22
6
how to optimize CentOS XEN dom0?
Hi,
I have a problematic CentOS XEN server and hope someone could point me
in the right direction to optimize it a bit.
The server runs on a Core2Quad 9300, with 8GB RAM (max motherboard can
take, 1U chassis) on an Intel motherboard with a 1TB SATA HDD.
dom0 is set to 512MB limit with a few small XEM VM''s running:
root@zaxen01:[~]$ xm list
Name ID
2010 Jun 22
1
The Host cpu(s) in this machine do not have support for full virtualization
Hi,
I'm geting this message from virt-manager.
Server: SuperMicro X8SIL with INTEL X3440
Here is my logs
/var/log/dmesg:
Bootdata ok (command line is ro root=/dev/md2)
Linux version 2.6.18-194.3.1.el5xen (mockbuild at builder10.centos.org)
(gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Thu May 13
13:49:53 EDT 2010
BIOS-provided physical RAM map:
Xen: 0000000000000000 -
2008 May 15
2
xen smp acpi failed
In hvm enviroment, acpi failed. why? centos5.1
===================================================
[root@hvm001 ~]# xm dmesg
__ __ _____ _ ____ ___ ____ _ ____
\ \/ /___ _ __ |___ / / | |___ \ / _ \___ \ ___| | ___|
\ // _ \ \047_ \ |_ \ | | __) |_| (_) |__) | / _ \ |___ \
/ \ __/ | | | ___) || |_ / __/|__\__, / __/ | __/ |___) |
/_/\_\___|_| |_| |____(_)_(_)_____| /_/_____(_)___|_|____/
2009 Mar 04
1
pv_ops kernel 2.6.29-rc6 boot failure
Hi,
I did a git pull on pv_ops tree this morning and now get a crash when
eth0 is started, here is the full boot log:
Booting ''Xen 3.4 / Linux 2.6.29-rc6-tip''
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /xen.gz com1=115200,8n1 console=com1,vga iommu=1
[Multiboot-elf, <0x100000:0x131748:0x8e8b8>, shtab=0x2c0078, entry=0x100000]
module
2012 Jul 27
4
3.5.0 dom0 crash on boot
Hi,
I''ve not tried pv_ops for a long time but just got a new system
(Supermicro X9DRL-iF) so decided to try 3.5.0 with the latest Xen
4.2-unstable, unfortunately the system crashes immediately after
loading dom0:
traps.c:486:d0 Unhandled invalid opcode fault/trap [#6] on VCPU 0 [ec=0000]
I''ve tried loading both bzImage and vmlinuz (gzip compressed vmlinuz)
with the same
2007 Jun 15
1
[PATCH RFC] add domain builder support for bzImage kernels
This implements a loader for version 2.07 boot protocol bzImage format
files. This allows a single bzImage kernel file to boot either native
from a normal bootloader (grub, etc), or paravirtualized under Xen.
These bzImages have two changes to make this possible:
1. There's a new field for the bootloader to tell the booted kernel
what kind of environment its coming up under. We
2007 Jun 15
1
[PATCH RFC] add domain builder support for bzImage kernels
This implements a loader for version 2.07 boot protocol bzImage format
files. This allows a single bzImage kernel file to boot either native
from a normal bootloader (grub, etc), or paravirtualized under Xen.
These bzImages have two changes to make this possible:
1. There's a new field for the bootloader to tell the booted kernel
what kind of environment its coming up under. We
2007 Jun 15
1
[PATCH RFC] add domain builder support for bzImage kernels
This implements a loader for version 2.07 boot protocol bzImage format
files. This allows a single bzImage kernel file to boot either native
from a normal bootloader (grub, etc), or paravirtualized under Xen.
These bzImages have two changes to make this possible:
1. There's a new field for the bootloader to tell the booted kernel
what kind of environment its coming up under. We