I have recently moved to using snv66+xen with the intention of migrating all of my domU''s across from a CentOS server. So far, after having enabled all the xctl services and creating what appears to be a valid xen client configuration file, I am having significant issues booting. My file-backed storage appears to be the issue at hand, which was originally defined under CentOS as: disk = [ ''tap:aio:/xen/images/c5-Services-1.img,xvda,w'' ] but it appears the tap:aio naming mechanism does not appear to work in the snv66+xen drop. Upon creating the running instance I see the following output: (terminal) # xm create c5-Services-1 -c Using config file "/etc/xen/c5-Services-1". Error: (xend.log) [2007-08-13 07:15:33 xend 29541] DEBUG (DevController:549) destroyCallback /loca l/domain/7/device/vbd/51712. [2007-08-13 07:15:43 xend 29541] ERROR (xmlrpclib2:218) Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/util/xmlrpclib2.py", line 197, in _ marshaled_dispatch File "/usr/lib/python2.4/SimpleXMLRPCServer.py", line 406, in _dispatch return func(*params) File "<string>", line 1, in <lambda> File "/usr/lib/python2.4/site-packages/xen/xend/server/ XMLRPCServer.py", line 52, in dispatch File "/usr/lib/python2.4/site-packages/xen/xend/ XendDomainInfo.py", line 518, in waitForDevices File "/usr/lib/python2.4/site-packages/xen/xend/server/ DevController.py", line 150, in waitForDevices File "/usr/lib/python2.4/site-packages/xen/xend/server/ DevController.py", line 159, in waitForDevice File "/usr/lib/python2.4/site-packages/xen/xend/server/blkif.py", line 146, in destroyDevice File "/usr/lib/python2.4/site-packages/xen/xend/server/ DevController.py", line 237, in destroyDevice EnvironmentError Performing a similat test with file backed storage (changing only the tap:aio to file) the system attempts to boot, however, the storage device is not discovered via probing during boot so it eventually fails with: switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! Any suggestions on how to proceed would be greatly appreciated. cheers, James
On Mon, Aug 13, 2007 at 07:22:52AM +1000, James Lever wrote:> My file-backed storage appears to be the issue at hand, which was > originally defined under CentOS as: > > disk = [ ''tap:aio:/xen/images/c5-Services-1.img,xvda,w'' ] > > but it appears the tap:aio naming mechanism does not appear to work > in the snv66+xen drop.The ''blktap'' mechanism for providing disk access from dom0 is not currently supported on Solaris.> Performing a similat test with file backed storage (changing only the > tap:aio to file) the system attempts to boot, however, the storage > device is not discovered via probing during boot so it eventually > fails with: > > switchroot: mount failed: No such file or directory > Kernel panic - not syncing: Attempted to kill init! > > Any suggestions on how to proceed would be greatly appreciated.The file /var/log/xpvd-event.log provides some debugging information about what happened during backend device creation. It would be useful to check that the backend device was successfully created, the file opened, etc. (include the relevant contents of the file if appropriate). What (Linux?) distribution is the guest running? Is it the default Xen kernel for that distribution? dme.
Hi David, On 13/08/2007, at 4:00 PM, David Edmondson wrote:> On Mon, Aug 13, 2007 at 07:22:52AM +1000, James Lever wrote:>> Performing a similar test with file backed storage (changing only the >> tap:aio to file) the system attempts to boot, however, the storage >> device is not discovered via probing during boot so it eventually >> fails with: >> >> switchroot: mount failed: No such file or directory >> Kernel panic - not syncing: Attempted to kill init! >> >> Any suggestions on how to proceed would be greatly appreciated. > > The file /var/log/xpvd-event.log provides some debugging information > about what happened during backend device creation. It would be useful > to check that the backend device was successfully created, the file > opened, etc. (include the relevant contents of the file if > appropriate).When using file:/path/to/disk-image-filename.img,xvda,w in my file variable, I can see it connecting ala: + xenstore-read backend/vbd/57/51712/type type=file + xenstore-read backend/vbd/57/51712/params file=/xen/images/c5-Services-1.img + [ file = file ] + [ ! -f /xen/images/c5-Services-1.img ] + xenstore-write backend/vbd/57/51712/physical-device 0:0 + connect + xenstore-write backend/vbd/57/51712/hotplug-status connected + exit I wonder if the issue is possibly a combination of the tap:aio interface and LVM probiing?> What (Linux?) distribution is the guest running? Is it the default Xen > kernel for that distribution?This is CentOS 5 latest updates running the default xen kernel. cheers, James
On Mon, Aug 13, 2007 at 07:22:52AM +1000, James Lever wrote:> Performing a similat test with file backed storage (changing only the > tap:aio to file) the system attempts to boot, however, the storage > device is not discovered via probing during boot so it eventually > fails with: > > switchroot: mount failed: No such file or directory > Kernel panic - not syncing: Attempted to kill init!Some Linux versions have a race with mounting the root filesystem. I believe at least an up to date CentOS 5 domU should not have this problem. regards john
On 13/08/2007, at 10:21 PM, John Levon wrote:> Some Linux versions have a race with mounting the root filesystem. > I believe at > least an up to date CentOS 5 domU should not have this problem.I think this one is possibly more to do with the type of device being presented and that it is using LVM above the filesystem layer. This domU is running kernel-2.6.18-8.1.8.el5xen (updated within the last 2 weeks). cheers, James