I''ve been trying for the last couple of days to get a routed
network setup functioning, preliminary to modifying the scripts
(simply) to do ip masquerading. I''m running on a Core 2 Duo laptop,
with a single (variable) IP address.
One problem that I''ve encountered is that most of the documentation
I''ve found (including the networking page on the Xensource wiki) seems
to be referring to netfront configurations with a vifD.I in the dom0,
rather than ioemu ones, where (as far as I can tell) you get a tapN
device. This is somewhat confusing, to say the least. (If I can get
this working, I will gladly update the wiki with better details). I
fear that the vif/tap difference may also be a cause of the following
error:
hrm@willow:scripts$ sudo xm create rhel4-base
Using config file "/etc/xen/rhel4-base".
Error: Device 0 (vif) could not be connected. Backend device not found.
Configuration for xend is using network-route and vif-route for the
relevant scripts. The domU configuration is shown below (mostly a copy
of the hvm example configuration).
Can anyone point me in the right direction?
Hugo.
---------------
# -*- mode: python; -*-
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 512
shadow_memory = 8
name = "rhel4-base"
#uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9"
vcpus=1
pae=1
acpi=1
apic=1
vif = [ ''type=ioemu, mac=00:16:3e:17:5e:65'' ]
disk = [ ''phy:/dev/primary/rhel4-base.root,hda,w'' ]
device_model = ''/usr/local/'' + arch_libdir +
''/xen/bin/qemu-dm''
boot="dca"
#snapshot=1
sdl=1
vnc=0
#vnclisten="127.0.0.1"
vncdisplay=1
#vncunused=1
#vncconsole=0
#nographic=0
stdvga=0
serial=''pty''
#full-screen=1
#usb=1
#usbdevice=''mouse''
#usbdevice=''tablet''
---------------
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk == PGP
key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Charting the inexorable advance of Western syphilisation... ---
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Tue, Nov 28, 2006 at 12:54:44PM +0000, Hugo Mills wrote:> I''ve been trying for the last couple of days to get a routed > network setup functioning, preliminary to modifying the scripts > (simply) to do ip masquerading. I''m running on a Core 2 Duo laptop, > with a single (variable) IP address. > > One problem that I''ve encountered is that most of the documentation > I''ve found (including the networking page on the Xensource wiki) seems > to be referring to netfront configurations with a vifD.I in the dom0, > rather than ioemu ones, where (as far as I can tell) you get a tapN > device. This is somewhat confusing, to say the least. (If I can get > this working, I will gladly update the wiki with better details). I > fear that the vif/tap difference may also be a cause of the following > error: > > hrm@willow:scripts$ sudo xm create rhel4-base > Using config file "/etc/xen/rhel4-base". > Error: Device 0 (vif) could not be connected. Backend device not found.It is a bug AFAICT http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=584> Configuration for xend is using network-route and vif-route for the > relevant scripts. The domU configuration is shown below (mostly a copy > of the hvm example configuration). > > Can anyone point me in the right direction?You can use the /etc/xen/qemu-ifup script to configure the networking which works OK for one hvm domain. For multiple hvm domains it gets really messy! Note that the qemu-ifup script is passed the interface name as $1 and the bridge name as $2, so you can set the bridge name different in each of your HVM domains, eg vif = [ ''type=ioemu, mac=00:16:3e:17:5e:65, bridge=rhel4'' ] Then use $2 in qemu-ifup to configure different stuff according to the bridge name. You could make the bridge name be the IP address too I suppose. -- Nick Craig-Wood <nick@craig-wood.com> -- http://www.craig-wood.com/nick _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Nov 28, 2006 at 04:07:53PM +0000, Nick Craig-Wood wrote:> On Tue, Nov 28, 2006 at 12:54:44PM +0000, Hugo Mills wrote: > > I''ve been trying for the last couple of days to get a routed > > network setup functioning, preliminary to modifying the scripts > > (simply) to do ip masquerading. I''m running on a Core 2 Duo laptop, > > with a single (variable) IP address.[snip]> > hrm@willow:scripts$ sudo xm create rhel4-base > > Using config file "/etc/xen/rhel4-base". > > Error: Device 0 (vif) could not be connected. Backend device not found. > > It is a bug AFAICT > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=584In that report, at least the domain starts. In my case, it doesn''t.> > Configuration for xend is using network-route and vif-route for the > > relevant scripts. The domU configuration is shown below (mostly a copy > > of the hvm example configuration). > > You can use the /etc/xen/qemu-ifup script to configure the networking > which works OK for one hvm domain. > > For multiple hvm domains it gets really messy!That''s a shame. I''m going to need multiple domains. :( Note also that my problem is being triggered _before_ qemu-ifup is run, so I doubt that putting things in the script is going to help...> Note that the qemu-ifup script is passed the interface name as $1 and > the bridge name as $2, so you can set the bridge name different in > each of your HVM domains, eg > > vif = [ ''type=ioemu, mac=00:16:3e:17:5e:65, bridge=rhel4'' ] > > Then use $2 in qemu-ifup to configure different stuff according to the > bridge name. > > You could make the bridge name be the IP address too I suppose.OK. Noted for later, when I can get to the point of configuring a running VM. Thanks, Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk == PGP key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- "You know, the British have always been nice to mad people." --- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Make sure the "tun" module is loaded : # modprobe tun François 2006/11/28, Hugo Mills <hugo-xen@carfax.org.uk>:> I''ve been trying for the last couple of days to get a routed > network setup functioning, preliminary to modifying the scripts > (simply) to do ip masquerading. I''m running on a Core 2 Duo laptop, > with a single (variable) IP address. >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Nov 28, 2006 at 04:28:08PM +0000, Hugo Mills wrote:> On Tue, Nov 28, 2006 at 04:07:53PM +0000, Nick Craig-Wood wrote: > > On Tue, Nov 28, 2006 at 12:54:44PM +0000, Hugo Mills wrote: > > > I''ve been trying for the last couple of days to get a routed > > > network setup functioning, preliminary to modifying the scripts > > > (simply) to do ip masquerading. I''m running on a Core 2 Duo laptop, > > > with a single (variable) IP address. > [snip] > > > hrm@willow:scripts$ sudo xm create rhel4-base > > > Using config file "/etc/xen/rhel4-base". > > > Error: Device 0 (vif) could not be connected. Backend device not found. > > > > It is a bug AFAICT > > > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=584 > > In that report, at least the domain starts. In my case, it doesn''t.Hmm... It sounds like the same problem just with different symptoms... You could comment everything out of vif-route to see if you can get the domain up.> Note also that my problem is being triggered _before_ qemu-ifup is > run, so I doubt that putting things in the script is going to help...Note it isn''t actually defined whether vif-route runs before qemu-ifup or after - I''ve certainly seen both cases. -- Nick Craig-Wood <nick@craig-wood.com> -- http://www.craig-wood.com/nick _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Nov 28, 2006 at 06:34:46PM -0500, François Lapointe wrote:> Make sure the "tun" module is loaded : > # modprobe tunYes, I have this loaded (for a separate OpenVPN connection). This isn''t clashing, though, as OpenVPN uses a tun device, not a tap device. Hugo.> 2006/11/28, Hugo Mills <hugo-xen@carfax.org.uk>: > > I''ve been trying for the last couple of days to get a routed > >network setup functioning, preliminary to modifying the scripts > >(simply) to do ip masquerading. I''m running on a Core 2 Duo laptop, > >with a single (variable) IP address. > >-- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk == PGP key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- Quantum est ille canis in fenestra? --- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Nov 29, 2006 at 09:58:07AM +0000, Nick Craig-Wood wrote:> On Tue, Nov 28, 2006 at 04:28:08PM +0000, Hugo Mills wrote: > > On Tue, Nov 28, 2006 at 04:07:53PM +0000, Nick Craig-Wood wrote: > > > On Tue, Nov 28, 2006 at 12:54:44PM +0000, Hugo Mills wrote: > > > > I''ve been trying for the last couple of days to get a routed > > > > network setup functioning, preliminary to modifying the scripts > > > > (simply) to do ip masquerading. I''m running on a Core 2 Duo laptop, > > > > with a single (variable) IP address. > > [snip] > > > > hrm@willow:scripts$ sudo xm create rhel4-base > > > > Using config file "/etc/xen/rhel4-base". > > > > Error: Device 0 (vif) could not be connected. Backend device not found. > > > > > > It is a bug AFAICT > > > > > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=584 > > > > In that report, at least the domain starts. In my case, it doesn''t. > > Hmm... It sounds like the same problem just with different symptoms... > > You could comment everything out of vif-route to see if you can get > the domain up.No luck. Removing the xen-hotplug-common.sh script (or anything containing it, such as vif-common.sh) just causes it to wait for several minutes before failing with "Hotplug scripts not working"> > Note also that my problem is being triggered _before_ qemu-ifup is > > run, so I doubt that putting things in the script is going to help... > > Note it isn''t actually defined whether vif-route runs before qemu-ifup > or after - I''ve certainly seen both cases.OK. I think this is looking like a bug of some kind in xend, but exactly what I don''t know. Surely I can''t be the only person who''s got this problem, or is trying to do this? Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk == PGP key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- Quantum est ille canis in fenestra? --- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Nov 29, 2006 at 04:26:08PM +0000, Hugo Mills wrote:> On Wed, Nov 29, 2006 at 09:58:07AM +0000, Nick Craig-Wood wrote: > > On Tue, Nov 28, 2006 at 04:28:08PM +0000, Hugo Mills wrote: > > > On Tue, Nov 28, 2006 at 04:07:53PM +0000, Nick Craig-Wood wrote: > > > > On Tue, Nov 28, 2006 at 12:54:44PM +0000, Hugo Mills wrote: > > > > > I''ve been trying for the last couple of days to get a routed > > > > > network setup functioning, preliminary to modifying the scripts > > > > > (simply) to do ip masquerading. I''m running on a Core 2 Duo laptop, > > > > > with a single (variable) IP address. > > > [snip] > > > > > hrm@willow:scripts$ sudo xm create rhel4-base > > > > > Using config file "/etc/xen/rhel4-base". > > > > > Error: Device 0 (vif) could not be connected. Backend device not found. > > > > > > > > It is a bug AFAICT > > > > > > > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=584 > > > > > > In that report, at least the domain starts. In my case, it doesn''t. > > > > Hmm... It sounds like the same problem just with different symptoms... > > > > You could comment everything out of vif-route to see if you can get > > the domain up. > > No luck. Removing the xen-hotplug-common.sh script (or anything > containing it, such as vif-common.sh) just causes it to wait for > several minutes before failing with "Hotplug scripts not working" > > > > Note also that my problem is being triggered _before_ qemu-ifup is > > > run, so I doubt that putting things in the script is going to help... > > > > Note it isn''t actually defined whether vif-route runs before qemu-ifup > > or after - I''ve certainly seen both cases. > > OK. I think this is looking like a bug of some kind in xend, but > exactly what I don''t know. Surely I can''t be the only person who''s got > this problem, or is trying to do this?I''m still having this problem. Can anyone offer any further suggestions or help? Is there a better forum to raise this issue in? I''m at my wits'' end here. Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk == PGP key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- Nothing wrong with being written in Perl... Some of my best --- friends are written in Perl. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
[ using vif-route with hvm domains ] On Wed, Dec 06, 2006 at 02:39:31PM +0000, Hugo Mills wrote:> I''m still having this problem. Can anyone offer any further > suggestions or help? Is there a better forum to raise this issue in? > I''m at my wits'' end here.Well, I made it work and I sent what I did already. Did you actually try those suggestions? If you can''t get those suggestions to work then I''d suggest installing xen-unstable from source and see if you can replicate the problem. The developers are much more likely to listen to problems if reported against xen-unstable. -- Nick Craig-Wood <nick@craig-wood.com> -- http://www.craig-wood.com/nick _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Dec 06, 2006 at 03:12:23PM +0000, Nick Craig-Wood wrote:> [ using vif-route with hvm domains ] > > On Wed, Dec 06, 2006 at 02:39:31PM +0000, Hugo Mills wrote: > > I''m still having this problem. Can anyone offer any further > > suggestions or help? Is there a better forum to raise this issue in? > > I''m at my wits'' end here. > > Well, I made it work and I sent what I did already. Did you actually > try those suggestions?Yes, I did -- see my reply to your mail.> If you can''t get those suggestions to work then I''d suggest installing > xen-unstable from source and see if you can replicate the problem. > The developers are much more likely to listen to problems if reported > against xen-unstable.After I sent the last email, I realised that one aspect of my system was unusual. It turns out that something -- I haven''t worked out what yet (probably xend) -- requires and assumes the existence of eth0. I normally have my "eth0" device renamed to "wired", and my "eth1" device to "wireless". If I boot the machine without using nameif to change the device names, then the Xen route scripts allow a domU to start, and I can then configure the networking manually. Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk == PGP key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- Q: What goes, "Pieces of seven! Pieces of seven!"? A: --- A parroty error. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, I have a machine running xen 3.0.1, I''ve just been assigned a new IP range to use as I''ve filled up the old one. They are on a different subnet mask. I''ve tried setting up the interfaces like I did before but it''s not working. Do I need to setup a new bridge on Dom0 or something? I''ll really stumped as to what to do. Please help. In my xen config file for the new vps I tried setting:- netmask = ''NEWNUMBER'' On the new vps itself, ifcfg-eth0 is set with the new netmask. It loads saying everything is ok, but then I cant ping or anything. I haven''t setup anything on dom0 that references the new netmask, so I''m guessing that''s the problem but have no idea what to do. Pls help. P.S. I''m still going to be using the old IP range and netmask as well. I need to use both. Also, on a side note. Is there an easy way for me to upgrade to the latest version without physical access? My machine is co-located, so I only have SSH and can''t afford any downtime for my sites. Lyle ------------------------------------------------------------ Lyle Hopkins - CosmicPerl.com CGI Scripts - Internet software solutions for the professional webmaster Email: webmaster@cosmicperl.com Web site: http://www.cosmicperl.com Specializing in Affiliate Software solutions ------------------------------------------------------------ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, How would I add a cdrom to a running windows domU ? Is there a command to add a ISO image as a cdrom ? Thanks Tonino _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
No worries. Turns out the problem was with the gateway being in a different subnet. All working now. Lyle ------------------------------------------------------------ Lyle Hopkins - CosmicPerl.com CGI Scripts - Internet software solutions for the professional webmaster Email: webmaster@cosmicperl.com Web site: http://www.cosmicperl.com Specializing in Affiliate Software solutions ------------------------------------------------------------ ----- Original Message ----- From: "Xen" <xen@cosmicnetworks.com> To: <xen-users@lists.xensource.com> Sent: Wednesday, December 06, 2006 4:48 PM Subject: [Xen-users] Using two IP ranges on separate netmasks> Hi, > I have a machine running xen 3.0.1, I''ve just been assigned a new IPrange> to use as I''ve filled up the old one. They are on a different subnet mask. > I''ve tried setting up the interfaces like I did before but it''s notworking.> > Do I need to setup a new bridge on Dom0 or something? I''ll really stumpedas> to what to do. Please help. > > In my xen config file for the new vps I tried setting:- > netmask = ''NEWNUMBER'' > On the new vps itself, ifcfg-eth0 is set with the new netmask. It loads > saying everything is ok, but then I cant ping or anything. > > I haven''t setup anything on dom0 that references the new netmask, so I''m > guessing that''s the problem but have no idea what to do. Pls help. > > P.S. I''m still going to be using the old IP range and netmask as well. I > need to use both. > > > Also, on a side note. Is there an easy way for me to upgrade to the latest > version without physical access? My machine is co-located, so I only have > SSH and can''t afford any downtime for my sites. > > > Lyle > > ------------------------------------------------------------ > Lyle Hopkins - CosmicPerl.com CGI Scripts - > Internet software solutions for the professional webmaster > Email: webmaster@cosmicperl.com > Web site: http://www.cosmicperl.com > Specializing in Affiliate Software solutions > ------------------------------------------------------------ > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ 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 TAG > Sent: Wednesday, December 06, 2006 11:10 AM > To: xen-users@lists.xensource.com > Subject: [Xen-users] adding a cdrom > > > Hi, > > How would I add a cdrom to a running windows domU ? > > Is there a command to add a ISO image as a cdrom ? > > Thanks > ToninoAssuming a domain_id of 14 which is found by running xm list xm block-attach 14 file://iso/dm_5_1_windows_server.ISO /dev/hdd ro _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi,>> How would I add a cdrom to a running windows domU ? >> >> Is there a command to add a ISO image as a cdrom ?> Assuming a domain_id of 14 which is found by running xm list > xm block-attach 14 file://iso/dm_5_1_windows_server.ISO /dev/hdd rothen how does the windows OS see this ? Thanks Tonino _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 7 Dec 2006 at 7:06, TAG wrote:> Hi, > > >> How would I add a cdrom to a running windows domU ? > >> > >> Is there a command to add a ISO image as a cdrom ? > > > Assuming a domain_id of 14 which is found by running xm list > > xm block-attach 14 file://iso/dm_5_1_windows_server.ISO /dev/hdd ro > > then how does the windows OS see this ?As a new IDE drive I''d guess. Why not try? Ulrich _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>> >> How would I add a cdrom to a running windows domU ? >> >> >> >> Is there a command to add a ISO image as a cdrom ? >> >> > Assuming a domain_id of 14 which is found by running xm list >> > xm block-attach 14 file://iso/dm_5_1_windows_server.ISO /dev/hdd ro >> >> then how does the windows OS see this ? > > As a new IDE drive I''d guess. Why not try?sorry, I did try and I could not see the device in windows, even under disk management. Thanks _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Dec 06, 2006 at 04:39:48PM +0000, Hugo Mills wrote:> After I sent the last email, I realised that one aspect of my > system was unusual. It turns out that something -- I haven''t worked > out what yet (probably xend) -- requires and assumes the existence of > eth0. I normally have my "eth0" device renamed to "wired", and my > "eth1" device to "wireless". If I boot the machine without using > nameif to change the device names, then the Xen route scripts allow a > domU to start, and I can then configure the networking manually.Ah... You need to name the netdev in /etc/xen/xend-config.sxp Eg (network-script ''network-route netdev=wired'') -- Nick Craig-Wood <nick@craig-wood.com> -- http://www.craig-wood.com/nick _______________________________________________ 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 TAG > Sent: Thursday, December 07, 2006 1:27 AM > To: xen-users@lists.xensource.com > Subject: RE: [Xen-users] adding a cdrom > > > > >> >> How would I add a cdrom to a running windows domU ? > >> >> > >> >> Is there a command to add a ISO image as a cdrom ? > >> > >> > Assuming a domain_id of 14 which is found by running xm list xm > >> > block-attach 14 file://iso/dm_5_1_windows_server.ISO /dev/hdd ro > >> > >> then how does the windows OS see this ? > > > > As a new IDE drive I''d guess. Why not try? > > sorry, I did try and I could not see the device in windows, > even under disk management. >If you run "xm block-list dom_id" does the new device show up as being attached? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Dec 07, 2006 at 11:46:25AM +0000, Nick Craig-Wood wrote:> On Wed, Dec 06, 2006 at 04:39:48PM +0000, Hugo Mills wrote: > > After I sent the last email, I realised that one aspect of my > > system was unusual. It turns out that something -- I haven''t worked > > out what yet (probably xend) -- requires and assumes the existence of > > eth0. I normally have my "eth0" device renamed to "wired", and my > > "eth1" device to "wireless". If I boot the machine without using > > nameif to change the device names, then the Xen route scripts allow a > > domU to start, and I can then configure the networking manually. > > Ah... You need to name the netdev in /etc/xen/xend-config.sxp > > Eg > > (network-script ''network-route netdev=wired'')Ah, gotcha. Thanks for that. For the record, I also found that I needed to set the same option for vif-script in the xend-config.sxp. Now all I have to work out is why it''s still trying to use vifD.X for the relevant interface in the dom0, instead of tapY. At the moment, I''m having to configure that bit manually. As you pointed out[1], though, that seems to be a bug. Hugo. [1] http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=584 -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk == PGP key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- Hey, Virtual Memory! Now I can have a *really big* ramdisk! --- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Did anyone find a solution for this? I''m having the same issue. -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Alain Black Sent: Thursday, December 07, 2006 8:29 AM To: tag@reaper.org; xen-users@lists.xensource.com Subject: RE: [Xen-users] adding a cdrom> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of TAG > Sent: Thursday, December 07, 2006 1:27 AM > To: xen-users@lists.xensource.com > Subject: RE: [Xen-users] adding a cdrom > > > > >> >> How would I add a cdrom to a running windows domU ? > >> >> > >> >> Is there a command to add a ISO image as a cdrom ? > >> > >> > Assuming a domain_id of 14 which is found by running xm list xm > >> > block-attach 14 file://iso/dm_5_1_windows_server.ISO /dev/hdd ro > >> > >> then how does the windows OS see this ? > > > > As a new IDE drive I''d guess. Why not try? > > sorry, I did try and I could not see the device in windows, > even under disk management. >If you run "xm block-list dom_id" does the new device show up as being attached? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hugo Mills wrote:> On Thu, Dec 07, 2006 at 11:46:25AM +0000, Nick Craig-Wood wrote: >> On Wed, Dec 06, 2006 at 04:39:48PM +0000, Hugo Mills wrote: >>> After I sent the last email, I realised that one aspect of my >>> system was unusual. It turns out that something -- I haven''t worked >>> out what yet (probably xend) -- requires and assumes the existence of >>> eth0. I normally have my "eth0" device renamed to "wired", and my >>> "eth1" device to "wireless". If I boot the machine without using >>> nameif to change the device names, then the Xen route scripts allow a >>> domU to start, and I can then configure the networking manually. >> Ah... You need to name the netdev in /etc/xen/xend-config.sxp >> >> Eg >> >> (network-script ''network-route netdev=wired'') > > Ah, gotcha. Thanks for that. For the record, I also found that I > needed to set the same option for vif-script in the xend-config.sxp.Hi Hugo and Nick, I just wanted to say thanks for documenting this issue. It helped me to get around the same problem on my system, and i have been pulling my hair out over it for hours! Regards, Paul <http://paulgear.webhop.net> -- A: Because it breaks the logical sequence of discussion. Q: Why shouldn''t i write my replies at the top of emails? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users