This is what I was looking for!
Thanks
-----Original Message-----
From: Michael J. Baysek [mailto:mjbaysek@xxxxxxxxxx]
Sent: Thursday, September 15, 2005 10:33 AM
To: Johnson, Michael
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] RE: Basic Xen Questions
I understand you are looking at dom0 interfaces here. If you are
talking about giving your domU's IP addresses, you need to do that from
inside the domU image. You don't see those IP address when doing an
ifconfig on dom0. The xen-br0 interface is a bridge. If you do a
# brctl show
you will see that your vifs belong to the bridge.
For your domU's to see the rest of your network and for you to be able
to ssh into them, you just need to configure them on the same subnet as
your dom0. As far as actually configuring the interface, just start an
xm console session into your domU and set it up the way you normally
would, just like any other host on your subnet.
Hope this helps
Johnson, Michael wrote:
> Here is what I get when I do an ifconfig -a. eth0 is the physical
> card/address. How do I configure the virtual interface with a
> different IP and connect to it via ssh or telnet?
>
> eth0 Link encap:Ethernet HWaddr 00:09:6B:8C:D5:54
> inet addr:10.131.142.213 Bcast:10.131.142.255
> Mask:255.255.255.128
> inet6 addr: fe80::209:6bff:fe8c:d554/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:252681 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1284 errors:0 dropped:0 overruns:0 carrier:0
> collisions:4 txqueuelen:1000
> RX bytes:18191313 (17.3 MiB) TX bytes:183225 (178.9 KiB)
> Interrupt:24
>
> eth1 Link encap:Ethernet HWaddr 00:09:6B:8C:D5:55
> BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> Interrupt:25
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:3096 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3096 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1824719 (1.7 MiB) TX bytes:1824719 (1.7 MiB)
>
> sit0 Link encap:IPv6-in-IPv4
> NOARP MTU:1480 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:250606 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> xen-br0 Link encap:Ethernet HWaddr 00:09:6B:8C:D5:54
> inet addr:10.131.142.213 Bcast:10.131.142.255
> Mask:255.255.255.255
> inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:252211 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1128 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:13616114 (12.9 MiB) TX bytes:161560 (157.7 KiB)
>
> ----------------------------------------------------------------------
> --
> *From:* Michael J. Baysek [mailto:mjbaysek@xxxxxxxxxx]
> *Sent:* Wednesday, September 14, 2005 4:08 PM
> *To:* Johnson, Michael; xen-users@xxxxxxxxxxxxxxxxxxx
> *Subject:* Basic Xen Questions
>
> I did the favor of making a new thread for this...
>
> Firstly. If you have not yet,
> http://www.fedoraproject.org/wiki/FedoraXenQuickstart
>
> I can tell you that even since FC4 was released, Xen has changed a
> lot. Since the FC4 packages are reflecting the 3.0 development, using
> the Xen 2.0 user guide is not 100% accurate, I have tried. Also, it
> seems that the latest FC release 1447 of Xen is noticably different
> than the 1398 release, as some of the xm commands are different.
> Personally I would expect future releases to do the same so I suggest
> test any upgrades on a staging server.
>
> *About Network: *As long as you have nics=1 in your conf file for
> your domU, the network device should be available in your guest OS as
> eth0. In Redhat-esque style, you would edit your network config in
> /etc/sysconfig/. I just copied /etc/sysconfig/network* from another
> machine, and did a
>
> grep -rin "192.168.0.3" /etc/sysconfig/*
>
> for the IP of the machine I took the config from, and updated to the
> new IP for my domU.
>
> As far as *installing OS* other than FC4 inside of domU, I have
> installed CentOS. Here are the steps I have used. I imagine you can
> use this for any distro that uses Yum.
>
> 1. Create my image (I use LVM, but you can use loopback), mke2fs -j
> to that image
> 2. Temporarily move /etc/yum.repos.d/* files out of that directory
> 3. Copy Centos-Base.repo into /etc/yum.repos.d/
> 4. Edit Centos-Base.repo to replace all the of variables with the
> values you want. Yum can't install for a different releasever
> and basearch, so you set these by hand in the repo file. You
> could also install from local filesystem like DVD by using
> file:// instead of http in the repo file.
> 5. Mount the image to /mnt/tmpdir
> 6. yum --installroot=/mnt/tmpdir -y groupinstall Base
> 7. Follow the rest of the steps in the Fedora Xen Howto for the
rest.
>
> I also have been running Gentoo 2005.0 which I moved over from
> User-Mode-Linux.
>
> Hope this helps.
>
>
>
> Johnson, Michael wrote:
>> Hi,
>> Could you help me with a few Xen questions? It's basic stuff. I'm
>> looking at Xen for the first time. We have VMWare already up and
>> running and are happy with it but I was asked to look at Xen.
>>
>> I installed FC4 from cd and chose to install everything, including
Xen.
>> Following the Xen User's manual Xen v2.0 for x86 I have a dom0 setup
>> and created a second domain and called it rawhide.
>>
>> Question,
>> How do I configure rawhide with an IP so I can either ssh or telnet
>> to it?
>>
>> Have you installed other operating systems, i.e. RedHat EL3.0 to run
>> in a domain?
>>
>> Thanks,
>> Mike
>>
>> -----Original Message-----
>> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
>> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Michael
J.
>> Baysek
>> Sent: Wednesday, September 14, 2005 2:21 PM
>> To: Eric Brown
>> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
>> Subject: Re: [Xen-users] xm shutdown & xm destroy won't get rid of VM
>>
>> I too have this problem:
>>
>> # xm list
>>
>> Name Id Mem(MB) CPU VCPU(s) State Time(s)
>> Domain-0 0 91 0 1 r---- 6753.9
>> lick 11 0 0 1 ----c 0.3
>> lick 11 0 0 1 ----c 0.3
>> lmon 4 255 0 1 -b--- 34997.5
>> lots 5 191 0 1 -b--- 5210.1
>> loud 6 511 0 1 ----- 6138.4
>>
>>
>>
>> In my case this happened after I ran out of memory in the lick domU
>> (no swap was setup yet). The oom-killer hosed the domU. Even the
>> console. So I tried to destroy and start another. It was then that I
>> did an xm list, to my horror.
>>
>>
>>
>> Eric Brown wrote:
>>
>>> I tried "xm shutdown" and then "xm destroy", my listing still shows:
>>>
>>> $ xm list
>>> Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 156 0 r----
>>> 766.2
>>>
>>
>>
>>> asgtest0 9 0 3 -b--- 1.2 9609 debianarchive 15 255 1 -b--- 6.4 9615
>>>
>>> What should i do to get rid of asgtest0?
>>>
>>> Thanks!
>>>
>>>
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-users
>>>
>>>
>>
>>
>
>
> --
>
> Michael J. Baysek
> Systems Analyst
> Carnegie Mellon University, Auton Lab
> http://www.autonlab.org
> mjbaysek@xxxxxxxxxx
>
> ----------------------------------------------------------------------
> --
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
--
Michael J. Baysek
Systems Analyst
Carnegie Mellon University, Auton Lab
http://www.autonlab.org
mjbaysek@xxxxxxxxxx
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home