similar to: Q: Understanding "xm block-list"

Hi, I''m kinda new to XEN stuff, and I''ve been trying to create a fully virtualized guest on CentOS 5.3 for almost 3 months and no luck yet. I approached this process through several methods, one with virt-install and creating config file manually. Following is what happens when I try to create a guest, and I have included qemu-dm and last part of xend.log logs below too.

Hi All, I am new to xen community. I am trying to setup Xen3.4.2 +FC11 Dom0 environs for lennovo T400. I have installed all prerequisite component for running xen and booted it. while I am trying to create DomU I am getting error. I tried doing googling but none of suggested solution is working for me. For more details please see below, I have highlighted few details in bold color just for

Hi All, I am new to xen community. I am trying to setup Xen3.4.2 +FC11 Dom0 environs for lennovo T400. I have installed all prerequisite component for running xen and booted it. while I am trying to create DomU I am getting error. I tried doing googling but none of suggested solution is working for me. For more details please see below, I have highlighted few details in bold color just for

Hi, have a debian 5.0 with all patches and xen 4.3.1 (debian repo) installed. If I use a VM with paravirtualizing it works fine. But a full virtualized image doesn''t boot. Message: ---8<--- # xm create deb50.cfg: Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. ---8<--- That is my deb50.cfg ---8<--- # Debian 5.0 import os, re arch = os.uname()[4]

Hi Guys, Now I am using Xen-4.0.0. I need to attach CDROM from ISO files to vitual machines when they are running. The VMs contain RHEL4.6, Windows Server 2003 32bit and Windows Server 2006 64bit. The disk configuration of the VMs is: disk = [ ''tap:vhd:/guest/SS_test/vhd/hmi-100130.vhd,hda,w''] (1) When I attach a CDROM to RHEL4.6 VM with the command: virsh

Hi Guys, Now I am using Xen-4.0.0. I need to attach CDROM from ISO files to vitual machines when they are running. The VMs contain RHEL4.6, Windows Server 2003 32bit and Windows Server 2006 64bit. The disk configuration of the VMs is: disk = [ ''tap:vhd:/guest/SS_test/vhd/hmi-100130.vhd,hda,w''] (1) When I attach a CDROM to RHEL4.6 VM with the command: virsh

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

the contexts are as follows, looking forward to your reply, thanks [1]enviromention : xen3.4.2+CentOS-5.5 [2]config file: xp.hvm, as follows _s_name = 'xp-101' _s_vnc_display = 5310 _s_vm_id = 101 _s_vm_mac = '00:16:3e:eb:ca:65' _s_memory = 512 _s_allow_destroy = False _s_use_vnc = True # -*- mode: python; -*-

Hi: we have following setup: 1. 2.6.16-33-based Xen 3.0.3/Xen-3.0.4 DOM-0 kernels. 2. Using LILO-mbootpack from USB we boot Xen-->DOM-0 setup 3. We mount harddisk and try to install xp.hvm While,we are successful with FCs as DOM-U, for XP we get, VBD (768) could not be connected. We do have max_loop count to 64 and enough loop devices. Note that above error is consistent on both 3.0.3

I am running Xen on Ubuntu. I am trying to attach a block device(usb pen drive) to domU. When i plug in my pen drive, it gets attached to dom0 on /dev/sdb1. I executed the command xm block-attach 3 phy:/dev/sdb1 /dev/sdc ro (3 is the guest vm''s id) i get the error. Error: Device 2080 (vbd) could not be connected. Device /dev/sdb1 is mounted in the privileged domain, and so cannot be

This fixes the xapi test case 02 with those parts that currently do not work disabled with ''if 0:'' Signed-off-by: Stefan Berger <stefanb@us.ibm.com> Index: root/xen-unstable.hg/tools/xm-test/tests/xapi/02_xapi-vbd_basic.py =================================================================== --- root.orig/xen-unstable.hg/tools/xm-test/tests/xapi/02_xapi-vbd_basic.py +++

I saw the pci dev''s config is different from vbd/vnif with following comments: # Parsing the device SXP''s. In most cases, the SXP looks # like this: # # [device, [vif, [mac, xx:xx:xx:xx:xx:xx], [ip 1.3.4.5]]] # # However, for PCI devices it looks like this: # # [device, [pci, [dev, [domain, 0], [bus, 0], [slot, 1]]]] # # It seems the reasoning for this difference is

Hello, I am trying to use Xen Enterprise (its free version). Until now I have no problem, but now I want to create a new virtual machine based in debian etch, not debian sarge (the debian version included in xen templates). So I am looking for a way to create my own template, but I haven''t found any documentation about that. Looking the files, I have found that templates are stored in

Next question:- eth0            8000.001c2596e32b       no              peth0 pan0            8000.000000000000       no virbr0          8000.000000000000       yes Presence virbr0 in report seems strange. Direct port  Xen 3.4.2  to F11 doesn''t install daemon libvirtd ( bridge virbr0 ) , unless you wrote xen-3.4.2-(x).fc12.src.rpm  yourself. So , from where bridge virbr0 comes 

$ git checkout RELEASE-4.2.2 $ git clean -ffdx [do a build, install, reboot] $ xl create a0 $ xl cd-eject a0 hdc [However, the guest OS still sees the CD inserted] $ xl block-list a0 Segmentation fault $ xl cd-insert a0 hdc file:/images/xs-tools-6.0.0.iso Segmentation fault The problem seems to be that xl cd-eject is writing corrupt values to xenstore. Note that vbd/1/5632 is still there

This logfile was recorded while the vm-start was running. -------------- next part -------------- [20120727T14:43:34.919Z| info|vh10|1021 UNIX /var/lib/xcp/xapi|session.logout D:dd291648d150|xapi] Session.destroy trackid=e3179eeb95ba96c64ab771d0cb1557b6 [20120727T14:44:02.180Z|debug|vh10|25|Starting periodic scheduler D:641021a392d0|backgroundscheduler] Adding function Logrotate to queue,

I have installed xen on a node and while starting up a guest while in the kernel boot I am experiencing a hold/pause. The kernel stops in the boot sequence still loading the kernel at: stdout ... [ 3240.186441] xencons_init: Initializing xen vfb; pass xencons=tty to prevent this [ 3240.186538] Xen virtual console successfully installed as xvc0 [ 3240.186598] Event-channel device installed. [

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 have a CentOS 5.2 Xen host, running several guest domains. Each guest domain has a single interface assigned to it. I am using both the network-bridge and vif-bridge scripts. On my only windows guest, the tap interface connected to the bridge keeps getting disabled. If I check "brctl show" the tap0 interface is not present, and there will be several message log entries indicating