similar to: Xen drivers for virt-builder images

On Wed, Jun 11, 2014 at 8:34 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Wed, Jun 11, 2014 at 06:15:33PM +0100, George Dunlap wrote: >> I've just been playing around with virt-builder, and it seems like a >> pretty useful tool. However, it seems that in a number of the images, >> the initrd file is missing drivers for Xen virtual block and network

Hello everyone, On gio, 2014-06-12 at 08:20 +0100, Richard W.M. Jones wrote: > On Wed, Jun 11, 2014 at 10:02:22PM +0100, George Dunlap wrote: > > On Wed, Jun 11, 2014 at 8:34 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > > > Do you know what extra packages have to be installed or commands need > > > to be run to enable Xen drivers in Fedora? > > >

What is the best kernel to run? is it better to run 3.4.4 or one from xen git? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

From: Ben Cressey <bcressey@amazon.com> The commit "minios: refactor xenbus state machine" caused "/state" to be appended to the local value of nodename. Previously the nodename variable pointed to dev->nodename. The xenbus_rm() calls were not updated to reflect this change, and refer to paths that do not exist. For example, shutdown_blkfront() for vbd 2049 would

Hi Ian, Natasha and I are interested in helping with the io emulation work for fully virtualized HVM guests you mentioned in your March 12th email: http://lists.xensource.com/archives/html/xen-devel/2006-03/msg00394.html In the post, you mentioned the following tasks: - get minios running on x86_64 - port xenbus/netfront/blkfront to minios - compile qemu-dm into minios - redirect IO to qemu-dm

Hi Konrad, I just tried linux-3.4-rc0 (linus his tree, last commit f52b69f86e27903d6896ed5fa7cd280fec8de532) with 3 additional branches from your tree pulled on top of that: branch stable/for-ingo-3.4.v2 (required for dom0 to boot) branch stable/for-jens-3.4 branch stable/for-jens-3.4-bugfixes Hypervisor is xen-4.1.3-rc1-pre linux 3.3 vanilla works fine Booting dom0 goes fine, but

When xen_emul_unplug=never is specified on kernel command line reading files from /sys/hypervisor is broken (returns -EBUSY). It is caused by xen_bus dependency on platform_pci and platform_pci isn''t initialized when xen_emul_unplug=never is specified. Fix it by allowing platform_pcii to ignore xen_emul_unplug=never, and do not intialize xen_[blk|net]front instead. Signed-off-by: Igor

Hi all, I've been working on a set of easy-to-run benchmarks for hypervisor optimization called virtbench, and the latest commit adds Xen support. http://ozlabs.org/~rusty/virtbench http://ozlabs.org/~rusty/virtbench/?archive/tip.tar.bz2 >From the README: # Build the code make # Set the guest kernel location and maybe more vi ./SETTINGS # Run the benchmark (local mode)

Hi all, I've been working on a set of easy-to-run benchmarks for hypervisor optimization called virtbench, and the latest commit adds Xen support. http://ozlabs.org/~rusty/virtbench http://ozlabs.org/~rusty/virtbench/?archive/tip.tar.bz2 >From the README: # Build the code make # Set the guest kernel location and maybe more vi ./SETTINGS # Run the benchmark (local mode)

Hi all, I've been working on a set of easy-to-run benchmarks for hypervisor optimization called virtbench, and the latest commit adds Xen support. http://ozlabs.org/~rusty/virtbench http://ozlabs.org/~rusty/virtbench/?archive/tip.tar.bz2 >From the README: # Build the code make # Set the guest kernel location and maybe more vi ./SETTINGS # Run the benchmark (local mode)

hello, I know this not quite a xen problem but im sure a fair number of people are using debian for their dom0 and maybe have some insight into this. I have a large number of dom0''s running squeeze and for a long time i was hoping for pvhvm to make into the official debian xen packages and recently during some periodic updates I noticed pvhvm working after a kernel package update. Now

I have installed xen on a node and while starting up a guest while in the kernel boot I am experiencing a hold/pause. The kernel stops in the boot sequence still loading the kernel at: stdout ... [ 3240.186441] xencons_init: Initializing xen vfb; pass xencons=tty to prevent this [ 3240.186538] Xen virtual console successfully installed as xvc0 [ 3240.186598] Event-channel device installed. [

On Thu, Jun 12, 2014 at 4:13 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Thu, Jun 12, 2014 at 03:12:46PM +0100, Richard W.M. Jones wrote: >> >> Not quite as easy as I imagined. However by using the attached patch >> I have managed to add the two Xen drivers to the initramfs. (I >> haven't been able to test that it boots in Xen however) >>

Hi, Let me start a new thread for this. I contacted the Grub people, and they seem more interested in creating a native Xen port of Grub than piggybacking the Mini-OS environment usin kexec as I tried. But they need some documentation on the Xen "firmware" to assess the task at least. What could be given to them apart from hvc_xen.c and xen-blkfront.c in the Linux sources?

Hi, Let me start a new thread for this. I contacted the Grub people, and they seem more interested in creating a native Xen port of Grub than piggybacking the Mini-OS environment usin kexec as I tried. But they need some documentation on the Xen "firmware" to assess the task at least. What could be given to them apart from hvc_xen.c and xen-blkfront.c in the Linux sources?

Hi, I''m doing some test on a network 10 gb nics and xen with version 3.1 i''m measuring 2.5 gb/sec from domU to an external physical machine with iperf. switching to 3.2 has reduced the measured performance to 40-50 Mb/sec. did anything change in the network interface? can someone help me? thanks _______________________________________________ Xen-users mailing list

Hello everyone, I''m quite a newbie with Xen and I''m currently having an issue. I run Xen 4 on Debian Squeeze x64 and I''m trying to build an OpenFiler DomU from the Xen domU filesystem tarbal they provide (See http://www.openfiler.com/community/download/). I downloaded the tarball and run ''tar xzpvf /root/soft/openfiler-2.3-x86_64.tar.gz'' to extract

The user has the option of disabling the platform driver: 00:02.0 Unassigned class [ff80]: XenSource, Inc. Xen Platform Device (rev 01) which is used to unplug the emulated drivers (IDE, Realtek 8169, etc) and allow the PV drivers to take over. If the user wishes to disable that they can set: xen_platform_pci=0 (in the guest config file) or xen_emul_unplug=never (on the Linux command

Not quite as easy as I imagined. However by using the attached patch I have managed to add the two Xen drivers to the initramfs. (I haven't been able to test that it boots in Xen however) I'm just building an updated Fedora 20 image which I'll upload later today. Are there other guests that need to be updated in the same way? The RHEL 7 RC guest probably no longer works, since it

Dear List-Colleagues: I have been working on installing Xen on Suse 10.3 for some time now. I am green as grass - both a total newbie to Xen and a relative newbie to Linux (as well as a total newbie to SuSE). Currently, I am at the point that when I click on the Xen entry in my grub loader I see Xen starting and running through much of its early setup. Eventually, however, it quits on