[one-users] Xen deployment problems (Users Digest, Vol 52, Issue 2)

[Rolandas Naujikas]

On 2012-06-01 12:35, Marcin Jarzab wrote:
> I tried to deploy VM on the XEN platform and have some problems.
>
> Platform is Ubuntu 12.04 (frontend and Xen hypervisor) with the NFS
> shared storage configuration.
>
> The deployment file:
> name = 'one-8'
> #O CPU_CREDITS = 256
> memory = '1024'
> vcpus = '1'
> bootloader = "/usr/lib/xen/boot/hvmloader"
> disk = [
> 'tap:aio:/srv/cloud/one/var//datastores/0/8/disk.0,hdc,r',
> 'tap:aio:/srv/cloud/one/var//datastores/0/8/disk.1,hda,w',

In Debian 6.0 and probably in Ubuntu also Xen is distributed without 
blktap device driver, so no support for tap:aio:. In newer Debian 7.0 
(testing/weezy) or Ubuntu 12.04 you probably can install package 
blktap-dkms and have this feature.

Regards, Rolandas Naujikas

> vif = [
> ' mac=02:00:ac:11:44:64,ip=172.17.68.100,bridge=xenbr0',
> ]
> vfb = ['type=vnc,vncdisplay=8']
>
> disk.0:
> file /srv/cloud/one/var//datastores/0/8/disk.0
> /srv/cloud/one/var//datastores/0/8/disk.0: # ISO 9660 CD-ROM filesystem
> data 'Ubuntu-Server 12.04 LTS i386 ' (bootable)
>
> disk.1:
> ../../1/ba1b95fee731571dca7d57feeba62dec: Linux rev 1.0 ext2 filesystem
> data, UUID=65f7eae2-efd4-43ce-80f2-5c8ed8075e9c (large files)
>
> 1. When using SunStone I got the first error related to permissions:
> ##################################################################################################
>
> ++ basename /var/tmp/one/vmm/xen/deploy
> Thu May 31 13:30:45 2012 [VMM][I]: ++ SCRIPT_NAME=deploy
> Thu May 31 13:30:45 2012 [VMM][I]: +
> domain=/srv/cloud/one/var//datastores/0/8/deployment.0
> Thu May 31 13:30:45 2012 [VMM][I]: ++ dirname
> /srv/cloud/one/var//datastores/0/8/deployment.0
> Thu May 31 13:30:45 2012 [VMM][I]: + mkdir -p
> /srv/cloud/one/var//datastores/0/8
> Thu May 31 13:30:45 2012 [VMM][I]: + cat
> Thu May 31 13:30:45 2012 [VMM][I]: ++ sudo /usr/sbin/xm create
> /srv/cloud/one/var//datastores/0/8/deployment.0
> Thu May 31 13:30:45 2012 [VMM][I]: Error: Disk isn't accessible
> /srv/cloud/one/var//datastores/0/8/disk.0
> Thu May 31 13:30:45 2012 [VMM][I]: + output='Using config file
> "/srv/cloud/one/var//datastores/0/8/deployment.0".'
> Thu May 31 13:30:45 2012 [VMM][I]: + error_exit 1 'Unable to create domain'
> Thu May 31 13:30:45 2012 [VMM][I]: + exit_code=1
> Thu May 31 13:30:45 2012 [VMM][I]: + message='Unable to create domain'
> Thu May 31 13:30:45 2012 [VMM][I]: + '[' x1 '!=' x0 ']'
> Thu May 31 13:30:45 2012 [VMM][I]: + error_message Unable to create domain
> Thu May 31 13:30:45 2012 [VMM][I]: + echo 'ERROR MESSAGE --8<------'
> Thu May 31 13:30:45 2012 [VMM][E]: + echo Unable
> ###################################################################################################
>
>
> 2. After logging on the target machine I run the regular Xen command and
> it seems that
> there are problems with files permissions.
>
> sudo /usr/sbin/xm create /srv/cloud/one/var//datastores/0/8/deployment.0
> Error: Disk isn't accessible /srv/cloud/one/var//datastores/0/8/disk.0
> oneadmin at host$ ls -al /srv/cloud/one/var//datastores/0/8/disk.0
> -rw-r----- 1 oneadmin cloud 705998848 May 31 13:30
> /srv/cloud/one/var//datastores/0/8/disk.0
>
> How to solve the permission problem to be set automatically by the ONE.
>
> 3. After channging the mode to 644 the command starts but it hangs:
>
> DEBUG (XendBootloader:113) Launching bootloader as
> [\047/usr/lib/xen/boot/hvmloader\047,
> \047--output=/var/run/xend/boot/xenbl.11066\047, \047-q\047,
> \047/srv/cloud/one/var//datastores/0/8/disk.0\047].
> [2012-06-01 10:10:43 1341] TRACE (XendDomainInfo:3525)
> XendDomainInfo.update({\047paused\047: 0, \047cpu_time\047:
> 273759722900L, \047ssidref\047: 0, \047hvm\047: 0,
> \047shutdown_reason\047: 255, \047dying\047: 0, \047mem_kb\047: 523908L,
> \047domid\047: 0, \047max_vcpu_id\047: 7, \047crashed\047: 0,
> \047running\047: 1, \047maxmem_kb\047: 524288L, \047shutdown\047: 0,
> \047online_vcpus\047: 8, \047handle\047: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
> 0, 0, 0, 0, 0, 0], \047cpupool\047: 0, \047blocked\047: 0}) on domain 0
>
> Any idea why the VM hangs during boot up process?
>
>