On Friday, 02 April 2010 at 22:29, Minjia Zhang wrote:
> I fail to use remus with xen-unstable (4.1)+ Linux-184.108.40.206:
> [root@server1 img]# xm create rhel5.hvm
> Using config file "./rhel5.hvm".
> Error: Device 768 (tap) could not be connected.
> server1:9000|aio:/dev/vgxen/hvmsnap does not exist
> Am I missing something? Any hints will be appreciated.
> According to Brendan's instruction on http://dsg.cs.ubc.ca/remus/doc.html
> the config should like following:
> disk = [ 'tap:remus:bkup:9000|aio:/dev/vmdisk/myguest,xvda1,w' ]
> According to my understanding，remus doesn't need the support of DRBD, cause
> it can continuously send memory state to backup server as well as write
> operation and network
> packages. So, what I do is to only ensure that /dev/vgxen/hvmsnap existing
> on both the primary and the backup and contain identical data.
> My config file:
> 1 import os, re
> 2 arch = os.uname()
> 3 if re.search('64', arch):
> 4 arch_libdir = 'lib64'
> 5 else:
> 6 arch_libdir = 'lib'
> 7 kernel = '/usr/lib/xen/boot/hvmloader'
> 8 builder = 'hvm'
> 9 memory = '512'
> 14 disk = [ 'tap:remus:server1:9000|aio:/dev/vgxen/hvmsnap,hda,w']
> 16 vif = ['type=ioemu, mac=00:1c:3e:17:22:13']
> 17 #boot = 'dc'
> 18 boot = 'c'
> 19 name = 'Rhel5-hvm1'
> 20 acpi = 1
> 21 apic = 1
> 22 device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
> 23 vnc=1
> 24 vncdisplay=2
> 25 sdl=0
> 26 opengl=1
> 27 vnclisten="0.0.0.0"
> 28 vncpasswd=''
> 29 serial='pty'
> "hvm.hvm" 29L, 975C
This config looks ok to me. You'll get an error like that with pygrub,
which doesn't work with the Remus disk replication yet, but your HVM
config looks correct. I've just tested 32-bit HVM ubuntu on
xen-4.0-testing (rc9), and this syntax works here.
I don't suppose you have any more information in /var/log/daemon.log
or the xen logs (e.g., /var/log/xen/xend.log) ?
Xen-devel mailing list