similar to: Xen network performance: default and ne2000

Has anyone gotten networking in an HVM domain to work with the emulated NE2000 rather than the emulated PCnet? I have Linux running in an HVM domain just fine with pcnet. If I change the config file to say ne2000=1, the tun0, vif0.1, and xenbr0 devices get created in dom0, the kernel in the HVM domain brings up eth0 OK (NE2000 support is built into the kernel), but I can''t get dom0 to

Hi folks, i have a problem to boot an Ubuntu CD in a hvm-enabled machine. I get a black screen when connecting via vnc to the virtual machine. When i change the line cdrom= to some other CD (grml Live CD, Windows CD, other ones) it runs fine. But any Ubuntu CD (kubuntu alternative, ubuntu server, ubuntu desktop) i get the mentioned error. I tried using sdl (no window opens) and with

Greetings xen gurus... I''m working with xen-3.0-testing downloaded on July 3, 2006. I have configured an hvm domain and want to use vif-route and network-route to configure the communication. The domU starts up fine. I was able to complete the installation of the OS (RHES3) and can restart the domain repeatedly. However, I cannot ping the network interface from dom0 using the

Hello, I''m trying to get my first HVM domU installed (another Debian domU is already working under the same dom0). I intend to install the guest OS from a bootable CD-ROM. But when I create the new HVM domU with ''xm create xp1-cd.cfg'' , I don''t get the expected installation-window and find this in /var/log/xen/qemu-dm.6575.log: domid: 6 qemu: the number

At some point the Cirrus VGA driver was commented out. Probably for debugging. The patch below adds it back in. It works just fine. Signed-Off-By: Leendert van Doorn <leendert@watson.ibm.com> diff -ru xeno-unstable.orig/tools/ioemu/hw/pc.c xeno-unstable.mine/tools/ioemu/hw/pc.c --- xeno-unstable.orig/tools/ioemu/hw/pc.c 2005-05-25 07:48:57.000000000 -0400 +++

Source: xen Version: 4.1.4-4 Severity: serious Tags: jessie sid User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value

Most of them bases on latestest Qemu. The modifications are the below: Adding logic in ne2000_update_irq() avoids exceptional logic. Another modification is the ne2000_can_receive(), "if (index < boundary)" -> "if (index <= boundary)". Others based on lastest Qemu. But the latest Qemu adds new features, which not been added in the patch. The qemu uses polling

I have a self built system using an Intel D 920 processor and a MB that supports VT. I''m able to run HVM domains fine, but have trouble getting multiple VCPUs for these domains. Here is an example of one of my configs. # -*- mode: python; -*- #============================================================================ # Python configuration setup for ''xm create''. #

Hi koonz I noticed that you are using the cdrom parameter in the config file I believe that''s no longer used in recent versions of Xen. I am running debian etch here atm and am trying to virtualize windows guests aswell I am able to boot up windows with the following configs although they do tend to hang at some point during the installation. ----- Config windows xp ----- import os,

All, We are facing some issues bringing up a DomVT on Xen x86_64(changeset 9267). We created a disk image with dd 8 G in size. We then booted an associated Dom-VT with a CD-ROM and did net-install of the sles-9 OS. This completes successfully. Then, when the system is brought around for a reboot (having changed the boot option from cdrom to disk), the system hangs after the line

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

The attached patch to the qemu emulation of the pcnet hardware fixes several problems. It will now only read and write a transmit or receive descriptor once. It will correctly handle transmitting frames with more than two fragments. It will discard oversize frames instead of corrupting memory. I have tested all the changes I have made and even seen an improvement in receive performance from

Hello, A preview of the qemu 0.8.1 based ioemu is now available at: http://xenbits.xensource.com/chris/add-ioemu-new and http://xenbits.xensource.com/chris/enable-ioemu-new In addition to these two patches, you need a copy of qemu-0.8.1 and place it into tools/ioemu-new -- one option is the tarball available at http://xenbits.xensource.com/chris/ioemu-cvs-qemu-0.8.1.tar.bz2 which extracts to

Hi all: I installed Fedora 6 on xen 3.0.4(which is intalled in fedoa 7) as domainU, I find the following information int the cfg file: # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. #vif = [ ''type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci'' ] # type=ioemu specify the NIC is an ioemu device not netfront

Hi all: I installed Fedora 6 on xen 3.0.4(which is intalled in fedoa 7) as domainU, I find the following information int the cfg file: # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. #vif = [ ''type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci'' ] # type=ioemu specify the NIC is an ioemu device not netfront

Hi. I''ve just upgrade my xen 3.0.1 to xen unstable. I noticed that there is no vmx driver here, only hvm. Actually I cannot start my VT domain: root@akira:/etc/xen# xm create bluszcz.hvm Using config file "bluszcz.hvm". Error: Device 768 (vbd) could not be connected. Backend device not found. root@akira:/etc/xen# my config: import os, re arch = os.uname()[4] if

Hi First of all I want to say I''m new to xen so please be patient. I want to run xen on a PentiumD Dual with Vanderpool. I use OpenSuse 10.1 as Hostsystem. VM settings: disk = [ ''phy:/dev/hda5,ioemu:hda,w'' ] memory = 256 vcpus = 2 builder = ''hvm'' device_model = ''/usr/lib/xen/bin/qemu-dm'' kernel =

Hello, When I start an HVM domU qemu return me the error "xs_read(): vncpasswd get error..." I''m running Xen 3.1 fedora patch + 2.6.20 + ubuntu feisty. Xen Packages come from Cedric Gabriello ( http://cedric.gabriello.fr/ ) <http://cedric.gabriello.fr/> It''s very strange because the VM seems to start ... but qemu process appear as [ defunc ] and of course

Hi list!, this is my first mail, nice to meet you ;-) The first, sorry for my english, this is not good, i am from Spain :-( The second THANKS in advance ;-) I am writing because I have a problem with the virtualization of M$ Windows on Xen. All system works OK when I virtulize systems based on GNU/Linux. When I start my Windows Machine for make installation with the CD (iso). The Windows

When I run "xm create winxp" my computer hard reboots. I am using the xen-sources, xen and xen-tools packages from gentoo ~amd64 (version 3.0.2) My virtual machine config is the following: kernel = "/usr/lib/xen/boot/hvmloader" builder = ''hvm'' memory = 512 name = "winxp" vcpus = 1 vif = [ ''type=ioemu, bridge=xenbr0'' ] disk = [