similar to: libvirt: how to set PV-on-HVM drivers??

Processing commands for xen@bugs.xenproject.org: > create ^ Created new bug #20 rooted at `<1571692646.20131009000945@eikelenboom.it>'' Title: `Re: [HVM} xen_platform_pci=0 doesn''t prevent platform device creation and disk and nic take over by PV drivers.'' > title it xen_platform_pci=0 doesn''t work with qemu-xen Set title for #20 to

Hi Karthick, For questions like this it''s good to loop in the xen-users list as answers may benefit others too. In terms of how to create an ISO.. that''s not quite the intention of these images. SolusVM intends for you to install the OS from an ISO which it will then manage. This is quite possible but I don''t know much about SolusVM. What you would need to do is: 1.

Hi, I''m the Mageia XEN packager and during QA, we stumbled into a problem. in fact, we wanted to test Mageia 3 installation on a HVM. so, we had a sparse image and a iso file: [ ''file:/opt/testhvm.img,sda,w'', ''file:/opt/mageialive.iso,hdb:cdrom,r'' ] the live booted, and was able to install to disk, but it never seemed to boot after the install...

Hello, I'm looking for an example configuration for a PVHVM domU that works with 4.3.1. The one at http://wiki.xen.org/wiki/Xen_Linux_PV_on_HVM_drivers causes 3 warnings and some errors: WARNING: ignoring "kernel" directive for HVM guest. Use "firmware_override" instead if you really want a non-default firmware WARNING: ignoring device_model directive. WARNING: Use

Wednesday, October 9, 2013, 2:00:02 PM, you wrote: > create ^ > title it xen_platform_pci=0 doesn''t work with qemu-xen > owner it Anthony Perard <anthony.perard@citrix.com> > thanks Perhaps in general looking at the libxl and xend .. and .. qemu-xen and qemu-xen-traditonal compatibility shoud be added too. Perhaps i''m a bit blunt .. but for users

If you are running CentOS Linux 7 inside a Xen DomU (VM) in PV mode, you can not upgrade to the standard 7.4.1708 kernel that is currently in the CR repo and that will be soon released in our file 7.4.1708 tree (3.10.0-693.*el7) The CentOS Plus kernel will be available when we release the 7.4.1708 tree and it does boot inside a Xen DomU PV, so you can either upgrade to the CentOS Plus kernel in

Hi all, I have some problem with xm save/restore in Xen-4.0.0 & linux-2.6.31.13, First, the /etc/init.d/xendomains seems do not work properly because of bash version. So I modified it as follow: root@r02k08027 # diff -up /etc/init.d/xendomains /etc/init.d/xendomains_31 --- /etc/init.d/xendomains 2010-04-08 00:12:04.000000000 +0800 +++ /etc/init.d/xendomains_31 2010-04-19

Hi all, I have some problem with xm save/restore in Xen-4.0.0 & linux-2.6.31.13, First, the /etc/init.d/xendomains seems do not work properly because of bash version. So I modified it as follow: root@r02k08027 # diff -up /etc/init.d/xendomains /etc/init.d/xendomains_31 --- /etc/init.d/xendomains 2010-04-08 00:12:04.000000000 +0800 +++ /etc/init.d/xendomains_31 2010-04-19

Hi I cant start a hvm domU with more than 3 nic's configured... why? it is a bug? With previous versions it was possible... here the config - it is an opnsense (openbsd) hvm domU: name = "fenrir.chao5.int" uuid = "7aedcd03-54e8-4055-8d1b-37dd34194859" maxmem = 2048 memory = 2048 loader = '/usr/lib64/xen/boot/hvmloader' type = "hvm" vcpus = 2

Hi I cant start a hvm domU with more than 3 nic's configured... why? it is a bug? With previous versions it was possible... here the config - it is an opnsense (openbsd) hvm domU: name = "fenrir.chao5.int" uuid = "7aedcd03-54e8-4055-8d1b-37dd34194859" maxmem = 2048 memory = 2048 loader = '/usr/lib64/xen/boot/hvmloader' type = "hvm" vcpus = 2

It seems to be a problem with kernel... I use the kernel-ml there (5.5.6)... with kernel from centos-virt repo (4.9.*) it works without this problem... --- ------ Greetz Am 27.02.2020 07:50, schrieb Christoph: > Hi > > I cant start a hvm domU with more than 3 nic's configured... why? it is > a bug? > With previous versions it was possible... > > here the config - it is

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-2 Hi, Hvm domU does not starts up afer dom0 reboot. Bridge br0 is set up manually. Dom0: Debian Wheezy 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux DomU: Debian Squeeze 2.6.32-5-amd64 #1 SMP Sun Sep 23 10:07:46 UTC 2012 x86_64 GNU/Linux config: ===<======== kernel = '/usr/lib/xen-4.1/boot/hvmloader' builder = 'hvm'

Hello, I was testing Fedora 16 (rc2) Xen host, with included Xen 4.1.1 rpms and Linux 3.1.0 dom0 kernel. Fedora 16 PV domUs seem to work nicely. I noticed a problem with Fedora 16 Xen HVM guests though. The F16 guest kernel (Linux 3.1.0) fails with the qemu-dm emulated DVD-ROM drive.. Full HVM guest kernel dmesg attached to this email. See the end of this email for Xen cfgfile for the

Here is the code, assuming 8 cores in the cpu. library('modeest') library('snow') cl = makeCluster(rep('localhost', 8), 'SOCK') x = vector(length=50) x = sapply(x, function(i) i=sample(c(1,0), 1)) pastK = function(n, x, k) { if (n>k) { return(x[(n-k):(n-1)]) } else {return(NA)} } predR = function(x, k) { pastList = lapply(1:length(x), function(n)

Dear all, I found a strange thing with the snow package. This will work: y = matrix(1:4, 2) cl = makeCluster(rep('localhost', 8), type='SOCK') parMM(cl, y, y) This will not: y = matrix(1:4, 2) ncore = system('nproc') parMM(cl, y, y) Error in cut.default(i, breaks) : invalid number of intervals I also tried: cl = makeCluster(rep('localhost', ncore),

hi list this is as probably more of networking problem than an icecast problem but it is related - hope people don't mind. I've been running tests for a project that starts 20 August. I'm sending stream from my audio software to a local icecast server, then relaying this to a commercial shoutcast service. Initially i was using 7000 for the relay port. Worked fine. Then one morning

the contexts are as follows, looking forward to your reply, thanks [1]enviromention : xen3.4.2+CentOS-5.5 [2]config file: xp.hvm, as follows _s_name = 'xp-101' _s_vnc_display = 5310 _s_vm_id = 101 _s_vm_mac = '00:16:3e:eb:ca:65' _s_memory = 512 _s_allow_destroy = False _s_use_vnc = True # -*- mode: python; -*-

The Xen module is unnecessary and it has been for a while. Most Xen systems will not be using the module, even now, because xen-detect is not installed by default on most Xen systems, and dracut uses xen-detect to decide whether to include the module. It also has some problems: 1) it does not try loading xen_platform_pci; 2) it loads modules unnecessarily; modules.alias is where all Xen

On 09/05/2017 02:26 PM, Kevin Stange wrote: > On 09/04/2017 05:27 PM, Johnny Hughes wrote: >> On 09/04/2017 03:59 PM, Kevin Stange wrote: >>> On 09/02/2017 08:11 AM, Johnny Hughes wrote: >>>> On 09/01/2017 02:41 PM, Kevin Stange wrote: >>>>> On 08/31/2017 07:50 AM, PJ Welsh wrote: >>>>>> A recently created and fully functional CentOS

The xen_platform_pci xl configuration parameter currently has no effect on upstream QEMU; creation of the platform device is hardcoded. I have created a patch to QEMU to remove this hardcoded creation. This patch specifies the appropriate -device argument on the QEMU command line (and hence creates the device) only when xen_platform_pci is true. Signed-off-by: Paul Durrant