similar to: Bug#654850: xen-hypervisor-4.0-i386: restore leave a VM not responding on console nor on network

Hi, I''m running a two node xen-Cluster with CentOS 5.3. I''m using gfs2 for the cluster filesystem and kernel 2.6.18-128.1.6.el5xen #1 SMP for Dom0 (xen 3.0.3). Live migration works fine as long as the DomU guest is running CentOS 5.3 or SLC 4.7 with kernel version 2.6.9-55.EL.cern. But if the SLC 4.7 guest is running the current 2.6.9-78.0.17.EL.cern kernel, the migration

Hello everyone, for research purposes I''m working on Xen 3.0.3 and trying to make some modifications to Xen migration. By looking at the documentation, I''ve learned that the part I''m interesting in are handled by two binaries (xc_save and xc_restore), so I thought about modifying just this two binaries instead of recompiling the whole Xen everytime, so what I do is just

hi, I have 2 servers running xen 3.2 on ubuntu 8.0.4.1 (64-bit) installed from the repositories (2.6.24-22-xen) with Intel-Quadcore CPU''s. The setup is based on http://www.asplund.nu/xencluster/xen-cluster-howto.html. I can start the domU (ubuntu 8.0.4.1 (64-bit)) on each server without problems. But when I start the live-migration with xm migrate dummy xen2 --live the migration

Package: xen-hypervisor-3.0-i386 Version: 3.0.2+hg9681-1 Severity: important Have been trying to get NetBSD to run under debian unstable with the debian supplied hypervisor. Using the 3.0.2-2 hypervisor supplied by XenSource, it works just fine. Because the install process overrides other things, reverified with debian hypervisor afterwards and symptom continues. Attaching the netbsd.cfg and the

----- Forwarded message from pakrat <pakrat@private.neotoma.org> ----- Forwarding to list without attachments. From: pakrat <pakrat@private.neotoma.org> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: xen-hypervisor-3.0-i386: cannot start NetBSD-HEAD X-Neotoma-Consulting-MailScanner: Found to be clean X-Neotoma-Consulting-MailScanner-From:

I am now testing XEN live migration on two physical hosts with XEN 4.0.1 pvops Ubuntu 10.10 (2.6.35-22). Host A also acts as a NFS server, and Host B acts as a NFS client. When I migrate a guest domain from B to A. The ssh connection experiences a downtime of about 1 minute (the terminal does not react to the keyboard input till about 1 minute later). However, the "sudo xm console" does

Package: xen-utils-4.0 Version: 4.0.1-2 If you reboot with the DomU disk DRBD domain destroy. pygrub error when trying to run a image on DRBD device My config DomU ------------------------------------------------------ bootloader = '/usr/lib/xen-default/bin/pygrub' vcpus = '1' memory = '256' cpus="8-15" root = '/dev/xvda2 ro' #disk

Hi there guys. I''m trying to setup an Ubuntu 9.04 DomU, it boot fine, but does finishes to load completelly, this is what I get. I''m using xen 4 Linux netwarrior 2.6.31.13 #7 SMP Wed Jun 30 18:09:49 ART 2010 x86_64 AMD Athlon(tm) II X4 630 Processor AuthenticAMD GNU/Linu * Skip starting firewall: ufw (not enabled)... [ OK ] * Configuring network

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 first of all, thank you for a great project i really enjoy! ok, now here comes the bug report... i''m trying to test xen migration capabilities, with xen-3.1, hand compilled, fetched from mercurial repository. my setup looks like this - x86_64 dom0, x86_32p dom0, x86_32p domU. when trying to migrate from 64 to 32 bit dom0 i''m

Hello, I have 2 Dell 1955 blade servers, running RHEL5-Xen. I''m testing the migrate functionality from one blade to another. I can start the domain, move it to one blade (minor delay/packet loss) and everything is fine. When I try to move it back to the original blade the migration fails and the DomU crashes c1b1 = Blade 1 (192.168.131.201) c1b2 = Blade 2

I have several systems running 64bit SLES11SP1. I''m trying to Live Migrate between a couple of them and it''s not working, although the same VM will run on each one starting it manually. The system are not identical. Would one expect migration to work between these two systems? See below. Thanks, James The first system is a ProLiant DL360 G6: Proc 1:2533 MHz Execution

Hi, I have a problem with a dom0 which is unable to launch my domU : all my dom0 are Debian Lenny amd64 with Debian kernel 2.6.26-2-xen-amd64 and xen-hypervisor-3.2-1-amd64. Then all domU (PV) are Debian Lenny amd64 too, with vanilla kernel 2.6.29.6. So, this new dom0 can''t launch any domU which are working on an other dom0. Software is same on both dom0, and hardware is near the

Hi guys I have few problems with live migration ... and I need some professional help :) I have 2 xen servers ... CentOS 5.3 and I want to have a high available cluster Now let`s begin .... xen0: [root@xen0 ~]# fdisk -l Disk /dev/sda: 218.2 GB, 218238025728 bytes 255 heads, 63 sectors/track, 26532 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start

If I start a domain with a number of vbd devices, it''s a crap shoot if they''ll all show up in the domU''s /proc/partitions. I''ll eventually see all the devices if I keep rebooting the domU. The value of /local/domain/$DOMID/device/vbd/*/state are all 1 for the missing devices, and 4 for the ones that show up. When it works: domU:~# cat /proc/partitions

Xen Host Server OS: SLES10 Kernel: 2.6.16.21-0.8-xen x86_64 Hardware: Sun 4200 Memory: 12Gb Guest Domains (2 total) RHEL4-U3 2.6.16-xen x86_64 2Gb Swap 4Gb RAM 2 Nics bridged to seperate physical Nics (Public and Private) Systems come up normal and we are able to mount filer space to the guest domains and do work. However, at some point, the guest

Hi, I am running Xen 3.1 on Ubuntu Gutsy, AMD64 distro. When I try to migrate a Windows XP domain, the domain migrates, but does not get restored in the destination node. The block device is provided by open-iscsi/iet and is accessible from both nodes. Below are logs from both source and destination nodes: Please throw some light on where the problem could be: TIA, Regards, -- Shuveb Hussain.

Hi, i do some tests with restoring HVM winxp-domU''s. Even, if i restore a saved DomU from a ramdisk, the Restoring-process has only a bandwidth about 23MB/sec: Here a example restoring an 512MB HVM opensuse10.3 DomU ...... [2008-05-07 22:40:12 3314] DEBUG (XendCheckpoint:218) restore:shadow=0x5, _static_max=0x20000000, _static_min=0x0, [2008-05-07 22:40:12 3314] DEBUG (balloon:132)

I have loaded FC6 with the virtualizations kernel, and I am attempting to load WinXP. I searched all the logs and docs and configured what I think is correct based on these. When I do an xm create dfw11286lv1.hvm, I get the following messages: Using config file "dfw11286lv1.hvm". Started domain dfw1128glv1 However, I never get a window with the installer. Also, when I open the

Hello, I have been struggling through the task of moving our infrastructure over to Xen VMs. We were initially using Ubuntu packages for both dom0 and our domUs, but experienced extreme instability so we moved to CentOS, which has been much more reliable for dom0. Since we already had a bunch of Ubuntu VMs, we left them using the Ubuntu 2.4.24-19-xen kernel, but this has turned out to be

Anybody out there running Windows XP, Windows XP SP2 or Windows 2003 server with the default XEN 3.0.3 on Ubuntu Feisty ? Have Ubuntu Feisty Dom0 with a number of Ubuntu 6.1/7.04, Debian and FC6 DomUs all working lovely. But it will not work for any windows versions. The install gets as far as the blue "Setup is Starting Windows" screen. Intel VT extensions are enabled and the F5 trick