This is to request help installing a DomU guest on Xen 3.1, upgraded from
3.0.3 on CentOS 5.1. After struggling for a week, the most success I have
had is with virt-install script for installing DomU guest clientdom.
Here''s
a capture of the virt-install session:
#
#virt-install
Would you like a fully virtualized guest (yes or no)? This will allow you
to run unmodified operating systems. yes
What is the name of your virtual machine? clientdom
How much RAM should be allocated (in megabytes)? 256
What would you like to use as the disk (path)? /xen/clientdom.img
How large would you like the disk (/xen/clientdom.img) to be (in
gigabytes)? 20
Would you like to enable graphics support? (yes or no) no
What is the virtual CD image, CD device or install location? /dev/scd0
Starting install...
Creating storage file... 100% |=========================| 20 GB 00:00
Creating domain... 0 B 00:00
Domain installation still in progress. You can reconnect
to the console to complete the installation process.
#
After the above, "xm console clientdom" generates:
#
xenconsole: Could not read tty from store: No such file or directory
#
error.
Using virsh generates similar error:
#
#virsh connect clientdom
libvir: error : no support for hypervisor
error: Failed to connect to the hypervisor
#
At this both host and guest OS appear in "xm list" and "xm
top", but can''t
successfully connect to hypervisor or guest console. The disk file
/xen/clientdom.img is created with 20 GB. The following network interfaces
are created, but no IP addresses assigned:
#
#ifconfig
eth0 Link encap:Ethernet HWaddr 00:1B:78:D0:04:C6
inet addr:10.0.0.250 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::21b:78ff:fed0:4c6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15266 errors:0 dropped:0 overruns:0 frame:0
TX packets:9332 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1469254 (1.4 MiB) TX bytes:2421157 (2.3 MiB)
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:826 errors:0 dropped:0 overruns:0 frame:0
TX packets:826 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:76216 (74.4 KiB) TX bytes:76216 (74.4 KiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:15265 errors:0 dropped:0 overruns:0 frame:0
TX packets:9333 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1530180 (1.4 MiB) TX bytes:2462443 (2.3 MiB)
Interrupt:18 Memory:f8000000-f8012100
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:9368 errors:0 dropped:0 overruns:0 frame:0
TX packets:15284 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2426477 (2.3 MiB) TX bytes:1470334 (1.4 MiB)
vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST NOARP 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:32
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:8890 (8.6 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:5952 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:456135 (445.4 KiB) TX bytes:0 (0.0 b)
#
I have tried almost an infinite combination of parameters to feed
virt-install, just not the correct ones.
Any help would be greatly appreciated.
Thanks,
Hamid.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users