New answers tagged

1

In your post you are using -cpu host on both the old and the new machine. While generally this shouldn't be a problem when migrating VMs, especially if the new machine has a newer same-brand CPU than the old one. However, in some cases this can still cause issues. You can try to manually specify the CPU type on the new machine to a CPU type that matches the ...


1

Your system is working as intended. You've allocated ~20G RAM to this VM, and your server OS reports its available RAM correctly. If your server is performing slow, it is likely just due to its disk cache needing to be warmed. After a reboot, no disk contents are cached in RAM. As processes read files off of disk, that data gets cached in RAM and future ...


0

HP ProLiant gen8 is quite new and a year ago I couldn't configure any raid because the kernel that was the latest at that moment didn't have the RAID driver required. HP works closely to Microsoft interests. In the gen7 it do work, so I guess it's matter of time that it can work. In the meantime focus on configuring LVM to work as a RAID 1.


0

If your system has only 2 HDDs and you still see 2 HDDs after setting up the RAID1 array, you didn't get it right. After the RAID config is done, you should only see one 500GB HDD. What kind of HP server have you got? Is the RAID controller HPs own (some sort of Smart Array) or aftermarket?


1

You should create a RAID 1 array using your hardware raid controller. It will them present that array to the OS as a single disk. You should then install your OS onto that disk using LVM if you want.


0

You can do almost the same thing that VMware p2v software does. What it does is create the new filesystems on the new system exactly as you want them to be, then do a tar of the filesystems across to the other server. This way you get everything exactly the same, and you are only copying files and space that are currently being used. Then you have to do ...


3

fuser -mv /dev/vg_dev/lv_home should show you the process PID you need to kill to free up the device. For example: # fuser -mv /dev/vg_dev/lv_home USER PID ACCESS COMMAND /dev/vg_dev/lv_home: sbonds 9627 ..c.. bash Now, you may not be able to actually kill it if it's blocked on I/O or some ...


0

Yes, you can shrink/move/grow an online root partition without any reboots (nor livecd, nor usbkey): consult this answer. It's very well written and easy to follow, although quite long and a little risky. This allows to bypass limitation of resize2fs not being able to shrink online ext4 partitions. Of course, if you only want to grow your ext4 partition, ...


0

Yes, you can shrink/move/grow an online root partition without any reboots (nor livecd, nor usbkey): consult this answer. It's very well written and easy to follow, although quite long and a little risky. This allows to bypass limitation of resize2fs not being able to shrink ext4 partitions. Of course, if you only want to grow your ext4 partition, you can ...


0

I think you have a few things mixed up: PV -> physical volume -> usually harddisks or arrays[1] VG -> volume groups -> a pool of one or more PVs put together LV -> logical volumes -> a subset of a VG, exported by LVM So far you don't have any filesystem at all, especially PVs do not contain full filesystems [2] Once you have LV, you treat it like a ...


0

Actually the filesystem is created at the logical volume (LV) level, not at the physical volume one. Physical Volumes are added to Volume Groups, and from there, you can create Logical Volumes inside that Volume Group. After that, you make a filesystem over that logical volume.


1

This happened to me during a dist-upgrade from Debian 7 Wheezy to Debian 8 Jessie, too, where the udev package was already upgraded, but the lvm2 wasn't yet. Upgrading the lvm2 package helped and the lvmcreate command worked fine again.


9

If your existing PV has < 300GB of data If your existing PV has less than 300GB of data on it, then you can simply relocate that data to the front of the disk and then use pvresize. First, create a new pv: pvcreate /dev/sda1 Relocate data from the existing pv onto the new pv: pvmove /dev/sda2 /dev/sda1 Remove the old pv: vgreduce myvg /dev/sda2 ...


0

The datastore ran out of space? You can add more physical storage and increase the datastore. Expect I/O errors and stopped VMs until you do. With enough space to mount the file systems you can delete those files. To resize the physical volumes to something realistic for the disks there is pvresize. There are limitations, in particular: pvresize will ...


0

Rather than commenting out the entire line, it is possible to add the disk partitions you want to add - in my case, I also wanted to add /dev/sdc1, so changed the line to the following: global_filter = [ "a|loop0|", "a|loop1|", "a|sda5|", "a|sdb5|", "a|sdc1|", "r|.*|" ] # from devstack After that, the pvcreate command worked fine. No reboot required. ...



Top 50 recent answers are included