similar to: Is there a way to differentiate PV-on-HVM devices from qemu-dm devices?

Hi Steven, I onced played with your PV-on-HVM driver before it is checked in into unstable, I remember at that time, there is a XENFEAT_64bit_shared_info flag to handle situation of 32bit guest on 64bit hypervisor, at least vnif works fine with it. Later, when the code is checked in, this flag is gone. At first I though this was an effort to make hypervisor more transparent to HVM guest, but now

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal Under this Xen setup, (Linux) HVM guests fail to have network active when running with *routed* networking, as some hosting providers require (in my case, OVH). In this scenario: * the host is a described below * the guest runs as HVM. * the guest runs exclusively with ioemu; virtual network drivers are not available (vanilla lenny

Hi all, my name is Hirofumi Tsujimura. We are porting and testing a PV-on-HVM in the IPF. This is a first time to send mail. I probably found the problem when I tested the VNIF. My operation for the test is following. 1. create a domain VTx and attach the VNIF in it. 2. create a domain U. 3. send a packet to the domain VTx from the domain U with ping command. Then, the domain VTx

On Thursday, 6 April 2017 12:04:20 CEST Richard W.M. Jones wrote: > Our previous test was wrong. It tested whether the xennet.ko module > exists. This module was renamed in more recent kernels (to > xen-netfront.ko), so it happened to not detect modern kernels as > PV-only, but this was by chance. Just stumbled upon this bit in v2v/convert_linux.ml: if family = `SUSE_family

samuel, I have a try with HVM stubdomain on r17062, but failed to make on 32b platform. Attached patch can fix it, but don''t know if okay. After installation, I failed to start stubdom. So I created it manually and got following debug mesg(both HVMdomain and stubdom are created) Can you give some lights on following questions: 1. I use default vnclisten. Does it matter? 2. Seems qemu

I am trying to get PV drivers running on both Centos 5.1 and Centos 5.3 HVMs, my DomU is Centos 5.2 with Xen 3.31. For 5.1 I install the kmod-xenpv RPM but for 5.3 the drivers seem to be built-in. For the network drivers to work I had to unload the Realtek NIC driver and renamed its .ko files to stop it loading. Adding the Xen-Vnif alias to modprobe.conf then got the PV NICs working nicely (Much

Add support for a xenstore dm command to flush qemu''s buffer cache. qemu will just keep mapping pages and not release them, which causes problems for the memory pager (since the page is mapped, it won''t get paged out). When the pager has trouble finding a page to page out, it asks qemu to flush its buffer, which releases all the page mappings. This makes it possible to find

all, On latest tip, following symbols are unresolved when inserting modules xen_balloon: Unknown symbol totalhigh_pages xen_vnif: Unknown symbol netfront_accelerator_call_resume xen_vnif: Unknown symbol netfront_accelerator_call_suspend_cancel xen_vnif: Unknown symbol netfront_accelerator_call_stop_napi_irq xen_vnif: Unknown symbol balloon_update_driver_allowance xen_vnif: Unknown symbol

Hi All, We tested the PV driver on HVM domain. When ten vif was defined in configuration file for VNIF, the HVM domain was not able to be created. ---------------------------------------------------------- # grep vif RHEL5GA_test.conf vif = [ ''mac=02:17:42:2f:01:11, bridge=xenbr0'', ''mac=02:17:42:2f:03:11, bridge=xenbr2'',

There would seem to be a potential deadlock in the netfront accelerator plugin support. When the configured accelerator changes in xenstore, netfront tries to load the new plugin using request_module(). It does this from a workqueue work item. request_module() will invoke modprobe which in some circumstances (I''m not sure exactly what - I''ve not managed to reproduce it myself)

Package: xen-utils-3.2-1 Version: 3.2.1-2 If I try to create an HVM domain I get the following error message: araminta:~# xm create -c heceptor.cfg Using config file "/etc/xen/heceptor.cfg". Error: Creating domain failed: name=heceptor xend-log has a Python backtrace in it: [2009-03-21 14:14:46 25927] DEBUG (XendDomainInfo:84) XendDomainInfo.create(['vm', ['name',

PCmark2005 running in Windows XP is known to need this mmio decoder. This patch also fixes some inconsistencies, the comments of mmio decoder use AT&T ordering for operands, but the syntax looks like Intel asm. This leads to much confusion. Signed-off-by: Qing He <qing.he@intel.com> Thanks, Qing _______________________________________________ Xen-devel mailing list

tag 554805 + patch thanks The problem to solve is that qemu-ifup assumes the world is always bridged, and vif-routed does not know of the concept of TAP devices, and even if it did, it has at this point no way to get at qemu's TAP device anyway. The following set of patches help run in the ioemu-HVM situation: * xend-image.py.diff : modifies the HVM loader so that when running in

Hi, Sorry, I should not have removed infomation on xend. image.py, line 399, in configVNC config.remove([''vncpasswd'', vncpasswd_vmconfig]) When vncpasswd is removed, qemu-dm cannot be started in reboot of hvm domain. Because necessary information disappears. It cannot be helped though information in config list remains in xenstore. This patch corrects above. Regards,

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

(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.

Patch the Xen version of ring.h Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com> diff -r 8fc927798476 xen/include/public/io/ring.h --- a/xen/include/public/io/ring.h Tue Sep 01 11:36:51 2009 +0100 +++ b/xen/include/public/io/ring.h Thu Oct 01 02:11:45 2009 +0800 @@ -97,7 +97,8 @@ struct __name##_sring { struct __name##_sring { \

Hi, $subject says pretty much all, this patch updates netfront and makes it store the network addresses of the interfaces in xenstore, so it''s much easier to figure what IP some virtual machine has and (for example) ssh into it. comments? Gerd _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Dear xen-users. First of all, I''m not a linux-guru and a beginner with xen and completly new in this mailinglist. I''ve installed Xen on debian 6 and I was successful creating two machines: one for tests and "fogserver" (to test speed of writing computer images), both para-virtualisations.

Hi Jeremy, I backported the branch I have in linux-next plus some older PV on HVM fixes to stable-2.6.32.x. Please pull: git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git stable-2.6.32-pvhvm Ian Campbell (11): xen: do not respond to unknown xenstore control requests xen: use new schedop interface for suspend xen: switch to new schedop hypercall by default. xen: