similar to: domU modules..

Hi, I can''t get rid of an annoying domU machines hanging issue with Hyperthreading enabled in my BIOS. Hardware config: IBM x325 series 2 * CPUs Intel Xeon 3.06 Ghz Xen version: 3.0.0 Kernel version: 2.6.12.6 Linux distrib: Debian Sarge 3.1 r1 I run 1 domU machine on my dom0, here is my Xen config: . xen0: /etc/xen/xend-config.sxp : (dom0-num-cpus 0) .

I have been playing with Xen 3.0.1 for some days now, using debian sarge for dom0 and domU''s, and it works like a charm. But, I have a problem with rebooting domU''s. Here is the output from /var/log/xend.log [2006-03-30 13:44:58 xend.XendDomainInfo] INFO (XendDomainInfo:823) Domain has shutdown: name=vmintraweb1 id=5 reason=reboot . [2006-03-30 13:44:58 xend.XendDomainInfo]

amd64:/usr/src/xen-unstable.hg#hg tip changeset: 6597:a1de77c1486c5f35884e9f578b7f33b6bd75c362 tag: tip user: shand@ubuntu.eng.hq.xensource.com date: Sat Sep 3 03:36:29 2005 summary: Enable ''live'' migration from a tools pov; prior to this the ''live'' flag was Which option in make ARCH=xen menuconfig should i disable to get rid of

Hi all, my domU guests stop booting in my new 3.2 (kernel 2.6.18.8) xen installation when run perfectly in my other 3.0.2 (2.6.16) xen server. whe i start the domU with "xm create" i get these messages: Using config file "./debian.4-0.xen3.cfg". Started domain debian.4-0 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table

I am having problem when I am trying to access serial port in domU. I found a solution from the wiki.xensource.com as in the following lines: ___________________________________________________________________________ To have access to the serial port in DomU, we need to prevent Dom0 from taken hold of this piece of hardware add to /etc/hotplug/blacklist the following modules to exclude from

Hi, every one: I had problem creating domU on diskless device by using xen-unstable. Following, please find out details. BTW, the same configuration works fine on device with hard disk (1) Xen, dom0 kernel and dom0 root file system are loaded/mounted over via eth0 (2) DomU root file system is created in a file-backed virtual block device(VBD). The file-backed VBD locates at some directory on

I am using ttylinux-xen file system image a a loopback device for the domain. I am mostly using the default configuration. I am not able to get networking on the domU. Are kernel "vmlinuz-2.6-xenU" as well as "2.6.11.12-xen0" both compiled w/o loadable module support? I guess it fails when it tries to initialize the iptables on the domU when it tries to do "modprobe".

hi, i''ve a little problem here with raid1 inside domU. My setup is, two block devices (gnbd) attached to domU (sda1, sdb1) and build raid1 inside domU. All works fine (mdadm --remove, block-detach, resize, block-attach, mdadm -add) except the part where i want to grow my raid to the new size (mdadm --grow .. --size=max). Sometimes (when not much fs load is done in domU) it works and

Hi, this is a repost of a previous question - since then I have tried rebuilding my Xen0 kernel numerous times and trying different configurations, but I haven''t yet ever got a single DomU to boot so I really don''t even know what is supposed to happen, let alone how to start debugging it... Can someone please speculate on how to debug this further? It''s a gentoo

As the subject says, I wanted to boot a domU from a CD to run a linux distribution installer (specifically, the 0.9.5-test2 installer ISO from http://www.sourcemage.org/). I looked for info on the web and in IRC on doing this, and most things that discuss it seem to suggest doing the install in a real system or using something line qemu first, then switching it to xen. I did get it to work using

Hello, I guess it possible distro specific issue but is it resolvable? I have one node(testing purpose) ganeti 2.0.1 cluster installed over Debian5 Lenny. Almost everything from distro repositories. Only ganeti 2.0.1 and ganeti-debootstrap are from sources. I have it successful run with vmlinuz-2.6.26-2-xen-686 and initrd.img-2.6.26-2-xen-686 from repositories. Both Dom0 and DomU are use the

I cannot boot domU: # xm create inhouse Using config file "inhouse". Started domain inhouse # xm list Name ID Mem(MiB) CPU VCPUs State Time(s) Domain-0 0 123 0 1 r----- 27.4 inhouse 8 2048 0 1 ------ 11.4 # xm console inhouse Linux version 2.6.12.6-xenU ( root@xen1) (gcc version 4.0.2 20050901 (prerelease)

Hello, gentlemen I need wise advice about how to tune  network for performance usage file server under domU I use bridged network. On dom0 network settings are: auto eth0 iface eth0 inet static address 192.168.1.100 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 up /etc/xen/scripts/network-bridge start bridge=br0 netdev=eth0 up ifconfig br0 up #up route add default gw

The Patch I made for SMP dom0 is also applicable to SMP domU. The issue is same for dom0 & domu as they both are compiled from the same code. The dom0 fix I sent earlier also fixes the domU SMP issue. Thanks & Regards, Nitin ------------------------------------------------------------------------ ----------- Open Source Technology Center, Intel Corp >-----Original Message-----

If I try to ifup eth0, I get the following: Device eth0 does not seem to be present, delaying initialization. DomU: Linux fedora1 2.6.16-1.2133_FC5xenU #1 SMP Tue Jun 6 02:58:27 EDT 2006 i686 i686 i386 GNU/Linux config: kernel = "/boot/vmlinuz-2.6-xenU" #ramdisk="/boot/initrd-2.6.16-1.2133_FC5xenU.img" memory = 128 name = "fedora1" #dhcp = "dhcp" disk =

Hi all, I got this error starting a domU Started domain <servername> xen_start_info @ffffffff80837000 shared @m00befea000 @ffffffff80107000=@ffffffffff5fd000 [0x802] xen_start_info: @ffffffff80837000 cr3 0000000000101000 pml4p ffffffff80101ff8 pml4e 0000000000103067 (real 00000004ea4f4067) pgdp ffffff8000103ff0 pgde 0000000000105067 (real

I run my production DomU''s using Xen 3.4.1 at the moment with the old 2.6.18.x dom0 kernel. I just built a new Xen version (4.0.1-rc5) with jemerys git repo of 2.6.32.16 dom0 pvops kernel. When starting domains the go instantly into a paused state and eventually i see this error on the command line. [root@host test1]# xm create -c vps.config Using config file

On 01/08/2018 02:10 PM, Shaun Reitan wrote: > While installing the experemental kernel on a CentOS 7 PV the following > happened. After a reboot of the PV the kernel looks to be installed but > there is no option for booting it in grub. ?I attempted to run yum > reinstall kernel-4.9.75-204.el7.centos.x86_64 and it installed fine but > still no entry in grub. No initramfs existed and

Hey, I''m having a bit of difficulty sshing from Dom0 to DomU and vice versa, my setup is as follows; Xen-3.0-unstable, XenLinux kernel 2.6.12 Dom0 on Redhat EL 4 Dom1 on SuSE linux 9.1 (with the standard xenU kernel included with xen-unstable) The server it runs on doesnt have a nic installed (well it does, just without drivers) the suse config file sets the eth0 interface up as

Hello, I can''t load the network in unprivileged domain with xen-unstable (Changset 8612). Xen boots fine and domain0 is OK. When I start a new domain I have the following report when booting: ----------------B<----------------------------- * Not running depmod because /lib/modules/2.6.12.6-xenU/ is not writeable. Loading modules... All modules loaded. FATAL: Could not load