Comments for technomasochism http://twobit.us/blog and two-wheeled vehicles Wed, 18 Jan 2012 23:51:09 +0000 hourly 1 http://wordpress.org/?v=3.2.1 Comment on Xen Network Driver Domain: How by Philip http://twobit.us/blog/2010/07/xen-network-driver-domain-how/comment-page-1/#comment-9601 Philip Wed, 18 Jan 2012 23:51:09 +0000 http://twobit.us/blog/?p=636#comment-9601 Well once you pass the network hardware through to the nicdom it won't show up in dom0 any longer. The networking scripts you're looking at in dom0 shouldn't get run (throw some echo's in there to prove it to yourself). You'll need those same scripts in the nicdom though because that's where they'll be run by the udev rules that you'll need to install in the nicdom as well. Well once you pass the network hardware through to the nicdom it won’t show up in dom0 any longer. The networking scripts you’re looking at in dom0 shouldn’t get run (throw some echo’s in there to prove it to yourself). You’ll need those same scripts in the nicdom though because that’s where they’ll be run by the udev rules that you’ll need to install in the nicdom as well.

]]> Comment on Xen Network Driver Domain: How by allen http://twobit.us/blog/2010/07/xen-network-driver-domain-how/comment-page-1/#comment-9372 allen Sun, 08 Jan 2012 08:20:56 +0000 http://twobit.us/blog/?p=636#comment-9372 Thanks for your attention, Philip, glad for communicating with you about xen. i think about what you said ,but after exporting the network hardware from dom0 to nicdom, i make "ifconfig -a" in domain0, there are three links :lo, pan0, and tmpbridge; But you know ,when starting the xend ,the script of "/etc/xen/scripts/network-bridge ", finds the device eth0 by default, at this time ,there is not eth0 in domian0, so i confused with this , /etc/sysconfig/network-scripts/ifcfg-eth0 configuration file, because in my system ,i can not find it . Thanks for your attention, Philip, glad for communicating with you about xen.
i think about what you said ,but after exporting the network hardware from dom0 to nicdom, i make “ifconfig -a” in domain0, there are three links :lo, pan0, and tmpbridge;
But you know ,when starting the xend ,the script of “/etc/xen/scripts/network-bridge “, finds the device eth0 by default, at this time ,there is not eth0 in domian0, so i confused with this ,
/etc/sysconfig/network-scripts/ifcfg-eth0 configuration file, because in my system ,i can not find it .

]]> Comment on Xen Network Driver Domain: How by Philip http://twobit.us/blog/2010/07/xen-network-driver-domain-how/comment-page-1/#comment-9333 Philip Fri, 06 Jan 2012 19:42:36 +0000 http://twobit.us/blog/?p=636#comment-9333 Thanks Allen, glad this was useful. First off I've never tried th is with an HVM guest. I don't think this will not work unless you have PV network drivers in your client as the driver VM (nicdom) will only offer network services through the netback driver. The error you're seeing in the hotplug log seems to be from attempting to add the virtual interface to the bridge. I'd guess that 'eth0' isn't the name of your bridge, likely that's the physical ethernet device. This may not be the case though because I remember the xen networking scripts doing some crazy stuff renaming interfaces and bridges so it may be that the script stole the name of the ethernet interface and gave it to the bridge. Regardless I'd check to see that when the script is running eth0 is in fact the device you think it is (the bridge). Good luck and let me know how your experiment turns out. If you're using a more recent version of Xen let me know. I'd love to update this howto for the latest Xen version soon. Thanks Allen, glad this was useful. First off I’ve never tried th is with an HVM guest. I don’t think this will not work unless you have PV network drivers in your client as the driver VM (nicdom) will only offer network services through the netback driver.

The error you’re seeing in the hotplug log seems to be from attempting to add the virtual interface to the bridge. I’d guess that ‘eth0′ isn’t the name of your bridge, likely that’s the physical ethernet device. This may not be the case though because I remember the xen networking scripts doing some crazy stuff renaming interfaces and bridges so it may be that the script stole the name of the ethernet interface and gave it to the bridge. Regardless I’d check to see that when the script is running eth0 is in fact the device you think it is (the bridge).

Good luck and let me know how your experiment turns out. If you’re using a more recent version of Xen let me know. I’d love to update this howto for the latest Xen version soon.

]]> Comment on Xen Network Driver Domain: How by allen http://twobit.us/blog/2010/07/xen-network-driver-domain-how/comment-page-1/#comment-9321 allen Fri, 06 Jan 2012 06:18:01 +0000 http://twobit.us/blog/?p=636#comment-9321 Great post! I tried to follow this setting 3 virtual machines( dom0, nicdom, client domain in HVM )with Xen and Debian, but I’m still having some truble. I’ve followed the guide till “udev events”, and i make "xm network-attach client mac=XX:XX:XX:XX:XX:XX,backend=nicdom", but i get this error: Error: Device 0 (vif) could not be connected. Hotplug scripts not working. so i looked at the /etc/xen/xen-hotplug.log, the error is "can`t add vif1.0 to bridge eth0: Operation not supported". Am i missing something? The followings are my udev rules, scripts: 1./etc/udev:hdparm.rules, pcmcia.rules 2./etc/xen/scripts Great post!
I tried to follow this setting 3 virtual machines( dom0, nicdom, client domain in HVM )with Xen and Debian, but I’m still having some truble.
I’ve followed the guide till “udev events”, and i make “xm network-attach client mac=XX:XX:XX:XX:XX:XX,backend=nicdom”, but i get this error:
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
so i looked at the /etc/xen/xen-hotplug.log, the error is “can`t add vif1.0 to bridge eth0: Operation not supported”.
Am i missing something?
The followings are my udev rules, scripts:
1./etc/udev:hdparm.rules, pcmcia.rules
2./etc/xen/scripts

]]> Comment on Kawasaki ZRX KYB shocks on ’04 Thruxton by Philip http://twobit.us/blog/2011/05/zrx-kyb-shocks-on-04-thruxto/comment-page-1/#comment-9088 Philip Sat, 24 Dec 2011 22:10:58 +0000 http://twobit.us/blog/?p=1067#comment-9088 I had these things back up on ebay pretty quick. Lost a few bucks on them but I got back enough to cover the Icon 7614s that I bought instead. The Icons aren't bad but I really had my heart set on the KYBs mostly because the piggybacks looked cool. I had these things back up on ebay pretty quick. Lost a few bucks on them but I got back enough to cover the Icon 7614s that I bought instead. The Icons aren’t bad but I really had my heart set on the KYBs mostly because the piggybacks looked cool.

]]> Comment on Kawasaki ZRX KYB shocks on ’04 Thruxton by Nick Serrano http://twobit.us/blog/2011/05/zrx-kyb-shocks-on-04-thruxto/comment-page-1/#comment-9085 Nick Serrano Sat, 24 Dec 2011 15:37:21 +0000 http://twobit.us/blog/?p=1067#comment-9085 That is a shame that those KYB's didn't work. They look great. Do you still have them? That is a shame that those KYB’s didn’t work. They look great. Do you still have them?

]]> Comment on EliteBook 2560p Intel 82579LM Debian Squeeze Install by attila lendvai http://twobit.us/blog/2011/08/elitebook-2560p-intel-82579lm-debian-squeeze-install/comment-page-1/#comment-7779 attila lendvai Fri, 30 Sep 2011 18:19:19 +0000 http://twobit.us/blog/?p=1321#comment-7779 thanks a lot for the info, got to this post after about an hour of struggling. an unfortunate situation that i first netinstall a debian, and on a hw that is not supported -- didn't know whether my expectations are wrong or the installer. here's the homepage for those unofficial images: http://kmuto.jp/debian/d-i/ thanks a lot for the info, got to this post after about an hour of struggling.

an unfortunate situation that i first netinstall a debian, and on a hw that is not supported — didn’t know whether my expectations are wrong or the installer.

here’s the homepage for those unofficial images:

http://kmuto.jp/debian/d-i/

]]> Comment on Xen Network Driver Domain: How by Useful Materials for Linux Network and Xen Drivers « De.LI.ghen.cE's Blog http://twobit.us/blog/2010/07/xen-network-driver-domain-how/comment-page-1/#comment-7240 Useful Materials for Linux Network and Xen Drivers « De.LI.ghen.cE's Blog Thu, 25 Aug 2011 05:43:48 +0000 http://twobit.us/blog/?p=636#comment-7240 [...] – Xen Network Driver Domain: How Like this:LikeBe the first to like this [...] [...] – Xen Network Driver Domain: How Like this:LikeBe the first to like this [...]

]]> Comment on Xen Network Driver Domain: How by Useful Materials for Linux Network « De.LI.ghen.cE's Blog http://twobit.us/blog/2010/07/xen-network-driver-domain-how/comment-page-1/#comment-7237 Useful Materials for Linux Network « De.LI.ghen.cE's Blog Thu, 25 Aug 2011 05:29:58 +0000 http://twobit.us/blog/?p=636#comment-7237 [...] Philip – Xen Network Driver Domain: How [...] [...] Philip – Xen Network Driver Domain: How [...]

]]> Comment on Another Go at My Masters Project by technomasochism - sVirt-like prototype http://twobit.us/blog/2011/05/another-go-at-my-masters-project/comment-page-1/#comment-7071 technomasochism - sVirt-like prototype Mon, 15 Aug 2011 00:53:55 +0000 http://twobit.us/blog/?p=995#comment-7071 [...] my first post under my MastersProject tag I laid out some of the justification for why separating QEMU instances [...] [...] my first post under my MastersProject tag I laid out some of the justification for why separating QEMU instances [...]

]]>