similar to: Question about adding CPU/RAM to Windows DomU

My dom0 is uing Centos 5.2 x64. I have just upgraded Xen from 3.3.0 to 3.3.1. After upgraded, I find that I cannot hotplug additional vcpu anymore. I have a domU "linux1" which is a paravirtualized vm with centos 5.2. I try to "xm vcpu-set linux1 4", it does not have any error message, but those vcpu cannot be displayed. I also tried to add vcpu using "virsh setvcpus

Hello, I have installed rpm version of xen 3.4.3+ libvirt 0.7.0-6 on my server with Centos 5.4 (kernel 2.6.18-238.12.1.el5xen) When I run reboot a domU (para virtualized Linux) by command "virsh reboot [vm]", sometimes domU cannot be rebooted but sometimes can, pattern is random. Also sometimes when domU reboots by "virsh reboot [vm]" , my ssh connection to dom0

I installed a 32 bit Windows 2003 enterprise edtion domU. xm list shows the domU has 7G RAM. But Windows 2003 shows only 3.75G RAM. I do not know what''s wrong. Anyone knows? [root@sjd-hot w2k3e]# xm info host : sjd-hot.rashost.com release : 2.6.18.8-xen version : #1 SMP Fri Nov 27 03:53:01 UTC 2009 machine : x86_64 nr_cpus

Package: xen-utils-4.0 Version: 4.0.1-5.2 After clean upgrade from Lenny I got xend highly use CPU resources causing domU don't being created - due to timeouts for vifs and vbds (mostly CPU Steal Time was increasing - no iowaits). Tried Xen boot options acpi=noirq|ht without success. Option acpi=off solved that issue, but performance of the server was horrible. The final workaround was to

What have I done wrong? I installed an xp (service pack 2) domU using the virt-install example from the man page, on a zfs volume. I noticed this behavior on build 129, and I replicated the behavior on build 130: root@opensolaris:/tmp# virsh version Compiled against library: libvir 0.7.0 Using library: libvir 0.7.0 Using API: Xen 3.0.1 Running hypervisor: Xen 3.4 root@opensolaris:/tmp#

My target is virtualized SBS2003 on dell PE T410 Now I test xen on my desktop. Centos 6 as dom0 - kernel: 2.6.32-131.12.1.el6.xendom0.x86_64 from http://xenbits.xen.org/people/mayoung/testing/x86_64/ hypervisor 4.1.1.3 from http://xenbits.xen.org/people/mayoung/EL6.xen/x86_64/ One NIC simple bridge-network configuration dom0 uses static IP with ISP router as gateway domU have also static IP

Hi, I have a running LVM-DRBD-Xen-HVM/Win2k3 cluster-stack under debian/ lenny managed by heartbeat/crm. At takeover/failover heartbeat first is stopping my HVM-domU with success apparently: -------------- corresponding heartbeat log line ----------------- greatmama-n2 lrmd: [3382]: info: RA output: (xendom_infra_win:stop:stdout) Domain infra-win2003sbs terminated All domains terminated

Hi all, Anybody know what it means for a DomU to show up in the "xm list" as follows: Name ID Mem VCPUs State Time(s) Domain-0 0 256 2 r----- 43929.3 Clonezilla 16 512 1 ------ 6.2 The domU "Clonezilla" does not have an "r" state

Hello I have Debian Linux 2.6.32-5-xen-amd64 Xen 4.0.1, 2 SAS drives in RAID 1, 16GB ram. I have virtualized Windows 2003R2 32bit where you install the latest version 0.11.0.295 gplpv After reading and reading forums and post testing, I noticed that the hard disk performance drops significantly when I assign the windows domU 9GB ram. (below I leave the config files) If I run the

Hello community! I need help with a problem I haven''t been solved with the network team. I manage a network that has over a thousand computers, and the most of the servers are virtualized over Debian / Xen by me. The specific issue arises when I try to set up a DomU HVM running Debian Squeeze, the VM doesn''''t recognize the network but it runs. It gives an error

Hi, I''m new to XEN and have the following Problem: If I shutdown my domU the network of the dom0 leaks. A ping from another server to my xen dom0 shows a Packetloss > 80%. Then if I restart the domU after some seconds the ping show a loss from 0%. I retryed that 3 times but it is really hard to go to the dom0 via ssh and recreate the domU if the packetloss is that high. I used google

Is serial port "passthrough" possible for the version of xen that ships with centos 5.2? I've disabled the xen hypervisor serial console, and can see the serial port in dom0. I've masked out the 8250, 8250_pnp and serial_core modules on dom0 and rebooted. xm create domain fails with the error that exactly 4 arguments are required and only 3 were given. Steps I followed: 1) I

Hi, I use Centos 5.4 x86_64 kernel used is 2.6.18-164.11.1.el5xen I have a physical machine running Debian Etch (32 bit) and Debian Lenny and I virtualized the first one as follows: *Created a HVM DomU with Virt-Manager with a virtual disk file of 40000 M *Boot from LiveCD, and created a swap and a ext3 partitions (Yes, very simple layout). *Rsync''d files from root partition of

Hi, I use Centos 5.4 x86_64 kernel used is 2.6.18-164.11.1.el5xen I have a physical machine running Debian Etch (32 bit) and Debian Lenny and I virtualized the first one as follows: *Created a HVM DomU with Virt-Manager with a virtual disk file of 40000 M *Boot from LiveCD, and created a swap and a ext3 partitions (Yes, very simple layout). *Rsync'd files from root partition of physical

Dear Xen Community, today we tried to upgrade our base server from a Xeon E5430 to a Xeon X5570 (Nehalem). This worked fine so far, but our DomUs with Kernel 2.6.27 no longer boot - they start up until the following message appears: [..] Mount-cache hash table entries: 256 Initializing cgroup subsys ns Initializing cgroup subsys cpuacct Initializing cgroup subsys memory Initializing cgroup

After a few days, one of my DomU becomes unresponsive. Here''s the output of my DomU''s. root@xenII:/var/log/xen# xl list Name ID Mem VCPUs State Time(s) Domain-0 0 7126 2 r----- 723932.0 redhat-sdsweb 11 4091 2 -b---- 92633.1 w2k8-AD

# HG changeset patch # User user@localhost.localdomain # Node ID 347948cff0621cd3b085dc02f15fb2c9b55148af # Parent cb70d4f8d7182b0d1b5bcee7044f59fbe4dc9839 Document the UUID domU configuration parameter in example configurations. Signed-off-by: Andrew D. Ball <aball@us.ibm.com> diff -r cb70d4f8d718 -r 347948cff062 tools/examples/xmexample.hvm --- a/tools/examples/xmexample.hvm Mon May 15

I want to give my clients access to their Xen domU consoles using VNC. This works great using vfb device configured as type=vnc. However I have 2 problems: * I can't figure out how I can add a vfb device to a running domain without restarting it (I have 100+ domU's I want to enable this on, and want to avoid restarting them all if possible) * Related, I can't figure out how I can

Package: xen-utils-4.1 Version: 4.1.1-3 I have an HVM domU which was created with xen-utils-4.0 (and Xen 4.0 hypervisor of course). Recently I've upgraded to Xen 4.1 and xen-utils-4.1, but after a reboot I was unable to do anything with it: "xm start" caused "Domain is already running" error, while "xm shutdown" simply hadn't printed any error messages, only

Hi, I''m running Nevada 75a configured as dom0. I added a domU HVM running Nevada 75a, on a Sun X4600 with 8 ADM Dual cores. I can get the domU installed and configured, however, I can not get any network connectivity. I followed the steps accoding to documents on Open Solaris. I also followed some of the threads of the list to verify the configuration, but I can not fix the