xen February 2008

xen@lists.fedoraproject.org

30 participants
21 discussions

xen vif rate limit.
by itamar 15 Feb '08

15 Feb '08

anyone know how to put xen vif rate limit to work ? http://xenbits.xensource.com/xen-unstable.hg?rev/dadadf9aeee7 -------------------- Itamar Reis Peixoto e-mail/msn: itamar(a)ispbrasil.com.br skype: itamarjp icq: 81053601 +55 11 4063 5033

2 1

Virt-Clone Fedora8/Xen 3.1
by Petrus B. van Bork 13 Feb '08

13 Feb '08

Dear List Colleagues: Wow! So much traffic on these neat but mysterious tools. I used the 'touch' workaround today and got virt-clone working - thank you both to christf1 and to Cole! The relief was literally indescribable when it ran (...pressure, what pressure?!) I have been in touch with Cole and he informs me that the latest and greatest version of virt-clone can be gotten from the virt-manager devel repository and that this version does not need the 'touch' work-around. For those of you who have not used virt-clone - when it finally works it is really great and as cloning is of vital importance to the project I am working on, many thanks to all who contribute to the virt-manager tools! In a previous post, on this thread today, it was mentioned that some of my results were unduplicable on the usage of switches such as "-f" and "--file" - interestingly, yesterday, the same day I experienced those problems I was unable to duplicate some of them, myself, when I went back to them. I do not know why this was/is the case or what happened, there the results I posted were copied from actual terminal windows where they had run. I am willing to run a set of tests against my machine with virt-clone and send them off to anyone interested in its functionality or lack thereof. I think that this is an important tool and I am willing to do whatever I can to help develop it. I have certainly found it to be 'touchy.' Cole has asked me, as a repository using newbie - who had a lack of success gaining access - to report on my experience of trying to get stuff out of the repository and I will do so, shortly, and report my experience so others can benefit from my efforts to gain competence and my report on how this is done - some steps do seem to be skipped in the instructions on that site! Thanks, again to Cole for pointers on what was going wrong for me, there. It was great to see my questions about LVM and virt-clone answered today, before I could even ask them myself! Best, Petrus fedora-xen-request(a)redhat.com wrote: > Send Fedora-xen mailing list submissions to > fedora-xen(a)redhat.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/fedora-xen > or, via email, send a message with subject or body 'help' to > fedora-xen-request(a)redhat.com > > You can reach the person managing the list at > fedora-xen-owner(a)redhat.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Fedora-xen digest..." > > > Today's Topics: > > 1. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Cole Robinson) > 2. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Daniel P. Berrange) > 3. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Daniel P. Berrange) > 4. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Asrai khn) > 5. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Daniel P. Berrange) > 6. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Cole Robinson) > 7. Xen packages for Vulnerability to CVE-2008-0600 (Russell McOrmond) > 8. Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be > an int or a float. (Christopher Fournier) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 12 Feb 2008 12:30:21 -0500 > From: Cole Robinson <crobinso(a)redhat.com> > Subject: Re: [Fedora-xen] virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk > size must be an int or a float. > To: christf1 <christf1(a)nortel.com> > Cc: fedora-xen(a)redhat.com > Message-ID: <47B1D7AD.3040102(a)redhat.com> > Content-Type: text/plain; charset=us-ascii > > christf1 wrote: > >> I tried the latest dev stream, and continued to have the problem. The quick >> fix is to simply touch the target file before launching 'virt-clone' >> >> touch <dir_to_VMs>/newvm.img >> virt-clone -o existing_vm -n new_vm -o <dir_to_VMs>/newvm.img >> >> Cheers! >> > > I'm not seeing this: > > hg clone http://hg.et.redhat.com/virt/applications/virtinst--devel > cd virtinst--devel > ./virt-clone -o xen-pv -n clone-pv -f /idontexist.img > > starts working, for an existing turned off guest named xen-pv on f8. > Is there anything you are doing differently? If so, can you detail it > and post the complete error message? > > Thanks, > Cole > > > > ------------------------------ > > Message: 2 > Date: Tue, 12 Feb 2008 17:35:27 +0000 > From: "Daniel P. Berrange" <berrange(a)redhat.com> > Subject: Re: [Fedora-xen] virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk > size must be an int or a float. > To: Asrai khn <asraikhn(a)gmail.com> > Cc: fedora-xen(a)redhat.com > Message-ID: <20080212173527.GK25829(a)redhat.com> > Content-Type: text/plain; charset=us-ascii > > On Tue, Feb 12, 2008 at 09:49:55PM +0500, Asrai khn wrote: > >> On Feb 12, 2008 8:24 PM, christf1 <christf1(a)nortel.com> wrote: >> >> >>> I tried the latest dev stream, and continued to have the problem. The >>> quick >>> fix is to simply touch the target file before launching 'virt-clone' >>> >>> touch <dir_to_VMs>/newvm.img >>> virt-clone -o existing_vm -n new_vm -o <dir_to_VMs>/newvm.img >>> >>> >> hi, >> >> i wonders virt-clone will work when one is doing LVM for domUs fro example >> here is mine virutal config file >> > > It won't care what type of storage the original VM is using - it'll > simply read the data off the original disk whether its a file or > block device or LVM vol. > > If you want to use LVM volumes in the destination VM, then you currently > need to manually create the LVM volume ahead of time - virt-clone itself > will not create new LVM volumes for you. This is in the future feature > list though, once libvirt storage management APIs are merged. > > Dan. >

1 0

Xen packages for Vulnerability to CVE-2008-0600
by Russell McOrmond 12 Feb '08

12 Feb '08

I suspect people are tracking this, and want to know about the process of the xen kernels. https://bugzilla.redhat.com/show_bug.cgi?id=432517 I tested right away, and the exploit works under Xen. -- Russell McOrmond, Internet Consultant: <http://www.flora.ca/> Please help us tell the Canadian Parliament to protect our property rights as owners of Information Technology. Sign the petition! http://www.digital-copyright.ca/petition/ict/ "The government, lobbied by legacy copyright holders and hardware manufacturers, can pry my camcorder, computer, home theatre, or portable media player from my cold dead hands!"

3 4

virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be an int or a float.
by Petrus B. van Bork 12 Feb '08

12 Feb '08

Dear Fellow-List Members: I am running the latest, fully updated, F8 Xen kernel with F8, updated DomU on top. I need to clone that DomU - indeed, a need to do rather a lot of cloning to fulfill our project's mission. I tried to run virt-clone but it will not perform as per the man's examples and despite hours of searching on the 'net I cannot find any reason why not. Here is the example from the man: -EXAMPLES - Clone the guest called "demo" which has a single disk to copy - - # virt-clone \ - --original demo \ - --name newdemo \ - --file /var/lib/xen/images/newdemo.img What I have tried: Where: HanoverGuest = name of functioning DomU (shut off for cloning...) KohaHanoverConf_Gold = name of new DomU New File Image: KohaHanoverConf_Gold.dsk Here is the command sequence I issue: #virt-clone --original HanoverGuest --name KohaHanoverConf_Gold --file /var/lib/xen/images/KohaHanoverConf_Gold.dsk -d I get: Fri, 08 Feb 2008 14:57:31 DEBUG start clone with HV Xen Fri, ditto DEBUG clone device list: ['/var/lib/xen/images/KohaHanoverConf_Gold.dsk'] Fri, ditto DEBUG clone device size: [1048570000L] Fri, ditto DEBUG clone device type: [True] ERROR: Disk size must an int or a float. What would you like to use as the disk (path)? ...I have tried many, many variants with no more luck and usually with the same error message. I have tried to run it without creating a disk image myself, with one of 0 bytes size and, as can be seen, one of 10gig size. No joy! Furthermore, I cannot find any information on the net on what those debug messages mean so I have little to judge what is going on. Apparently the ERROR msg. itself,likely, is generated by: @@ -83,9 +77,13 @@ class VirtualDisk: if size is None and not os.path.exists(self.path): raise ValueError, \ _("A size must be provided for non-existent disks") - if size is not None and size <= 0: + if size is not None and \ + (__builtin__.type(size) is not __builtin__.type(1) and \ + __builtin__.type(size) is not __builtin__.type(1.0)): + raise ValueError, _("Disk size must be an int or a float.") ...which comes from a September 28, 2007 patch authored by Cole Robinson for virtinst validation fixes, found here: http://www.spinics.net/linux/fedora/et-mgmt-tools/msg01760.html ...alas, without knowing all the code I am not sure what is going on. It seems to suggest that somehow the diskimage file is not recognized as a built in data type or something similar - but there seem to be no commands available in virt-clone to set the datatype, adapt for the date type or even tell a user what datatype they need. Since I am a relative Linux newbie I may very well be making a classic 'flat-forehead' error - but what? I tried to run virt-clone as a basic interactive tool - the man states that it can run interactively with no command line switches. Here is what happens: #virt-clone ..and I get... ERROR: A new disk image file for the clone guest is required and then it goes back to the prompt. Not helpful! I very badly need to clone DomU's effectively during our development process - and afterwards and I would be excruciatingly grateful for any help anyone can provide! Regards, Petrus

5 10

Re: virt-clone/Fedora 8/Xen3.1 ... ERROR: Disk size must be an int or a float.
by Petrus B. van Bork 12 Feb '08

12 Feb '08

Dear Cole & Fellow List Members: Had some 'tap-dance' at the virt-manager site (which I will deal with later) so I patched CloneManager.py, on my machine, as per the first link Cole, so kindly, provided. I deleted the one line shown in red with a minus, and added the following line, in green, with a plus (...just for the record). This resulted in virt-clone running - but very touchy. After the change virt-clone would still not run interactively - it would ask for a disk and go back to the prompt and it would not run with a full string of command line switches (...as illustrated in my last email and Cole's reply). It would, however, run: #virt-clone -f foo.dsk ...at that point it would ask for several things, including the original clone's UUID or name (...this for those trying it for the first time, seems to need the Virtual Machine Manager running and connected to the Xen hypervisor but, of course, with the DomU to be cloned "Shutoff"). When the cloning began it started with: libvir: Xen Daemon error : GET operation failed: libvir: Xen Daemon error : GET operation failed: ...then I got - to my relief... Cloning from /home/xenguest/hanoverguest.dsk to KohaHanoverConf_Gold.dsk ...this worked...sort of...no more error messages BUT the result I ended up with was: * an .sxp file that did not have a disk path to the .dsk, * and it was missing a number of other things as well such as the reference to localhost:5900 * tried running "xm create" But...xm create would not run command xm create -c /... path to UUID/config.sxp resulted in: Error: Errors were found at line 5 while processing /var/lib/xend/domains/...UUID.../config.sxp: (VCPUs_live 1) - alas, this was the 100% identical line from the config.sxp that it was lifted from (...the running DomU). * virsh didn't like the .sxp either and I was not sure how to create an xml for it to read, just don't know enough and not enough documentation available. At the end of the day - another day spent fruitlessly trying, trying, trying... I am a little further than yesterday but I am no further than I was this morning. Still completely unable to get the new cloned DomU to run. Using #xm start <domainName> changes the status to 'running' in Virtual Machine Manager but with 0 CPU usage and RAM usage. Does anyone have any idea what is wrong? I am still in the dark and would still be most grateful for any more illumination on this! Best, P. ------------------------------------------- Other Issues with virt-clone after fix, this morning: #virt-clone ...result: ERROR: A new disk image file for the cloned guest is required, followed by a command prompt... [...no interactive functionality available, as yet...] #virt-clone -f testdisk.dsk ..result "What is the name or uuid of the original virtual machine? [...which is the correct response but you have not fed the script a path and will result in a config.sxp with no path for the disk!] #virt-clone -f /var/lib/xen/images/testdisk.dsk ...result: ERROR: Disk size must be an in or a float. What would you like to use as the disk path? [...problematic...can't seem to use '-f' switch, as per man syntax, unless I have misread the man....) #virt-clone --file /var/lib/xen/images/testdisk.dsk ...result: "What is the name or uuid of the original virtual machine? So...my question to Cole: "Does the version from the virtual manager site, as per your second provided link, fix the above as well? Or, not yet?" Obviously, if the material at the repository is better/later, I will use it, once I figure out "hg" - which is 'unknown command' on my system, presently.

2 1

newbie's request for info
by Bob Jones 12 Feb '08

12 Feb '08

Greetings list. I have what might be a strange request but will ask it anyway -- but first some background info. I am new to Xen, having just started using it on Fedora 8 within the last month or 2 on my server (homebuilt AMD x2 6400+ on Asus M2N-E Sli board and 8GB DDR2-800 memory on software RAID5 1TB). Having great sucess on the server running 3 Windows VM's (XP Pro, 2000 server with SQL 2000, and SBS2003 server), I wanted to setup my laptop similarly for client demo purposes. The laptop I am using is a new Dell Latitude D531 running a Turion 64x2 TL-60 with 4GB memory and 100GB drive. My problem is this -- booting into the xen kernel works fine (well, sound doesnt work and won't work with less than 2.6.23 kernel, but thats no big deal). I can create a HVM using virt-manager, allocating memory, vcpu's, etc. etc. However, upon booting the VM the entire laptop locks up (drive activity immediately stops, keyboard and mouse are completely unresponsive). This forces a hard shutdown. Upon starting back up the DomU VM is not listed and when I attempt to create a new fully virtualized VM (HVM?), I am told that virtualization support is present in the CPU but not enabled in the BIOS (but it IS .. verified many times). I suspect that there is a bug in the BIOS that is showing virtualization enabled when in fact it is not. My questions are: 1) Has anyone on this list seen the same symptoms and if so, did you find a workaround? 2) How do I go about logging and checking what is happening when it locks up so I can take that to Dell and file a bug report? Thanks in advance for all pointers. Bob J

2 1

How is network bridging for Xen handled in F7?
by Christian Reiter 06 Feb '08

06 Feb '08

Hi! Can anybody tell me where i can find docs about handling network bridges for xen domUs in Fedora 7? Something changed since FC6, so i cannot figure out how to create simple bridges without dhcp for my xen domUs. All what i want is: xenbrINTERNET should bridge to eth1 xenbrLAN should bridge to eth0 eth0 and eth1 of my dom0 should also have an IP Address. I do not want routing or nat for my domUs. Thanks! regards, christian

3 7

Two NICs
by Augusto Castelan Carlson 04 Feb '08

04 Feb '08

Hello! I'm running Fedora 8 with two network interfaces. I will have 2 guests. On guest and the host (dom0) need to be connected through eth0 and the other guest through eth1. When I try to create a guest with virt-manager, in the network options for "shared physical device", I have "peth0 (bridged eth0)" and "eth1 (not bridged)". Both the guest and the host will be connected to the same network: Dom0: 172.16.1.2/24 Dom1: 172.16.1.3/24 Dom2: 172.16.1.4/24 What I need to change in the xen network scripts to make eth1 to be a bridged interface? How I set Dom0 be connected through eth0? Thanks in advance. Regards, -- Augusto Castelan Carlson

1 0

no xend on f8 x64
by Huub 04 Feb '08

04 Feb '08

Hi, On my AMD64, running F8, I just installed the virtualization package with yum and rebooted into the Xen kernel. But I can't create a new virtual machine. I read that the xend daemon should be running for that, but I can't find it. Should it be installed or how should I do that? Thanks.

2 1

what steps are required to manually move a PV domU from one machine to another?
by fcxen user 04 Feb '08

04 Feb '08

Hi, I am having a problem - I created a lovely bunch of F8 x86_64 domUs and I want to create a vast clone army of them using different dom0s. The problem is, I do: fm # virt-install c1 (no graphics) fm # xm start c1 fm # xm shutdown c1 [ ok I don't _always_ shut it down :P ] fm # scp -p c1.img othermachine:/var/lib/xen/images then: om1 # virsh define c1.xml om1 # xm start c1 and hangville, if I do: om1 # xmstart c1 -c it seems to hang just after the grub boot menu. I assume I am "doing it wrong" but this worked great in the past. I've been selling F8/Xen as the answer to all problems, any help would be appreciated. VMWare looms like a line of dark clouds on the horizon... Thanks.

4 4

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen February 2008