here we go:
1) compile a kernel
*******************
i did that on a separate host, kernel config file attached (config-3.0.0)
source:
- http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.0.tar.bz2
important: don't apply git4 patch, doesn't work yet with xen, xen host
doesn't boot anymore.
xen host
********
2xhd250gb
2xhd2tb
16gb ram
hp dl 320g5
partitions raid 1
*****************
md0 > 12gb > swap
md1 > 238gb > ext4 /
md2 > 2tb > lvm2
lvm2
****
lv group > vgmain
lv device > lv_server01 > 100gb
2) xen host configuration
*************************
debian squeeze install 6.0.2.1, without preselected package, plain.
http://cdimage.debian.org/debian-cd/6.0.2.1/amd64/iso-cd/debian-6.0.2.1-amd6
4-netinst.iso
aptitude install lsof mc ssh console-data git-core mercurial locales udev
initramfs-tools
rm -r /etc/resolv.conf
touch /etc/resolv.conf
nano /etc/resolv.conf
***
domain domain.net
search *
nameserver 212.40.0.10
nameserver 212.40.5.50
***
rm -r /etc/kernel-img.conf
touch /etc/kernel-img.conf
nano /etc/kernel-img.conf
***
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
***
aptitude update
dpkg-reconfigure locales
dpkg-reconfigure tzdata
dpkg-reconfigure console-data
aptitude update
aptitude safe-upgrade
apt-get clean
aptitude clean
rm -r /etc/inittab
touch /etc/inittab
nano /etc/inittab
***
id:2:initdefault:
si::sysinit:/etc/init.d/rcS
~~:S:wait:/sbin/sulogin
l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
z6:6:respawn:/sbin/sulogin
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now
pf::powerwait:/etc/init.d/powerfail start
pn::powerfailnow:/etc/init.d/powerfail now
po::powerokwait:/etc/init.d/powerfail stop
1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6
#T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
#T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100
#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3
***
rm -r /etc/ssh/sshd_config
touch /etc/ssh/sshd_config
nano /etc/ssh/sshd_config
***
Port 22
#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
UsePrivilegeSeparation yes
KeyRegenerationInterval 3600
ServerKeyBits 768
SyslogFacility AUTH
LogLevel INFO
LoginGraceTime 120
PermitRootLogin no
StrictModes yes
RSAAuthentication yes
PubkeyAuthentication yes
#AuthorizedKeysFile %h/.ssh/authorized_keys
IgnoreRhosts yes
RhostsRSAAuthentication no
HostbasedAuthentication no
#IgnoreUserKnownHosts yes
PermitEmptyPasswords no
ChallengeResponseAuthentication no
#PasswordAuthentication yes
#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
#UseLogin no
#MaxStartups 10:30:60
#Banner /etc/issue.net
AcceptEnv LANG LC_*
Subsystem sftp /usr/lib/openssh/sftp-server
UsePAM yes
***
# xen install
aptitude install gcc make uuid-dev libcurl4-openssl-dev flex gettext
libncurses5-dev bin86 bcc iasl python-dev python texinfo texi2html
pciutils-dev bison bzip2 checkinstall autoconf debhelper debconf-utils
docbook-xml docbook-xsl dpatch xsltproc bridge-utils
cd /usr/src
hg clone http://xenbits.xensource.com/xen-unstable.hg xen-unstable
cd /usr/src/xen-unstable
make clean
make xen
make tools
make stubdom
make install-xen
make install-tools PYTHON_PREFIX_ARG=
make install-stubdom
rm -r /etc/network/interfaces
touch /etc/network/interfaces
nano /etc/network/interfaces
***
auto lo
iface lo inet loopback
auto br0
iface br0 inet static
address 10.10.10.21
netmask 255.255.255.0
network 10.10.10.0
broadcast 10.10.10.255
gateway 10.10.10.1
bridge_ports eth0
bridge_stp on
bridge_maxwait 0
auto eth1
iface eth1 inet static
address 10.255.255.1
netmask 255.255.255.0
network 10.255.255.0
broadcast 10.255.255.255
***
rm -r /etc/sysctl.conf
touch /etc/sysctl.conf
nano /etc/sysctl.conf
***
kernel.domainname = local.net
#kernel.printk = 3 4 1 3
#net.ipv4.conf.default.rp_filter = 1
#net.ipv4.conf.all.rp_filter = 1
#net.ipv4.tcp_syncookies = 1
net.ipv4.ip_forward = 1
net.ipv6.conf.all.forwarding = 1
#net.ipv4.conf.all.accept_redirects = 0
#net.ipv6.conf.all.accept_redirects = 0
#net.ipv4.conf.all.send_redirects = 0
#net.ipv4.conf.all.accept_source_route = 0
#net.ipv6.conf.all.accept_source_route = 0
#net.ipv4.conf.all.log_martians = 1
***
rm -r /etc/xen/xend-config.sxp
touch /etc/xen/xend-config.sxp
nano /etc/xen/xend-config.sxp
***
# -*- sh -*-
#(logfile /var/log/xen/xend.log)
#(loglevel DEBUG)
#(xsm_module_name dummy)
#(xen-api-server ((unix)))
#(xend-http-server no)
#(xend-unix-server no)
#(xend-tcp-xmlrpc-server no)
#(xend-unix-xmlrpc-server yes)
(xend-relocation-server yes)
#(xend-relocation-ssl-server no)
#(xend-udev-event-server no)
#(xend-unix-path /var/lib/xend/xend-socket)
#(xend-tcp-xmlrpc-server-address 'localhost')
#(xend-tcp-xmlrpc-server-port 8006)
#(xend-tcp-xmlrpc-server-ssl-key-file xmlrpc.key)
#(xend-tcp-xmlrpc-server-ssl-cert-file xmlrpc.crt)
#(xend-port 8000)
(xend-relocation-port 8002)
#(xend-relocation-ssl-port 8003)
# xend-relocation-ssl-server is set.
#(xend-relocation-server-ssl-key-file xmlrpc.key)
#(xend-relocation-server-ssl-cert-file xmlrpc.crt)
#(xend-relocation-ssl no)
#(xend-address '')
#(xend-address localhost)
(xend-relocation-address '')
#(xend-relocation-hosts-allow '')
(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')
#(console-limit 1024)
(network-script 'network-bridge antispoof=yes')
(vif-script vif-bridge)
#(vif-script vif-route)
#(vif-script vif-nat)
(dom0-min-mem 256)
(enable-dom0-ballooning yes)
(total_available_memory 0)
(dom0-cpus 0)
#(enable-dump no)
#(external-migration-tool '')
(vnc-listen '0.0.0.0')
(vncpasswd '')
#(vnc-tls 1)
#(vnc-x509-cert-dir vnc)
#(vnc-x509-verify 1)
(keymap 'de-ch')
#(resource-label-change-script '')
#(qemu-dm-logrotate-count 10)
#(xend-domains-path /var/lib/xend/domains)
#(device-create-timeout 100)
#(pscsi-device-mask ('*'))
***
rm -r /etc/default/xendomains
touch /etc/default/xendomains
nano /etc/default/xendomains
***
XENDOMAINS_SYSRQ=""
XENDOMAINS_USLEEP=100000
XENDOMAINS_CREATE_USLEEP=5000000
XENDOMAINS_MIGRATE=""
XENDOMAINS_SAVE=/var/lib/xen/save
XENDOMAINS_SHUTDOWN="--halt --wait"
XENDOMAINS_SHUTDOWN_ALL="--all --halt --wait"
XENDOMAINS_RESTORE=false
XENDOMAINS_AUTO=/etc/xen/auto
XENDOMAINS_AUTO_ONLY=true
XENDOMAINS_STOP_MAXWAIT=500
***
rm -r /etc/default/grub
touch /etc/default/grub
nano /etc/default/grub
***
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
#GRUB_TERMINAL=console
#GRUB_GFXMODE=640x480
#GRUB_DISABLE_LINUX_UUID=true
#GRUB_DISABLE_LINUX_RECOVERY=true
GRUB_DISABLE_OS_PROBER=true
#GRUB_INIT_TUNE="480 440 1"
***
rm -r /etc/grub.d/08_xen
touch /etc/grub.d/08_xen
nano /etc/grub.d/08_xen
***
#!/bin/sh
exec tail -n +3 $0
menuentry "Xen 4.2 Unstable / Debian Squeeze kernel 3.0.0" {
insmod ext2
insmod multiboot2
insmod lvm
insmod part_msdos
insmod raid
insmod mdraid
set root='(md/1)'
search --no-floppy --fs-uuid --set [UUID]
echo 'Loading multiboot kernel ...'
multiboot (md/1)/boot/xen.gz placeholder dom0_mem=1024M
echo 'Loading initial kernel ...'
module (md/1)/boot/vmlinuz-3.0.0 placeholder root=UUID=[UUID] ro
quiet console=tty0 nomodeset
echo 'Loading initial ramdisk ...'
module (md/1)/boot/initrd.img-3.0.0
}
***
chmod -x /etc/grub.d/20_linux_xen
chmod 755 /etc/grub.d/08_xen
update-grub2
update-rc.d xencommons defaults 19 18
update-rc.d xend defaults 20 21
update-rc.d xendomains defaults 21 20
/etc/init.d/xencommons start
/etc/init.d/xend start
/etc/init.d/xendomains start
rm -r /etc/modules
touch /etc/modules
nano /etc/modules
***
loop max_loop=64
lp
rtc
xen-evtchn
xen-gntdev
xen-netback
xen-blkback
xenfs
blktap
***
rm -r /etc/xen/server02.cfg
touch /etc/xen/server02.cfg
nano /etc/xen/server02.cfg
***
name = 'server01'
kernel = 'hvmloader'
builder = 'hvm'
device_model = 'qemu-dm'
maxmem = 1024
memory = 1024
vcpus = 1
acpi = 1
apic = 1
uuid = '[UUID]'
vif = [ 'bridge=br0,mac=xx:xx:xx:xx:xx:xx' ]
#disk = [
'phy:/dev/vgmain/lv_server01,hda,w','file:/var/xen/debian-6.0.2.1-amd64-neti
nst.iso,hdc:cdrom,r' ]
disk = [ 'phy:/dev/vgmain/lv_server01,hda,w' ]
boot = 'dc';
usbdevice = 'tablet'
sdl = 0
stdvga = 1
serial = 'pty'
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
vnc = 1
vnclisten = '0.0.0.0'
vncviewer = 1
***
-----Original Message-----
From: Mark Schneider [mailto:ms@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Dienstag, 26. Juli 2011 00:09
To: Walter Robert Ditzler
Subject: Re: [Xen-devel] xen 4.2 unstable; HVM; 2.6.39.3; HD/Network card
error
Walter,
where can I find these two files? (kernel config and your "how to do"?
Thank you / regards
Mark
Am 25.07.2011 01:04, schrieb Walter Robert Ditzler:
> nope, but have all documented in 2 txt file, 1 is the kernel config
> and the other a complete install after having a running virgin squeeze
box.
> checkinstall made problems.
>
> thanks walter
>
> -----Original Message-----
> From: Mark Schneider [mailto:ms@xxxxxxxxxxxxxxxxxxxxxx]
> Sent: Sonntag, 24. Juli 2011 23:33
> To: Walter Robert Ditzler; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] xen 4.2 unstable; HVM; 2.6.39.3; HD/Network
> card error
>
> Hello Walter,
>
> good news - congratulations :)
>
> Do you have .deb packages for xen 4.2 unstable and the xen-kernel you
> have used?
>
> Thank you for your short info.
>
> regards,
> Mark
>
>
> Am 25.07.2011 00:21, schrieb Walter Robert Ditzler:
>
>> hi list members,
>>
>> i had several problems with my new xen installations, 4.2 unstable
>> with
>> 2.6.39-3 and hvm guests. I can finally say that almost all problems
>> have been gone :-) to be honest I believe the kernels 2.6.39.1/2 and
>> 3 were the problem.
>>
>> this weekend I used the mainline 3.0.0 kernel with an actual version
>> of xen
>> 4.2 unstable, and here we go:
>>
>> - booting of squeeze guests, ok (before hang on grub)
>> - booting of win 7 x64 guests, ok
>> - booting of win 2008r2 x64 guests, ok
>>
>> the only little problem which has left is on squeeze guests.
>>
>> the squeeze guest comes up until grub. but then it takes around 2
>> minutes until the squeeze guest installation continues to start up.
>> that would be really nice get to be solved in the near future.
>>
>> thanks walter
>>
>>
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Walter Robert Ditzler [mailto:ditwal001@xxxxxxxxx]
>> Sent: Mittwoch, 20. Juli 2011 14:09
>> To: 'Stefano Stabellini'
>> Cc: konrad.wilk@xxxxxxxxxx; xen-devel@xxxxxxxxxxxxxxxxxxx;
>> xen-users@xxxxxxxxxxxxxxxxxxx
>> Subject: RE: [Xen-devel] xen 4.2 unstable; HVM; 2.6.39.3; HD/Network
>> card error
>> Importance: High
>>
>> stefano,
>>
>> i found the problem, if it is really a one! I will explain it step by
>> step what solved my problem which works for both, win7 and debian
>> squeeze
>> guest's:
>>
>> network card / network
>> **********************
>> the guest network works brilliant only with that configuration:
>>
>> auto brX
>> iface brX inet static
>> address 10.41.10.42
>> netmask 255.255.255.0
>> network 10.41.10.0
>> broadcast 10.41.10.255
>> gateway 10.41.10.1
>> bridge_ports eth0
>> bridge_stp on
>> bridge_maxwait 0
>>
>> vif = [ 'bridge=brX,mac=xx:xx:xx:xx:xx:xx' ]
>>
>>
>> strange is that I now have to configure a bridge interface. with
>> older xen version it was enough to setup "bridge=eth0". now I had to
>> setup "bridge=brX"!
>>
>>
>> disk controller
>> ***************
>> for a windows 7 x64 guest system I got it running with:
>> disk = [
>> 'phy:/dev/vgmain/lv_server01,hda,w','file:/var/xen/win7.iso,hdc:cdrom
>> ,
>> r' ]
>>
>> for a debian squeeze guest system I needed to change it into:
>> disk = [
>> 'phy:/dev/vgmain/lv_server01,sda,w','file:/var/xen/debian-6.0.1a-amd6
>> 4
>> -netin
>> st.iso,hdc:cdrom,r' ]
>>
>>
>> even here is strange that debian squeeze guest's now see the qemu disk
>> as a "SDA". squeeze used to see qemu disk in older xen versions (< 4.2)
>>
> as "HDA"
>
>> and that definitely doesn't work anymore.
>>
>> I found that out having a deeper look at the debian installer log.
>>
>>
>> guy's, thank you very much for your help, had become a lot of new
>> input's. I hope I could give some useful feedback back to you too.
>>
>> finally I only would like to know, if this SDA-behavior is now a new
>> behavior of xen 4.2 ++?
>>
>> thanks a lot, walter
>>
>>
>>
>> *** original guest config file ***
>> name = 'server01'
>> kernel = 'hvmloader'
>> builder = 'hvm'
>> device_model = 'qemu-dm'
>> maxmem = 1024
>> memory = 1024
>> vcpus = 1
>> acpi = 1
>> apic = 1
>>
>> vif = [ 'bridge=eth0,mac=00:16:3e:1a:b3:4b' ]
>> #vfb = [ 'type=vnc,vnclisten=0.0.0.0,vncunused=0,vncdisplay=1'
>>
> ]
>
>> disk = [
>> 'phy:/dev/vgmain/lv_server01,hda,w','file:/var/xen/debian-6.0.1a-amd6
>> 4
>> -netin
>> st.iso,hdc:cdrom,r' ]
>>
>> boot = 'dc'
>> usbdevice = 'tablet'
>>
>> sdl = 0
>>
>> stdvga = 1
>> serial = 'pty'
>>
>> on_poweroff = 'destroy'
>> on_reboot = 'restart'
>> on_crash = 'restart'
>>
>> vnc = 1
>> vnclisten = '0.0.0.0'
>> vncviewer = 1
>> ***
>>
>>
>>
>>
>> -----Original Message-----
>> From: Stefano Stabellini [mailto:stefano.stabellini@xxxxxxxxxxxxx]
>> Sent: Mittwoch, 20. Juli 2011 13:40
>> To: Walter Robert Ditzler
>> Cc: Stefano Stabellini; konrad.wilk@xxxxxxxxxx;
>> xen-devel@xxxxxxxxxxxxxxxxxxx; xen-users@xxxxxxxxxxxxxxxxxxx
>> Subject: RE: [Xen-devel] xen 4.2 unstable; HVM; 2.6.39.3; HD/Network
>> card error
>>
>> On Tue, 19 Jul 2011, Walter Robert Ditzler wrote:
>>
>>
>>> hi stefano,
>>> hi konrad,
>>>
>>> thanks for replying :-) i followed your suggestions and changed the
>>> guest config file. I have now the following test szenario:
>>>
>>> server01> should be a debian squeeze 6.0.1a amd64 netinst
>>> installation
>>> server02> is a successfully installed windows 7 x64 installation
>>>
>>> bellow I paste the both config files. as you can see from the screen
>>>
>>>
>> shots:
>>
>>
>>> server01 installation
>>> *********************
>>> sh11: server01_debian-installer-1.JPG
>>> sh12: server01_debian-installer-2.JPG
>>> sh13: server01_debian-installer-3.JPG
>>>
>>> the debian installation has some difficulties to find a harddisk.
>>> strange is, that the networkcard was found straight away and I
>>> became a dhcp lease from my infrastructure.
>>>
>>> server02 installation
>>> *********************
>>> sh21: server02_xen_win7.JPG
>>>
>>> the windows has been successfully installed onto my xen guest, but!!!!!
>>>
>>>
>>> Q U E S T I O N S
>>> *****************
>>> - why do I see my server HP DL320G5 network card and disk controller?
>>> - I thought, HVM means fully virtualized?! I expected to see
>>> something like qemu/xen harddrive and qemu/xen network card!?
>>> - Is here my xen really doing HVM
>>> - how can I do HVM, I need my guests to be transferred to any
>>> different hw boxes without need to deal with guest disk and network
>>> card
>>>
>>>
>> drivers?
>>
>> What exactly are the network card and disk controller that you are
>> seeing in your guests?
>>
>>
config-3.0.0
Description: Binary data
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home