The math is correct; I'm playing with a 50 Gb OS image because I have several applications that I want to test running on a thin client.
I am using a very simple network; I have the initiator and the target linked together via Ethernet cable. The Linux target is running a dhcp server and iscsitarget.
For boot, I am running gpxe 1.0.1 DVD on the initiator; the boot commands I am running are:
dhcp net0
set keep-san 1
sanboot ${root-path}
#################### Dhcpd.conf ###########################
option space gpxe;
option gpxe-encap-opts code 175 = encapsulate gpxe;
option gpxe.priority code 1 = signed integer 8;
option gpxe.keep-san code 8 = unsigned integer 8;
option gpxe.no-pxedhcp code 176 = unsigned integer 8;
option gpxe.bus-id code 177 = string;
option gpxe.bios-drive code 189 = unsigned integer 8;
option gpxe.version code 235 = string;
option iscsi-initiator-iqn code 203 = string;
ddns-update-style interim;
allow booting;
allow bootp;
DHCPDARGS=eth0;
authoritative;
option domain-name "Lanbo.org";
option domain-name-servers 192.168.1.100;
INTERFACES="eth0 eth1 net0 net1";
filename "";
host lanbo-server {
hardware ethernet 00:06:5b:84:53:86;
fixed-address 192.168.1.100;
}
option root-path "iscsi:192.168.1.100::::iqn.2007-08.100.1.168.192:iscsiboot";
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.201 192.168.1.220;
default-lease-time 86400;
max-lease-time 86400;
option routers 192.168.1.1;
option ip-forwarding off;
option broadcast-address 192.168.1.255;
option subnet-mask 255.255.255.0;
option ntp-servers 192.168.1.100;
option netbios-name-servers 192.168.1.100;
host lanbo-client {
#hardware ethernet 00:d0:c9:ab:ea:6c;
hardware ethernet 00:d0:c9:ae:80:9e;
fixed-address 192.168.1.102;
option gpxe.keep-san 1;
}
host lanbo-client2 {
hardware ethernet 00:d0:c9:ab:ea:6c;
fixed-address 192.168.1.101;
}
}
log-facility local7;
#################### Dhcpd.conf ###########################
#################### ietd.conf ###########################
Target iqn.2007-08.100.1.168.192:iscsiboot
Lun 0 Path=/home/erincof/W7_64.img,Type=fileio
#################### ietd.conf ###########################
#################### initiators.allow ###########################
iqn.2007-08.100.1.168.192:iscsi 192.168.1.102
#################### initiators.allow ###########################
Any ideas of where the problem is?
Thank you for your help on this,
Erin
-----Original Message-----
From: Joseph L. Casale [mailto:***@activenetwerx.com]
Sent: Tuesday, March 08, 2011 8:15 AM
To: Etherboot-***@lists.sourceforge.net
Subject: Re: [Etherboot-discuss] Does the TARGET server need to be running a 64 bit OS if the initiator wants to run a 64 bit OS?
Post by Coffey, ErinI build the Window 7, 64 bit OS on the initiator and, then I remove the HD and up load the OS
to the Linux target using "dd if=/dev/sdb of=/home/erincof/W7_64.img bs=8225280 count=6885"
Any suggestions on where I went wrong?
Well, how did you come up with the math for bs/count in your dd cmd? How big is your original disc?
What's your target config look like? How are presenting the image to the initiator?
Any reason why you don't just install directly to the target?
jlc
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Etherboot-discuss mailing list
Etherboot-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/etherboot-discuss