similar to: System seams slower with Xenified kernel and xend dies with SIG 15

I''ve been looking at anti-virus software for Xen use on Linux systems, on both Dom0 and DomU, in industrial environments. Reviewing documentation on various packages seems to show that all the commercial ones insist on sticking kernel modules into a limited set of standard known kernels. This of course creates some serious risks until the anti-virus packages are developed in and

Hi, I''m trying to build non sles10 domU under sles10 dom0. I''ve downloaded centos and debian images from www.jailtime.org fixed the config file and try to start domU. After creating domU from images I get Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) I''m running without problems two sles10 domU machines. After using google allot :-)

Hi all, I manage to create a VM (slackware image) and hide the PCI device (qlogic HBA) from Dom0 to DomainU. Now the Dom0 cant see this HBA and the ''xm list -l'' shows this pci device under the DomainU. But how can I do some scsi inquiry or check if this PCI device is visible to the DomainU from the DomainU''s console. Any help? Thanks and regards Ashit

Hello People!! I''ve a problem with the xend service, when i want to run it don'' t show me nothing, so then i tried to run it like these: /usr/sbin/xend start and show me a lot of errors see --> ERROR: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): File "/usr/sbin/xend", line 33, in ?

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

Hi, I am sucesfully running 2.6.30 xenified kernel: Machine DELL Optiplex 960 CPU intel E8400 8GB RAM Debian lenny 5.0 x64 Xen 3.4.1 rc11 + kernel 2.6.30.2 xenified thanks to howto from bderzhavets: http://bderzhavets.wordpress.com/2009/07/07/building-xenified-2-6-30-1-kernel-via-xen-patches-2-6-30-2-tar-bz2/ So far running ok. 1) I am not able to resolve issue while booting xenified

Hello,   I can say that I have searched the entire ''world wide web'' and still haven''t found ''complete  and clear answers'' to the often asked question of: Given a Xen (release) build (say 3.2.0), which by default tries to get and build and assume Linux kernel-xen 2.6.18 from the mercurial repository, HOW TO override the build and make it work with a

Known bug for 32-bit. Workaround is on the net. http://mulps.wordpress.com/2009/05/29/compiling-xen-kernel-2-6-29-2/ Boris ________________________________ From: Mehdi Sheikhalishahi <mehdi.alishahi@gmail.com> To: bderzhavets@yahoo.com Sent: Sun, January 3, 2010 4:25:00 PM Subject: Xenified linux kernel Hi Dear: I am refering to the

I''m not seeing the problem that Fan Zhao is reporting, instead I get this one. Not sure if ti''s the same one or a different problem... This happens with my simple-guest [i.e. not using hvmloader, as I described before]. This worked fine yesterday. (XEN) event_channel.c:178:d0 EVTCHNOP failure: domain 0, error -22, line 178 (XEN) bad shared page: 0 (XEN) domain_crash_sync called

Hello all, I have a problem with Xen and FibreChannel. The Dom0 can''t export a Disk on a FibreChannel SAN-Box to the DomU''s. In the DomU configuration I try: disk = [ ''phy:/dev/sdb1,/dev/sda1,w'' ] or disk = [ ''file:/mnt/sambashare.img,sda1,w'' ] sambashare.img is a 512MB great Diskimage on a Partition on the FC-SAN-Box, the Dom0 mount this

Hi developers, I met some domU issues and the log suggests missing interrupt. Details from here: http://www.gossamer-threads.com/lists/xen/users/263938#263938 In summary, this is the suspicious log: (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3 I''ve checked the code in question and found that mode 3 is an ''reserved_1'' mode. I want to trace down the source of this

Hi: we have following setup: 1. 2.6.16-33-based Xen 3.0.3/Xen-3.0.4 DOM-0 kernels. 2. Using LILO-mbootpack from USB we boot Xen-->DOM-0 setup 3. We mount harddisk and try to install xp.hvm While,we are successful with FCs as DOM-U, for XP we get, VBD (768) could not be connected. We do have max_loop count to 64 and enough loop devices. Note that above error is consistent on both 3.0.3

Hello, I use Gentoo and I can't get R 2.0.1 to compile. I used the portage system, Gentoo's source package sytem, and after it uncompresses the source to R, it says that I don't have a fortran compiler. It told me to use f77 flag and re-emerge gcc, which I did with the f77 and fortran flags, but it still won't compile. Does anyone have any ideas? I suspect that gcc has changed

> Hmmm... wouldn''t it be nice if we didn''t have a bespoke, > buggy & incomplete emulator for hvm mmio. ;-) In the process of solving this one, I''ve got to (another) of the blocking points... At the moment, we translate the virtual address from the guest in the page-fault-handler to guest physical address via the gva_to_gpa() function in svm.c/vmx.c:

I can boot a 64-bit HVM image on my SVM-system, and it goes quite a long way before it crashes (due to not finding the hard-disk image and thus no root FS - which I think may well be the configuration file). But if I set debug=y in the Rules.mk, I don''t get very far at all - it crashes well before it gets to any user-mode (Ring3) - in fact, I think it''s crashing pretty much as

paging mechanism clarification Hi All, The Xen uses 2 level Paging Mechanism to resolve the Virtual Addresses into frame numbers from domU.The first level is taken care by the MMU for the domU i.e translation from virtual address to the physical address just like normal paging mechanism. The second level of translation is done by the Xen hypervisor.It translates the pseduo physical address

What are methods to debug domU when it hangs? Using xen 3.1 compiled from sources I could not manage to launch no domU. Fot instance, I run something like this: =====8<===================== disk = [ ''file:/oradata-act/sles.disk,hda1,w'', '',hdc:cdrom,r'' ] kernel = "/boot/vmlinuz-2.6.18-xen" ramdisk = "/boot/initrd-2.6.18-xen" cpus =

This is a new Centos 5.1 install on a HP nc2400 (that use to run XP). Completely clean install; blew away the XP partitions... After applying all the updates, and configuring for the rpmforge repo, I used yumex to install dkms and the dkms-ipw3945, ipw3945-firmware, and ipw3945d rpms. lsmod|grep ipw shows: ipw3945 180391 1 ieeee80211 33417 1 ipw3945 and dmesg)grep

Hello, it''s not the first time but ... Who know? Well, I use xen in HVM. All works fine, my keyboard in Dom0 is AZERTY, but this keyboard become QWERTY when i enter in VM, it''s not useful to type password. How can i keep my keyboard AZERTY in my VM and in Dom0? -- Benjamin HENRION Elève de 4eme année de l'' EXIA (Nancy) Ecole supérieure d''informatique Spé

Good morning, I installed on xen a windows XP and a Windows 2003 domU. Windows operating system does not know the real network card but it setup up an AMD pcnet card 10mbps. Is it possible to setup a full virtualized domU with a real network card ? I installed also windows on a trial xen enterprise and real network card seeems to work fine. What differences between xen and xen entrprise as far