WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 		  
Home Products Support Community News
 
   
 

xen-users

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [Xen-users] [Q] VmError: Disk isn't accessible with tap2:tapdisk:vhd

from [Todd Deshane] [Permanent Link][Original]
To: Hiroyuki Sato <hiroysato@xxxxxxxxx>
Subject: Re: [Xen-users] [Q] VmError: Disk isn't accessible with tap2:tapdisk:vhd
From: Todd Deshane <todd.deshane@xxxxxxx>
Date: Thu, 4 Aug 2011 12:38:54 -0400
Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 04 Aug 2011 09:40:39 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=lfns0eBL7byqBCB7txb+AMcDIdzVnN6qL9vpt/LgrPo=; b=F/uk7k/25aAZQ98pFq2B9xulJ+cuYp1J1OJJFHL0ShY8kcGkJgXTh4HI9p299pr6W1 9yiszUoOkVOW6mE4l8YPcsCyCTObtwEed3abwcrcuk5FXeQKDVLnYpWgJV7rRF4kwF3n Z+BUmlwbwjqIunl01CD/luKD4tG6F2gFmVJ38=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CA+Tq-RosyHiQ_ib10KSatXXTZj5qVg=A58N6=p-9AoWnM8G_gg@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <CA+Tq-RosyHiQ_ib10KSatXXTZj5qVg=A58N6=p-9AoWnM8G_gg@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
On Thu, Aug 4, 2011 at 5:19 AM, Hiroyuki Sato <hiroysato@xxxxxxxxx> wrote:
> I'm newbie Xen-4.1.1
>
> I'm trying to boot DomU with the following configuration.
> Sometime DomU boot, but sometime boot failed
>
> I'm not sure what is the problem.
>
> I can attach that image with tap-ctl on Dom0.
>
> Does anybody advice me about this problem??
>
> Sincerely
>
> * Environment
>
>  OS : Scientific Linux 6.1 x86_64
>  Kernel : 2.6.32.43
>      git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
>  Xen : 4.1.1
>
>
> * Error
>
> #
> # tap2:tapdisk:vhd
> #
>
>  /usr/sbin/xm create xentest2 -c
>  Using config file "./xentest2".
>  Error: Disk isn't accessible
>
>
>  cat xentest2
>  name    = "test"
>  maxmem  = 512
>  memory  = 512
>  vcpus   = 1
>  bootloader = "/usr/bin/pygrub"
>  on_poweroff = "destroy"
>  on_reboot = "restart"
>  on_crash = "restart"
>  disk = [ "tap2:tapdisk:vhd:/tmp/tkoan.22561/test.vnd,xvda,w" ]

Could it be that the disk specification is incorrect?
http://xen.markmail.org/search/?q=vhd%20tap#query:vhd%20tap+page:1+mid:qzorvzxlpchikvf6+state:results


>  vif = [ "mac=00:16:3e:10:e8:01,bridge=virbr0,script=vif-bridge" ]
>
>
>  # tap-ctl allocate
>  /dev/xen/blktap-2/tapdev0
>  # tap-ctl spawn
>  tapdisk spawned with pid 2004
>  # tap-ctl attach -p 2004 -m 0
>  # tap-ctl open -p 2004 -m 0 -a vhd:/tmp/tkoan.22561/test.vnd
>  # tap-ctl list
>      2004  0    0        vhd /tmp/tkoan.22561/test.vnd
>  # sfdisk /dev/xen/blktap-2/
>  blktap0  control  tapdev0
>  # sfdisk -d /dev/xen/blktap-2/tapdev0
>  # partition table of /dev/xen/blktap-2/tapdev0
>  unit: sectors
>
>  /dev/xen/blktap-2/tapdev0p1 : start=     2048, size=   204800, Id=83, 
> bootable
>  /dev/xen/blktap-2/tapdev0p2 : start=   206848, size=  2097152, Id=82
>  /dev/xen/blktap-2/tapdev0p3 : start=  2304000, size= 18667520, Id=83
>  /dev/xen/blktap-2/tapdev0p4 : start=        0, size=        0, Id= 0
>
> * log
>
> [2011-08-04 17:49:39 1676] DEBUG (XendDomainInfo:103)
> XendDomainInfo.create(['vm', ['name', 'test'], ['memory', 512],
> ['maxmem', 512], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'],
> ['on_crash', 'restart'], ['on_xend_start', 'ignore'], ['on_xend_stop',
> 'ignore'], ['vcpus', 1], ['oos', 1], ['bootloader',
> '/usr/bin/pygrub'], ['bootloader_args', ''], ['image', ['linux',
> ['videoram', 4], ['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity',
> 1], ['device', ['tap2', ['uname',
> 'tap2:tapdisk:vhd:/tmp/tkoan.22561/test.vnd'], ['dev', 'xvda'],
> ['mode', 'w']]], ['device', ['vif', ['bridge', 'virbr0'], ['mac',
> '00:16:3e:10:e8:01'], ['script', 'vif-bridge']]]])
> [2011-08-04 17:49:39 1676] DEBUG (XendDomainInfo:2498)
> XendDomainInfo.constructDomain
> [2011-08-04 17:49:39 1676] DEBUG (balloon:187) Balloon: 884828 KiB
> free; need 16384; done.
> [2011-08-04 17:49:39 1676] DEBUG (XendDomain:476) Adding Domain: 1
> [2011-08-04 17:49:39 1676] DEBUG (XendDomainInfo:2836)
> XendDomainInfo.initDomain: 1 256
> [2011-08-04 17:49:39 1676] INFO (XendDomainInfo:3270) Mounting
> /tmp/tkoan.22561/test.vnd on /dev/xvdp.
> [2011-08-04 17:49:40 1676] DEBUG (DevController:95) DevController:
> writing {'backend-id': '0', 'virtual-device': '51952', 'device-type':
> 'disk', 'state': '1', 'backend':
> '/local/domain/0/backend/vbd/0/51952'} to
> /local/domain/0/device/vbd/51952.
> [2011-08-04 17:49:40 1676] DEBUG (DevController:97) DevController:
> writing {'domain': 'Domain-0', 'frontend':
> '/local/domain/0/device/vbd/51952', 'uuid':
> '85d3a006-d760-4eec-7a03-f7b05097e1c8', 'bootable': '0', 'dev':
> '/dev/xvdp', 'state': '1', 'params': '/dev/xen/blktap-2/tapdev0',
> 'mode': 'r', 'online': '1', 'frontend-id': '0', 'type': 'phy',
> 'tapdisk-params': 'tapdisk:vhd:/tmp/tkoan.22561/test.vnd'} to
> /local/domain/0/backend/vbd/0/51952.
> [2011-08-04 17:49:40 1676] DEBUG (DevController:144) Waiting for 51952.
> [2011-08-04 17:49:40 1676] DEBUG (DevController:628)
> hotplugStatusCallback
> /local/domain/0/backend/vbd/0/51952/hotplug-status.
> [2011-08-04 17:49:40 1676] DEBUG (DevController:628)
> hotplugStatusCallback
> /local/domain/0/backend/vbd/0/51952/hotplug-status.
> [2011-08-04 17:49:40 1676] DEBUG (DevController:642) hotplugStatusCallback 1.
> [2011-08-04 17:49:40 1676] DEBUG (DevController:144) Waiting for 51952.
> [2011-08-04 17:49:41 1676] DEBUG (DevController:628)
> hotplugStatusCallback
> /local/domain/0/backend/vbd/0/51952/hotplug-status.
> [2011-08-04 17:49:41 1676] DEBUG (DevController:642) hotplugStatusCallback 1.
> [2011-08-04 17:49:41 1676] ERROR (XendBootloader:43) Disk isn't accessible
> [2011-08-04 17:49:41 1676] INFO (XendDomainInfo:3289) Unmounting
> /dev/xvdp from /dev/xvdp.
> [2011-08-04 17:49:41 1676] DEBUG (XendDomainInfo:1276)
> XendDomainInfo.destroyDevice: deviceClass = tap2, device = /dev/xvdp
> [2011-08-04 17:49:41 1676] DEBUG (DevController:649)
> deviceDestroyCallback
> /local/domain/0/backend/vbd/0/51952/hotplug-status.
> [2011-08-04 17:49:41 1676] DEBUG (DevController:649)
> deviceDestroyCallback
> /local/domain/0/backend/vbd/0/51952/hotplug-status.
> [2011-08-04 17:49:41 1676] ERROR (XendDomainInfo:488) VM start failed
> Traceback (most recent call last):
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
> line 474, in start
>    XendTask.log_progress(31, 60, self._initDomain)
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line
> 209, in log_progress
>    retval = func(*args, **kwds)
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
> line 2838, in _initDomain
>    self._configureBootloader()
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
> line 3285, in _configureBootloader
>    bootloader_args, kernel, ramdisk, args)
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendBootloader.py",
> line 44, in bootloader
>    raise VmError(msg)
> VmError: Disk isn't accessible
> [2011-08-04 17:49:41 1676] DEBUG (XendDomainInfo:3071)
> XendDomainInfo.destroy: domid=1
> [2011-08-04 17:49:41 1676] DEBUG (DevController:658) deviceDestroyCallback 6.
> [2011-08-04 17:49:41 1676] DEBUG (XendDomainInfo:2406) No device model
> [2011-08-04 17:49:41 1676] DEBUG (XendDomainInfo:2408) Releasing devices
> [2011-08-04 17:49:41 1676] ERROR (XendDomainInfo:108) Domain construction 
> failed
> Traceback (most recent call last):
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
> line 106, in create
>    vm.start()
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
> line 474, in start
>    XendTask.log_progress(31, 60, self._initDomain)
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line
> 209, in log_progress
>    retval = func(*args, **kwds)
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
> line 2838, in _initDomain
>    self._configureBootloader()
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
> line 3285, in _configureBootloader
>    bootloader_args, kernel, ramdisk, args)
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendBootloader.py",
> line 44, in bootloader
>    raise VmError(msg)
> VmError: Disk isn't accessible
>
>
> --
> Hiroyuki Sato
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>



-- 
Todd Deshane
http://www.linkedin.com/in/deshantm
http://www.xen.org/products/cloudxen.html
http://runningxen.com/

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [Xen-users] XEN | kernel 3.0 vs 2.6.34-xen - no pci backend?, Todd Deshane
Next by Date:  Re: [Xen-users] Which kernel for Dual GPU Passthrough?, Todd Deshane
Previous by Thread:  [Xen-users] [Q] VmError: Disk isn't accessible with tap2:tapdisk:vhd, Hiroyuki Sato
Next by Thread:  Re: [Xen-users] [Q] VmError: Disk isn't accessible with tap2:tapdisk:vhd, Hiroyuki Sato
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy