search for: shaunr

...1 kernel parameter, acct=1 nf_conntrack module option or sysctl net.netfilter.nf_conntrack_acct=1 to enable it. physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. ---------------------------------------------------- ~ShaunR _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I run my production DomU''s using Xen 3.4.1 at the moment with the old 2.6.18.x dom0 kernel. I just built a new Xen version (4.0.1-rc5) with jemerys git repo of 2.6.32.16 dom0 pvops kernel. When starting domains the go instantly into a paused state and eventually i see this error on the command line. [root@host test1]# xm create -c vps.config Using config file

Years ago when i first started using xen i specified a dom0_mem=xxx in grub. I no longer do this, what i do now is set the dom0_min-mem setting in xend-config.sxp to 1024. I also have a few scripts that run at boot and one of them does a `xm mem-set 0 1024`. after that a xm list 0 shows dom0 allocated 1024 Ram. The problem comes on teh system when i run free or free -m, free shows dom0

This patch fixes the problem with xentop where it returns an exit code of 0 when passing it invalid options when it should return 1. The issue comes from getopt() returning ''?'' and the case from switch matching it. The solution was to remove the case ''?'' so that the default match could be triggered. Quote from `man 3 getopt` "If getopt() does not