similar to: Starting Xenbr0 looses connectivity

Hi, I''ve prepared a Ubuntu 10.04 LTS server on a Xen 3.2-1 host running Debian Lenny on kernel 2.6.26-2-xen-amd64. The Ubuntu 10.04 domU is running a 2.6.32-24-server kernel from the Ubuntu repositories, which is (must be :-) ) xen-aware. The domU uses pygrub to boot and it works like a charm. Now I''m trying to deploy this domU on a Xen 3.2-1 host running Debian Etch on kernel

I''m running Xen 3.2 on Debian 5.0 (Lenny) and am having trouble booting up a Debian Etch DomU. It hangs at the end when it says "Starting periodic command scheduler: cron." It''s just completely frozen. At one point I set it sit for a few hours and got back into the console and it said something about "time went backwards" but I used the

Hi, I''m running Xen on a Debian Xeon E3110 using the Debian 2.6.26-2-xen kernel. As filesystem for my lvm domU partitions I choosed xfs. I get the following error in kern.log of domU when booting a domU: blkfront: sda2: write barrier op failed blkfront: sda2: barriers disabled end_request: I/O error, dev sda2, sector 0 end_request: I/O error, dev sda2, sector 0 Filesystem

Hello, I''ve got a big problem when I try to install Zimbra on a xen debian etch vm. Eeek! page_mapcount(page) went negative! (-1) page pfn = 7141 page->flags = 4000083c page->count = 2 page->mapping = cd946510 vma->vm_ops = 0x0 ------------[ cut here ]------------ kernel BUG at mm/rmap.c:669! invalid opcode: 0000 [#1] SMP Pid: 7717, comm: java Not tainted

I have successfully joined a domain with Samba 3.0.30 But after approx. one or two hours, winbind looses connection to the domain controller and users are not allowed to connect shares. After a 'killall winbindd' and restarting of winbind, the users can connect to the shares again. How can I work around this bug? Configuration looks like this: [global] dos charset = ISO-8859-1

Hi, It seems to be a very basic question, but need confirmation. I am using Centos as my Dom0, running xen, using paravirtualization. Can I run NON-CentOS (more specifically Debian) operating system on domU, -- Regards, Meghanand N. Acharekar " A proud Linux User " Reg Linux User #397975 ------------------------------------------ I was born free! No Gates and Windows can restrict

Package: xen-utils-common Version: 4.3.0-3 Severity: normal Dear Maintainer, I've just set up a fresh Jessie system using the installer dated 2014-03-05, then installed and enabled Xen 4.3. I've done this quite a few times before using Wheezy and 4.1. I set up xenbr0, then created a test domU using xen-create-image, which completed without issue. However I was unable to start the new

After hours of googling and not really finding a definitive solution to my problem, I''m a little stuck and would really appreciate some help from others. I have a CentOS 5.4 x86-64 server running Xen 3.3 from the gitco repos as dom0. On this I have created two logical volumes comprising 8GB for the system disk (xvda) and 1.5GB for swap (xvdb). I ran mkfs.ext3 and mkswap on these to

Hi, I''m trying to install xen with this configuration: dom0 -> Centos 5.3 dom1 -> Fedora 10 dom2 -> Fedora 10 Centos kernel = (2.6.18-128.1.10.el5.centos.plusxen) XEN Version = 3.0.3 I''m having some problems trying to install xen on my mychine, but i''ve been able to solve all of them but one: i can''t reach my gateway from

As the issue concerns both the -user (configuration) and -devel (OOPS), I''m sending this message to both lists. Some time ago I complained about two problems: - VLANs are not working on machines with 100 Mbit cards - I get a kernel Oops (sometimes panic) when I try to use bonding and VLANs with Xen The root of the issue is the same in both cases: VLAN interfaces must *not* be

As the issue concerns both the -user (configuration) and -devel (OOPS), I''m sending this message to both lists. Some time ago I complained about two problems: - VLANs are not working on machines with 100 Mbit cards - I get a kernel Oops (sometimes panic) when I try to use bonding and VLANs with Xen The root of the issue is the same in both cases: VLAN interfaces must *not* be

Hello! I''me run windows 2008 server in Debian etch amd64 8 gb memory. if given > 2gb memory to w2k8. dom0 is down. In no logs anything interesting. configs: (logfile /var/log/xen/xend.log) (loglevel DEBUG) (network-script ''network-virtual bridgeip="172.16.16.1/24" brnet="172.16.16.0/24"'') (vif-script ''vif-bridge

Hi. I want use xen with dynamic slices. For example, I have 20 domU based on FreeBSD, xen hypervisor 3.3.1, Debian Lenny dom0 system. All domUs have 80Gb LVM partitions, but realy they use 20 of this 80Gb and I want to create more domU''s. How can I do it? I know that some virtualisation have possibility to do dynamic slices(4 example Virtul box) -- Best Regards, alex.faq8@gmail.com

Hi, My configuration is the following: Xen 3.3.1 compiled from sources(with PAE enabled) Dom0 Debian Etch i386 I''m trying to create Debian domU from scratch with netinst and get the kernel and ram disk to boot to installation procedure from install.386/ folder of netinst iso image. Then I use the following config file debian.cfg for installation: kernel =

Hello, I am trying to boot a FC6 domU on Xen 3.2 (compiled on a FC6 system). After compiling Xen 3.2 successfully on FC6 and making the ramdisk, I modified the conf.grub as shown below. With this, I was able to boot xen. ------------------------------ --------------------------------------------------------------------------------- # grub.conf generated by anaconda # # Note that you do not have

Hi, dom0: Debian Lenny 2.6.26-2-xen-amd64, domU: same. Xen 3.2-1 After resizing a LV on dom0, Xen is not reporting the new extended size to the PV domU even though dom0 is well aware of the new size. I''ve rebooted domU (not dom0 yet as that''s running a lot of other domU''s). The LV I tried to resize is encrypted. Resizing unencrypted volumes works as expected. dom0:~#

Hi,   I just upgraded the xen-hypervisor-3.2-1 package in Debian etch from the backports (3.2.1-2~bpo4+1) and now my HVM instance won''t boot any more. The error message in the log is:   -c config qemu network with xen bridge for tap0 xenbr0 bridge xenbr0 does not exist! /etc/xen/scripts/qemu-ifup: could not launch network script Could not initialize device

I tried netperf / netserver with Dom0 / DomU, but I could''nt get a correct NW traffic with xentop. Is there anybody could help me? At Host1''s Dom0, run netperf -H VMIP At Host2''s DomU (with VMIP named TTVM), run netserver At Host1, run xentop this way ->"xentop -n -b -d 1" At Host2, run xentop this way->"xentop -n -b -d 1" In Host2''s

I added a virtual interface eth0:1 on one of my machines and suddenly networking breaks on startup of the system (eth0 is gone) when xend starts and runs the network-bridge script. This is supposed to be fixed according to: https://bugzilla.redhat.com/show_bug.cgi I checked and the network-bridge script contains this fix. It works fine on one of my PCs when eth0:1 is added, but not on this

It seems that with their specific Xen packages, Debian likes to go against the norm, and rather than calling the Xen bridging device something sensible like "xenbr0", they rename the main physical ethernet device "eth0" to "peth0" and create "eth0" as the Xen bridge (as far as I can tell, anyways). Anyone know where exactly they do this so I can reverse it?