search for: keeler

Package: xen Version: 4.0.1-2 Severity: normal /proc/uptime shows idle bigger than uptime: dom0: % cat /proc/uptime 518389.91 944378.70 % one domU: % cat /proc/uptime 417536.22 764826.15 % another domU: % cat /proc/uptime 426960.17 795800.89 % This is normal on multicore / ht cpu, but this is old amd: % lscpu Architecture: i686 CPU(s): 1 Thread(s) per core: 1

Package: xen-utils-4.0 Version: 4.0.1~rc3-1 Severity: wishlist Please include pv-grub images in xen-utils or as a seperate package. Pv-grub allows securely booting guest kernels. [0] http://wiki.xensource.com/xenwiki/PvGrub -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux

...parts are command line compatible. - Add a selector to /etc/default/xend: IMPLEMENTATION=xm/xl - Make xm/xl error out if the other implementation is selected and supported/available. - Start xend only is xm is used. Bastian -- Lots of people drink from the wrong bottle sometimes. -- Edith Keeler, "The City on the Edge of Forever", stardate unknown

After upgrading to xen unstable packages I'm seeing the following problem: skx@itchy:~$ sudo /etc/init.d/xend restart Restarting XEN control daemon: xendTraceback (most recent call last): File "/usr/lib/xen-3.0-unstable-1/bin/xend", line 40, in ? from xen.xend.server import SrvDaemon File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 17,

Hi, I followed this guide<http://wiki.kartbuilding.net/index.php/Xen_Networking#Routed_Networking_with_NAT_2>, and started my xend service with nat-network support: (network-script network-nat) (vif-script vif-nat) Then I started my domU with the following vif configure: vif = [''ip=10.0.0.1'' ] my domU is a win7 system, and I configured the network as: ip: