Re: [CentOS] KVM Questions
On 05/08/2015 11:41 PM, James Hogarth wrote: was wondering if this procedure might work to do what I desire: 1.) Shutdown the VMs 2.) Archive the VM image directory /home/vmimages to a network drive 3.) Use parted or fdisk to delete present /home partition 4.) Use parted or fdisk to re-create smaller/home partition and new vm-images 5.) Create XFS file system on /home and /vm-images 6.) Extact VM image directory archive into /vm-images 7.) Use virt-manager to change default location of images to /vm-images Is there any chance that after all this the VMs would actually start up again especially after a re-boot? They are just disk images so as long as you don't mind deleting home then this will work. So it turns out this was even easier than I expected. The home partition was actually built upon LVM so some relatively simple use of LVM allowed me to do exactly what I wanted. However I have some very subtle issue that I don't understand. virt-manager, df and du incorrectly think this: df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/centos_mric--srv2-root52403200 5717192 46686008 11% / devtmpfs 163782200 16378220 0% /dev tmpfs 16388924 88 16388836 1% /dev/shm tmpfs 16388924 9224 16379700 1% /run tmpfs 163889240 16388924 0% /sys/fs/cgroup /dev/mapper/centos_mric--srv2-home 43337856032928 433345632 1% /home /dev/sda1 508588 219764288824 44% /boot /dev/mapper/centos_mric--srv2-vm--images 67858700 16294864 51563836 25% /vm-images du -k /vm-images 16261904/vm-images But ls has it correct: ls -alt /vm-images total 16261908 -rw---. 1 qemu qemu 51547734016 May 9 15:15 centos7.0-1.qcow2 -rw---. 1 qemu qemu 12887130112 May 9 15:15 centos7.0.qcow2 drwxr-xr-x. 21 root root4096 May 9 15:13 .. drwxr-xr-x. 2 root root 52 May 9 13:39 . Any idea how I make this correct? There are no side effects that I see but it is extremely puzzling to me as to why the new partition does not have the correct size. It appears the larger of the two VM images is not getting counted. -- Paul (ga...@nurdog.com) (303)257-5208 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ldap host attribute is ignored
On May 8, 2015, at 11:14 AM, Ulrich Hiller hil...@mpia-hd.mpg.de wrote: /etc/pam.d/system-auth: --- #%PAM-1.0 # This file is auto-generated. # User changes will be destroyed the next time authconfig is run. authrequired pam_env.so authsufficientpam_unix.so nullok try_first_pass authrequisite pam_succeed_if.so uid = 200 quiet_success authsufficientpam_sss.so use_first_pass authrequired pam_deny.so authrequiredpam_env.so authoptionalpam_gnome_keyring.so account required pam_unix.so broken_shadow account sufficientpam_succeed_if.so uid 2000 quiet account [default=bad success=ok user_unknown=ignore] pam_sss.so account required pam_permit.so account requisite pam_unix.so try_first_pass account sufficient pam_localuser.so account requiredpam_sss.so use_first_pass account sufficient pam_localuser.so passwordrequisite pam_pwquality.so try_first_pass local_users_only retry=3 authtok_type= passwordsufficientpam_unix.so md5 shadow nullok try_first_pass use_authtok passwordsufficientpam_sss.so use_authtok passwordrequired pam_deny.so passwordrequisite pam_cracklib.so passwordoptionalpam_gnome_keyring.souse_authtok passwordsufficient pam_unix.so use_authtok nullok shadow try_first_pass passwordrequiredpam_sss.so use_authtok session optional pam_keyinit.so revoke session required pam_limits.so -session optional pam_systemd.so session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid session required pam_unix.so session sufficient pam_sss.so session requiredpam_unix.so try_first_pass session optionalpam_umask.so session optionalpam_gnome_keyring.soauto_start only_if=gdm,gdm-password,lxdm,lightdm Is it normal to have pam_unix and pam_sss twice for each each section? -- Jonathan Billings billi...@negate.org ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] KVM Questions
Am 09.05.2015 um 23:19 schrieb Paul R. Ganci ga...@nurdog.com: On 05/08/2015 11:41 PM, James Hogarth wrote: was wondering if this procedure might work to do what I desire: 1.) Shutdown the VMs 2.) Archive the VM image directory /home/vmimages to a network drive 3.) Use parted or fdisk to delete present /home partition 4.) Use parted or fdisk to re-create smaller/home partition and new vm-images 5.) Create XFS file system on /home and /vm-images 6.) Extact VM image directory archive into /vm-images 7.) Use virt-manager to change default location of images to /vm-images Is there any chance that after all this the VMs would actually start up again especially after a re-boot? They are just disk images so as long as you don't mind deleting home then this will work. So it turns out this was even easier than I expected. The home partition was actually built upon LVM so some relatively simple use of LVM allowed me to do exactly what I wanted. However I have some very subtle issue that I don't understand. virt-manager, df and du incorrectly think this: df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/centos_mric--srv2-root52403200 5717192 46686008 11% / devtmpfs 163782200 16378220 0% /dev tmpfs 16388924 88 16388836 1% /dev/shm tmpfs 16388924 9224 16379700 1% /run tmpfs 163889240 16388924 0% /sys/fs/cgroup /dev/mapper/centos_mric--srv2-home 43337856032928 433345632 1% /home /dev/sda1 508588 219764288824 44% /boot /dev/mapper/centos_mric--srv2-vm--images 67858700 16294864 51563836 25% /vm-images du -k /vm-images 16261904 /vm-images But ls has it correct: ls -alt /vm-images total 16261908 -rw---. 1 qemu qemu 51547734016 May 9 15:15 centos7.0-1.qcow2 -rw---. 1 qemu qemu 12887130112 May 9 15:15 centos7.0.qcow2 drwxr-xr-x. 21 root root4096 May 9 15:13 .. drwxr-xr-x. 2 root root 52 May 9 13:39 . Any idea how I make this correct? There are no side effects that I see but it is extremely puzzling to me as to why the new partition does not have the correct size. It appears the larger of the two VM images is not getting counted. modern filesystems and image formats do not allocate the whole space if not neccessary (qcow2 feature). -- LF ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] openvpn and firewalld
On Fri, May 8, 2015 12:06, Bowie Bailey wrote: Replying to myself here, I finally figured out how to do it with direct rules. Firewalld on CentOS 7 defaults to a drop rule for the FORWARD chain which my previous server didn't have. So I needed to put the rules in the FORWARD chain rather than the INPUT chain. This does not make sense to me. The INPUT, OUTPUT and FORWARD chains are swimlanes. A packet starts out, following PREROUTING, in exactly one of these three and never leaves it. It can JUMP to shared chains but it will always return to its original chain until ACCEPTed, DROPped or REJECTed. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] KVM Questions
On 05/08/2015 11:41 PM, James Hogarth wrote: Don't forget to virsh edit each domain and update the paths in that. In addition don't forget to fix your selinux contexts: semanage fcontext -a -e /var/lib/libvirt/images /vm-images Thank you for the reminder. My monitor would have taken some verbal abuse but I would have figured it out eventually. :) -- Paul (ga...@nurdog.com) (303)257-5208 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 7 and qemu-kvm
On Sat, May 09, 2015 at 10:11:16AM -0500, Robert Nichols wrote:
On 05/09/2015 08:26 AM, Jerry Geis wrote:
so I installed virt-manager - I have file images and those work.
some times I do directly to a USB connected disk.
I do not see how to do that in virt-manager ???
How do I use a device like /dev/sdh as my disk???
Click on Add Hardware, select Storage, then Select managed or
other existing storage and type /dev/sdh into the box. You can
choose IDE disk or Virtio Disk as the device type, and the
device will be available as /dev/sd? or /dev/vd? accordingly.
Alternatively you might be able to do this using hotswap code. eg I have
a USB based 'scope that I want to pass through to a windows instance.
To do this I have a udev rule:
% cat /etc/udev/rules.d/90-owon.rules
ACTION==add, \
SUBSYSTEM==usb, \
SYSFS{idVendor}==5345, \
SYSFS{idProduct}==1234, \
RUN+=/usr/bin/virsh attach-device XP_VM1 /etc/libvirt/HotPlug/owon.xml
ACTION==remove, \
SUBSYSTEM==usb, \
SYSFS{idVendor}==5345, \
SYSFS{idProduct}==1234, \
RUN+=/usr/bin/virsh detach-device XP_VM1 /etc/libvirt/HotPlug/owon.xml
Then the 'owon.xml' file determines the device as seen by the VM:
% cat /etc/libvirt/HotPlug/owon.xml
hostdev mode='subsystem' type='usb'
source
vendor id='0x5345'/
product id='0x1234'/
/source
/hostdev
This passes the USB device 'raw' through to the VM. For Windows this
means I can load the native drivers and it'll look like I've plugged
the 'scope directly into the windows machine.
Pretty sure something like this would work for hotswap disks as well.
Just make sure the Vendor/product ID numbers match the device you're
plugging in!
--
rgds
Stephen
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 7 and qemu-kvm
On 05/09/2015 08:26 AM, Jerry Geis wrote: Still trying to migrate to CentOS 7. I used to use qemu-kvm on centos 6. tried to compile on centos 7 and get error about undefined reference to timer_gettime searching for that says basically use virt-manager so I installed virt-manager - I have file images and those work. some times I do directly to a USB connected disk. I do not see how to do that in virt-manager ??? How do I use a device like /dev/sdh as my disk??? Click on Add Hardware, select Storage, then Select managed or other existing storage and type /dev/sdh into the box. You can choose IDE disk or Virtio Disk as the device type, and the device will be available as /dev/sd? or /dev/vd? accordingly. -- Bob Nichols NOSPAM is really part of my email address. Do NOT delete it. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Q: respecting .ssh/id_rsa
On Fri, May 8, 2015 13:23, m.r...@5-cent.us wrote: Devin Reade wrote: --On Friday, May 08, 2015 09:58:32 AM -0400 James B. Byrne byrn...@harte-lyne.ca wrote: While attempting to debug something else I ran across this: ssh -vvv somehost . . . debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/identity-cert type -1 debug3: Not a RSA1 key file /root/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace [snip] The password-less connections complete in any case but I am perplexed as to what is the problem with the root identity key that ssh is reporting. Can anyone explain to me what this means? IIRC there was a time when id_rsa could refer to either an RSA1 key or RSA2 key. I believe ssh is first trying to read the file as an RSA1 key, finding problems, and then opening it as an RSA2 key. In fact, if you scroll down from there you probably see a line like the following: debug1: identity file /home/somebody/.ssh/id_rsa type 1 which is a successful read (note the type is 1 and not -1). In other words, it's nothing to worry about. The messages are a bit different under CentOS 7 (I suspect you're running CentOS 6 on the client), but they say about the same thing. snip I would *strongly* recommend editing your /etc/ssh/sshd_config, and comment or delete the fallback, and replace it, like: #Protocol 2,1 Protocol 2 That way, it won't even try. mark If the problem is indeed a lookup on id_rsa for an rsa1 type key then the setting you suggest does not prevent it. All of the sshd_conf files in our CentOS-6 systems already have that set and I believe that it is the default setting for the distro. # Disable legacy (protocol version 1) support in the server for new # installations. In future the default will change to require explicit # activation of protocol 1 Protocol 2 However, your suggestion causes me to consider whether or not there is a similar setting for ssh_config. The problematic key lookup occurs on the client side of the connection. It seems unlikely that sshd server settings on client host would have much of an effect. Indeed there is no reason to suppose that sshd is even present. Respecting the other recommendations offered in various messages: These are, insofar as I can determine, already in effect. There are no AVCs reported, the ssh connections complete as expected, and there are no odd messages in /var/log/secure or /var/log/messages. The user in this case is root. The problem being debugged was automated internal network rsync transfers over ssh. All permissions, contexts and ownerships of the associated files and directories are as they were originally created by ssh-keygen. It seems to me likely that these messages are the result of code in the client application which simply reports and ploughs on when it runs into a file format it is not expecting leaving the final determination of whether or not the encounter is an error condition to somewhere later in the program. Thank you for the guidance. P.S. Also thanks for the info on SYN in ACK, . . ., SYN. Due to the problems some on the list are having with my emails I now find myself avoiding simple acknowledgements of help given. But it is gratefully received nonetheless. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Centos 7 and qemu-kvm
Still trying to migrate to CentOS 7. I used to use qemu-kvm on centos 6. tried to compile on centos 7 and get error about undefined reference to timer_gettime searching for that says basically use virt-manager so I installed virt-manager - I have file images and those work. some times I do directly to a USB connected disk. I do not see how to do that in virt-manager ??? How do I use a device like /dev/sdh as my disk??? Thanks, Jerry ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 7 and qemu-kvm
On 09.05.2015 15:26, Jerry Geis wrote: Still trying to migrate to CentOS 7. I used to use qemu-kvm on centos 6. tried to compile on centos 7 and get error about undefined reference to timer_gettime searching for that says basically use virt-manager Why are you trying to compile it yourself and not use the version that comes with the OS? Regards, Dennis ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] NFS performance on CentOS 7
I am setting up a file server with CentOS 7. I'm seeing performance which is considerably slower than a similar server running CentOS 6.6. A 3Gb directory can be copied to/from the CentOS 6.6 server in about 50 seconds. The same directory takes about 270 seconds to copy to/from the CentOS 7 system. I see the same performance difference with NFS mounted file systems or using scp, so it doesn't appear to be an NFS issue. The MTU on the NICs on both systems is 1500, and changing it to 6000 on the CentOS 7 system had no effect. Anyone have any ideas what might cause this problem or how to fix it? -- Michael Eagerea...@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] firewalld trouble opening a port
Hey all, I'm having a little trouble opening up a port on a C7 machine. Here's the default zone: [root@appd:~] #firewall-cmd --get-default-zone home So I try to add the port: [root@appd:~] #firewall-cmd --zone=home --add-port=8181/tcp success Then I reload firewalld: [root@appd:~] #firewall-cmd --reload success Simple! That should do it. Right? Well not quite. Cuz when I telnet to that host on that port, it's not connecting: #telnet appd.mydomain.com 8181 Trying xx.xx.xx.xx... ---obscuring the real IP telnet: connect to address xx.xx.xx.xx: Connection refused telnet: Unable to connect to remote host Yet, that port is definitely listening on the host: [root@appd:~] #lsof -i :8181 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME java13423 root 333u IPv6 3526508 0t0 TCP *:intermapper (LISTEN) And if I stop the firewall momentarily : I can telnet to that port from a remote location: #telnet appd.mydomain.com 8181 Trying xx.xx.xx.xx... Connected to appd.mydomain.com. Escape character is '^]'. Of course I bring up the firewall right away once I'm done testing: [root@appd:~] #systemctl start firewalld [root@appd:~] #systemctl status firewalld firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled) Active: active (running) since Sat 2015-05-09 14:56:20 EDT; 7s ago Main PID: 18826 (firewalld) CGroup: /system.slice/firewalld.service └─18826 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid May 09 14:56:20 appd systemd[1]: Started firewalld - dynamic firewall daemon. Any ideas on what I'm doing wrong? Thanks, Tim -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] openvpn and firewalld
On 5/9/2015 8:32 AM, James B. Byrne wrote: On Fri, May 8, 2015 12:06, Bowie Bailey wrote: Replying to myself here, I finally figured out how to do it with direct rules. Firewalld on CentOS 7 defaults to a drop rule for the FORWARD chain which my previous server didn't have. So I needed to put the rules in the FORWARD chain rather than the INPUT chain. This does not make sense to me. The INPUT, OUTPUT and FORWARD chains are swimlanes. A packet starts out, following PREROUTING, in exactly one of these three and never leaves it. It can JUMP to shared chains but it will always return to its original chain until ACCEPTed, DROPped or REJECTed. I was a bit confused when I originally posted. This is the only machine that does forwarding and I haven't touched the iptables setup on it in years. The original machine had a shared chain between INPUT and FORWARD with rules that allowed the traffic. I had forgotten how the INPUT and FORWARD chains worked and didn't realize at first that this was a shared chain, so I was putting the rules in the INPUT chain on the new box, which (of course) didn't work. The other thing that caught me was that the new box has a reject rule at the end of the FORWARD chain that I didn't notice until I did an iptables-save and combed through the rules. Is there a better way to get an overview of ALL the rules with firewalld? None of the firewall-cmd options that I can find will show me that there is a reject rule on the FORWARD chain. -- Bowie ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] firewalld trouble opening a port
On 9 May 2015 at 14:57, Tim Dunphy bluethu...@gmail.com wrote: Hey all, I'm having a little trouble opening up a port on a C7 machine. Here's the default zone: [root@appd:~] #firewall-cmd --get-default-zone home So I try to add the port: [root@appd:~] #firewall-cmd --zone=home --add-port=8181/tcp success Then I reload firewalld: [root@appd:~] #firewall-cmd --reload success Simple! That should do it. Right? Well not quite. Cuz when I telnet to that host on that port, it's not connecting: #telnet appd.mydomain.com 8181 Trying xx.xx.xx.xx... ---obscuring the real IP telnet: connect to address xx.xx.xx.xx: Connection refused telnet: Unable to connect to remote host Yet, that port is definitely listening on the host: [root@appd:~] #lsof -i :8181 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME java13423 root 333u IPv6 3526508 0t0 TCP *:intermapper (LISTEN) And if I stop the firewall momentarily : I can telnet to that port from a remote location: #telnet appd.mydomain.com 8181 Trying xx.xx.xx.xx... Connected to appd.mydomain.com. Escape character is '^]'. Of course I bring up the firewall right away once I'm done testing: [root@appd:~] #systemctl start firewalld [root@appd:~] #systemctl status firewalld firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled) Active: active (running) since Sat 2015-05-09 14:56:20 EDT; 7s ago Main PID: 18826 (firewalld) CGroup: /system.slice/firewalld.service └─18826 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid May 09 14:56:20 appd systemd[1]: Started firewalld - dynamic firewall daemon. Any ideas on what I'm doing wrong? Thanks, Tim -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos I saw that you are doing firewall-cmd --reload; however you did not had the following: firewall-cmd --permanent --zone=home --add-port=8181/tcp The problem is you added the rule in runtime and when you reloaded it removed the rule that you added; therefore you need to use --permanent or do not reload. Let me know if this helps. -- Kind Regards Earl Ramirez ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] firewalld trouble opening a port
Hi Earl, The problem is you added the rule in runtime and when you reloaded it removed the rule that you added; therefore you need to use --permanent or do not reload. Thanks! That worked. [root@appd:~] #firewall-cmd --zone=home --list-ports [root@appd:~] #firewall-cmd --zone=home --add-port=8181/tcp --permanent success [root@appd:~] #firewall-cmd --reload success [root@appd:~] #firewall-cmd --zone=home --list-ports 8181/tcp #telnet appd.mydomain.com 8181 Trying xx.xx.xx.xx... Connected to appd.mydomain.com. Escape character is '^]'. On Sat, May 9, 2015 at 3:14 PM, Earl A Ramirez earlarami...@gmail.com wrote: On 9 May 2015 at 14:57, Tim Dunphy bluethu...@gmail.com wrote: Hey all, I'm having a little trouble opening up a port on a C7 machine. Here's the default zone: [root@appd:~] #firewall-cmd --get-default-zone home So I try to add the port: [root@appd:~] #firewall-cmd --zone=home --add-port=8181/tcp success Then I reload firewalld: [root@appd:~] #firewall-cmd --reload success Simple! That should do it. Right? Well not quite. Cuz when I telnet to that host on that port, it's not connecting: #telnet appd.mydomain.com 8181 Trying xx.xx.xx.xx... ---obscuring the real IP telnet: connect to address xx.xx.xx.xx: Connection refused telnet: Unable to connect to remote host Yet, that port is definitely listening on the host: [root@appd:~] #lsof -i :8181 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME java13423 root 333u IPv6 3526508 0t0 TCP *:intermapper (LISTEN) And if I stop the firewall momentarily : I can telnet to that port from a remote location: #telnet appd.mydomain.com 8181 Trying xx.xx.xx.xx... Connected to appd.mydomain.com. Escape character is '^]'. Of course I bring up the firewall right away once I'm done testing: [root@appd:~] #systemctl start firewalld [root@appd:~] #systemctl status firewalld firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled) Active: active (running) since Sat 2015-05-09 14:56:20 EDT; 7s ago Main PID: 18826 (firewalld) CGroup: /system.slice/firewalld.service └─18826 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid May 09 14:56:20 appd systemd[1]: Started firewalld - dynamic firewall daemon. Any ideas on what I'm doing wrong? Thanks, Tim -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos I saw that you are doing firewall-cmd --reload; however you did not had the following: firewall-cmd --permanent --zone=home --add-port=8181/tcp The problem is you added the rule in runtime and when you reloaded it removed the rule that you added; therefore you need to use --permanent or do not reload. Let me know if this helps. -- Kind Regards Earl Ramirez ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS-virt] iTunes
On 05/09/2015 07:35 AM, Nico Kadel-Garcia wrote: I tend to run Windows natively Hi Nico, The guy's wife is a Junkware magnet. So they were looking to have the base in Linux. SL 7 doesn't support Wine 32, so we were looking at Fedora. -T -- ~~ Computers are like air conditioners. They malfunction when you open windows ~~ ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] iTunes
On 05/09/2015 07:48 AM, PJ Welsh wrote: On Sat, May 9, 2015 at 9:35 AM, Nico Kadel-Garcia nka...@gmail.com mailto:nka...@gmail.com wrote: On Sat, May 9, 2015 at 4:37 AM, ToddAndMargo toddandma...@zoho.com mailto:toddandma...@zoho.com wrote: Hi All, I am putting together a high end workstation quote for a customer. He is going to want a Virtual Machine, specifically so he can run iTunes (his wife buys music through iTunes and sync's them to her iPod). VMware Player may be a good option for you. It's free and has decent USB passthrough support for the type of USB interaction you need. I have not tried as much with Virtual Box to enable passthrough, but it has functioned when I did, also. Thank you. Looks like I will have to learn VMPlayer. -T ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] iTunes
Hi All, I am putting together a high end workstation quote for a customer. He is going to want a Virtual Machine, specifically so he can run iTunes (his wife buys music through iTunes and sync's them to her iPod). So which VM would you guys use? KVM or Virtual Box? I am very familiar with KVM and adore it. It's USB support is kind of weird though (iPod). I have been seriously burned by Virtual Box before and do not care much for the way Oracle does things, so I would have to bite my pride if Virtual Box would be better to run iTunes. (Who knows, maybe Virtual Box has gotten better.) What do you guys think? Many thanks, -T -- ~~ Computers are like air conditioners. They malfunction when you open windows ~~ ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] KVM and USB
Hi All, On KVM, is there a way to pass USB Flash drives automatically to the guest without having to go into virt-manager and selecting the specific USB device? -T -- ~~ Computers are like air conditioners. They malfunction when you open windows ~~ ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] iTunes
On Sat, May 9, 2015 at 9:35 AM, Nico Kadel-Garcia nka...@gmail.com wrote: On Sat, May 9, 2015 at 4:37 AM, ToddAndMargo toddandma...@zoho.com wrote: Hi All, I am putting together a high end workstation quote for a customer. He is going to want a Virtual Machine, specifically so he can run iTunes (his wife buys music through iTunes and sync's them to her iPod). VMware Player may be a good option for you. It's free and has decent USB passthrough support for the type of USB interaction you need. I have not tried as much with Virtual Box to enable passthrough, but it has functioned when I did, also. PJ ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] iTunes
On Sat, May 9, 2015 at 4:37 AM, ToddAndMargo toddandma...@zoho.com wrote: Hi All, I am putting together a high end workstation quote for a customer. He is going to want a Virtual Machine, specifically so he can run iTunes (his wife buys music through iTunes and sync's them to her iPod). For personal laptops or workstations, I tend to run Windows natively for the raw speed of the native apps and to get the latest drivers, and run Scientific Linux in VirtulalBox, which has worked very well. I much prefer the user interface of Virtualbox to the virt-manager suite for KVM or for Xen. It's just been easier, for me, to get tools like the VMware clients or Xencenter for managing *other* virtual environments to work well on Windows, and Outlook for Exchange servers has been critical in too many environments. SL runs very well and robustly in virtualization with all the virtualization technologies. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
