Re: [CentOS-virt] CentOS Images on AWS with partitions on /dev/xvda1 are awkwared to resize
On Wed, Apr 29, 2015 at 11:33 PM, Kelly Prescott kpresc...@coolip.net wrote: to follow-up, I will give an example. Here is the listing for the official centos AMI: IMAGE ami-96a818feaws-marketplace/CentOS 7 x86_64 (2014_09_29) EBS HVM-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-d2a117ba.2 aws-marketplace available public [marketplace: aw0evgkw8e5c1q413zgy5pjce] x86_64 machineebs hvm xen BLOCKDEVICEMAPPING EBS /dev/sda1 snap-591037fd 8 false standardNot Encrypted as you can see the block device mapping is by default set to BLOCKDEVICEMAPPING EBS /dev/sda1 snap-591037fd 8 false standardNot Encrypted it is a standard volume, not encrypted, and 8 GB my modification consists in adding this to my run command for my ami launch: -b /dev/sda1=snap-591037fd:20:false:gp2 I set the drive the same, the snapshot the same, and I give it 20GB instead of 8, I also use the gp2 type instead of the standard as well as telling it not to delete the volume when the instance terminates. Hope this helps. kp Perhaps so, and I appreciate the pointer. I can try to work with that to integrate command line based deployment and get this option. So you're working from the command line tools in the EPEL 'cloud-init' package, not the AWS GUI? Because when I tried expanding the size of the base disk image in the GUI, I wound up with an an 8 Gig default /dev/xvda1 on a 20 Gig /dev/xvda. That's why I was looking at how do I resize this thing safel? Unfortunately, it doesn't help a lot with what I already have built, but could be useful going forward. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] CentOS Images on AWS with partitions on /dev/xvda1 are awkwared to resize
I think the command-line is far more flexable then the GUI interface. I use ec2-api-tools, but the python boto stuff works virtually the same. On Thu, 30 Apr 2015, Nico Kadel-Garcia wrote: On Wed, Apr 29, 2015 at 11:33 PM, Kelly Prescott kpresc...@coolip.net wrote: to follow-up, I will give an example. Here is the listing for the official centos AMI: IMAGE ami-96a818feaws-marketplace/CentOS 7 x86_64 (2014_09_29) EBS HVM-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-d2a117ba.2 aws-marketplace available public [marketplace: aw0evgkw8e5c1q413zgy5pjce] x86_64 machineebs hvm xen BLOCKDEVICEMAPPING EBS /dev/sda1 snap-591037fd 8 false standardNot Encrypted as you can see the block device mapping is by default set to BLOCKDEVICEMAPPING EBS /dev/sda1 snap-591037fd 8 false standardNot Encrypted it is a standard volume, not encrypted, and 8 GB my modification consists in adding this to my run command for my ami launch: -b /dev/sda1=snap-591037fd:20:false:gp2 I set the drive the same, the snapshot the same, and I give it 20GB instead of 8, I also use the gp2 type instead of the standard as well as telling it not to delete the volume when the instance terminates. Hope this helps. kp Perhaps so, and I appreciate the pointer. I can try to work with that to integrate command line based deployment and get this option. So you're working from the command line tools in the EPEL 'cloud-init' package, not the AWS GUI? Because when I tried expanding the size of the base disk image in the GUI, I wound up with an an 8 Gig default /dev/xvda1 on a 20 Gig /dev/xvda. That's why I was looking at how do I resize this thing safel? Unfortunately, it doesn't help a lot with what I already have built, but could be useful going forward. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] CentOS Images on AWS with partitions on /dev/xvda1 are awkwared to resize
So you're working from the command line tools in the EPEL 'cloud-init' package, not the AWS GUI? Because when I tried expanding the size of the base disk image in the GUI, I wound up with an an 8 Gig default /dev/xvda1 on a 20 Gig /dev/xvda. That's why I was looking at how do I resize this thing safel? No experience with amazon here, but I routinely resize filesystems online without issues. Repartition xvda so that xvda1 is the size you want (make sure you use the same start sector, just change the end of the partition). Run partprobe and confirm that fdisk -l /dev/xvda1 shows the new size. (You may need to reboot). After that just run resize2fs /dev/xvda1 (works online). - Nathan ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] ipv6 routing problem
I have centos 6 running kvm. IPv4 works perfectly works. But I am having some problem with ipv6, looks like its bridge routing problem but stuck. here are my bridge detail: bridge name bridge id STP enabled interfaces br0 8000.000af75613f2 no eth1 vnet1 br4 8000.000af75613f0 no eth0 ip -6 route shows : unreachable ::/96 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 unreachable :::0.0.0.0/96 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 unreachable 2002:a00::/24 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 unreachable 2002:7f00::/24 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 unreachable 2002:a9fe::/32 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 unreachable 2002:ac10::/28 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 unreachable 2002:c0a8::/32 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 unreachable 2002:e000::/19 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 2a00:c88:4000:1431::/64 dev br0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 2a00:c88:4000:1650::/64 dev br4 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 unreachable 3ffe:::/32 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 fe80::/64 dev vnet0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev vnet1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev vnet2 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev vnet3 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev br0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev br4 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 default via 2a11:c99:4111:110::11:211 dev br4 metric 1 mtu 1500 advmss 1440 hoplimit 4294967295 Then I added, /etc/sysconfig/network-script/ifcfg-br4 DEVICE=br4 TYPE=Bridge ONBOOT=yes BOOTPROTO=static IPADDR=ipv4address here NETMASK=255.255.255.0 DNS1=mydnsserver.org DELAY=0 NM_CONTROLLED=no IPV6INIT=yes IPV6_AUTOCONF=no #IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=yes IPV6ADDR=2a11:c99:4111:110::11:65/64 IPV6_DEFAULTGW= 2a11:c99:4111:110::11:211 I can ping the gateway from the kvm host but I cannot ping6 out from the kvm guest, also I cannot ping kvm guest from external host that is in ipv6 network. I appreciate some guidance on this. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
