similar to: xennet and xenblk

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

Hi List, I''d compiled Xen-3.0.3-testing (changeset 11740) on Suse 10.0 Enterprise Server. The compilation succeeded without any errors but the mkinitrd command fails(???) The initrd is being created but when loading the xen kernel, I get the following message repeatedly: "azx_get_reponse() timeout" after pressing ^c the computer continue to run... Then, when I start a gnome

Thanks you all guys. I am able to create the RHEL5 PVM on RHEL5 host successfully. Only thing that i need to add is /mnt/etc/fstab in inintrd command and preload to both the fronthend drivers. As blow. # mount /home/disk /mnt # mkinirtd /boot//boot/initrd-2.6.18-8.el5xenU.img 2.6.18-8.el5xen --fstab /mnt/ etc/fstab --with xenblk --with xennet --preload xenblk --preload xennet Thanks a lot,

Hi everyone! I''m sorry, I think I''m missing something obvious, but I can''t figure out what :/ I have a CentOS 5.2 dom0 on a HP Proliant ML150 with - kernel 2.6.18-92.1.18.el5xen - Xen 3.2.1 and I''m trying to boot a domU installation from the CentOS DVD. I made a custom initrd with mkinitrd /boot/initrd-vm `uname -r` --with xenblk --with xennet --preload

Hi all, This is my first post in the list. Nowadays I am starting with xen due a work task, for some of you my problem should be something very basic but for me it is taking long hours doing research on the issue and trying different things. What I have is a Xen image already built and what I want to do is just play it and make it accessible by the network. I can play it, that is not a problem at

I followed the book called "Professional Xen Virtualization" written by William von Hagen,and published by Wiley Publishing,Inc. Here are some configuration files: #cat /xen/ubuntu/ubuntu.xen3.cfg kernel = "/boot/vmlinuz-2.6.18-128.1.16.el5xen" ramdisk = "/boot/initrd-2.6.18-128.1.16.el5xen-no-scsi.img" memory = "512" name = "Ubuntu804" vif =

I have a CentOS 5.1 dom0 running on a machine with two cores and 4gb of memory. It runs three 4.6 domUs and one 5.1 domU. Just out of the blue the other night all the 4.6 domUs crashed, but the dom0 stayed up. I ran xm console (domU-name) and got the Oops information below. I didn't get anything from the 5.1 domU. I think it had been rebooted a few days before and hadn't come up

I have a CentOS 5.1 dom0 running on a machine with two cores and 4gb of memory. It runs three 4.6 domUs and one 5.1 domU. Just out of the blue the other night all the 4.6 domUs crashed, but the dom0 stayed up. I ran xm console (domU-name) and got the Oops information below. I didn't get anything from the 5.1 domU. I think it had been rebooted a few days before and hadn't come up

I saw some really bad things happening on our production servers. First dom0: Ubuntu xen1 2.6.24-24-xen Xen 3.4.0 compiled from source. I don''t remember exactly what GPLPV version was installed but I know for sure from early 10.x series. domU: Windows Server 2008 64-bit (Test mode enabled) Second dom0 has almost identical setup, thou on different hardware. When I start copying large

Hi there, After updating a server from CentOS 5.3 to 5.4 my Xen pci-passthru setup has some troubles. The server has two NICs, one used by dom0 and the other assigned to a domU and one SCSI controler assigned to another domU. It has been working fine since CentOS 5.1, when I did the initial setup. After upgrading to 5.4, I get this error when starting the domU with one of the NICs assigned:

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

Hi all, when I try to build an initial ramdisk with the option --with=xennet, I get the following error No module xennet found for kernel 2.6.18.8-xen I looked at the /lib/modules/2.6.18.8-xen/kernel/drivers/xen and there is no xennet module over there, which causes the problem. How can I get the xennet module? Thanks, Luca _______________________________________________ Xen-users

On Fri, 2014-12-19 at 16:21 +1300, Peter wrote: > On 12/19/2014 03:52 PM, Dave Stevens wrote: > > what you say makes sense, but leaves me with two problems - what to do > > and how did this happen? > > You never mentioned if this is for a dom0 or domu, if it's a domu is it > a pv or hvm domain and does it use pvgrub, pygrub or does it boot > directly to a kernel on

Hello, we have a bug on any xen kernel > 3.4 like this: kernel BUG at /home/abuild/rpmbuild/BUILD/kernel- xen-3.7.9/linux-3.7/fs/buffer.c:2952! [ 628.054552] invalid opcode: 0000 [#1] SMP [ 628.054557] Modules linked in: bridge stp llc iptable_filter ip_tables x_tables nbd blktap2 pciback usbbk xen_scsibk openvswitch blkbk blkback_pagemap netbk xenbus_be gntdev evtchn ocfs2_dlmfs

https://bugzilla.mindrot.org/show_bug.cgi?id=2538 Bug ID: 2538 Summary: openssh v7 config parse regression Product: Portable OpenSSH Version: 7.1p1 Hardware: Other OS: All Status: NEW Severity: normal Priority: P5 Component: ssh Assignee: unassigned-bugs at mindrot.org

Hi Shimizu --- Shimizu Miki <> schrieb: > Hello, > > Doesn''t the vircual nic work at all? After the hint of Timo (http://lists.xensource.com/archives/html/xen-users/2006-05/msg00091.html) I got the virtual xen network card show up in yast. However, when I configured it, yast came up with an error message that''no driver module for the device found''

Updates commit 7eb219d1938968c4d6bffda038aaace936f7efbf. --- v2v/linux_kernels.ml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/v2v/linux_kernels.ml b/v2v/linux_kernels.ml index 2efd070a6..9fbc43b60 100644 --- a/v2v/linux_kernels.ml +++ b/v2v/linux_kernels.ml @@ -182,7 +182,8 @@ let detect_kernels (g : G.guestfs) inspect family bootloader = List.mem what

I am having an issue getting a DomU to boot properly. There is never any indication of a stop error or kernel panic, it simply hangs after "Starting crond [ OK ]" and never continues. I''ve included my mkinitrd and output from xm create... please help! ##### XENBUS errors ##### XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2050

Quoting Ulf Volmer <u.volmer at u-v.de>: > On 12/18/2014 08:11 PM, Dave Stevens wrote: >> ran routine updates on the lernel this morning and got this: >> >> WARNING: No module xenblk found for kernel 2.6.18-400.1.1.el5, >> continuing anyway > > i'm not sure that i can help you, i have currently no centos5 vm on xen. > > But i guess the warning is

On 12/18/2014 08:11 PM, Dave Stevens wrote: > ran routine updates on the lernel this morning and got this: > > WARNING: No module xenblk found for kernel 2.6.18-400.1.1.el5, > continuing anyway i'm not sure that i can help you, i have currently no centos5 vm on xen. But i guess the warning is from the normal, not xen enabled kernel. Does /boot/vmlinuz-2.6.18-400.1.1.el5xen