pyvpx: hey, never knew you were in here :) so, centos 7 has a lot different, but it's kinda.. badass. up_the_irons: I may be submitting an ISO request soon :P bring it I'll wait until thy release a "minimal" iso. right now, it's either netboot, or DVD I knew ifconfig and netstat have been "deprecated" for a long time.. but, a minimal C7 install doesn't have them at all now. it requires installing a seperate package. guess it's time to learn the new school :P i have forced myself to use the iproute2 tools and that is what I use out of habit \o/ (except for netstat, but thats because ss' output is ugly) yeah,, I should have done that too. but "ss" is funky I'm going to have to get used to the new interface names, too. oh those i have been getting those on my laptop for a while now I could edit them and set them back to "eth0" but then, I'll find myself in this same boat in the next release. so I may as well just embrace it. I don't see any rhyme or reason for them. on one VM, its in the form of xyz0s5 on the other, its xyz12345678 My desktop at work named its primary Ethernet "eno1", which I hate but I laugh at too. "e no one" it's all alone lol (my thinkpad has wlp2s0 and enp8s0, I have no idea how it arrived at those names, aside from the obvious e/w) (maybe WireLess Port 2 Session 0, and EtherNet Port 8 Session 0, but the port/session bits don't make much sense) Ohhh those match up with the lspci "slots" actually Mystery solved, thanks #arpnetworks right, I haven't found the naming convention yet. I'm sure it means.. something. what about the "np" or "lp" jpalmer: see the capitalized letters WireLess EtherNet s/Session/Slot/ (maybe WireLess Port 2 Slot 0, and EtherNet Port 8 Slot 0, but the port/session bits don't make much sense) OH! got it somewhat less annoying now that I understand the convention.. but still don't understand why they couldn't stick with "eth#" or follow the BSD's convention of "name it after the driver" like em0 or rl0 ditto I suspect th new convention is going to make it more difficult to use things like chef/puppet/ansible. of course, those tools will adapt as well, I'm sure. (probably even before I will) I'm guessing it's supposed to be more descriptive, based on type+location, so you could change out NICs and the new NIC would keep the same name (but then, it would have anyways...) (Well, it would have unless udev had locked the name to the MAC) well, no.. with the /etc/udev/rules.d/70.persistant-rules in EL5 and 6, it wouldn't re-use old interface names if you swap out the NIC ^ already caught that ;) sorry, was typing and talking at same time heh It does solve the same problem as the udev rule though. Many moons ago, sometimes NICs would flip which was eth0 and eth1, (depending on driver load order) yeah, that part is cool. I'm reading about all the changes now. I was wary of the systemd change, but I actually think I'm going to like it. yea, i don't mind systemd at all yeah overall, I think EL7 is going to be a bit of a learning curve (for me) but I think most of it is good stuff. it's my own fault for hanging onto ifconfig, and netstat as long as I did. that's going to be the hardest change for me to hammer home. i didn't know it was being replaced, haha https://www.archlinux.org/news/deprecation-of-net-tools/ 2011-06-08 haha i guess that just shows how infrequently i use ifconfig haha i haven't booted my arch install since april i think I guess I should PRACTICE using ip since ifconfig really had to go I guess its not so bad aside from active development, what's wrong with it? As far as I'm concerned, that's the only reason (and the only reason cited by Arch) ah Means that should there be a kernel API change, there's no central group to release an updated ifconfig (etc), each distro would just pass around a set of patches Also lacks support for new and crazy things. I couldn't tell you what exactly... I do know that ifconfig doesn't show GbE link state (it topped out at 100mbps) (Obviously, we're talking about Linux ifconfig and net-tools. BSD's ifconfig is completely separate, and maintained, and does a lot more than just set IP addresses.) yeah, i guess that's what confused me since i don't really use linux that regularly i have.. 1.5 linux boxes 1 kvm box (which i'd happily swap out for bhyve once it's stable) and 1 raspi I've been meaning to get bhyve up and running now that I have a FreeBSD10 box woo, thunderstorms nice :) yeah, my fav time of year desert thunderstorms are awesome I miss monsoon season Toronto, Ontario :: Scattered Clouds :: 20C nice here today our high today was 36C haha m0unds: same here, and I'm 2hrs from the Canadian border :( i.e. It shouldn't be this fucking hot lol Actually the high was 34C, but we exceeded the high how complicated is it to roll your own kvm server setup on Ubuntu 14.04 without a graphical desktop? umm, not really too hard configure your host network (i just use a bridged interface) and then install libvirt and associated stuffs ditto does the vnc server come standard, or is that an addon install? i didn't have to install anything separately iirc i believe it defaults to incrementally assigning vnc ports too, or you can hard-assign them vnc does come standard you can also use that new thing ahh spice spice is nice if it's just you using it i'd definitely recommend trying spice i can web browse over lan with it without it feeling slow <3 spice i can't say the same about vnc :) and over wan it's good too how do I get libvirt to listen for remote connections? my kvm box has no gui and I am trying to connect with : virt-manager -c qemu://10.10.2.61 no luck maybe it's binding to localhost? try netsta -tnlp ? netstat -tnlp as root it'll show what tcp ports are listening owned by what proceses withjout trying to reverse lookup http://pineapplesoftware.blogspot.ca/2012/11/configuring-unsecure-remote-access-to.html had to be configured explicitly Configuring unsecure remote access to libvirt on Ubuntu using TCP ok can 2 bridges bind to the same physical interface, say eth0 ? Why wouldn't you just use 1 bridge? I am trying to virtualize pfsense and provide 2 distinct nics but use the same physical Sure I get that. But on the host, that could/would still be done with one bridge my attempt at adding a second bridge lead to "empty bridge" I have an interface section like: http://pastebin.com/jnL2S8h4 what do I need to do to get a second interface with that same bridge? (I can't help with libvirt specifics, sorry) Wouldn't you just add another with br0? trying that now brycec: the graphical Virtual Machine Manager had options to add secondary devices and it accepted the bridge used for 2 interfaces Cool ok, now that even centos has officially deprecated ifconfig and the lpi still requires ifconfig for their exams and hasn't heard about iproute, can we deprecate the lpi now, too?