Comments on: Endian 2.3 in Xen on Debian Lenny

By: uk

uk — Wed, 12 May 2010 22:41:42 +0000

@eine Million: Thanks a lot

By: eine Million

eine Million — Mon, 10 May 2010 13:43:07 +0000

Only want to say your article is striking. The clarity in your post is simply impressive and i can take for granted you are an expert on this subject. Well with your permission allow me to grab your rss feed to keep up to date with incoming post. Thanks a million and please keep up the gratifying work.

By: MysteryX

MysteryX — Wed, 14 Apr 2010 16:09:13 +0000

Hi @ all
if you can not login to the shell make shure you added

“xvc0″ to /etc/securetty

By: Kyeto

Kyeto — Thu, 03 Dec 2009 15:47:50 +0000

Hello,

I have the same problem,
It’s impossible to log with the password ‘endian’ on root. However on my vmware, that’s the source of my vmdk, i can.

On the boot, just before the console :
Device “br0″ does not exist.

I have no network, on the shutdown, i have this error :
ioctl: Invalid argument
ioctl: Invalid argument
ioctl: Invalid argument
ioctl: Invalid argument

By: uk

uk — Wed, 02 Dec 2009 13:01:07 +0000

Hmm, strange. Delays occure, in my experience, mostly if you use nis or ldap for passwd and group lookups (do you?). Of course there is the “password is wrong, let the evil hacker wait”-delay… My only (but wild) guess is that there are some right issues while copying the files into the one large filesystem (as in the articel described). When mounting the filesystem of your endian-root-disk and chroot into it, have a look at the /etc/shadow-file before and after you change the password (does it change?). Assure it has 0640 and belongs to root:shadow. After this, i’m out of ideas But i dont think it’s endian+xen related.

By: Kenneth

Kenneth — Fri, 27 Nov 2009 15:48:28 +0000

I got the samething on my 32bit installation, can´t login and but on that installation I could log in to the WEB interface och configure everything. So NIC:s found on that one.

The wrong password takes a couple of seconds to show, so a small delay.

By: uk

uk — Fri, 27 Nov 2009 12:09:01 +0000

Nope, only installed it in a 32bit OS for now. However, you should boot Endian with your 32bit Kernel, not the one from the OS itself. Do you experience a long timeout before “wrong password” or does it show up immediately ? Maybe it’s somewhat related to the missing network adapter. A guess: Maybe your CentOS Xen does not name it XEN-eth0. But i dont know how find this out without logging in to your running Endian.

By: Kenneth

Kenneth — Fri, 27 Nov 2009 06:22:10 +0000

Hello again,

tried to install Endian on an Centos 64 bit and can´t get it to work, something about not finding the network adapter
But when I try to find what the problem is I tried to login to the shell, but I´m getting wrong password all the time.
If I try to change the password it is succesfully changed but can´t login. Both root and admin behaves the same way.

Have you noticed something similarities?

By: uk

uk — Fri, 13 Nov 2009 14:57:57 +0000

Hmm, this looks all good.
I can think only of one thing left: does your img-file work? Try mount -o loop /var/vm/endian-disk.img /somewhere.

If your images works fine (no errors), please email me your logs while booting the endian DomU (/var/log/xen/xend.log and /var/log/xen/xend-debug.log).

Depending on the XEN version you are using (i have 3.3), maybe this helps:
http://lists.xensource.com/archives/html/xen-users/2007-04/msg00200.html

By: Kenneth

Kenneth — Fri, 13 Nov 2009 14:16:50 +0000

Thank´s for your reply, but can´t get it to start even after trying everything I can come up with.

kernel = ‘/boot/vmlinuz-2.6.18-164.6.1.el5xen’
ramdisk = ‘/boot/initrd-2.6.18-164.6.1.el5xen.img’
memory = ’512′
root = ‘/dev/xvda2 ro’
disk = ['file:/var/vm/endian-swap.img,xvda1,w", 'file:/var/vm/endian-disk.img,xvda2,w" ]
name = ‘endian’
vif = ['ip=192.168.1.10,bridge=xenbr0,vifname=endian_red']
on_poweroff = ‘destroy’
on_reboot = ‘restart’
on_crash = ‘restart’
vcpus = 1
extra = ’2 console=xvc0 xencons=xvc0′

I´m using the image directly to test starting upp, maybe I should try to create the LVM to test if it helps.

My endian domu´s fstab:
proc /proc proc defaults 0 0
none /dev/pts devpts gid=5,mode=620 0 0
/dev/xvda1 none swap sw 0 0
/dev/xvda2 / ext3 defaults,errors=remount-ro 0 1