similar to: Xen-unstable (Error: Unable to connect to xend)

Hi, On a slightly different topic there seems to be some sort of issue with Intel chipset 915G and windows 2003. The guests seem to stop responding after some time unless you connect via VNC to the guest and move the mouse over the window, the guest them comes back to life. Another guy said it was like a symptom that he had seen before called ''lost interupt'' I was wondering if

Hello, I''m using Xen-unstable and the kernel 2.6.18. Doing some particular tests, I need to disable the SMP Support in the kernel configuration and surprisingly I receive this error after compiling the kernel: CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 drivers/built-in.o: In function `take_machine_down'': machine_reboot.c:(.text+0x58a6c):

I''ve installed a Fedora Core 5 2054 and Xen 3.0.4.1 on a Intel 945 mainboard with xen3.0 user manual, everything seemed fine then. After I rebooted and chosed to enter into xen kernel , I find xend doesn''t run . when I try to run manually by input: /etc/init.d/xend start there some dot(indicating time maybe) appeared, and then nothing happened, the xend jun didn''t get

Hello, I have a question about the way Xentrace takes a trace. In previous versions of Xen, I took a trace by setting the size of buffers, activating them and writing the information into a file (optional). setsize 20 tbctl 1 xentrace /tmp/xentrace.dat Now I''m using xen-unstable and I see that setsize is already integrated in xentrace command. My question is: does start/stop buffer is

v2 -> v3: - Rebase on top of the other patches. Rich.

NOTE: not for upstream, yet. v1 -> v2: - Remove the dependency on enabling ACPI, since ACPI is now enabled all the time. Rich.

Due to IA64 balloon driver not ready and it depends on max memory value to allocate its memory. So this fix is necessary now. Thanks & Best Regards -Xiantao OTC,Intel Corporation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, I am using xen-unstable and interested to trace the hypervisor. In previous versions, I was able to trace it by: setsize 20 tbctl 1 xentrace /tmp/xentrace.dat And these functions don''t exist in xen-unstable. xentrace --help shows that in more recent versions the buffers'' size could be determined as a parameter for xentrace. But I can not find any replacement for

Package: xen-hypervisor-3.0-unstable-1-amd64 Version: 3.0-unstable+hg11561-1 Severity: important The HVM domU won't start. The following is the config (comments stripped). --------------------begin-------------------- import os, re arch = os.uname()[4] if re.search('64', arch): arch_libdir = 'lib64' else: arch_libdir = 'lib' kernel =

I must be missing something obvious. I have a large domU guest: dom0# cat /etc/xen/turing name = "turing" uuid = "8d3383a0-f0ae-f0b1-215d-c2e04115e9fe" maxmem = 40000 memory = 40000 vcpus = 12 bootloader = "/usr/bin/pygrub" kernel = "/var/lib/xen/boot_kernel.nrTJko" ramdisk = "/var/lib/xen/boot_ramdisk.y6Gcn9" extra = "ro

I''m getting the error: xend (12, ''Cannot allocate memory'') From the command line after the Dom-0 goes through a period of heavy memory usage. I don''t have any hard numbers on how to duplicate it, but I''ll give you the steps I''ve gone through to duplicate the problem. First, some information about my setup. It''s a new setup, and

As I understand concept of xenballooning, it allow to take memory from guest and return it to hypervisor. This allow to reduce amount of memory allocated to VM in realtime without rebooting VM. But how we can add more memory to guest VM in realtime, than was at boot time? Can we somehow make balloon inflated at start time? (F.e. VM starts with memory = 512Mb and balloon inflating to +512Mb).

Hi, I got this error when starting a domU on Centos 5.1 i386, Device 0 (vif) could not be connected. Hotplug scripts not working. Why is this happening ? I should restart the machine to see if this still happends after a fresh network bridge. But it's somehow a production server, I would like not to restart it, if possible. No domU is currently running. I could start domUs a week ago.

Hi list, I try to understand memory ballooning. I have a xen server (kernel 2.6.27.54-0.2-xen) with 32 gb total memory. A domU has been started with "memory=4096" and "maxmem=8192". This is the status of the balloon driver in the domU: test:~ # cat /proc/xen/balloon Current allocation: 4194304 kB Requested target: 4194304 kB Minimum target: 565248 kB Maximum

Hi Ewan, I''m almost ready to integrate some PPC-specific stuff into xend, and I was wondering if you had a plan for how that should work. First example: the device tree data structure we talked about a few weeks ago. We will need to pass the config data to PPC code, probably in XendDomainInfo.initDomain(), and then pass the resulting data structure into libxc''s xc_linux_load()

Hi, I am trying to install Windows 2003 server as a guest OS in Centos 5 Xen and installation is freeze , i am attaching screen shot, here is xend log file details [2007-10-29 17:04:11 xend.XendDomainInfo 3413] DEBUG (XendDomainInfo:190) XendDomainInfo.create(['vm', ['name', 'testwin'], ['memory', '1024'], ['maxmem', '1024'],

I''m getting the error: xend (12, ''Cannot allocate memory'') From the command line after the Dom-0 goes through a period of heavy memory usage. I don''t have any hard numbers on how to duplicate it, but I''ll give you the steps I''ve gone through to duplicate the problem. First, some information about my setup. It''s a new setup, and has

I am running Pentium D 930 with 2 gigs of ram. Fedora Core 6 with Xen enabled. I am able to start the install and it goes to the first stage of needing to be rebooted. I restart the Domain and it starts to finalize the windows install. And is fine until it starts asking for serial numbers or computer names. Then all of a sudden the guest freezes. The guest CPU goes to zero and so does the

Hello. Centos 7.6 with libvirt build from base "virt" repository: libvirt-daemon-driver-lxc-5.0.0-1.el7.x86_64 libvirt-client-5.0.0-1.el7.x86_64 libvirt-daemon-5.0.0-1.el7.x86_64 libvirt-daemon-driver-network-5.0.0-1.el7.x86_64 libvirt-libs-5.0.0-1.el7.x86_64 + systemd-219-62.el7_6.2.x86_64 Now lxc containers with type='direct' can be started, but can't be stopped :)

Hi, I finally updated the Debian libguestfs packages: http://honk.sigxcpu.org/con/Libguestfs__Virtual_Machine_Image_Swiss_Army_Knife.html Sine we can't run the fuse tests easily in a chroot (since we might be unable to load the module) I'm using the attached patch to skip the tests if /dev/fuse doesn't exist. This probably isn't clean enough to go upstream though. The other