similar to: network falls asleep on guest

I am trying to install Windows 2003 Server as a xen guest and I am having a problem. After the guest is booted from CD-ROM i partition disk OK, and while system is trying to copy files needed for the installation, it cannot read some files from CD-ROM (starting with wow32.dll etc.). I have tried also to copy installation disk onto local disk and load it from .iso file, but the same problem

I have an issue on my gentoo xen server. If i create linux domU''s, regardless of whether they are HVM or PV, my networking on the domU eventually "falls asleep". If i log into the domU using the VFB or xm console, then utilize the network in some manner (i.e. ping) the network jumps right up and is working. This happens on fedora, ubuntu, and ipcop (2.4 kernel)

Hello list, I have two differents installation Xen Hypervisor on two identical physical server, on the same switch : The problem is on my new server (Xen 4.0.1 with pvops kernel 2.6.32.24), I have bad performance on bandwidth I have test with a files copy and "iperf". Result iperf average: Transfert Bandwidth XEN-A -> Windows

Hi, Curiously, it''s worth noting that Xeon Processor 5100 series are not in the list of HVM Compatible Processors : http://wiki.xensource.com/xenwiki/HVM_Compatible_Processors Patrick ----- Message d''origine ---- De : Mohamed Zohny <mohamad.zohny@gmail.com> À : xen-users <xen-users@lists.xensource.com> Envoyé le : Mercredi, 8 Novembre 2006, 9h17mn 08s Objet :

Does anyone have some tips for setting up Broadcom's 802.3AD support or just getting their driver compiled / installed? First off, I noticed redhat claims the broadcom bcm5708 driver has been added to the rhel4 kernel. But I don't see /proc/net/nicinfo which broadcom claims the driver creates when it's successfully initialized. So, I'm trying to build the driver based on the

Hi all, We''ve been using Xen 3.0.3-1 on Debian Etch for around 2 years now using standard Xen bridging. Over the past few months, we''ve experienced the periodic disappearance of VIF macs from the FDB of the bridge. It seems to happen at random, primarily with domUs that typically receive less network traffic. When the VIF stops responding, the mac address for it still shows up

Hello, Earlier this week I installed a test server with CentOS 5.6 with Virtualization enabled during the installer. Today I installed another server using the same method (they are identical servers). I just did a yum update and I found something curious. Both servers have a different kernel. Server 1 is at 9.1 version and server 2 at 5.1. How can this be? How to I get the latest version on

Hi, I have Solaris Express snv_27 installed on an x86 pc with 4 SATA drives. I have 1 zpool called data with 16 ZFS filesystems. From times to times, it looks like ZFS falls asleep, i.e. when I do a df -k, it takes about a second to list each ZFS filesystem. If I re-issue the command straight away or a couple of minutes later, it takes a second to list all the filesystems. I checked in the

Hi all I'm trying to setup second ethernet on Dell 2950 server but there isn't any eth1 device (in the bios are ON) # dmesg |grep eth eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz found at mem f8000000, IRQ 169, node addr 001c23d878bb eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz found at mem f4000000, IRQ 169, node addr 001c23d878bd

Hi, I hope someone can help me, I cannot seem to get a system's ethernet interface to correctly work in promiscuous mode... I have a Centos 6.4 system with 2 bnx2 interfaces on it. I have set up eth1 in promiscuous mode and am sending traffic to it using the port mirroring configuration on a Nortel 3510-24T switch. The switch reports that it is sending a fair amount of traffic to the

Hi all, got this every time: Error: Device 5632 (vbd) could not be connected. Backend device not found. didn''t have any problem in b95 Any idea? thanks Philip xm info host : snv release : 5.11 version : snv_97 machine : i86pc nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1

Hi all, I'm trying to run Windows Server 2008 x86_64 on XEN, but I have a problem... The instalation works fine, but at the first reboot after instalation I get an "Stop 0x0000007E" error. Please, can you help me with this problem? My *processor*: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz My *xm info*: xm info host : vs01.lan.specto.com.br release :

I am posting the message below again because it did not go through last night. Help! Steve Timm -- ------------------------------------------------------------------ Steven C. Timm, Ph.D (630) 840-8525 timm@fnal.gov http://home.fnal.gov/~timm/ Fermilab Computing Division, Scientific Computing Facilities, Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.

https://bugzilla.samba.org/show_bug.cgi?id=6695 Summary: whitespace problem in directory paths; I know of no work-around Product: rsync Version: 3.0.6 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org

I''m a bit surprised I can''t find anything about this in the mailing list archives. Basically since Mongrel 1.0.1 I''ve had Mongrels fall asleep without any real cause. A deep sleep, actually more like a coma. The mongrel in question (I''m using a cluster of three) can not be revived. A cluster::stop, then cluster::start is nessesary. A ::restart would not

Is serial port "passthrough" possible for the version of xen that ships with centos 5.2? I've disabled the xen hypervisor serial console, and can see the serial port in dom0. I've masked out the 8250, 8250_pnp and serial_core modules on dom0 and rebooted. xm create domain fails with the error that exactly 4 arguments are required and only 3 were given. Steps I followed: 1) I

Hello All, I have been having a very difficult time getting any template to work on xen. Here is what I am running root@personal:/etc/xen-tools# xm info host : personal release : 2.6.22-14-xen version : #1 SMP Tue Feb 12 09:27:26 UTC 2008 machine : i686 nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1

Hello, I have a big problem: Dom0 is centos5.1, domU are centos5.1. My setup is really simple, the only thing is that I give 3 nics to the domU so I use a modified network script (which has worked since january... since fedora 6): " #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 "$dir/network-bridge" "$@" vifnum=1