experchange > slackware

James H. Markowitz (11-05-18, 05:48 AM)
I have a Slackware VM that I have taken some time tuning up and
configuring. What I would like to do now is to take the VM and install it
as native in actual iron. If anybody in this forum has tackled this issue
I would be interested to learn about their experiences.
Grant Taylor (11-05-18, 08:20 AM)
On 11/04/2018 08:48 PM, James H. Markowitz wrote:
> I have a Slackware VM that I have taken some time tuning up and
> configuring. What I would like to do now is to take the VM and install
> it as native in actual iron. If anybody in this forum has tackled this
> issue I would be interested to learn about their experiences.


I've not done that particular task. But I have done something similar a
number of times.

Linux is quite forgiving about moving hardware. It's possible, and not
overly difficult, to copy an install from one piece of (virtual)
hardware to another piece of (virtual) hardware.

Make sure that your disks are functionally the same and that your broad
platform type (BIOS vs EFI) is the same. Copy data from the source to
the destination. Install the boot loader. Tweak settings for
differences between the hardware, like the NIC's MAC address.

It's possible to overcome bigger changes (different disk / file system
layout, processor, memory, maybe even BIOS vs EFI) but they do take more
work. I suggest that you stick with as close as reasonably possible
when first trying.

If it helps, I've used this method both personally and professionally
for the last 10+ years. I've successfully restored multiple systems
from full backups using this method many a time. I've also done similar
to restore Solaris systems.
Bit Twister (11-05-18, 10:07 AM)
On Mon, 5 Nov 2018 03:48:55 +0000 (UTC), James H. Markowitz wrote:
> I have a Slackware VM that I have taken some time tuning up and
> configuring. What I would like to do now is to take the VM and install it
> as native in actual iron. If anybody in this forum has tackled this issue
> I would be interested to learn about their experiences.


Hmm, without looking, I would
1. create, format, label target hardware partitions
2. download systemrescuecd.iso from
3. clone the vm
4. attach systemrescuecd.iso to the cloned vm
5. boot the clone, create a mount point, mount the clone's drive
6. Modify /etc/fstab, /etc/hostname, /etc/hosts, network configuration file

You might want to bookmark the following url

and put
copy virtualbox to real hardware
in the box to see what you can see.

And create a check list of any additional steps required to manage the
project.
me (11-06-18, 01:42 AM)
Am Mon, 05 Nov 2018 03:48:55 +0000 schrieb James H. Markowitz:

> I have a Slackware VM that I have taken some time tuning up and
> configuring. What I would like to do now is to take the VM and install
> it as native in actual iron. If anybody in this forum has tackled this
> issue I would be interested to learn about their experiences.


1. Attach the new physical harddrive(s) to your host

2. Mount the virtual disk(s) on your host using (Google: mount vdi)

3. Use dd to clone the virtual disk(s) onto the physical one(s)
Bit Twister (11-06-18, 01:53 AM)
On Mon, 5 Nov 2018 23:42:56 +0000 (UTC), me wrote:
> Am Mon, 05 Nov 2018 03:48:55 +0000 schrieb James H. Markowitz:
> 1. Attach the new physical harddrive(s) to your host
> 2. Mount the virtual disk(s) on your host using (Google: mount vdi)
> 3. Use dd to clone the virtual disk(s) onto the physical one(s)


I would use rsync if it were me. If target drive has other partitions,
dd would wipe the partition table. :(
Grant Taylor (11-06-18, 01:58 AM)
On 11/05/2018 04:42 PM, me wrote:
> 3. Use dd to clone the virtual disk(s) onto the physical one(s)


Be mindful of partition layout changes / size / geometry.

I'd be more inclined to dd a file system than an entire drive. Even
then, you're likely going to need to use FS specific tools to adjust the
size (grow) the file system.
me (11-06-18, 06:04 PM)
Am Mon, 05 Nov 2018 16:58:14 -0700 schrieb Grant Taylor:

> On 11/05/2018 04:42 PM, me wrote:
>> 3. Use dd to clone the virtual disk(s) onto the physical one(s)

> Be mindful of partition layout changes / size / geometry.
> I'd be more inclined to dd a file system than an entire drive. Even
> then, you're likely going to need to use FS specific tools to adjust the
> size (grow) the file system.


Well, I like simple solutions. Therefore I'd prefere to dd an entire
drive first than use (g)parted on the target drive - if necessary at all.
Similar Threads