Hi,
I added additional storage to my domU using xm block-attach and tap:aio.
Then increased my root device (using vgextend, lvextend and resizefs) which
is / or /dev/mapper/VolGroup00-LogVol00. Everything worked fine util I did
"xm save domid test1.img"
This stopped my domU. And now when I run: xm create domU -c , I am seeing
--
Scanning logical volumes
Reading all physical volumes. This may take a while...
Couldn''t find device with uuid
''5VJWnI-e3u7-66nX-wGT0-wHlO-CXAU-Nid3ma''.
Found volume group "VolGroup00" using metadata type lvm2
Activating logical volumes
Couldn''t find device with uuid
''5VJWnI-e3u7-66nX-wGT0-wHlO-CXAU-Nid3ma''.
Couldn''t find device with uuid
''5VJWnI-e3u7-66nX-wGT0-wHlO-CXAU-Nid3ma''.
Refusing activation of partial LV LogVol00. Use --partial to override.
Couldn''t find device with uuid
''5VJWnI-e3u7-66nX-wGT0-wHlO-CXAU-Nid3ma''.
1 logical volume(s) in volume group "VolGroup00" now active
Creating root device.
Mounting root filesystem.
mount: could not find filesystem ''/dev/root''
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
----
But I can run my domU using: xm restore test1.img (ignoring some errors
like: EXT3-fs error (device dm-0): ext3_lookup: unlinked inode 726639 in dir
#717378
)
So what might have gone bad here?
Thanks !
Paras.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
