similar to: dom0 reboot like domU

After download of Xen4.0, Is there a simple way to disable to not download from git implicitly ? (I already did it offline and would like to use that build instead.) Idea is: "make world" would not enforce git automatically. Any suggestions ? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hi,   I am trying to build dom0 iso. I have following in my isolinux.cfg file. I see error: "Invalid or corrupt image file".   --- default 1 prompt 1 timeout 300 display menu.txt label 1   kernel boot/vmlinuz.vm   append boot/xen.gz  ramdisk_size=131072 initrd=boot/ramdisk.gz root=/dev/ram0 ---   The image I check is valid. xen.gz is actually xen-3.4.2.gz: xen.gz: gzip compressed data,

I am not clear with the working of hypervisor xen. How does an instruction executed by kernel in Ring0 of DomU gets mapped or executed by hypervisor and then is excuted in Dom0. Is this thing some where on the wiki page? -- Tapas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I am not clear with the working of hypervisor xen. How does an instruction executed by kernel in Ring0 of DomU gets mapped or executed by hypervisor and then is excuted in Dom0. Is this thing some where on the wiki page? -- Tapas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I have a sles10 domU running on a sles11 dom0. xen is version 3.4. We''re trying to pass through a scsi card to the domU. We assign the domU the scsi card through virt manager. When we try to boot the domU it won''t boot. We need to update fstab and menu.lst, but we need to boot with the hardware attached to see how it''s being seen by the domU. On a physical machine we

Starting udev: Wait timeout. Will continue in the background.[FAILED] so slowly. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Starting udev: Wait timeout. Will continue in the background.[FAILED] so slowly. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi all, I just upgraded my Debian/Etch with Xen3.3 machine to Debian/Squeeze Xen4.0 and now have problems with starting the Dom0 kernel. I always get the error message: Kernel panic not syncing: the kernel parameter noapic is incompatible with xen. My grub.cfg is: menuentry ''Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN 4.0-i386'' --cl$ insmod part_msdos

Hi, I just updated to xen 3.0.4 and linux-2.6.16.49-xen0 (gentoo linux). After reboot xen starts up just fine but instead of starting the dom0 kernel the machine just reboots. The last messages I see on my screen are: (XEN) Scrubbing Free RAM: .......done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and

Team, Sorry to bother your busy day! I was hoping you could guide me to the right direction. One of our users are running the open source version of Xen that comes bundled in Red Hat''s RHEL 5.3 and 5.4 products. Running XEN over NFS. We would like to know the XEN timeout value for NFS. Is it true that Xen has a hardcode timeout value for NFS. Is it true that it is recommended we run

Hi,     I just downloaded Xen4.0 from:     http://www.xen.org/products/xen_source.html     Trying=0A to build:     Create xen entries under /sys/hypervisor =0A(XEN_SYS_HYPERVISOR) [Y/n/?] y     #     # configuration written to =0A.config     #     make-3.79.1-p7[3]: Leaving directory =0A`/foo/xen40/xen-4.0.0/linux-2.6-pvo=     ps.git''     make-3.79.1-p7 -C

i want to create a domU using iscsi disk. Since virt-manager and virt-install do not support, pls advise the config file which will be used by xm create to create a xen guest. Yahoo!香港提供網上安全攻略，教你如何防範黑客! 請前往 http://hk.promo.yahoo.com/security/ 了解更多! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

On Debian Squeeze (2.6.32-5) running Xen 4.0, I have created 2 Ubuntu Lucid Lynx (Ubuntu 10.04) vms. The vms, in a stress test, pass a large file between them via nfs file sharing. A previous entry in this forum helped to establish that some ethernet cards improve VM IO performance. However, our box installed with better intel nics is still rebooting under heavy VM IO loads. The kernel call

Hello Friends I''d like to ask about how many interfaces can I configure on my domU. I''ve one x4600 (Sun Fire) with 32GB RAM and 16 CPU''s AMD Opteron, with RedHat AS 4up5, and I created two guest machines with 4 CPU''s each, 2 NICs and 2GB RAM. So, I needed set 3 IP address then I set one IP in eth0, another in eth0:1 (alias) and another in eth1. On first

  Sure. Thanks again for the prompt help - very appreciated. As I see I am trying to do what only few have done wrt Xen dom0 to package as bootable iso with ramdisk.   Now error below Xen dom 0 is trying to bring up Linux:   <..clipped..> md: ... autorun DONE. RAMDISK: ext2 filesystem found at block 0 RAMDISK: image too big! (524288KiB/4096KiB)   <...clipped: Details below...>

  Sure. Thanks again for the prompt help - very appreciated. As I see I am trying to do what only few have done wrt Xen dom0 to package as bootable iso with ramdisk.   Now error below Xen dom 0 is trying to bring up Linux:   <..clipped..> md: ... autorun DONE. RAMDISK: ext2 filesystem found at block 0 RAMDISK: image too big! (524288KiB/4096KiB)   <...clipped: Details below...>

Hello! I am using xen some years now and it just runs without any problems. But now one customer needs a stupid WinXP domU and I am trying to get this running for about two weeks... I am using 2.6.26-2-xen-amd64 kernel, set up a dummy network auto dummy0 allow-hotplog dummy0 iface dummy0 inet static address 10.0.0.1 netmask 255.255.255.0 broadcast 10.0.0.255 xend-config: (network-script

I''ve been looking for a solution that doesn''t involve dual booting, or chrooting things to get my x86 domU to work. I have a Debian xen server on an amd64 platform. It would seem that I should be able to also install or force the install of a non-xen i486 kernel. When I recieved this server it had a manufacturer''s install of Etch with an i486 kernel. Once I have both

I''m running xen on SLES10SP2. It''s been much more stable than SP1, but I still occasionally have issues. For example, one of my servers (8 CPU/32GB RAM) has five sles pv domUs and five fully virtualized windows 2k3 domUs. It had been up for almost 60 days. Yesterday afternoon one of the sles domU''s stopped responding. I went to check on it and I couldn''t using

I''m running SLES10 SP1 and have been using file:/ for my file-backed domUs. The domUs sit on a shared OCFS2 SAN-backed filesystem and are run on my three or four XEN servers. I''m having issues with the loopback devices not being released when the domUs shutdown or migrate, so I decided to switch over to tap:aio for my file-backed domUs. This isn''t working, either.