search for: nedospasov

...inuously, correct? Can someone explain why this would happen. Could this be caused by a xend restart? After googling, I''m surprised a best practice solution isn''t listed on XenFaq... considering how many users seem to be frustrated with this issue. All the best, D. -- Dmitry Nedospasov <dmitry@nedos.net> -- Twitter: @nedos Web: http://nedos.net -- Github: http://github.com/nedos _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...ot; -j ACCEPT 2>/dev/null >From what i can tell the goal of these lines is to allow networking even if the default FORWARD policy is DENY, am I right? Is there any additional side-effect if I comment these lines out in vim-common.sh, that I''m not considering? Thanks, D. -- Dmitry Nedospasov <dmitry@nedos.net> -- Twitter: @nedos Web: http://nedos.net -- Github: http://github.com/nedos _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Dear All. I have set up a Xen testbed on a computer.(Dom0 use debian lenny) I would like to know the possible ways to monitor the network traffic of DomU''s from Dom0. # command ''xentop'' display NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) VBDS VBD_OO VBD_RD VBD_WR SSID debianlenny --b--- 14 0.0 270204 25.8 278528 26.6 1 0 0

This is a relatively simple fix i found, I don't know if it need to be reported to upstream. Since the script resolves additional dependencies anyway by appending the path, we simply move the import xen.lowlevel.xc line to below the line that appends path. Worked like a charm for me. Rergards, Dmitry -------------- next part -------------- A non-text attachment was scrubbed... Name:

>From FAQ, it seems that oVirt didn't support XEN..but... Does current oVirt release support XEN? -- Tao-Sheng Chen -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ovirt-devel/attachments/20100225/b1101f28/attachment.htm>

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

Package: xen-utils-4.0 Version: 4.0.1~rc3-1 Severity: important When invoking pygrub either via command line or via bootloader being set in the configuration file, pygrub fails because it cannot import xen.lowlevel.xc. Example output: # /usr/lib/xen-default/bin/pygrub Traceback (most recent call last): File "/usr/lib/xen-default/bin/pygrub", line 20, in <module> import

Hi Everyone, I am stack between two identical systems (2U Twin2, 4 nodes, SuperMicro) servers that have the same exact specs except for HDDs. These nodes will all either have Asterisk installed with CentOS or will have Asterisk install in virtual environment. Option 1: *12* x 3.5" HDD (3 HDDs per node) Option 2: *24* x 2.5" HDD (6 HDDs per node) **both options come to the same price.

Today i Upgraded to 4.0.1~rc5-1, this overwrote my local changes to /lib/xen-default/bin/pygrub, and pygrub began to silently fail again. Can we please just apply my patch. This simply moves the line calling xenlovel to the line after which the path can be correctly resolved. As of now, pygrub "simply" fails silently, which is very, very, very confusing, and apparently I get to