Migration Squeeze vers Wheezy => les DomU de xen ne démarrent plus

Bonjour,

Je viens de passer un Dom0 de squeeze xen4.0 vers wheezy xen 4.1.

Le problème est que je n'arrive pas à redémarrer les DomU (PV) ni à
démarrer un DomU fraîchement créé.

le stockage des DomU est sur du lvm lui-même sur du raid5.

Le symptôme pour le fraîchement créé est que le DomU attend ces disques
en les identifiant sur le lvm du Dom0...

<---------------- Configuration du DomU nuage ------------------------>
kernel = '/boot/vmlinuz-3.2.0-4-amd64'
ramdisk = '/boot/initrd.img-3.2.0-4-amd64'
vcpus = '1'
memory = '1024'
xen_platform_pci = 1
root = '/dev/xvda2 ro'
disk = [
'phy:/dev/g00/nuage-root,xvda2,w',
'phy:/dev/g00/nuage-oc-data,xvda5,w',
'phy:/dev/g00/nuage-home,xvda4,w',
'phy:/dev/g00/nuage-var,xvda3,w',
'phy:/dev/g00/nuage-swap,xvda1,w',
]
name = 'nuage'
vif = [ 'ip=192.168.3.40 ,mac=00:16:3E:C8:19:AB,bridge=br_safe'
]
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
<---------------- Configuration du DomU nuage ------------------------>

<--------------- Trace de la console du create ----------------------->
[ 1.092595] XENBUS: Device with no driver: device/vbd/51714
[ 1.092599] XENBUS: Device with no driver: device/vbd/51717
[ 1.092602] XENBUS: Device with no driver: device/vbd/51716
[ 1.092605] XENBUS: Device with no driver: device/vbd/51715
[ 1.092608] XENBUS: Device with no driver: device/vbd/51713
[ 1.092611] XENBUS: Device with no driver: device/vif/0
[ 1.092616] /build/linux-5VIh7j/linux-3.2.78/drivers/rtc/hctosys.c:
unable to open rtc device (rtc0)
[ 1.092636] Initializing network drop monitor service
[ 1.092898] Freeing unused kernel memory: 584k freed
[ 1.093090] Write protecting the kernel read-only data: 6144k
[ 1.095784] Freeing unused kernel memory: 640k freed
[ 1.096373] Freeing unused kernel memory: 684k freed
Loading, please wait...
[ 1.192426] udevd[49]: starting version 175
Begin: Loading essential drivers ... [ 1.272261] SCSI subsystem
initialized
[ 1.281803] microcode: no support for this CPU vendor
modprobe: can't load module microcode
(kernel/arch/x86/kernel/microcode.ko): No such device
done.
Begin: Running /scripts/init-premount ... Begin: Requesting microcode
update using per-core interface ... done.
done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top
... Begin: Assembling all MD arrays ... mdadm: No devices listed in conf
file were found.
Failure: failed to assemble all arrays.
done.
[ 1.303958] device-mapper: uevent: version 1.0.3
[ 1.304332] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19)
initialised: dm-devel@redhat.com
Volume group "g00" not found
Skipping volume group g00
Unable to find LVM volume g00/swap
done.
Begin: Waiting for root file system ...
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/xvda2 does not exist. Dropping to a shell!
modprobe: module ehci-hcd not found in modules.dep
modprobe: module uhci-hcd not found in modules.dep
modprobe: module ohci-hcd not found in modules.dep
modprobe: module usbhid not found in modules.dep


BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)
<--------------- Trace de la console du create ----------------------->


les lignes de message du type "XENBUS: Device with no driver"
m'interpellent mais je ne trouve pas leur cause (xen_platform_pci n'y
change rien du moins vu comme je l'ai utilisé).

Je tourne en rond depuis une douzaine d'heures...

J'ai recopié le répertoire /lib/3.2.0-4-amd64 de Dom0 sur
/dev/g00/nuage-root/
(http://wiki.linuxservertech.com/index.php?action=artikel&cat=2&id=174&artlang=en)

Pour les anciens qui démarrait avec pygrub, j'ai replacé le démarrage
par
kernel = '/boot/vmlinuz-3.2.0-4-amd64'
ramdisk = '/boot/initrd.img-3.2.0-4-amd64'
#bootloader = '/usr/lib/xen-default/bin/pygrub'

Même symptôme au démarrage...


J'ai donc râté un truc mais quoi !?

Merci
et bon Dimanche à vous

Yann.