similar to: booting from HVM (?pv?)

Aiming at a release later in October (before Xen Summit I would hope), I''d like to cut RC1 next week. Please indicate any bug fixes that so far may have been missed in the backports already done. Jan

i''m the Mageia Xen package maintainer, and a user reported that i had missing symbols in my ocaml bindings: https://bugs.mageia.org/show_bug.cgi?id=5199 i''m using Xen 4.2.1 and ocaml 3.12.1 the problem is that if you just to a simple hello world and you''re using certain bindings (eg: xeneventch): you get missing symbols. (others appear to be fine). I know next to

Hi, can anyone provide any pointers as to how to avoid this issue? A CentOS 5.3 domU on snv_111 dom0 is crashing on bott unless I remove /lib/modules/2.6.18-128.1.6.el5/kernel/drivers/xenpv_hvm dom0: haggis:~$ uname -a SunOS haggis 5.11 snv_111 i86pc i386 i86xpv Name: SUNWxvm Summary: Hypervisor Header Files Category: System/Virtualization State: Installed

Hello, I''m currently trying to understand some problems I had in the past with mixing look-back with blktap(2) for HV and PV domains. I''m stuck reading the source code, so I''d like to get some help from the list. Interrupt me if I got something fundamentally wrong in my understanding so far: 1. With pure-HV the domU gets an emulated IDE (or whatever) disk. The

Hello, While testing Fedora 16 Xen PVHVM guests I noticed the following problem: When starting F16 PVHVM guest I can see the vifX.0 and tapX.0 interfaces appear on dom0, but after the guest kernel (Linux 3.1.0) starts and loads PVHVM drivers the vif/tap interfaces disappear from dom0.. so the bridge in dom0 doesn''t have any vifs/taps connected to it anymore. Has anyone seen that

In the past I have used clonzilla under xen to backup windows domains. I just tried it and it will not work. this is xen 4.1.2 and clonzilla-live 1.2.10-14 the disk line is: disk = [ ''phy:/dev/xvg0/nfdlts-c,hda,w'', ''file:/extra/isoimages/clonzilla.iso,hdc:cdrom,r'' ] It boots cd OK. The problem is devices are xvda not hda and clonzilla is not happy with

I''m trying to add extra zvols to a Solaris10 DomU, sv_113 Dom0 I can use virsh attach-disk <name> <zvol> hdb --device phy to attach the zvol as c0d1. Replacing hdb by hdd gives me c1d1 but then that is it. Being able to attach several more zvols would be nice but even being able to get at c1d0 would be useful Am I missing something or can I only attach to hda/hdb/hdd?

Moving to public discussion... This was found with Xen hypervisor version supporting device unplugging and the domU kernel having net-/blkfront and pci platform built-in (or as module). The block device is defined as hda and the NIC type=ioemu (so theoretically guests without pv support would work, too). Since both drivers are present, the kernel tries to unplug the emulated devices and

Hi, I build Xen 4.1.1 on a Gentoo base dom0. Everything is working great. I tried one of Joseph Glanville''s PV-HVM image (debian6) and its working as it should. Now l''im trying to build a Gentoo based domU with then same specs as Joseph''s PV-HVM. I used a copy of the .cfg and adapted to my needs to make the gentoo work. when booting the minimal install image using

I am running Xen 4 and want users to be able to install arbitrary HVM images. We want both PV and emulated drivers to appear. The reason for this is for compatibility with images that were prepared for Xen 3.3, which assume emulated devices exist at boot time (particularly for running the boot loader). If I do not specify on the boot line xen_emul_unplug=never, then under some guest OS''s

>-----Original Message----- >From: xen-users-bounces@lists.xensource.com >[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Liang Yang >Sent: 2006年9月12日 8:57 >To: xen-users@lists.xensource.com >Subject: [Xen-users] Help: Xen HVM Domain can ONLY support four hard >drivesat most??? > >Hi, > >I have 5 SATA hard drives and I want to expose all these five

Hi, From cset 10921, ioemu: prefix is removed from disk config in /etc/xen/xmexample.hvm. Now HVM VBD driver is available, this thus raises a question: how would HVM domain know if one disk is a qemu-dm disk or a VBD disk? From current implementation, qemu-dm will recognize disk had, hdb, hdc, hdd, and VBD drive can recognize all disk (had~hdd, hde, hdf ...) . So the result is: qemu-dm will

Dom0 is Wheezy 64 bit with kernel 3.2.0-1-amd64 version 3.2.4-1, xen from xen-unstable.hg changeset 24858:a88ba599add1 plus these patch for not fail build: http://xen.1045712.n5.nabble.com/PATCH-0-of-2-rename-libxl-yajl-gen-alloc-td5469362.html And also this change for lib patch modified with multiarch support: vi config/StdGNU.mk LIBLEAFDIR_x86_64 ?= lib DomUs PV working, domUs with

Hi,All, I installed a guest os with full-virtualization and a local volume as the disk, now becuase of poor performance, I want to change the full-virtualization guest to para-virtualization, so I just changed the config file to boot the guest os with para-virtualization, but it fails to boot. but how can I convert the full-virtualization guest to para-virtualization without reinstall the os,on

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

Hello, We are planning to install a Windows 2008 DomU in one of our servers (SUSE 10/SP2, XEN 3.2). Does someone have some experience in installing 2008 ? Are they some know problems (and solutions if possible) to success in thre process. Here is the setup we will use for that DomU : ------------------------------------------------------------------- # SR3 MV9 name="SAP-IDES-ECC"

I know these are mostly gamers but they have a lot of experience doing PCI pass though: https://discord.gg/du9ecG I have found them extremely helpful in the past doing libvirt PCI passthough. *Paul O'Rorke* On 2020-02-05 10:13 a.m., Jim Fehlig wrote: > On 2/4/20 1:04 AM, Christoph wrote: >> this config does not work... why? > > Without more details, I don't know why

Hi. I want to create a full-virtualization xen VM with autoyast installation. how can i do that? and how does the configuration file to be configured? I use suse linux 11 SP2. looking forward your replay. Jing. -- View this message in context: http://xen.1045712.n5.nabble.com/how-to-create-a-full-virtualization-xen-VM-with-autoyast-tp5714901.html Sent from the Xen - User mailing

Hi, This issue only happens on my IA32E VMX domain. IA32 VMX domain is okay. I am trying VBD disk in IA32E VMX domain. I used following disk configuration to create an IA32E VMX domain. disk = [ ''file:/mnt/disk1.img,hda,w'', ''file:/mnt/disk2.img,hde,w'' ] After creating VMX, its keyboard can not be used properly. For example, if pressing

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