similar to: HVM Network Speed

Newbie here. My hardware supports HVM (full virtualization), but I only need to run Linux on it. I initially tried to create a HVM domU, but couldn''t get pciback to work with a telephony card I need for use with Asterisk. However everything seems to be working fine under a paravirtualized guest as long as I use permissive mode on the card. (Knock on wood-I''ve had some weird

Hi, We have found that exist a huge degradation in performance when doing I/O to a disk images contained in single files from a paravirtualized domain and from an HVM at the same time. The problem was found in a Xen box with Fedora 8 x86_64 binaries installed (Xen 3.1.0 + dom0 Linux 2.6.21). The test hardware was a rack mounted server with two 2.66 Ghz Xeon X5355 (4 cores each one, 128 Kb L1

>> I''d like to change the xen x86 caps to such format: >> xen_caps : xen-3.0-x86_64 hvm-x86_32 hvm-x86_32p >> hvm-x86_64 >> i.e. remove the xen version info from hvm caps string, >> because it makes no sense for HVM guests. >> How about your opinion? > >I can''t see any harm in having a version identifier. When we start

Hi, I have problem installing or running domU OS (Windows XP or Redhat 7.3). The machine runs CentOS 4.4 X86_64, Xen-3.0.3. Paravirtual domU works without problem. The problem is that when I run command "xm create <config>", nothing would happen. hvmloader does not seem get started at all. I''ve tried installing both 64bit and 32bit vnc, sdl but did not see any

Hi All, I was hoping to run a Windows 2003 server in production on Centos 5.2 however the performance isn't very good. The host is Centos 5.2 64 bit. I did some file transfers and I'm seeing about 12Mb/s on a Windows 2003 VM and about 8Mb/s on a Windows 2003 32 bit VM. Numbers are measured using the builtin Windows 2003 server networking monitor (Press Ctrl Alt Del in Windows and go

> I''d like to change the xen x86 caps to such format: > xen_caps : xen-3.0-x86_64 hvm-x86_32 hvm-x86_32p > hvm-x86_64 > i.e. remove the xen version info from hvm caps string, > because it makes no sense for HVM guests. > How about your opinion? I can''t see any harm in having a version identifier. When we start adding the option for paravirtual

Hello community! I need help with a problem I haven''t been solved with the network team. I manage a network that has over a thousand computers, and the most of the servers are virtualized over Debian / Xen by me. The specific issue arises when I try to set up a DomU HVM running Debian Squeeze, the VM doesn''''t recognize the network but it runs. It gives an error

Hi, I know it''s a problem that has already been discussed, but as I didn''t see any solution, I''m asking... We''ve been trying to use Xen 3.0.3 HVM mode with windows or linux in the past few weeks, and have been suffering from bad network performance. First, I must say that we didn''t succed to setup Windows 2000/2003 directly using  Xen, we had to

I recently got my hands on a VMX-supporting processor and I''ve been trying to install different OSes. I managed to get a Windows XP guest working in HVM mode (with SDL, VNC gives me messed up input) but I''m having issues with the install on the linux guest. Until that''s fixed, I''m setting up the linux guest as a paravirtualized host. I''m using a

Package: xen-hypervisor-3.0.3-1-i386 Version: 3.0.3-0-1 Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, When you have a HVM domain running, if you try to boot a regular paravirtualized domain, dom0 (or maybe the hypervisor) crashes immediately (reboot). The opposite (trying to boot a HVM domain while a regular paravirtualized domain is running) crashes the system as well. I

Hey, Has anyone seen the following behavior: I''m running a linux hvm guest with usbdevice = ''tablet'' for correct mouse tracking over vnc. Everything works fine, until I use any application that touches the network (including a simple ping), and the entire guest freezes up and becomes unusable. This behavior happens for usbdevice = ''mouse'' as

I have couple of HVM guests on xen 3.2. When guests boot, qemu-dm uses alot of cpu for approx 20 minutes post boot then load drops to average 0.50. I did some debugging and see this is going on, I suspect display output is using the CPU. Disabling VNC and SDL didn''t help with the CPU usage. any ideas how to reduce the cpu or stop it all together? My setup is as following: Xen

Hello, This is my first post in this list. I''m running Debian Squeeze as Dom0 on a bi-xeon 64 bits : root@sd-29499:/etc/xen# uname -a Linux sd-29499 2.6.32-5-xen-amd64 #1 SMP Tue Mar 8 00:01:30 UTC 2011 x86_64 GNU/Linux I''m trying to install a Squeeze DomU but there is no network card, even during install wich doesn''t show any network card with lspci (but when I

Hi, I''ve installed Solaris 10 u4 as a hardware virtual machine guest domain on SXDE 1/08 (aka Nevada b79b) which was fine, i.e. after the virt-install the domain was fine. However when I went to shutdown the domain I issued "virsh shutdown solarisHVM" which appeared to immediately terminate the guest domain. Note, I also have a paravirtualized domain

Hi all, I now have Xen running on Intel Core2 duo system, and am running a HVM domU with Microsoft Windows XP Home Edition, cold-installed from distribution CD. Problem is, Windows can''t get to the network. My dom0 ifconfig looks correct, as far as I can tell. I have a DHCP server on my local network, but the Windows XP domU claims to be unable to find DHCP. I''ve also tried

Hi, We''ve been using Amazon EC2 a fair bit. We''ve discovered that to run a proprietary, commerical bioinformatics piece of software that is liscenced by physical SOCKET instead of cores, we needed to use a virtualization technology that converts multiple cores into a single socket. (This proprietary software will allow us to use up to 4 cores per physical socket, so

Hello. I''m trying to set up hvm for linux or windows. I start with a very simple configuration without disks at all. but the virtual machine does boot or even "power up". If i remove the ioemu from the network device and specify type=brige or type=route everything goes fine, the boot process is starting but then I cant get network working in the guest.

Dear, I''ve attempted to upgrade a Xen box from 3.1.2 to 3.2.1. Unfortunately it has been a partial success only. At this point I''m really stuck with a network problem that affects my HVM machines (Linux PV run fine). The really odd thing is that everything seems to work properly, except that the "vif" network interfaces in dom0 seem to have only dropped TX packets for

If I understand correctly, a HVM domain''s network adapter gets a tapX device created for it in Dom0 for qemu to talk to, and a vifY.Z device for the PV drivers (which probably aren''t there) to talk to. How can I stop the qemu code creating the virtual Realtek driver? What will happen if I try and use PV and Realtek drivers at the same time? Will the Realtek driver just talk to

xend uses rtl8139, and we want xl to be compatible with xm. Some older operating systems don''t have e1000 drivers, and we want widest compatibility rather than best performance (people who want good performance are best advised to use PV-on-HVM drivers). We''ll probably switch to a new default when switching to upstream qemu, in the Xen 4.2 release cycle. Signed-off-by: Ian