Hello Tincho,
Firstly, try CTL+[ after xm console locks you in. That''s the oldschool
''terminal disconnect'' command, and it should take you from the
DomU terminal back to your Dom0 shell.
''b'' basically means ''idle''. If it changes
to ''r'', things are actively being executed.
Now, the problem that you''re experiencing is that the DomU is not
booting to a console OR is failing to boot due to lack of udev and TTYs. If you
have openssh-server setup to autoinstall with xen-create-image, you should be
able to SSH around this. If that doesn''t work, recreate the domU, but
add this to your xen-create-image command...
--role udev
Then add this to the domU config file, destroy the domU, and recreate it.
extra = ''xencons=tty''
Let me know if this helps!
Best Regards
Nathan Eisenberg
Sr. Systems Administrator
Atlas Networks, LLC
support@atlasnetworks.us
http://support.atlasnetworks.us/portal
-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Tincho ylm
Sent: Tuesday, May 26, 2009 11:30 AM
To: xen-users@lists.xensource.com
Subject: [Xen-users] Installing and running XEN
Hi all! I''m new on the list.
I have read many HowTos about xen installations and I have an error
that I cant find solution.
(S.O: Debian Lenny)
First, this is what I did:
Hypervisor
# aptitude install xen-hypervisor-i386 libc6-xen xen-utils xen-tools
bridge-utils
Kernel
# aptitude install xen-linux-system-2.6.26-2-xen-686
-----
# nano /etc/modules
loop max_loop=128
# nano /etc/xen/xend-config.sxp
Comment:(network-script network-dummy)
Uncomment:
(network-script network-bridge)
(vif-script vif-bridge)
(dom0-min-mem 196)
(dom0-cpus 0)
Reboot and select XEN kernel
# nano /etc/xen-tools/xen-tools.conf
#
#
dir = /vserver
#
#
debootstrap = 1
#
#
size = 2Gb # Disk image size.
memory = 256Mb # Memory size
swap = 512Mb # Swap size
fs = ext3 # use the EXT3 filesystem for the disk image.
dist = lenny # Default distribution to install.
image = sparse # Specify sparse vs. full disk images.
#
#
gateway = xxx.xxx.xxx.xxx
netmask = 255.255.255.240
#
#
kernel = /boot/vmlinuz-2.6.26-2-xen-686
initrd = /boot/initrd.img-2.6.26-2-xen-686
#
#
mirror = http://ftp.debian.at/debian/
# xen-create-image --hostname test02 --ip xxx.xxx.xxx.xxx
# xm create test02.cfg
so, everything is ok so far. so, I run:
# xm list and I see
Name ID Mem VCPUs State Time(s)
Domain-0 0 207 1 r----- 195.7
test02 5 64 1 -b---- 6.8
WHAT is that B? why is blocked? how do I fix that?
and go on:
# xm console test02
and the PC stops to response... I have to reboot...
why is that? thanks in advance.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users