This message should be sent to the list (sorry if it was already).
---------- Forwarded message ----------
From: Tiantian Liu <tiantianl@xxxxxxxxx>
Date: Fri, Jul 29, 2011 at 9:37 AM
Subject: VM's vif didn't work in Xen 4.2 unstable
To: todd.deshane@xxxxxxx
Hi
I built Xen-4.2-unstable and kernel-2.6.32.40 on CentOS 5.5
successfully! I also implemented fault tolerance and high avaliability
via remus.
But I got new problems:
1. The vif of VM didn't work, when I start a new VM by command: "xm
cr myvm.hvm", system returned message: "the <VM> does not exist".
my VM's configuration file is:
ernel = "hvmloader"
builder='hvm'
memory = 512
name = "myvm"
vcpus=4
vif = [ 'type=ioemu, bridge=eth0,mac=00:16:3e:3a:7a:dd' ]
pae = 1
acpi = 1
apic = 1
#disk = [ 'file:/home/xen/tpl/hvm/base.img,hda,w',
'file:/home/xen/tpl/hvm/CentOS-5.5-x86_64-bin-DVD-1of2.iso,hdc:cdrom,r'
]
disk = [ 'file:/home/xen/tpl/hvm/win.img,hda,w',
'file:/home/xen/tpl/hvm/windows-XP.iso,hdc:cdrom,r' ]
device_model = 'qemu-dm'
boot="cd"
sdl = 0
vnc = 1
vnclisten = "0.0.0.0"
stdvga = 0
serial = "pty"
if I deleted the "vif = [ 'type=ioemu,
bridge=eth0,mac=00:16:3e:3a:7a:dd' ]" , the vm started successfully,
but the VM could not access network.
I have installed the bridge-utilty package properly.
I checked the /val/log/message, it showed:
Jul 29 04:04:34vnix06 kernel: [ 205.540203] device vif1.0 entered
promiscuous mode
Jul 29 04:04:34 vnix06 kernel: [ 205.545969] eth0: port 2(vif1.0)
entering forwarding state
Jul 29 04:04:34 vnix06 kernel: [ 205.811565] eth0: port 2(vif1.0)
entering disabled state
Jul 29 04:04:34 vnix06 kernel: [ 205.818948] device vif1.0 left
promiscuous mode
Jul 29 04:04:34 vnix06 kernel: [ 205.818955] eth0: port 2(vif1.0)
entering disabled state
Jul 29 04:04:35 vnix06 logger: /etc/xen/scripts/block: Path closed
or removed during hotplug add: backend/vbd/1/5632 state: 6
Jul 29 04:04:35 vnix06 logger: /etc/xen/scripts/block:
xenstore-read backend/vbd/1/5632/node failed.
Jul 29 04:04:35 vnix06 logger: /etc/xen/scripts/block:
/etc/xen/scripts/block failed; error detected.
could you tell me how to address this problem?
2. The NFS worked well in CentOS5.5, but when I compiled
kernel-2.6.32-40 and Xen-4.2-unstable and got into dom0.
the NFS didn't work, and could not mount the remote NFS server. I
tried command: "service nfs restart", but the failed.
I used command: "mount <IP>:/home /mnt", the system returned:
mount <IP>/home /mnt
mount.nfs: No such device
what's wrong?
I am waiting for your help! thank you very much!
--
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
|
Home