Hi *, I was looking at our local hardware e-shop for CPUs supporting HVM. I would like to experiment with Xen and join the development. AFAIK the cheapest CPU supporting HVM is Athlon64 3800+ for AM2. No particular support from motherboard (and chipset) needed. 1) Can somebody confirm this? 2) According to my observations the solution from Intel is a bit more needy (the better chipset, only dual core CPUs support VT). Am I right? 3) What motherboard with AM2 is good according to your observation? Thank you -- Tomas Kouba _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Tomas Kouba > Sent: 17 July 2006 14:50 > To: xen-users@lists.xensource.com > Subject: [Xen-users] Cheap HVM support > > Hi *, > I was looking at our local hardware e-shop for CPUs > supporting HVM. I would > like to experiment with Xen and join the development. AFAIK > the cheapest > CPU supporting HVM is Athlon64 3800+ for AM2. No particular > support from > motherboard (and chipset) needed. > 1) Can somebody confirm this?Yes, any Rev F (which means AM2) processor except Semperon will have SVM in it. I''m not sure which models are the least expensive, as I don''t really have to pay for mine ;-)> 2) According to my observations the solution from Intel is a > bit more needy > (the better chipset, only dual core CPUs support VT). Am I right?Can''t answer this one...> 3) What motherboard with AM2 is good according to your observation?Sorry, can''t help here, other than saying that good brands are usually the way to go, so Gigabyte, MSI, Tyan and such are probably better than the "noname" companies... -- Mats _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Monday 17 July 2006 10:49 am, Tomas Kouba wrote:> Hi *, > I was looking at our local hardware e-shop for CPUs supporting HVM. I would > like to experiment with Xen and join the development. AFAIK the cheapest > CPU supporting HVM is Athlon64 3800+ for AM2. No particular support from > motherboard (and chipset) needed. > 1) Can somebody confirm this?I have it working with an Athlon64 3200+. Anything AM2 except for Sempron will work, apparently.> 2) According to my observations the solution from Intel is a bit more needy > (the better chipset, only dual core CPUs support VT). Am I right?I have no first-hand experience with Intel''s VT myself, but other posts indicate that you''re correct here.> 3) What motherboard with AM2 is good according to your observation?I''m using an ASUS M2NPV-VM, which I am very impressed with, so far. -- James Oakley Engineering - SolutionInc Ltd. joakley@solutioninc.com http://www.solutioninc.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > 2) According to my observations the solution from Intel is a bit more needy > > (the better chipset, only dual core CPUs support VT). Am I right?It is needy in the sense that the chipset and bios must support VT.. but dual-core is not necessarily a requirement. The Intel Core Solo chips support VT -- the Mac Mini with Core Solo supports VT. However, this is the only intel processor I''m aware of that supports VT. -- Eric Windisch <lists@bwbohh.net> _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 7/17/06, Eric Windisch <lists@bwbohh.net> wrote:> > > 2) According to my observations the solution from Intel is a bit more needy > > > (the better chipset, only dual core CPUs support VT). Am I right? > > It is needy in the sense that the chipset and bios must support VT.. but > dual-core is not necessarily a requirement. The Intel Core Solo chips > support VT -- the Mac Mini with Core Solo supports VT. However, this is > the only intel processor I''m aware of that supports VT. > > -- > Eric Windisch <lists@bwbohh.net>You can see for yourself at http://www.intel.com/products/processor_number/proc_info_table.pdf I just did a quick scan and saw 4 models that said dual core - no, vt - yes. Greg _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Steve Kemp
2006-Jul-17 20:47 UTC
Re: [Xen-users] Communicating with VM before Network is configured.
Perhaps this will help?
1. Copy a script to do the setup into your new images then
boot up the new system with an extra command line argument
"init=/path/to/script".
That can read kernel command line arguments to setup things,
etc.
2. At the end of your script run "reboot", or from a shell run
"xm reboot name"
3. Run "xm create ..." to boot up the image once it has been
configured.
Failing that why not just try DHCP ?
Steve
--
http://xen-hosting.org/
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Steve Kemp
2006-Jul-17 21:00 UTC
Re: [Xen-users] Re: Communicating with VM before Network is configured.
On Tue, Jul 18, 2006 at 02:22:40AM -0400, Ligesh wrote:> How do we do the same on a windows VM? On a remote hosting setup, it is always preferable to assign static ips to the virtual machines. DHCP is cumbersome method to manage ip addresses.Sorry I must have missed the reference to Windows. I imagine you could write a small script in VBScrip/JScript and place it in the startup directory - or add a registry key to make it auto-run once. It has been a few years since I had to do that kind of thing on Windows, but I think the principle is sound. Bootup the machine once with the script to do the magic, then reboot it afterwards. I guess you''d need to organise yourself, so for example, you could have a range of IPs to be tested and do something like this: base=192.168.1.100 while( 1 ) { if ( ping( $base ) ) { # Address is "live" base += 1; (Note you can''t do that really!) } else { # Found an unallocated IP setupIP here reboot } } I''d recommend you look at AutoIT for your scripting language if you''ve not got a personal preference. Very nice to use, and free. (Albeit not "free".) Steve -- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jerry Amundson
2006-Jul-17 21:17 UTC
Re: [Xen-users] Re: Communicating with VM before Network is configured.
On Tue July 18 2006 01:22, Ligesh wrote:> How do we do the same on a windows VM? On a remote hosting setup, it > is always preferable to assign static ips to the virtual machines. > DHCP is cumbersome method to manage ip addresses.How DHCP got so darn popular, I''ll never understand... ;-) Off the top of my head, there are a few cases to not use DHCP: 1. It''s a DNS server. 2. It has a brain-damaged dhcp client that won''t update DNS. 3. It''s on a small and/or virtual net with no DHCP server. Otherwise, I don''t see how you could find it "cumbersome"... jerry _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
tbrown@baremetal.com
2006-Jul-17 22:16 UTC
Re: [Xen-users] Re: Communicating with VM before Network is configured.
On Tue, 18 Jul 2006, Ligesh wrote:> I have a specific requirement to assign static ips to a VM. My question > is: is there a way to accomplish this. In Vmware you can do it by > defining a variable machine.id in the config file variable, which can be > accessed from inside VM using the the vmware-guestd on linux or > vmwareservice.exe on linux. This is generally a good idea, and I want to > know if Xen supports something like this, or what I should do to get > this implemented etc etc.I expect vmware does this by controlling both the MAC address and the DHCP server, that certainly seems like the simplest way ... you could impliment the same functionality yourself. Failing that, you can pass info to the domU kernel "command line" the same way the root device is passed in. I use this method with my initrd to pass in nbd boot parameters: extra="NBDHOST=65.39.183.43 NBDPORT=8001 ip=192.168.2.254:1.1.1.1:192.168.2.86:255.255.255.0" for an init script it''s really simple, as those NBD* parms are already loaded into environment variables :) ... but in the more general case you would need to parse them out of /proc/cmdline I don''t believe xen has any specific methods for passing config parameters to the domU, but I''m no expert. Oh, and looking back at the subject line... those ip config parameters might be of use to you... ip=192... You''ll need a kernel with autoconfig enabled. -Tom _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
John McCullough
2006-Jul-17 22:25 UTC
Re: [Xen-users] Re: Communicating with VM before Network is configured.
On Mon, Jul 17, 2006 at 03:16:52PM -0700, tbrown@baremetal.com wrote:> On Tue, 18 Jul 2006, Ligesh wrote: > > > I have a specific requirement to assign static ips to a VM. My question > > is: is there a way to accomplish this. In Vmware you can do it by > > defining a variable machine.id in the config file variable, which can be > > accessed from inside VM using the the vmware-guestd on linux or > > vmwareservice.exe on linux. This is generally a good idea, and I want to > > know if Xen supports something like this, or what I should do to get > > this implemented etc etc. > > I expect vmware does this by controlling both the MAC address and the DHCP > server, that certainly seems like the simplest way ... you could impliment > the same functionality yourself. > > Failing that, you can pass info to the domU kernel "command line" the > same way the root device is passed in. I use this method with my > initrd to pass in nbd boot parameters: > > extra="NBDHOST=65.39.183.43 NBDPORT=8001 > ip=192.168.2.254:1.1.1.1:192.168.2.86:255.255.255.0" >I think the original poster was hoping to work with Windows. You can set the MAC address for the virtual machine in it''s config via: vif = [''mac=DE:AD:BE:EF:CA:FE,type=ioemu,bridge=xenbr0''] If you really wanted to do it with a script and no DHCP server, you could read the MAC address and set the ip based on the last byte or two. ~John McCullough _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Chris McKeever
2006-Jul-17 23:45 UTC
Re: [Xen-users] Re: Communicating with VM before Network is configured.
On 7/17/06, tbrown@baremetal.com <tbrown@baremetal.com> wrote:> extra="NBDHOST=65.39.183.43 NBDPORT=8001 > ip=192.168.2.254:1.1.1.1:192.168.2.86:255.255.255.0" > > for an init script it''s really simple, as those NBD* parms are already > loaded into environment variables :) ... but in the more general > case you would need to parse them out of /proc/cmdline > > I don''t believe xen has any specific methods for passing config > parameters to the domU, but I''m no expert. > > Oh, and looking back at the subject line... those ip config parameters > might be of use to you... ip=192... >I have been playing with this myself - and I can''t seem to get the kernel autoconfig working (FC5) - My xen kernel has been compiled with the CONFIG_IP_PNP option set, and then reboot I ''try'' to pass the kernel the following parameters at boot, but they just dont seem to take: vif = [ ''ip=192.168.1.61'' ] netmask = "255.255.255.0" gateway = "192.168.1.1" hostname = "ds-1" any suggestions as to what I may be missing? Thanks Chris> You''ll need a kernel with autoconfig enabled. > > -Tom > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- ---------------------------------- please respond to the list .. if you need to contact me direct cgmckeever is the account prupref.com is the domain <A href="http://www.prupref.com">Simply Chicago Real Estate</A> _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ligesh
2006-Jul-18 06:04 UTC
[Xen-users] Communicating with VM before Network is configured.
Hi folks, There is a fundamental problem with Xen (at least as far as my current knowledge go) in bootstrapping a fully functional virtual machine, and its that you need to configure the network manually through the console, and this makes it a little difficult to manage, especially in a remote setup. Is there some way I can communicate with a program running inside a VM. The way it can work is that I have pre-created images all of which run a particular script. Now the there has to be some method to send data to this script. In Vmware, there is the vmService.exe program, using which you can get a particular string from the config file of the Virtual Machine (which is residing in the host). So there should be an option called as ''communication-string'' in the virtual machine config file, and there should be a Xen utility which can get you this value from inside the VM. This can be used to configure static ip addresses inside the virtual machine. So is there some such mechanism already for Xen? Thanks. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ligesh
2006-Jul-18 06:22 UTC
[Xen-users] Re: Communicating with VM before Network is configured.
How do we do the same on a windows VM? On a remote hosting setup, it is always preferable to assign static ips to the virtual machines. DHCP is cumbersome method to manage ip addresses. -- :: Ligesh :: http://ligesh.com On Mon, Jul 17, 2006 at 09:47:03PM +0100, Steve Kemp wrote:> > > Perhaps this will help? > > 1. Copy a script to do the setup into your new images then > boot up the new system with an extra command line argument > "init=/path/to/script". > > That can read kernel command line arguments to setup things, > etc. > > 2. At the end of your script run "reboot", or from a shell run > "xm reboot name" > > 3. Run "xm create ..." to boot up the image once it has been > configured. > > > Failing that why not just try DHCP ? >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ligesh
2006-Jul-18 06:40 UTC
[Xen-users] Re: Communicating with VM before Network is configured.
OK, but then how do I know which is the IP with which the new VM got configured? I think there should be some way to communicate; something like what Vmware provides, which seems like a general purpose mechanism to me. Thanks. -- :: Ligesh :: http://ligesh.com On Mon, Jul 17, 2006 at 10:00:09PM +0100, Steve Kemp wrote:> On Tue, Jul 18, 2006 at 02:22:40AM -0400, Ligesh wrote: > > How do we do the same on a windows VM? On a remote hosting setup, it is always preferable to assign static ips to the virtual machines. DHCP is cumbersome method to manage ip addresses. > > Sorry I must have missed the reference to Windows. > > I imagine you could write a small script in VBScrip/JScript and > place it in the startup directory - or add a registry key to make it > auto-run once. > > It has been a few years since I had to do that kind of thing on > Windows, but I think the principle is sound. Bootup the machine once > with the script to do the magic, then reboot it afterwards. > > I guess you''d need to organise yourself, so for example, you could > have a range of IPs to be tested and do something like this: > > base=192.168.1.100 > > while( 1 ) > { > if ( ping( $base ) ) > { > # Address is "live" > base += 1; (Note you can''t do that really!) > } > else > { > # Found an unallocated IP > setupIP here > reboot > } > } > > I''d recommend you look at AutoIT for your scripting language if you''ve > not got a personal preference. Very nice to use, and free. (Albeit > not "free".) >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ligesh
2006-Jul-18 07:11 UTC
[Xen-users] Re: Communicating with VM before Network is configured.
On Mon, Jul 17, 2006 at 04:17:54PM -0500, Jerry Amundson wrote:> On Tue July 18 2006 01:22, Ligesh wrote: > > How do we do the same on a windows VM? On a remote hosting setup, it > > is always preferable to assign static ips to the virtual machines. > > DHCP is cumbersome method to manage ip addresses. > > How DHCP got so darn popular, I''ll never understand... ;-)With DHCP you have to keep track of two generally unmemorizable numbers--Mac address and the ipaddress. With the method I have described, you need to keep track of only one generally unmemorizable number, leading to a huge saving in neural energy, ultimately leading a better universe and good health for the entire species--not to mention that this is pivotal for the ultimate attainment of World peace. Isn''t that reason enough?> > Off the top of my head, there are a few cases to not use DHCP: > 1. It''s a DNS server. > 2. It has a brain-damaged dhcp client that won''t update DNS. > 3. It''s on a small and/or virtual net with no DHCP server. >I have a specific requirement to assign static ips to a VM. My question is: is there a way to accomplish this. In Vmware you can do it by defining a variable machine.id in the config file variable, which can be accessed from inside VM using the the vmware-guestd on linux or vmwareservice.exe on linux. This is generally a good idea, and I want to know if Xen supports something like this, or what I should do to get this implemented etc etc. Thanks. -- :: Ligesh :: http://ligesh.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ligesh
2006-Jul-18 08:25 UTC
[Xen-users] Re: Communicating with VM before Network is configured.
On Mon, Jul 17, 2006 at 03:16:52PM -0700, tbrown@baremetal.com wrote:> On Tue, 18 Jul 2006, Ligesh wrote: > > > I have a specific requirement to assign static ips to a VM. My question > > is: is there a way to accomplish this. In Vmware you can do it by > > defining a variable machine.id in the config file variable, which can be > > accessed from inside VM using the the vmware-guestd on linux or > > vmwareservice.exe on linux. This is generally a good idea, and I want to > > know if Xen supports something like this, or what I should do to get > > this implemented etc etc. > > I expect vmware does this by controlling both the MAC address and the DHCP > server, that certainly seems like the simplest way ... you could impliment > the same functionality yourself.Sorry, I guess my statement wasn''t clear. The machine.id doesn''t set the ip address or anything. It is just a method to send a string to the Virtual Machine without using the network communication. If you want to use it to set the ip address, you have to do the work yourself, that is, you have write an init script for both linux and windows that will use the vmwareService to get the machine.id, and inside this machine.id you can put the ipaddress. So in the config file you define like this: -------- machine.id = "myMachine 68.55.56.89" ------ In the VM, you have to write a script -------------- $string=/etc/vmware/vmware-guestd --cmd ''machine.id.get'' $ip=`echo $string | cut -d 1 ` ifconfig eth0 $ip ------------- You can do whatever you want actually. Vmware just provides you a mechanism to transfer a string to the VM without the help any of the higher level transportation services that''s all. It is an internal mechanism. Most likely the vmware-guestd executes a trapped instruction recognized by the Vmware VM Monitor, which then supplies it with the variable. It would just be nice to have this feature in Xen.> > Failing that, you can pass info to the domU kernel "command line" the > same way the root device is passed in. I use this method with my > initrd to pass in nbd boot parameters: >Yes. But what to do with Windows? On linux it is really possible. But we need a mechanism so that everything transparently works cross platform. Running Windows side by side is the greatest advantage of Xen. Quite frankly, I think for linux only virtualization, openVz is a slightly better idea, since it is so easy to manage. You can just manage everything inside the VM by using the vzctl command. vzctl set 50 --ipadd 192.168.1.1 or generally vzctl exec 50 "cmd" Thanks for your response. -- :: Ligesh :: http://ligesh.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Chris McKeever
2006-Jul-18 16:23 UTC
[Xen-users] Re: Communicating with VM before Network is configured.
From: Chris McKeever <cgmckeever@prupref.com> Date: Jul 18, 2006 11:21 AM Subject: Re: [Xen-users] Re: Communicating with VM before Network is configured. To: cgmckeever@prupref.com On 7/18/06, Chris McKeever <techjedi@gmail.com> wrote:> > > > > > I have been playing with this myself - and I can''t seem to get the > > > kernel autoconfig working (FC5) - > > > My xen kernel has been compiled with the CONFIG_IP_PNP > > > option set, and then reboot > > > > > > I ''try'' to pass the kernel the following parameters at boot, but they > > > just dont seem to take: > > > > > > vif = [ ''ip=192.168.1.61'' ] > > > netmask = "255.255.255.0" > > > gateway = "192.168.1.1" > > > hostname = "ds-1" > > > > > > > > > any suggestions as to what I may be missing? > > > > > If you check this link: > http://lists.xensource.com/archives/html/xen-devel/2006-02/msg00147.html > > you can see that the method you are using, actually (in terms of the > referenced doc) is supposed to be available for config parameters: > ip="blah" > netmask="blah" > gateway="blah" > > the config parameters are also documented in, > http://www.cl.cam.ac.uk/Research/SRG/netos/xen/readmes/user/user.html#SECTION03210000000000000000 > and ip address is stated to be part of vif (of course I may be > misinterpretting the use of the ip address in that context) > > I''ll give the extras a try - seems like it should work via the > documented way - but it probably does, I am just missing something. > > > > AFAIK, your vif line doesn''t need an IP address, as the default scripts > > are in bridging mode, and you don''t need to tell xen what IP address to > > route in bridged mode. The netmask and gateway parameters I''ve never seen > > before. > > > > If you want/need the kernel to autoconfigure so it can do a network based > > boot, then you to copy the parameter format I was using. > > > > The full kernel command line syntax is > > ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf> > >using the ''extra'' parameter seems to have passed all the appropriate network config options based on Tom''s suggestion - Any ideas why the network config options don''t work as described? http://www.cl.cam.ac.uk/Research/SRG/netos/xen/readmes/user/user.html#SECTION03210000000000000000 netmask Manually configured IP netmask. gateway Manually configured IP gateway. hostname Set the hostname for the virtual machine> > which would be > > ip=192.168.1.61:1.1.1.1:192.168.1.1:255.255.255.0 > > > > for the parameters you have shown above, and that would go into the > > "extras" variable... > > > > > > > > Thanks > > > Chris > > > > > > > > > > > > > You''ll need a kernel with autoconfig enabled. > > > > > > > > -Tom > > > > > > > > > > > > > > > > _______________________________________________ > > > > Xen-users mailing list > > > > Xen-users@lists.xensource.com > > > > http://lists.xensource.com/xen-users > > > > > > > > > > > > > -- > > > ---------------------------------- > > > please respond to the list .. if you need to contact me direct > > > cgmckeever is the account > > > prupref.com is the domain > > > > > > <A href="http://www.prupref.com">Simply Chicago Real Estate</A> > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > > > > > > > ---------------------------------------------------------------------- > > tbrown@BareMetal.com | Courage is doing what you''re afraid to do. > > http://BareMetal.com/ | There can be no courage unless you''re scared. > > | - Eddie Rickenbacker > > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
tbrown@baremetal.com
2006-Jul-18 16:44 UTC
Re: [Xen-users] Re: Communicating with VM before Network is configured.
> > On 7/18/06, Chris McKeever <techjedi@gmail.com> wrote: > > > > > > > > I have been playing with this myself - and I can''t seem to get the > > > > kernel autoconfig working (FC5) - > > > > My xen kernel has been compiled with the CONFIG_IP_PNP > > > > option set, and then reboot > > > > > > > > I ''try'' to pass the kernel the following parameters at boot, but they > > > > just dont seem to take: > > > > > > > > vif = [ ''ip=192.168.1.61'' ] > > > > netmask = "255.255.255.0" > > > > gateway = "192.168.1.1" > > > > hostname = "ds-1"just as a side note... it is more usefull if you quote the things that do work, as compared to the things that do not work. People on this list often refer folks to the mailing list archives, but it takes a fair amount of work to pull usefull information out of those archives. Then again, I don''t know why the xen code couldn''t convert network configuration parameters into the kernel auto-config format. I don''t know if it is a good idea, but it seems possible.> > If you check this link: > > http://lists.xensource.com/archives/html/xen-devel/2006-02/msg00147.html > > > > you can see that the method you are using, actually (in terms of the > > referenced doc) is supposed to be available for config parameters: > > ip="blah" > > netmask="blah" > > gateway="blah"AFAIK, all these settings are _mostly_ for configuring dom0 and the xen network. Given that XEN can host basically any linux distribution it is not realistic to believe that every distribution is going to fish out the parameters that were configured in the xen config files and not over-ride them with it''s own settings. In fact, the default XEN "bridge" setup basically requires that the domU configure itself. The only time you really _need_ to configure the domU from the dom0 (or dhcp) is if you want the kernel to boot over the network. e.g. with an NFS root or from a network block device as I was doing. Any search on "linux nfs root" should turn up the magic string for having the Linux kernel auto-configure the network stack. It is: ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf> AFAIK, The server-ip string seems to be mandatory, and 0.0.0.0 does not work. -Tom _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Chris McKeever
2006-Jul-18 23:58 UTC
Re: [Xen-users] Re: Communicating with VM before Network is configured.
On 7/18/06, tbrown@baremetal.com <tbrown@baremetal.com> wrote:> > > > On 7/18/06, Chris McKeever <techjedi@gmail.com> wrote: > > > > > > > > > > > > > > vif = [ ''ip=192.168.1.61'' ] > > > > > netmask = "255.255.255.0" > > > > > gateway = "192.168.1.1" > > > > > hostname = "ds-1" > > just as a side note... it is more usefull if you quote the things that do > work, as compared to the things that do not work.for clarity - none of the network configs were passed via the command line. Therefore, none of the setup as described worked (outside of using the extra parameter as you described)> > Then again, I don''t know why the xen code couldn''t convert network > configuration parameters into the kernel auto-config format. I don''t know > if it is a good idea, but it seems possible.>From what I have seem - it is supposed to:http://www.nabble.com/IP-configuration-for-domU-ignored-t1779301.html but in this case, it doesnt - for me at least.> > AFAIK, all these settings are _mostly_ for configuring dom0 and the xenDo you have any reference on this? This is where I am confused, as the mentions I have found (posted in this reply) indicate that the config file will create the appropriate kernel command line string> network. Given that XEN can host basically any linux distribution it is > not realistic to believe that every distribution is going to fish out theno fishing, from what I have found (although not proven) - xen does the formating, and creates the passed string.> parameters that were configured in the xen config files and not over-ride > them with it''s own settings. In fact, the default XEN "bridge" setup > basically requires that the domU configure itself. >> ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf> > > AFAIK, The server-ip string seems to be mandatory, and 0.0.0.0 does not > work.some reference to leaving it blank may work as well (untested): ip=<client-ip>::<gw-ip>:<netmask>:<hostname>:<device>:<autoconf> - Chris> > -Tom > >-- ---------------------------------- please respond to the list .. if you need to contact me direct cgmckeever is the account prupref.com is the domain <A href="http://www.prupref.com">Simply Chicago Real Estate</A> _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
tbrown@baremetal.com
2006-Jul-19 00:41 UTC
Re: [Xen-users] Re: Communicating with VM before Network is configured.
On Tue, 18 Jul 2006, Chris McKeever wrote:> > Then again, I don''t know why the xen code couldn''t convert network > > configuration parameters into the kernel auto-config format. I don''t know > > if it is a good idea, but it seems possible. > > >From what I have seem - it is supposed to: > > http://www.nabble.com/IP-configuration-for-domU-ignored-t1779301.html > > but in this case, it doesnt - for me at least.unless you''re running into the same problem he describes ... which is that the server parameter is not being specified, and as such the kernel doesn''t consider it a valid ip config and doesn''t pre-configure eth0 for you. he covers it: ip=172.28.77.99::172.28.77.1:255.255.255.0:knscsl021-vm3:eth0:off vs ip=172.28.77.99:1.2.3.4:172.28.77.1:255.255.255.0:knscsl021-vm3:eth0:off If I set the ip= parameter manually, ip-config fails... If I spec an ipvalue in my config file, then xen builds an ip=... kernel parameter line which supplies an "nfs_server" of 1.2.3.4 by default>> AFAIK, The server-ip string seems to be mandatory, and 0.0.0.0 does not >> work. > >some reference to leaving it blank may work as well (untested): >ip=<client-ip>::<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>Hhmm, maybe, or maybe it doesn''t and this is the reason why. "seems to be mandatory" would imply that I tried leaving it out (I did) ... and :: would be the only way to do that. OK. I''ve just done some testing. as far as I can see, xen-3.0.2-2 does fill in a nfs_server entry of 1.2.3.4 and should avoid the problem I''m describing and that Pablo talks of at the top of that page. But at the bottom he says his problem went away with a recompiled kernel. Anyhow, if you are getting an ip=... kernel parameter with a blank nfs-server entry, you can try adding this to your config file: nfs_server="4.3.2.1" When you boot, there should be some "clues"... e.g. Using config file "test.ip". Started domain test Linux version 2.6.16-xenU (root@xen1.baremetal.com) (gcc version 3.4.5 20051201 (Red Hat 3.4.5-2)) #3 SMP Tue Jul 18 11:39:43 PDT <snip> Kernel command line: ip=192.168.2.254:5.4.3.2:192.168.2.86:255.255.255.0::eth0:off root=/dev/nbd0 ro NBDHOST=65.39.183.43 NBDPORT=8000 single <snip> Using IPI No-Shortcut mode IP-Config: Complete: device=eth0, addr=192.168.2.254, mask=255.255.255.0, gw=192.168.2.86, host=192.168.2.254, domain=, nis-domain=(none), bootserver=4.3.2.1, rootserver=4.3.2.1, rootpath Freeing unused kernel memory: 132k freed Red Hat nash version 4.2.1.6 starting I''ve left shifted the clues... e.g. the kernel command line and the IP-Config: settings. If you''re not getting an IP-Config setting, then the either your kernel isn''t compiled right, or your ip= kernel parameters are not recognized as legit. obviously, my root=/dev/nbd0 and the NBD* parameters are not going to be the same in your config... ... damn, I''m out of "day". I hope the above makes sense, it was written in about four passes. -Tom _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Chris McKeever
2006-Jul-19 12:54 UTC
Re: [Xen-users] Re: Communicating with VM before Network is configured.
On 7/18/06, tbrown@baremetal.com <tbrown@baremetal.com> wrote:> On Tue, 18 Jul 2006, Chris McKeever wrote: > > > > Then again, I don''t know why the xen code couldn''t convert network > > > configuration parameters into the kernel auto-config format. I don''t know > > > if it is a good idea, but it seems possible. > > > > >From what I have seem - it is supposed to: > > > > http://www.nabble.com/IP-configuration-for-domU-ignored-t1779301.html > > > > but in this case, it doesnt - for me at least. > > unless you''re running into the same problem he describes ... which is that > the server parameter is not being specified, and as such the kernel > doesn''t consider it a valid ip config and doesn''t pre-configure eth0 for > you. > > he covers it: > ip=172.28.77.99::172.28.77.1:255.255.255.0:knscsl021-vm3:eth0:off > vs > ip=172.28.77.99:1.2.3.4:172.28.77.1:255.255.255.0:knscsl021-vm3:eth0:offI was not referencing his issue, more so that his post implies that the config file (netmask,hostname,gateway) gets transcribed into the above format as opposed to the conversation of it being passed in the ''extra'' variable.> > OK. I''ve just done some testing. as far as I can see, xen-3.0.2-2 > does fill in a nfs_server entry of 1.2.3.4 and should avoid the > problem I''m describing and that Pablo talks of at the top of that page. > But at the bottom he says his problem went away with a recompiled kernel. > > > Anyhow, if you are getting an ip=... kernel parameter with a blank > nfs-server entry, you can try adding this to your config file: > > nfs_server="4.3.2.1" >are you saying that you are not using the ''extra'' variable here - and are in fact getting xen to build the command line string for network config of the guest via the config (gateway,netmask, etc) parameters? If so, that is all I have been on a quest for this whole time.> When you boot, there should be some "clues"... > > e.g. > > Using config file "test.ip". > Started domain test > Linux version 2.6.16-xenU (root@xen1.baremetal.com) (gcc version > 3.4.5 20051201 (Red Hat 3.4.5-2)) #3 SMP Tue Jul 18 11:39:43 PDT > <snip> > Kernel command line: > ip=192.168.2.254:5.4.3.2:192.168.2.86:255.255.255.0::eth0:off > root=/dev/nbd0 ro NBDHOST=65.39.183.43 NBDPORT=8000 single > <snip> > Using IPI No-Shortcut mode > IP-Config: Complete: > device=eth0, addr=192.168.2.254, mask=255.255.255.0, gw=192.168.2.86, > host=192.168.2.254, domain=, nis-domain=(none), > bootserver=4.3.2.1, rootserver=4.3.2.1, rootpath> Freeing unused kernel memory: 132k freed > Red Hat nash version 4.2.1.6 starting > > I''ve left shifted the clues... e.g. the kernel command line and > the IP-Config: settings. If you''re not getting an IP-Config > setting, then the either your kernel isn''t compiled right, or > your ip= kernel parameters are not recognized as legit. >your config file here would help - as I no longer know if we are even talking the same issue - if all this is still on the ''extra'' variable - we arent To asnwer your inquiry - I do get the kernel command line and IP-Config settings ONLY when I use the extra variable. When I rely on the individual config parameters - I get nothing in the kernel command line except the root definition Thanks _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Chris McKeever
2006-Jul-19 13:39 UTC
Re: [Xen-users] Re: Communicating with VM before Network is configured.
On 7/19/06, Chris McKeever <techjedi@gmail.com> wrote:> On 7/18/06, tbrown@baremetal.com <tbrown@baremetal.com> wrote: > > On Tue, 18 Jul 2006, Chris McKeever wrote: > > > > > > Then again, I don''t know why the xen code couldn''t convert network > > > > configuration parameters into the kernel auto-config format. I don''t know > > > > if it is a good idea, but it seems possible. > > > > > > >From what I have seem - it is supposed to: > > > > > > http://www.nabble.com/IP-configuration-for-domU-ignored-t1779301.html > > >well - to put this to wraps (at least for my issue) - I have gotten xen to build the kernel command line network string: config: vif = [''''] ip="192.168.1.61" netmask="255.255.255.0" gateway="192.168.1.1" hostname="ds-1" Result: Kernel command line: ip=192.168.1.61:1.2.3.4:192.168.1.1:255.255.255.0:ds-1:eth0:off root=/dev/sda1 ro just a side note - the kernel needs to be built with IP autoconfig - note that the server IP is defaulted when not supplied (as suggessted by Tom in an earlier post)> > > > > OK. I''ve just done some testing. as far as I can see, xen-3.0.2-2 > > does fill in a nfs_server entry of 1.2.3.4 and should avoid the > > problem I''m describing and that Pablo talks of at the top of that page. > > But at the bottom he says his problem went away with a recompiled kernel. > > > > > > Anyhow, if you are getting an ip=... kernel parameter with a blank > > nfs-server entry, you can try adding this to your config file: > > > > nfs_server="4.3.2.1" > > > > are you saying that you are not using the ''extra'' variable here - and > are in fact getting xen to build the command line string for network > config of the guest via the config (gateway,netmask, etc) parameters? > If so, that is all I have been on a quest for this whole time. > > > When you boot, there should be some "clues"... > > > > e.g. > > > > Using config file "test.ip". > > Started domain test > > Linux version 2.6.16-xenU (root@xen1.baremetal.com) (gcc version > > 3.4.5 20051201 (Red Hat 3.4.5-2)) #3 SMP Tue Jul 18 11:39:43 PDT > > <snip> > > Kernel command line: > > ip=192.168.2.254:5.4.3.2:192.168.2.86:255.255.255.0::eth0:off > > root=/dev/nbd0 ro NBDHOST=65.39.183.43 NBDPORT=8000 single > > <snip> > > Using IPI No-Shortcut mode > > IP-Config: Complete: > > device=eth0, addr=192.168.2.254, mask=255.255.255.0, gw=192.168.2.86, > > host=192.168.2.254, domain=, nis-domain=(none), > > bootserver=4.3.2.1, rootserver=4.3.2.1, rootpath> > Freeing unused kernel memory: 132k freed > > Red Hat nash version 4.2.1.6 starting > > > > I''ve left shifted the clues... e.g. the kernel command line and > > the IP-Config: settings. If you''re not getting an IP-Config > > setting, then the either your kernel isn''t compiled right, or > > your ip= kernel parameters are not recognized as legit. > > > > your config file here would help - as I no longer know if we are even > talking the same issue - if all this is still on the ''extra'' variable > - we arent > > To asnwer your inquiry - I do get the kernel command line and > IP-Config settings ONLY when I use the extra variable. When I rely on > the individual config parameters - I get nothing in the kernel command > line except the root definition > > > Thanks >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users