Re: [Libvirt-cim] [PATCH] [TEST] #3 LXC support using DefineSystem & VSMS.01
zli(a)linux.vnet.ibm.com wrote:
diff -r 5c77329cb53e -r 277b821188f2
suites/libvirt-cim/lib/XenKvmLib/const.py
--- a/suites/libvirt-cim/lib/XenKvmLib/const.py Fri May 30 14:26:38 2008 +0800
+++ b/suites/libvirt-cim/lib/XenKvmLib/const.py Wed Jun 04 10:06:11 2008 +0800
@@ -85,3 +85,5 @@
#vxml.LXCXML
LXC_init_path = os.path.join(_image_dir, 'cimtest_lxc_init')
LXC_default_tty = '/dev/ptmx'
+LXC_default_mp = '/tmp'
+LXC_default_source = '/tmp/lxc_files'
The LXC_init_path used to be created by 'create_lxc_files' in vxml.py.
It's not created here. But somehow libvirt shows me a running container
even if the init_path file doesn't exist.
The same with LXC_default_source. It's a non-exist directory.
I am inclined to move the init_path and default_source to the place
where xen/kvm kernel image and disk image is created. Then we don't need
to create a init_path upon every test case execution.
Thoughts?
--
- Zhengang