similar to: domUloader Vs pygrub

domUloader potentially makes my life a lot easier, but from experiments and looking at the code, it doesn''t seem like there is any way to pass kernel command line arguments with it. Am I just missing something? Thanks, John Byrne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, how can I install a openSuSE 10.3 PV-guest on a LVM-drive of a openSuSE 10.3 host with Xen 3.10? On 10.2 with Xen 3.0.3 the openSuSE-YaST-module for managing VMs could install the system also on block-devices, unfortunately this is not possible anymore with OSS 10.3 :-( What I have tried: - I created two LVM-partitions, one for "/" one for swap. - Installing an OSS 10.2 PV-guest

Fix for pygrub path on Solaris. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/tools/python/xen/xend/XendDomainInfo.py b/tools/python/xen/xend/XendDomainInfo.py --- a/tools/python/xen/xend/XendDomainInfo.py +++ b/tools/python/xen/xend/XendDomainInfo.py @@ -37,7 +37,7 @@ from xen.util.blkif import blkdev_uname_ from xen.util.blkif import blkdev_uname_to_file from xen.util

Hi all, did somebody successfuly export ISDN Cards to DomU? I want to have 2 ISDN Cards in DomU (for Asterisk with mISDN) lspci -vt -[0000:00]-+-00.0 nVidia Corporation MCP55 Memory Controller +-01.0 nVidia Corporation MCP55 LPC Bridge ... +-05.1 nVidia Corporation MCP55 SATA Controller +-06.0-[0000:01]--+-00.0 Cologne Chip Designs GmbH ISDN

I have a sles10 domU running on a sles11 dom0. xen is version 3.4. We''re trying to pass through a scsi card to the domU. We assign the domU the scsi card through virt manager. When we try to boot the domU it won''t boot. We need to update fstab and menu.lst, but we need to boot with the hardware attached to see how it''s being seen by the domU. On a physical machine we

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1346945306 -7200 # Node ID 8a2eef481d3ab3ca5692dd0083c95cf314fe1da3 # Parent 19d367bf07b7687b831c212a57a70e73ea14d3b7 pygrub: always append --args If a bootloader entry in menu.lst has no additional kernel command line options listed and the domU.cfg has ''bootargs="--args=something"'' the additional

Hi, On Mon, Jan 16, 2006 at 11:26:09PM +0000, Kurt Garloff wrote: > (1) A patch to xend/XenDomainInfo.py, xend/XenBootloader.py and > xm/create.py, making sure that all the needed info is passed > to the bootloader and also stored for reuse on rebooting. Some more remarks: XendBootloader.py misses a timeout and waits for the bootloader to finish forever; I just made a TODO.

Hi, I have searched the question which I am asking.But if some one has mentioned on their blog or link some where they have mentioned as how they installed CentOS as DomU on Debian Lenny (dom0)running xen-3.2.1 and I should have a look Then please share it here. -- Tapas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hello, I have a small Xen farm of 8 dom0 servers with 64 virtual machines running para-virtualized and this has been working great. Unfortunately, I''ve hit a limit: my iSCSI hardware supports only 512 concurrent connections and so I''m pretty much at the limit. (Wish I would have seen that problem sooner!) Of course, 87% of those connections are idle-- but necessary because I

Hi: Reading Red Hat''s Website and a printed manual of RH184 (Red Hat Virtualization course) I see that RHEL 5 only supports RHEL 4.5 and RHEL 5 as paravirtualized guests. So I asume this is the same situation for CentOS 5, right? What''s the dependency between Xen versions for paravirtualized guests? I ask this questions because I got this experiences: 1. Running CentOS 5 as

I don''t think that modelling domUloader (or pygrub, for that matter) is going to be optional for VSM 1. Do the CIM providers have any plans for this? Thanks. Andrew _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi: Reading Red Hat's Website and a printed manual of RH184 (Red Hat Virtualization course) I see that RHEL 5 only supports RHEL 4.5 and RHEL 5 as paravirtualized guests. So I asume this is the same situation for CentOS 5, right? What's the dependency between Xen versions for paravirtualized guests? I ask this questions because I got this experiences: 1. Running CentOS 5 as Dom0 - RHEL

I am trying to extract and combine the various pieces of information found in [1] and its sub-pages and the Xen in-tree documentation in order to make xen boot (potentially non-smp without some later changes). But since I am not familiar enough with Arm I think I am stuck doing something wrong. I compiled the hypervisor with debug and early printk for midway and use the xen.bin file (I could get

Hi, Now that the Arndale board is supported in upstream Xen I don''t get any output on the serial console. I followed the instructions on the wiki with no luck: The xen repository I''m using is: git://xenbits.xen.org/xen.git last commit: 61c6dfce3296da2643c4c4f90eaab6fa3c1cf8b3 The linux repository is: git://xenbits.xen.org/people/julieng/linux-arm.git last commit:

Note: I could simply direct boot the appropriate kernel/initrd to get the alpha1 installation going as always done in the past, but I think this should work. The Debian alpha 1 installer page says it should. Details $ sudo xm create -c wheezytest.cfg Using config file "./wheezytest.cfg". Error: Boot loader didn''t return any data! direct pygrub test run: # pygrub

Hi, I have a Xen server running OpenSuSE 10.2, with Xen version 3.0.3_11774. It''s happily hosting two DomU''s running the same OS / kernel. Now I tried to create a new DomU running a newer OS - OpenSuSE 11.1. It comes with Xen version 3.3.1_18494_03. Unfortunately for me, it doesn''t work - this is what I get: > xen1:/etc/xen/vm # xm create NEW > Using config file

Hi, I have three Xen hosts running Xen 4.0.2 (OpenSuSE 11.4 based). I also have one ''NFS'' server with an NFS export holding VM images and configuration files. Each host has a dedicated LAN link directly to the NFS server. I have another separated NFS export for VM locking (but I had the same issues before). When I attempt to live migrate a VM, it *looks''*like

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU

Hi Nik, Flushing MDB can only be done when we are managing it per station not per port. For that we need to have MCAST_TO_UCAST, EHT and FAST_LEAVE. Here one more point is - some vendors may offload MCAST_TO_UCAST conversion in their own FW to reduce CPU. So, the best way is to have MCAST_TO_UCAST enabled and MDB will become per station, so we can delete MDB on disconnect. Shall, I create one