Re: [Xen-users] Xen 4 with Suse 11.0

[Mark Pryor <tlviewer@xxxxxxxxx>]

--- On Tue, 3/29/11, JOSÉ FORMIGA <jformiga.rs@xxxxxxxxx> wrote:

From: JOSÉ FORMIGA <jformiga.rs@xxxxxxxxx>
Subject: [Xen-users] Xen 4 with Suse 11.0
To: xen-users@xxxxxxxxxxxxxxxxxxx
Date: Tuesday, March 29, 2011, 7:04 AM

Hi.
Please, I have a problem and I am not finding similar cases in internet.
I am using the http://wiki.xen-br.org/index.php?title=P2v-howto orientation and 
I am migranting a Suse 11.0.
 
After copy (rsync), and during VM startup, the process hang with these messages:
 
   0.940474] xvda1: detected capacity change from 0 to 96636764160
[    0.945347] blkfront: xvda2: barriers enabled
[    0.952885] Setting capacity to 18874368
[    0.954193] xvda2: detected capacity change from 0 to 9663676416

[    1.280398] device-mapper: uevent: version 1.0.3
[    1.286278] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: 
dm-devel@xxxxxxxxxx
[    1.423883] kjournald starting.  Commit interval 5 seconds

[    1.425335] EXT3-fs: mounted filesystem with ordered data mode.
[    5.729381] Adding 9437176k swap on /dev/xvda2.  Priority:-1 extents:1 
across:9437176k SS
[    6.257182] EXT3 FS on xvda1, internal journal
root@debian6:~#


Some idea about what is occuring ?
--------------
Your kernel/ramdisk are from Debian Squeeze. There the console is different. 
Change all

  xvc0->hvc0

Likely the bridge is wrong. Verify with `brctl show`

  xenbr0->eth0

-- 
Mark






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