similar to: i386 VM on x86_64 host in Xen

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

Hi, Live migration was working well for me with 3.1. Recently I move to 3.2, and now live migration does not work anymore. Here is what i obtain on source node : ---- xm migrate --live webdav node2 Error: /usr/lib/xen-3.2-1/bin/xc_save 26 6 0 0 1 failed Usage: xm migrate <Domain> <Host> [...] ---- And in the xend.log (still on the source node) : ---- [2008-03-03 10:12:52 15205] INFO

Hi all, I had met with a question about vhd format when i install xen 4.2.0 source code on suse11_x86_64_sp2. execute steps: 1)Install fully suse 11 sp2 to host pc 2)Boot from Xen kernel menu 3)Download xen 4.2.0 source code from http://xen.org/download/index_4.2.0.html 4)Download bin86-0.16.19.tar.gz cmake-2.8.9.tar.gz Dev86src-0.16.19.tar.gz gettext-0.18.1.1.tar.gz

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

Package: xen Version: 4.0.1-5.5 Severity: critical --- Please enter the report below this line. --- Hi! Since the update last weekind in stable/squeeze I'm experiencing problems with running Xen on amd64 and multiple domUs losing their network connection/VIFs. From http://blog.windfluechter.net/content/blog/2013/02/26/1597-xen-problems-vms-2632-5-xen-amd64 Unfortunately this update

-----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

Hi, since I upgraded from Lenny, DRBD VBD scripts not works at all. This config works : disk = [ 'phy:/dev/drbd/by-res/ads-disk,xvda,w' ] But his one doesn't work at all : disk = [ 'drbd:ads-disk,xvda,w' ] I obtain this error : # xm create ads.cfg Using config file "/etc/xen/ads.cfg". Error: Device 51712 (vbd) could not be connected. Hotplug scripts

Hi, I have 6 DomU's with 4-virtual interfaces and 1 DomU with only one. When starting the DomU's in order where the domain with only one interface is started last it refuses to start with following error. If I start it first there is no problem starting them all. ---Error--- [2011-10-02 18:37:33 xend.XendDomainInfo 6728] DEBUG (XendDomainInfo:1335) XendDomainInfo.handleShutdownWatch

Hi All I have xen 4.0 in centos dom0 the machine was working fine for months and yesterday out of sudden I can no longer provision new vms and to make things worst If any vm shutdown I cannot re run it again . the vm stop at the process of detecting the (ubuntu and debian all versions) [!] Detect Disks "No disk drive was detected. If you know the name of the driver needed by your disk

After a yum update my two guests that had been shutdown do not start any more. I have two other guests running that seem to work okay but I am now afraid that they won't come up again if I restart them. I am running CentOS5 with kernel 2.6.18-8.1.8.el5xen. Previously I had following xen versions installed: Oct 14 23:45:10 Updated: xen-libs.i386 3.0.3-25.0.4.el5 Oct 14 23:46:05 Updated:

Dear xen-users. First of all, I''m not a linux-guru and a beginner with xen and completly new in this mailinglist. I''ve installed Xen on debian 6 and I was successful creating two machines: one for tests and "fogserver" (to test speed of writing computer images), both para-virtualisations.

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

First let me say that I'm not a sysadmin, but am simply wearing that hat this week so please excuse my ignorance. I need to temporarily move some virtual servers from a CentOS-KVM platform to a CentOS-XEN platform while I do some upgrades to the CentOS box. I've created a local LV, and used DD and SCP to transfer the block device from the VKM machine to the XEN machine. For quite a

I''ve been using Xen strictly for PV for a while now, but I recently upgraded to hardware capable of HVM domUs. I''m trying to get a really basic HVM instance going so I can get my hands around making them work, in anticipation of using one to run a BSD to act as a firewall for other domUs on the machine. (I like PF.) Also, I might need run windows at some point, I suppose.

Hi, I cannot boot Windows XP domU on SXCE104 dom0. It was running for weeks.. Is it a known bug? # virsh start wxpp01 & # virsh dumpxml wxpp01 <domain type=''xen'' id=''-1''> <name>wxpp01</name> <uuid>fb96e8c9-940d-7e0a-12ef-f167a7f1102c</uuid> <os> <type>hvm</type>

Hi all, I''m trying to get a pci card working on a guest os (ast01) on dum0 I hided the pci card w/: # modprobe pciback hide=''(0b:08.0)'' then added this line to the guest os config file (/etc/xen/ast01) pci = [ "0000:08:0e.0" ] Whenever I try to start it fails w/: # xm create ast01 Using config file "/etc/xen/ast01". Error: function takes exactly 4

Hi all, I''d like to know if it''s possible to have more verbose output when running a block-prefix script. Other than xend.log. To be more specific I''d like to use bash -x to see why I''m running into the following error: > # xm create -c host.cfg > Using config file "host.cfg". > aa:bb:cc:dd:ee:ff > Error: Device 51712 (vbd) could not be

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:

When I try to use stubdom-dm in lieu of qemu-dm, the guest domain crashes almost immediately if I specify an emulated NIC (''vif='') in the guest configuration file. If I don''t specify a vif, it works fine. If I use the same configuration with qemu-dm instead of sutbdom-dm, it works fine. Is there some reason QEMU emulated networking doesn''t work with stub domains