similar to: [PATCH] New tool: virt-edit

Hi I am having some problems installing a paravirt RHEL guest on a deb amd64 xen machine uname -a = Linux debxen 2.6.20-1-xen-amd64 #1 SMP Tue Apr 24 22:23:22 UTC 2007 x86_64 GNU/Linux ============== xm info ============== host : debxen release : 2.6.20-1-xen-amd64 version : #1 SMP Tue Apr 24 22:23:22 UTC 2007 machine : x86_64

Returns free memory size per node in "xm info". This info can help users who want to bind their guest domain in one node of their NUMA machines thought set CPU affinity. I also write IA64 part support which I would send to XEN-IA64 mail-list. Thanks. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

# HG changeset patch # User john.levon@sun.com # Date 1196969481 28800 # Node ID 2c28ac4db1f7542220b1472821e8631b79b6a23a # Parent 4a98d4b6e4daccd610175e3c0f8cab49b056c649 Fix ioemu compile serial.c was including another Linux-specific header. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/tools/ioemu/hw/serial.c b/tools/ioemu/hw/serial.c --- a/tools/ioemu/hw/serial.c +++

Before, in my "Hard Problem" email I was trying to communicate a design issue were trying to solve with Xen. This is what we need to do: 1) Deploy 24 Windows XP VMs in parallel. 2) Boot them from a shared Windows XP C: drive. 3) Since this is a read-only shared image we obviously can''t have multiple VM''s writing to it. 4) All writes to the boot image for logging,

Before, in my "Hard Problem" email I was trying to communicate a design issue were trying to solve with Xen. This is what we need to do: 1) Deploy 24 Windows XP VMs in parallel. 2) Boot them from a shared Windows XP C: drive. 3) Since this is a read-only shared image we obviously can''t have multiple VM''s writing to it. 4) All writes to the boot image for logging,

Hi, I have set up KVM on FC12. I was wondering if its possible to Display the VM using spice + libvirt? As in, if I can define my domain with graphics like: <graphics type='spice' port='-1' autoport='yes' listen='0.0.0.0'/> or <graphics type='spice' port='5903' '

If I have a linux kernel on dom0 from xen 3.0.2 and my xen binary is version 3.1.0, can I expect things to work? What about if my dom0 kernel and xen binary are both 3.1.0 and I have a para virt domU with xen 3.0.2 code in? What about if the tools are from a different version of xen? I''m asking because I''m running fedora 6 and I''d like to try out xen 3.1.0 or 3.0.4

Hi, I defined several xen domains with libvirt. Can anybody tell me where libvirt stores these definitions? E.g. what files would one need to back up? Is it correct, that the xen domain definitions in /var/lib/xend/domains are overwritten regularly by libvirt? Many thanks, Arik

Hi all. have fglrx driver working with xen, opengl runs fine for me. see http://pastebin.ca/350588 it''s tested with kernel 2.6.19, driver version 8.33.6, xen version 3.0.3 and 3.0.4 thanks to Jacob Gorm Hansen for suggestions testing, feedback (and bugreports - hope not) are welcome Christian -- "Without music to decorate it, time is just a bunch of boring production

Hi! On x86_64, changeset 18081, running/building on rhel5, trying to use the HVM direct boot causes the domain to reboot immediately and then the log says the domain is restarting too rapidly. No obvious hints as to where the problem is. If I build the in-tree ioemu code, things work. Any clues as to where to look or how to get some useful debugging output? Thanks, John Byrne

Hello, it''s not the first time but ... Who know? Well, I use xen in HVM. All works fine, my keyboard in Dom0 is AZERTY, but this keyboard become QWERTY when i enter in VM, it''s not useful to type password. How can i keep my keyboard AZERTY in my VM and in Dom0? -- Benjamin HENRION Elève de 4eme année de l'' EXIA (Nancy) Ecole supérieure d''informatique Spé

Hello, Recently I ran yum update on a RHEL5 x86_64 machine and as part of the update, the following packages were installed: Updated: xen-libs-3.0.3-41.el5.x86_64 Updated: xen-libs-3.0.3-41.el5.i386 Installed: kernel-xen-2.6.18-53.1.14.el5.x86_64 Updated: xen-3.0.3-41.el5.x86_64 After the update, I rebooted the machine. Now, I cannot get xend to start:

--- configure.ac | 2 +- images/Makefile.am | 5 +++-- lib/Makefile.am | 14 +++++++------- ocaml/Makefile.am | 3 ++- ocaml/t/hivex_300_fold.ml | 3 +-- python/run-python-tests | 25 ------------------------- python/run-python-tests.in | 25 +++++++++++++++++++++++++ 7 files changed, 39 insertions(+), 38 deletions(-) delete mode

Announcing the open-ovf project and source code availibility. Hi folks, we are announcing the availibility of source code for the open-ovf project. OVF is a standard packaging format for virtual machines and software appliances. The open-ovf project is seeking contributors and users to help establish OVF as a transparent and platform-nuetral method for packaing virtual machine images. We

Hi, Sorry, I should not have removed infomation on xend. image.py, line 399, in configVNC config.remove([''vncpasswd'', vncpasswd_vmconfig]) When vncpasswd is removed, qemu-dm cannot be started in reboot of hvm domain. Because necessary information disappears. It cannot be helped though information in config list remains in xenstore. This patch corrects above. Regards,

On Fri, Dec 07, 2007 at 04:30:09PM -0800, Xen patchbot-unstable wrote: > tools: Rationalise library soname versions. > > * Arrange for the sonames of libxenstore, libxc, libfsimage and > libblktap to be set from a single place in Config.mk. Grumble... I don''t like this at all. You just bumped libfsimage for no reason. Can we please fix libfsimage back to the correct

Hi folks, Xen''s qemu-dm version has a ''-vncunused'' command line switch which asks the internal vnc server to pick any unused tcp port to listen on. The actual port is communicated to the outside world via xenstore. I''m looking for a reasonable way to implement that functionality in upstream qemu. First, I think it shouldn''t be a separate command

The attached patch changes the logfile name generated by qemu-dm to use the pattern qemu-dm-[NAME].log instead of qemu-dm-[PID].log. This makes it easier for the adminsitrator to figure out which log corresponds to which guest (particularly after a crash where you no long know what PID the qemu-dm process for your guest had). It also prevents the number of log files from growing unbounded.

Hello..I am not very proficient in Linux kernel stuffs although I know my basics. I have a question and all suggestions/solutions will be highly appreciated... I got to know that RHEL 5 has inbuilt Xen Support...So I tried to install a RHEL 5.0 Server on my P4 machine. On top of it I tried to install Xen specific RPMs and some other RPMs needed by Xen. The additinal RPMs added after base

Hi, When I tested xm new command without uuid parameter repeatedly, I saw many same managed domain as follows. # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 941 2 r----- 51.9 # xm new /xen/vm1.conf Using config file "/xen/vm1.conf". # xm new /xen/vm1.conf Using config file