similar to: old RHEL3 domu kernel

Hi all, I have a rhel 5.1 xen server with two rhel 3 ES hvm guests installed. Both rhel3 guests use an internal xen bridge (xenbr1) which it isn''t binded to any physical interface host. On this bridge throughput it is very very poor, only 2.5 Mbs. How can I increase this throughput??? Many thanks. -- CL Martinez carlopmart {at} gmail {d0t} com

HI, Is the CentOS 7 PV kernel available? I installed latest CentOS 7 & I found out that it is a HVM guest. So, if we wanted to have CentOS PV guest for CentOS 7, is there any specific steps to follow? or the same kernel will work as both PV & HVM? -- Thanks & Regards, Venkateswara Rao Dokku.

On Sun, Mar 15, 2015 at 3:17 PM, Pasi K?rkk?inen <pasik at iki.fi> wrote: > On Thu, Mar 12, 2015 at 10:34:39PM -0400, Nico Kadel-Garcia wrote: >> I'm looking at a CentOS 5 Xen server that I'd really like to put some >> more recent VM's. There are reasons not to touch it at the moment, so >> I can't upgrade it in place today. >> >> Has anyone

(The list appears to have eaten my previous attempt to send this. Apologies if you receive multiple copies.) The attached patches allow you to use paravirtualised network and block interfaces from fully virtualised domains, based on Intel''s patches from a few months ago. These are significantly faster than the equivalent ioemu devices, sometimes by more than an order of magnitude.

Perhaps someone has ideas on this topic, a recent attempt to play with Xen was a reather unlucky event, all what I will be able to demonstrate on that system is a PV ONNV domU which ikely will not be very attractive to the audience :( HW: U40M2, 2 x 2 core AMD revF procs, 8GB MEM, Phonix BIOS 1.5 (latest) 1 x 200GB internal SATA drive SW: dom0 ONNV build 82, latest VirtManager from

hello! i think i have an very common problem. i want to run a distro based on a 2.4 kernel (Scientific Linux 3/Centos 3/RHEL 3) in xen3 as domu. the dom0 is a 2.6 based and works fine. so i think the way to go is to "simply" use an 2.6 kernel. but now i see there are several things which don''t work for example module-init-tools are missing and i expect problems with the glibc.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I''ve been working on a project recently which we want to virtualize. It runs on Windows Server 2003, so my first attempt was to put it in a HVM domU. Sadly, this application requires network performance higher than HVM is seemingly capable of. In the absence of PV drivers for Windows, I tried running it on VMWare instead, and I

I totally agree with Luc Boudreau about this problem. On modern branded server they ALL use Broadcom chipset... I must admit that: a) lot of people are experiencing the problem but can tolerate it or b) someone already experienced this problem and solved it Lets'' approach the problem pragmatically... just start with a survey on the list. ... hope we solve this issue soon. Ivan

Hi All, Sorry if this is a stupid question. I am walking into someone else''s xen install, and don''t have access to the host os at the moment. How do I tell just from a domU (with Ubuntu) if it is PV or HVM. I have looked through the forums and documentation and it seems to be very easy to figure this out from dom0, but unfortunately that isn''t possible at the

I have been using the built in Xen Paravirt NIC drivers for paravirt networking and had bad performance until I disabled all offload setting on the bridge and paravirt nic (From Dom0). There are 2 related questions I have, where should I be tweaking the offload settings, the Dom0 Physical NIC, The Bridge or the DomU NIC? Which settings in particular tend to cause trouble? (I just disabled all of

# dd if=/dev/zero of=/srv/xen/webserver.img oflag=direct bs=1M seek=4095 count=1 # dd if=/dev/zero of=/srv/xen/webserver.img oflag=direct bs=1M count=4096 root@debian:~# grub-install /dev/xvda Searching for GRUB installation directory ... found: /boot/grub The file /boot/grub/stage1 not read correctly. Darkbasic _______________________________________________ Xen-users mailing list

Hello every body. Well, my question is very simple . I Have a HVM working fine ( I hope so ... ) on a CentOS 5.1 , xen 3.1. I created config file by hand .. I''m not using virtmanager from CentOS .. I '' m using LVM dev w/o file system formated. My HDA is configured like this: disk = [ ''phy:/dev/vms_1/win01,hda,w'' ] My question , what is the diference if I

Hi, we''re contemplating getting a large new server, where we will run a number of virtual servers. Are there any things we need to keep in mind in that case? Are there limitations on what a Xen system can manage? We''re talking about a 4 x Quad core CPU server with 64 GBs of RAM and a couple of terabytes of RAIDed SATA storage. -Morten (Re-sending this, as the first message

Hi Everyone, In my HVM guest''s config file, I have given my guest 3 interface. I have called them fw1, fw2 and fw3. I have joined each interface to a bridge on the Dom0. This does appear when I do a "brctl show". However, there are 3 other interfaces also added called tapx.0,tapx.1 and tapx.2 (Where x is the domain ID for the guest). Furthermore, I am only able to run

Hi Is it true that the GPLPV drivers is incompatible with QCOW images? The Windows DomU works fine with raw standard "file:/" images, and paravirtualized Linux DomU works fine with QCOW and raw images. If i use QCOW images with my Windows DomU''s i get a stop error: 0x00000007b (inaccessible boot device). It looks like the blkback.3.hda process, that normally starts with

Andy, OSOL 2009.06 been installed in stub domain (hvm domain) at mentioned Dom0 with 2.6.30 xenified kernel via xen-patches-2.6.30-2.tar.bz2 refuse to activate PV drivers. When same Dom0 starts with 2.6.29.4 xenified kernel (xen-patches-2.6.29-6.tar.bz2) kernel OSOL 2009.06 in stub (hvm) domain does activate PV drivers for xdf, xnf . Boris

I''ve just uploaded 0.10.0.50 which fixes a few bugs related to high network load (BSoD''s & packet corruption). It should upgrade any previous 0.10.x.x. Additionally, I''ve also uploaded uninstall_0.9.x.txt (rename it to .bat) which will uninstall 0.9.x drivers. After running that, reboot and they should be gone. Please do a backup first though as I have only tested

I''ve just uploaded 0.10.0.50 which fixes a few bugs related to high network load (BSoD''s & packet corruption). It should upgrade any previous 0.10.x.x. Additionally, I''ve also uploaded uninstall_0.9.x.txt (rename it to .bat) which will uninstall 0.9.x drivers. After running that, reboot and they should be gone. Please do a backup first though as I have only tested

In config file, ''*type=ioemu*'' is added with vif . Does it make the difference if we don''t add. Because i did not notice any difference in para as well as full virtulization. Same as in case of exporting the disk to Guest dom. Is it just a placeholder or else ? Second thing, I am running RHEL3 as a HVM DomU on xen-3.0.4. Every thing works fine, but i had a problem to

In my experiments with setting up a NAS as a VM, I can only successfully import three drives; the root drive, the cd and one more. However, I have plenty that I want to use: disk=[''file:/vserver/vm_disks/Patch.disk.xm,hda,w'', ''phy:/dev/sda,ioemu:hdd,w'', ''phy:/dev/sdb,ioemu:hde,w'', ''phy:sdc,ioemu:hdf,w'',