Some links about virtualization
http://cookerspot.tuxfamily.org/wikka.php?wakka=Blog20080716VirtualizationVirtualizationVirtualBox
VirtualizationKVM
cf. http://cookerspot.tuxfamily.org/wikka.php?wakka=VirtualBoxWindows for initial work done to virtualize windows using VirtualBox
Virtualizing Windows XP on disk to VirtualBox
(no success so far, still a black screen :/)For 16 GB : begin at 22h27 of dd, end at 22h38 (apparently I've got 50 MB I/O throughput which should take me approximately 5 minutes to end up, or rather 10 minutes if I/O include read/writes : 16 GB * 1024 / 50 MB/s / 60 seconds * 2 to get the result in minutes )
ok confirmed :
[root@localhost vm]# dd if=/dev/sda1 of=vmwin.dd 34587882+0 enregistrements lus 34587882+0 enregistrements écrits 17708995584 octets (18 GB) copiés, 695,955 s, 25,4 MB/s
cd /media/data1/vm/ mkdir vmwinmount mount -o loop vmwin.dd /media/data1/vm/vmwinmount # and the partition is available for modification
# mount /dev/sda5 on / type ext4 (rw,noatime,acl,commit=600) none on /proc type proc (rw) /dev/sda7 on /media/data1 type ext4 (rw,noatime,acl,commit=600) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) fusectl on /sys/fs/fuse/connections type fusectl (rw) gvfs-fuse-daemon on /home/baud/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=baud) /dev/loop0 on /media/data1/vm/vmwinmount type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096)
du -k ; du -m ; du -h # shows (kB, MB, GB...) 17293952 16889 17G
At approximately 70 MB writing on disk, it should end up in 5 min (well, yes it took 5 min :D)
VBoxManage convertdd vmwin.dd vmwin.vdi Converting from raw image file="vmwin.dd" to file="vmwin.vdi"... Creating dynamic image with size 17708995584 bytes (16889MB)...
first boot of VM newly created using vmwin.vdi results only in a black screen and 1 CPU running at 100% till stopping the VM :/ some possible reasons :
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1016613 boot.ini configured with the parameter /burnmemory = 4096, the RAM is reduced to 4 GB (reduces the RAM another 4 GB, which leaves the virtual machine with 0 GB of RAM o_O)
http://communities.vmware.com/thread/223482 migration with VMware, driver lsilogic vs ide...
Seem the option for VBoxManage has changed:
VBoxManage convertfromraw vmwin.dd vmwin.vdi WARNING: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (3.3.8-desktop-2.mga2) or it failed to load. Please recompile the kernel module and install it by sudo /etc/rc.d/init.d/virtualbox start You will not be able to start VMs until this problem is fixed. Converting from raw image file="vmwin.dd" to file="vmwin.vdi"... Creating dynamic image with size 17708995584 bytes (16889MB)...
reasons for black screen of death when migrating windows xp to VirtualBox
looking for the reason why I've got a black screen, cursor blinking when first booting windows migrated to VirtualBox
apparently not related
https://www.virtualbox.org/ticket/4942 due to upgrade
https://www.virtualbox.org/ticket/1633 due to guest additions
https://forums.virtualbox.org/viewtopic.php?f=2&p=99321 due to upgrade
http://www.itwriting.com/blog/1538-fixing-a-virtualbox-windows-xp-blue-screen.html blue screen when moving VM
intelppm.sys virtualbox
https://www.virtualbox.org/ticket/420
https://www.virtualbox.org/wiki/Migrate_Windows There are a few Windows device drivers that does not play nice on VirtualBox' hardware. A similar problem may exist with intelppm.sys, which can also cause a hang of the guest OS.
Trying yet another time
Some objectives:- using the dd I made of a physical installation (not available any more :/)
- convert it to a VM usable under GNU/Linux
- launch visio for example, office eventually
- map the C: and D: (data, My Documents) drives correctly
- edit necessary .ini files (D: drive for example)
- debug boot even though I get a black-screen of death (there might be some log, somewhere)
- reduce the size of the VM: 12 GB is a bit huge, it corresponds to a dd if=/dev/sda1 of=vmwin.dd there is unused space imho, 4 or even 8 GiB would be better :)
- launch visio on the .dd file from wine ? (using the original registry for example?)
- try p2v with qemu or KVM, maybe VirtualBox will do it in the end?
md5sum vmwin.* 2e795421f05f0140be240182c7e39551 vmwin.dd 066303a8b37a2a178f378413741d838d vmwin.vdi
I made a backup to my USB drive, formatted as ext4 (better for files 12 GiB large... than fat32)
df -h . Sys. fich. Taille Util. Dispo Uti% Monté sur /dev/sda7 50G 44G 4,1G 92% /media/data1
hmmm I won't be able to work on this, copying on another laptop ;-)
some more links
http://communities.vmware.com/message/1671329http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&document=DT_KB_1_1&searchString=p2v other searches
software installed for virtualization
rpm -qa|grep -iE "virt|vbo|emu"|grep -v virtuoso|sort dkms-virtualbox-4.1.18-1.mga2 libvirt0-0.9.10-5.mga2 libvirt-gconfig1.0_0-0.0.7-1.mga2 libvirt-glib1.0_0-0.0.7-1.mga2 libvirt-gobject1.0_0-0.0.7-1.mga2 libvirt-utils-0.9.10-5.mga2 python-libvirt-0.9.10-5.mga2 python-virtinst-0.600.1-1.mga2 qemu-1.0-6.2.mga2 qemu-img-1.0-6.2.mga2 virtualbox-4.1.18-1.mga2 vboxadditions-kernel-3.3.8-desktop-2.mga2-4.1.18-1.mga2 vboxadditions-kernel-desktop-latest-4.1.18-1.mga2 virt-manager-0.9.1-2.mga2 virtualbox-guest-additions-4.1.18-1.mga2 virt-viewer-0.4.2-1.mga2 x11-driver-video-vboxvideo-4.1.18-1.mga2
CategoryVirtualization
