Hi All,
We tested the PV driver on HVM domain.
When ten vif was defined in configuration file for VNIF,
the HVM domain was not able to be created.
----------------------------------------------------------
# grep vif RHEL5GA_test.conf
vif = [ 'mac=02:17:42:2f:01:11, bridge=xenbr0',
'mac=02:17:42:2f:03:11, bridge=xenbr2',
'mac=02:17:42:2f:01:12, bridge=xenbr0',
'mac=02:17:42:2f:03:12, bridge=xenbr2',
'mac=02:17:42:2f:01:13, bridge=xenbr0',
'mac=02:17:42:2f:03:13, bridge=xenbr2',
'mac=02:17:42:2f:01:14, bridge=xenbr0',
'mac=02:17:42:2f:03:14, bridge=xenbr2',
'mac=02:17:42:2f:01:15, bridge=xenbr0',
'mac=02:17:42:2f:03:15, bridge=xenbr2' ]
# xm create -f RHEL5GA.conf
Using config file "./RHEL5GA.conf".
Started domain RHEL5GA
# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 1024 4 r----- 291.1
RHEL5GA 10 2048 1 ------ 0.0
# cat /var/log/xen/qemu-XXX.log
domid: 10
qemu: the number of cpus is 1
Too Many NICs
----------------------------------------------------------
The cause is to exceed the number of maximum in ioemu NIC.(MAX_NICS=8)
However, VNIF can be used because of nine more expanding grant table.
We usually use and operate VNIF of ten or more.
Even if the maximum number of ioemu NICs is exceeded when VNIF is used,
the HVM domain should be able to be created.
It was corrected that ioemu disregarded it
when the maximum number of NIC was exceeded.
It has been confirmed that the problem solves by this patch.
Signed-off-by: Takanori Kasai <kasai.takanori@xxxxxxxxxxxxxx>
Signed-off-by: Tsunehisa Doi <Doi.Tsunehisa@xxxxxxxxxxxxxx>
Best Regards,
--
Takanori Kasai
exceed-ioemu-max-nics-for-vnif.patch
Description: Binary data
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home