[Xen-users] Wierd behavior of DomU after migration

Hi,

I have a problem with one DomU after migration. The problem is
reproduceable although I don't have any clue how this is happening.

My Setup:
Multiple Logical Volumes for the DomUs (using CLVM on two Dom0s, every
Dom0 has the same lvs output, all LVs are active):

[root@jbtest01 vm]# lvs
  LV                    VG         Attr   LSize  
  apache-private-1      vm         -wi-a-   2.00G
  apache-private-2      vm         -wi-a-   2.00G
  apache-root           vm         -wi-a-   6.00G
  apache-swap-1         vm         -wi-a- 512.00M
  apache-swap-2         vm         -wi-a- 512.00M
  jboss-common          vm         -wi-ao   2.00G
  jboss-private-1       vm         -wi-ao   2.00G
  jboss-private-2       vm         -wi-ao   2.00G
  jboss-private-3       vm         -wi-ao   2.00G
  jboss-private-4       vm         -wi-ao   2.00G
  jboss-private-5       vm         -wi-ao   2.00G
  jboss-private-6       vm         -wi-ao   2.00G
  jboss-root            vm         -wi-ao   6.00G
  jboss-swap-1          vm         -wi-ao 512.00M
  jboss-swap-2          vm         -wi-ao 512.00M
  jboss-swap-3          vm         -wi-ao 512.00M
  jboss-swap-4          vm         -wi-ao 512.00M
  jboss-swap-5          vm         -wi-ao 512.00M
  jboss-swap-6          vm         -wi-ao 512.00M
 
Two xen configurations to create 6 jboss and 2 apache DomUs.
These two classes share the jboss-root or apache-root LV in a read-only
manner (the Guest OS is configured to be read-only, and the disk is
exported read-only).
I have 6 jboss VMs running and can migrate them without problems between
two Dom0s.

The only difference between the apache and the jboss Dom0s is that the
jboss-root LV has a partition table (two partitions with ext3) and is
booted via pygrub boatloader and the apache-root LV has no partition
table (ext3 filesystem) and is booted via a kernel lying in the Dom0.
Nothing is mounted in the Dom0s.

I can create 2 apache DomUs on one Dom0 and they work without a problem.

But now comes the Problem:
As soon as I migrate an apache DomU to the other Dom0 it starts behaving
wierd. While the migrated DomU is still running (and apache still
working) after the migration I can't use most of the commands on the
machine:

[root@apache-1 ~]# less /var/log/messages
/usr/bin/less: line 1: syntax error near unexpected token `newline'
/usr/bin/less: line 1: `O_ELLIPSIZE_NONE</property>'
[root@apache-1 ~]# halt
shutdown: No such file or directory
[root@apache-1 ~]# which ls
-bash: /usr/bin/which: Permission denied
[root@apache-1 ~]# ls
[root@apache-1 ~]# vi
/bin/vi: line 1: 4247: Read-only file system
/bin/vi: line 2: e89cb5: No such file or directory
/bin/vi: line 3: e89cb7: No such file or directory
/bin/vi: line 4: e89cb8: No such file or directory

It looks like programs under /usr aren't working anymore (just a guess).
The DomU only has 2 partitions in use (everything is installed in / +
swap).

Remember migrating the jboss DomUs just works fine.
What could be the problem? That I'm using a kernel that is lying in the
Dom0 (and is not available on the other Dom0)?

Thanks,
Reinhard


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users