Re: P2V with VMWare - ERR M
Thanks for the replay. I was not sure which man page you were referring to, but I took a quick glance at installboot. I have often cloned linux systems at work with rsync. I have also done bare-bone restores using system-rescue cd and backups from our backup system. I thought it would be interesting to see how others do it with openbsd. What exactly are you referring to Diskimage route it's not so easy.? Are you referring to cloning the system? Similar to this example http://www.monkey.org/openbsd/archive/tech/0112/msg00079.html What tool does one use to Diskimage the system? You could probably try this tool if I understand what you mean by Diskimage http://sanbarrow.com/moa-video-vdiskmanager-as-ghost.html Zlfar M. E. Johnson Sk}rr [EMAIL PROTECTED] 569 5100 http://www.skyrr.is http://www.skyrr.is/legal/disclaimer.txt -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fabian Heusser Sent: 27. febrzar 2008 17:47 To: Zlfar M. E. Johnson Subject: Re: P2V with VMWare - ERR M Sorry, I refered to the second example in installboot(8) : http://www.openbsd.org/cgi-bin/man.cgi?query=installbootapropos=0sektion=0; manpath=OpenBSD+Currentarch=i386format=html It's the same as this step from your linked FAQ # cp /usr/mdec/boot /mnt/boot # /usr/mdec/installboot -v /mnt/boot /usr/mdec/biosboot sd0 Yes a howto would be nice, for windows there are many, for linux some, and for Openbsd not so many. But as Nick said, it's realy simple if you go the dump/restore route. It's 90% percent of the FAQ you are referring. But If you go the Diskimage route it's not so easy. In the FAQ, they restore first / and boot into single user mode and then restore the rest. Does somone know if it makes any difference if i restore all partitions in one step and then booting in the finished restore? On Wed, Feb 27, 2008 at 3:32 PM, Zlfar M. E. Johnson [EMAIL PROTECTED] wrote: Hi, Did you use http://www.openbsd.org/faq/faq14.html#Backup to restore your old box to a vmware server image. The only part I am confused by is At the end I installed the boot loader as described in the manpages with success. What man page are you referring to? What steps did you use to restore the boot loader? Just curious. Could be good fodder for setting up a wiki or howto for transferring openbsd physical setups to virtual setups on vmware. Zlfar M. E. Johnson Sk}rr [EMAIL PROTECTED] 569 5100 http://www.skyrr.is http://www.skyrr.is/legal/disclaimer.txt -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fabian Heusser Sent: 26. febrzar 2008 23:48 To: misc@openbsd.org Subject: Re: P2V with VMWare - ERR M Nick, thank you for taking the time to answer my questions. As you successfully detected, i have done some brute force with no luck. Thank you for your tip about dump/restore, i applied it with success. With the help of a OpenBSD live CD i managed to do some instant dump restore over the network. For this i used a command sequence like the following for each partition: # mount /dev/sd0a /mnt/hd1 # cd /mnt/hd1 # ssh 192.168.1.52 dump -0f - /dev/sd0a | restore -rvf - # cd / # umount /dev/sd0a At the end I installed the boot loader as described in the manpages with success. What was confusing me was that fdisk /dev/sd0c returns the same as the proper fdisk /dev/sd0 which mixed up my idea of the things. Fabian Fabian Heusser wrote: Hello I have an old box (3.6) which makes a lot of noise, so i like to virtualize it. I made an Image with acronis and converted it with vmware converter. When i start the virtual machine Loading... ERR M is shown. (dmesg at the bottom) I loaded cd36.iso as cdrom and at the boot prompt tried the following: machine boot hd0b - ERR M I'm surprised you get THAT error, but it is a nonsense command. boot hd0a:/bsd - Invalid argument failed(22). will try /bsd also with hd0b, hd0c um. did you really think that /bsd might be on the b, c, or d partitions?? if i boot with the cd, select shell and run the following # mount /dev/sd0c /mnt i get Inappropriate filetype or format. also with /dev/sd0a - d I'd *hope* you can't mount sd0c like that. If i run # cp /usr/mdec/boot /boot # /usr/mdec/installboot -v /boot /usr/mdec/biosboot sd0 i get the following output: -8-- boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c /usr/mdec/biosboot: entry point 0 proto bootblock size 512 installboot: cross-device install -8-- but the error persists. You couldn't read the file system, so you figured you would just run a utility to alter a random sector someplace on the disk. Did you notice the little error message? cross-device install
Re: P2V with VMWare - ERR M
I used Acronis (like Ghost) to get an image and converted it with vmware converter to a virtual machine. but the file system was not useable after this procedure. On Thu, Feb 28, 2008 at 10:52 AM, Zlfar M. E. Johnson [EMAIL PROTECTED] wrote: Thanks for the replay. I was not sure which man page you were referring to, but I took a quick glance at installboot. I have often cloned linux systems at work with rsync. I have also done bare-bone restores using system-rescue cd and backups from our backup system. I thought it would be interesting to see how others do it with openbsd. What exactly are you referring to Diskimage route it's not so easy.? Are you referring to cloning the system? Similar to this example http://www.monkey.org/openbsd/archive/tech/0112/msg00079.html What tool does one use to Diskimage the system? You could probably try this tool if I understand what you mean by Diskimage http://sanbarrow.com/moa-video-vdiskmanager-as-ghost.html Zlfar M. E. Johnson Sk}rr [EMAIL PROTECTED] 569 5100 http://www.skyrr.is http://www.skyrr.is/legal/disclaimer.txt -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fabian Heusser Sent: 27. febrzar 2008 17:47 To: Zlfar M. E. Johnson Subject: Re: P2V with VMWare - ERR M Sorry, I refered to the second example in installboot(8) : http://www.openbsd.org/cgi-bin/man.cgi?query=installbootapropos=0sektion=0; manpath=OpenBSD+Currentarch=i386format=html It's the same as this step from your linked FAQ # cp /usr/mdec/boot /mnt/boot # /usr/mdec/installboot -v /mnt/boot /usr/mdec/biosboot sd0 Yes a howto would be nice, for windows there are many, for linux some, and for Openbsd not so many. But as Nick said, it's realy simple if you go the dump/restore route. It's 90% percent of the FAQ you are referring. But If you go the Diskimage route it's not so easy. In the FAQ, they restore first / and boot into single user mode and then restore the rest. Does somone know if it makes any difference if i restore all partitions in one step and then booting in the finished restore? On Wed, Feb 27, 2008 at 3:32 PM, Zlfar M. E. Johnson [EMAIL PROTECTED] wrote: Hi, Did you use http://www.openbsd.org/faq/faq14.html#Backup to restore your old box to a vmware server image. The only part I am confused by is At the end I installed the boot loader as described in the manpages with success. What man page are you referring to? What steps did you use to restore the boot loader? Just curious. Could be good fodder for setting up a wiki or howto for transferring openbsd physical setups to virtual setups on vmware. Zlfar M. E. Johnson Sk}rr [EMAIL PROTECTED] 569 5100 http://www.skyrr.is http://www.skyrr.is/legal/disclaimer.txt -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fabian Heusser Sent: 26. febrzar 2008 23:48 To: misc@openbsd.org Subject: Re: P2V with VMWare - ERR M Nick, thank you for taking the time to answer my questions. As you successfully detected, i have done some brute force with no luck. Thank you for your tip about dump/restore, i applied it with success. With the help of a OpenBSD live CD i managed to do some instant dump restore over the network. For this i used a command sequence like the following for each partition: # mount /dev/sd0a /mnt/hd1 # cd /mnt/hd1 # ssh 192.168.1.52 dump -0f - /dev/sd0a | restore -rvf - # cd / # umount /dev/sd0a At the end I installed the boot loader as described in the manpages with success. What was confusing me was that fdisk /dev/sd0c returns the same as the proper fdisk /dev/sd0 which mixed up my idea of the things. Fabian Fabian Heusser wrote: Hello I have an old box (3.6) which makes a lot of noise, so i like to virtualize it. I made an Image with acronis and converted it with vmware converter. When i start the virtual machine Loading... ERR M is shown. (dmesg at the bottom) I loaded cd36.iso as cdrom and at the boot prompt tried the following: machine boot hd0b - ERR M I'm surprised you get THAT error, but it is a nonsense command. boot hd0a:/bsd - Invalid argument failed(22). will try /bsd also with hd0b, hd0c um. did you really think that /bsd might be on the b, c, or d partitions?? if i boot with the cd, select shell and run the following # mount /dev/sd0c /mnt i get Inappropriate filetype or format. also with /dev/sd0a - d I'd *hope* you can't mount sd0c like that. If i run # cp /usr/mdec/boot /boot # /usr/mdec/installboot -v /boot /usr/mdec/biosboot sd0 i get the following output
Re: P2V with VMWare - ERR M
Fabian Heusser wrote: Yes a howto would be nice, for windows there are many, for linux some, and for Openbsd not so many. Recipes don't teach you how to cook.
Re: P2V with VMWare - ERR M
On 09:42:17 Feb 28, Steve Shockley wrote: Recipes don't teach you how to cook. I can second this because I have been cooking for more than three years now. And God alone knows how hard it has been. I never consult any book or even the Internet. I simply ask ladies and that too the ones whose food I have tasted. In spite of my making mistakes and experimentation I still cannot be sure how my dish will end up tasting. It is the same with programming or anything with computers. No matter what you read, until you try it out for yourself and get experience it is useless. -Girish -- unix soi qui mal y pense UNIX to him who evil thinks
Re: P2V with VMWare - ERR M
On Fri, Feb 29, 2008 at 07:24:41AM +0530, Girish Venkatachalam wrote: On 09:42:17 Feb 28, Steve Shockley wrote: Recipes don't teach you how to cook. I can second this ... In spite of my making mistakes and experimentation I still cannot be sure how my dish will end up tasting. One needs the right kind of cookbook (which cannot be a culinary howto). The uninitiated will perhaps find these explanations tiresome. But, on closer examination, you will realize that they are indispensible because they embody the fundamental principles, methods, procedures, etc., that, provided the explanations have been understood, will allow you to achieve perfect success in any recipe you undertake. (Madame E. Saint-Ange) Toning down the hyperbolic flourish at the end, it brings to mind the man pages and the FAQ (which, as we all surely agree, is infinitely superior to any collection of mere howtos).
Re: P2V with VMWare - ERR M
RANT ALERT!! RANT ALERT!! Zlfar M. E. Johnson wrote: Thanks for the replay. I was not sure which man page you were referring to, but I took a quick glance at installboot. I have often cloned linux systems at work with rsync. I have also done bare-bone restores using system-rescue cd and backups from our backup system. I thought it would be interesting to see how others do it with openbsd. very simply, actually. :) What exactly are you referring to Diskimage route it's not so easy.? Are you referring to cloning the system? Similar to this example http://www.monkey.org/openbsd/archive/tech/0112/msg00079.html What tool does one use to Diskimage the system? You could probably try this tool if I understand what you mean by Diskimage http://sanbarrow.com/moa-video-vdiskmanager-as-ghost.html All the P2V (and imaging) stuff is really missing a big point: If the target machines weren't hopelessly broke, it shouldn't be a big deal to move to a VM system. Just activate your DR plan! Ah, but the problem is...lots of broken designs exist, running with obsolete apps on obsolete and over-complex OSs that can't run on modern HW and no one can figure out how to reload the apps on a new system. Why are there no tools for P2V for OpenBSD? Why would you need them? The tools you need are in the OS: dump/restore, tar, cpio, dd. Granted, you might just have to spend a couple hours understanding how your OS works..but MUCH better to do that on your schedule than with 500 people sitting around idle asking When are the computers going to be back up? These tools shouldn't need to exist for other OSs, either. Just activate your Disaster Recovery plan on to the VM system. Oh, you don't have a DR plan? That means your system was not well designed. Migrating a system SHOULD be no more difficult than restoring your backup...and you should have tested that process. Oh, your system is too old to run on modern HW? Your system was either not well designed or not well managed, in that it was allowed to outlive its useful life. Oh, no one knows how to recover your existing system? Your system was not well managed, as documentation wasn't kept, people weren't cross-trained (or they were all driven away faster than they could cross-train new people as happened at my previous employer). Oh, your system is too complicated or time consuming to migrate through normal DR processes? Perhaps sticking configuration info in magical places that most backup systems never touch? Bad decisions were made on the design and product selection. Hey, these things happen, so P2V software for some OSs is pretty close to mandatory for some tasks...but remember what it is -- it is a work around for a problem which should NEVER HAVE EXISTED in the first place, and an indication of bad design, not a proper way of doing things. Quintuple bypass surgery and heart-lung machines are really fantastic equipment...but it is better if you can admire them from a distance... It is easy to get into the cool tools mindset. You should have seen the first draft of the note I first posted to this thread -- I had a really cool process of using dd and growfs and then I realized I was solving a problem that didn't exist (there are times when you might want to use dd and growfs, and at least one time when I seem to have NEEDED to, but that's pretty unusual). Backup! Restore! Ta-Da! Failure to be able to do this should be your first warning sign that something is very wrong, and rather than migrating or virtualizing your problems, be a real engineer and FIX the real problem, don't just change it. Remember, virtualized systems can need Disaster Recovery, too... (end Rant) Nick.
Re: P2V with VMWare - ERR M
Hi, Did you use http://www.openbsd.org/faq/faq14.html#Backup to restore your old box to a vmware server image. The only part I am confused by is At the end I installed the boot loader as described in the manpages with success. What man page are you referring to? What steps did you use to restore the boot loader? Just curious. Could be good fodder for setting up a wiki or howto for transferring openbsd physical setups to virtual setups on vmware. Zlfar M. E. Johnson Sk}rr [EMAIL PROTECTED] 569 5100 http://www.skyrr.is http://www.skyrr.is/legal/disclaimer.txt -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fabian Heusser Sent: 26. febrzar 2008 23:48 To: misc@openbsd.org Subject: Re: P2V with VMWare - ERR M Nick, thank you for taking the time to answer my questions. As you successfully detected, i have done some brute force with no luck. Thank you for your tip about dump/restore, i applied it with success. With the help of a OpenBSD live CD i managed to do some instant dump restore over the network. For this i used a command sequence like the following for each partition: # mount /dev/sd0a /mnt/hd1 # cd /mnt/hd1 # ssh 192.168.1.52 dump -0f - /dev/sd0a | restore -rvf - # cd / # umount /dev/sd0a At the end I installed the boot loader as described in the manpages with success. What was confusing me was that fdisk /dev/sd0c returns the same as the proper fdisk /dev/sd0 which mixed up my idea of the things. Fabian Fabian Heusser wrote: Hello I have an old box (3.6) which makes a lot of noise, so i like to virtualize it. I made an Image with acronis and converted it with vmware converter. When i start the virtual machine Loading... ERR M is shown. (dmesg at the bottom) I loaded cd36.iso as cdrom and at the boot prompt tried the following: machine boot hd0b - ERR M I'm surprised you get THAT error, but it is a nonsense command. boot hd0a:/bsd - Invalid argument failed(22). will try /bsd also with hd0b, hd0c um. did you really think that /bsd might be on the b, c, or d partitions?? if i boot with the cd, select shell and run the following # mount /dev/sd0c /mnt i get Inappropriate filetype or format. also with /dev/sd0a - d I'd *hope* you can't mount sd0c like that. If i run # cp /usr/mdec/boot /boot # /usr/mdec/installboot -v /boot /usr/mdec/biosboot sd0 i get the following output: -8-- boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c /usr/mdec/biosboot: entry point 0 proto bootblock size 512 installboot: cross-device install -8-- but the error persists. You couldn't read the file system, so you figured you would just run a utility to alter a random sector someplace on the disk. Did you notice the little error message? cross-device install??? Read the man page, read the FAQ, and think about that command. Does anyone have an idea what i'm doing wrong? Almost everything so far. You can't just type random commands without understanding what you are saying to the computer. What you are doing is very, very dangerous. If you want to get some idea what went wrong, boot a CD, and do a disklabel sd0 and fdisk sd0, see what that tells you. There was obviously something that went very wrong with your imaging transfer process, which doesn't surprise me, the process of migrating OpenBSD is so simple, it is hard to get anyone worried about making a special tool, 'specially since it wouldn't have this kind of flexibility. Quit using special tools, and use the OS. SIMPLE way: dump(8) each existing partition to a file, move the file, then restore(8) the files to the partitions of the new disk. Install your boot loader (PROPERLY this time), and done. And YES, I am being deliberately vague about how to do this. You need to spend some time with the man pages and the FAQ and thinking about how things work, not magic commands to type. The PROPER way of doing this, however, being this is a many year old, unmaintained install, is to build a new 4.2 or 4.3 system, install the apps, and transfer the data files. I'm guessing it is a screwed up system, or it would have been properly maintained and be running 4.2 now. So, why would you want to blindly migrate a mess to new hardware? Nick.
Re: P2V with VMWare - ERR M
Sorry, I refered to the second example in installboot(8) : http://www.openbsd.org/cgi-bin/man.cgi?query=installbootapropos=0sektion=0; manpath=OpenBSD+Currentarch=i386format=html It's the same as this step from your linked FAQ # cp /usr/mdec/boot /mnt/boot # /usr/mdec/installboot -v /mnt/boot /usr/mdec/biosboot sd0 Yes a howto would be nice, for windows there are many, for linux some, and for Openbsd not so many. But as Nick said, it's realy simple if you go the dump/restore route. It's 90% percent of the FAQ you are referring. But If you go the Diskimage route it's not so easy. In the FAQ, they restore first / and boot into single user mode and then restore the rest. Does somone know if it makes any difference if i restore all partitions in one step and then booting in the finished restore? On Wed, Feb 27, 2008 at 3:32 PM, Zlfar M. E. Johnson [EMAIL PROTECTED] wrote: Hi, Did you use http://www.openbsd.org/faq/faq14.html#Backup to restore your old box to a vmware server image. The only part I am confused by is At the end I installed the boot loader as described in the manpages with success. What man page are you referring to? What steps did you use to restore the boot loader? Just curious. Could be good fodder for setting up a wiki or howto for transferring openbsd physical setups to virtual setups on vmware. Zlfar M. E. Johnson Sk}rr [EMAIL PROTECTED] 569 5100 http://www.skyrr.is http://www.skyrr.is/legal/disclaimer.txt -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fabian Heusser Sent: 26. febrzar 2008 23:48 To: misc@openbsd.org Subject: Re: P2V with VMWare - ERR M Nick, thank you for taking the time to answer my questions. As you successfully detected, i have done some brute force with no luck. Thank you for your tip about dump/restore, i applied it with success. With the help of a OpenBSD live CD i managed to do some instant dump restore over the network. For this i used a command sequence like the following for each partition: # mount /dev/sd0a /mnt/hd1 # cd /mnt/hd1 # ssh 192.168.1.52 dump -0f - /dev/sd0a | restore -rvf - # cd / # umount /dev/sd0a At the end I installed the boot loader as described in the manpages with success. What was confusing me was that fdisk /dev/sd0c returns the same as the proper fdisk /dev/sd0 which mixed up my idea of the things. Fabian Fabian Heusser wrote: Hello I have an old box (3.6) which makes a lot of noise, so i like to virtualize it. I made an Image with acronis and converted it with vmware converter. When i start the virtual machine Loading... ERR M is shown. (dmesg at the bottom) I loaded cd36.iso as cdrom and at the boot prompt tried the following: machine boot hd0b - ERR M I'm surprised you get THAT error, but it is a nonsense command. boot hd0a:/bsd - Invalid argument failed(22). will try /bsd also with hd0b, hd0c um. did you really think that /bsd might be on the b, c, or d partitions?? if i boot with the cd, select shell and run the following # mount /dev/sd0c /mnt i get Inappropriate filetype or format. also with /dev/sd0a - d I'd *hope* you can't mount sd0c like that. If i run # cp /usr/mdec/boot /boot # /usr/mdec/installboot -v /boot /usr/mdec/biosboot sd0 i get the following output: -8-- boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c /usr/mdec/biosboot: entry point 0 proto bootblock size 512 installboot: cross-device install -8-- but the error persists. You couldn't read the file system, so you figured you would just run a utility to alter a random sector someplace on the disk. Did you notice the little error message? cross-device install??? Read the man page, read the FAQ, and think about that command. Does anyone have an idea what i'm doing wrong? Almost everything so far. You can't just type random commands without understanding what you are saying to the computer. What you are doing is very, very dangerous. If you want to get some idea what went wrong, boot a CD, and do a disklabel sd0 and fdisk sd0, see what that tells you. There was obviously something that went very wrong with your imaging transfer process, which doesn't surprise me, the process of migrating OpenBSD is so simple, it is hard to get anyone worried about making a special tool, 'specially since it wouldn't have this kind of flexibility. Quit using special tools, and use the OS. SIMPLE way: dump(8) each existing partition to a file, move the file, then restore(8) the files to the partitions of the new disk. Install your boot loader (PROPERLY this time), and done. And YES, I am being deliberately vague about how to do this. You need to spend some time with the man pages
Re: P2V with VMWare - ERR M
Nick, thank you for taking the time to answer my questions. As you successfully detected, i have done some brute force with no luck. Thank you for your tip about dump/restore, i applied it with success. With the help of a OpenBSD live CD i managed to do some instant dump restore over the network. For this i used a command sequence like the following for each partition: # mount /dev/sd0a /mnt/hd1 # cd /mnt/hd1 # ssh 192.168.1.52 dump -0f - /dev/sd0a | restore -rvf - # cd / # umount /dev/sd0a At the end I installed the boot loader as described in the manpages with success. What was confusing me was that fdisk /dev/sd0c returns the same as the proper fdisk /dev/sd0 which mixed up my idea of the things. Fabian Fabian Heusser wrote: Hello I have an old box (3.6) which makes a lot of noise, so i like to virtualize it. I made an Image with acronis and converted it with vmware converter. When i start the virtual machine Loading... ERR M is shown. (dmesg at the bottom) I loaded cd36.iso as cdrom and at the boot prompt tried the following: machine boot hd0b - ERR M I'm surprised you get THAT error, but it is a nonsense command. boot hd0a:/bsd - Invalid argument failed(22). will try /bsd also with hd0b, hd0c um. did you really think that /bsd might be on the b, c, or d partitions?? if i boot with the cd, select shell and run the following # mount /dev/sd0c /mnt i get Inappropriate filetype or format. also with /dev/sd0a - d I'd *hope* you can't mount sd0c like that. If i run # cp /usr/mdec/boot /boot # /usr/mdec/installboot -v /boot /usr/mdec/biosboot sd0 i get the following output: -8-- boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c /usr/mdec/biosboot: entry point 0 proto bootblock size 512 installboot: cross-device install -8-- but the error persists. You couldn't read the file system, so you figured you would just run a utility to alter a random sector someplace on the disk. Did you notice the little error message? cross-device install??? Read the man page, read the FAQ, and think about that command. Does anyone have an idea what i'm doing wrong? Almost everything so far. You can't just type random commands without understanding what you are saying to the computer. What you are doing is very, very dangerous. If you want to get some idea what went wrong, boot a CD, and do a disklabel sd0 and fdisk sd0, see what that tells you. There was obviously something that went very wrong with your imaging transfer process, which doesn't surprise me, the process of migrating OpenBSD is so simple, it is hard to get anyone worried about making a special tool, 'specially since it wouldn't have this kind of flexibility. Quit using special tools, and use the OS. SIMPLE way: dump(8) each existing partition to a file, move the file, then restore(8) the files to the partitions of the new disk. Install your boot loader (PROPERLY this time), and done. And YES, I am being deliberately vague about how to do this. You need to spend some time with the man pages and the FAQ and thinking about how things work, not magic commands to type. The PROPER way of doing this, however, being this is a many year old, unmaintained install, is to build a new 4.2 or 4.3 system, install the apps, and transfer the data files. I'm guessing it is a screwed up system, or it would have been properly maintained and be running 4.2 now. So, why would you want to blindly migrate a mess to new hardware? Nick.
P2V with VMWare - ERR M
Hello I have an old box (3.6) which makes a lot of noise, so i like to virtualize it. I made an Image with acronis and converted it with vmware converter. When i start the virtual machine Loading... ERR M is shown. (dmesg at the bottom) I loaded cd36.iso as cdrom and at the boot prompt tried the following: machine boot hd0b - ERR M boot hd0a:/bsd - Invalid argument failed(22). will try /bsd also with hd0b, hd0c if i boot with the cd, select shell and run the following # mount /dev/sd0c /mnt i get Inappropriate filetype or format. also with /dev/sd0a - d If i run # cp /usr/mdec/boot /boot # /usr/mdec/installboot -v /boot /usr/mdec/biosboot sd0 i get the following output: -8-- boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c /usr/mdec/biosboot: entry point 0 proto bootblock size 512 installboot: cross-device install -8-- but the error persists. Does anyone have an idea what i'm doing wrong? Other Openbsd machines which i installed from scratch to a virtual machine are running fine. Thank You Fabian Infos: 00 Virtual machine running in VMWare Server 2 Beta Ubuntu 7.10 as Host New Box infos unfortunately only as pictures New Box dmesg http://www.w3p.ch/tmpp/openbsd/dmesg.gif New Box fdisk http://www.w3p.ch/tmpp/openbsd/fdisk.gif New Box disklabel http://www.w3p.ch/tmpp/openbsd/disklabel.gif Old box dmesg (http://www.w3p.ch/tmpp/openbsd/dmesg.txt) -8-- OpenBSD 3.6-stable (GENERIC) #1: Sun Jun 12 16:14:49 CEST 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III (GenuineIntel 686-class) 592 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,F XSR,SSE real mem = 267948032 (261668K) avail mem = 237608960 (232040K) using 3296 buffers containing 13500416 bytes (13184K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(69) BIOS, date 02/29/00, BIOS32 rev. 0 @ 0xfd7d2 pcibios0 at bios0: rev 2.1 @ 0xfd7d0/0x830 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf00/224 (12 entries) pcibios0: PCI Exclusive IRQs: 9 pcibios0: PCI Interrupt Router at 000:15:0 (ServerWorks ROSB4 SouthBridge rev 0x00) pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0x800 0xc8800/0xc00 0xc9800/0x800 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 ServerWorks CNB20LE Host rev 0x05 pchb1 at pci0 dev 0 function 1 ServerWorks CNB20LE Host rev 0x05 pci1 at pchb1 bus 3 ppb0 at pci1 dev 2 function 0 Intel i960 RP PCI-PCI rev 0x05 pci2 at ppb0 bus 4 ami0 at pci1 dev 2 function 1 Intel 80960RP ATU rev 0x05: irq 11 HP 466/32b ami0: FW F.02.02, BIOS vB.02.01, 16MB RAM ami0: 1 channels, 16 targets, 1 logical drives scsibus0 at ami0: 8 targets sd0 at scsibus0 targ 0 lun 0: AMI, Host drive #00, SCSI2 0/direct fixed sd0: 17354MB, 2212 cyl, 255 head, 63 sec, 512 bytes/sec, 35540992 sec total xl0 at pci1 dev 5 function 0 3Com 3c905C 100Base-TX rev 0x78: irq 9xl0: reset didn't complete , address 00:0a:5e:50:fc:0b exphy0 at xl0 phy 24: 3Com internal media interface xl0: reset didn't complete siop0 at pci1 dev 6 function 0 Symbios Logic 53c896 rev 0x06: irq 5, using 8K of on-board RAM scsibus1 at siop0: 16 targets siop1 at pci1 dev 6 function 1 Symbios Logic 53c896 rev 0x06: irq 5, using 8K of on-board RAM scsibus2 at siop1: 16 targets st0 at scsibus2 targ 3 lun 0: HP, C1537A, L105 SCSI2 1/sequential removable st0: drive empty or not ready fxp0 at pci0 dev 4 function 0 Intel 82557 rev 0x08: irq 9, address 00:10:83:fc:c9:3d inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4 vga1 at pci0 dev 5 function 0 ATI Mach64 GY rev 0x7a wsdisplay0 at vga1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pcib0 at pci0 dev 15 function 0 ServerWorks ROSB4 SouthBridge rev 0x4f pciide0 at pci0 dev 15 function 1 ServerWorks OSB4 IDE rev 0x00: DMA atapiscsi0 at pciide0 channel 0 drive 0 scsibus3 at atapiscsi0: 2 targets cd0 at scsibus3 targ 0 lun 0: ARTEC, WRR-4848, 1.00 SCSI0 5/cdrom removable cd0(pciide0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 2 isa0 at pcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker sysbeep0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec biomask fd65 netmask ff65 ttymask ffe7 pctr: 686-class user-level performance counters enabled mtrr: Pentium Pro MTRR support dkcsum: sd0 matched BIOS disk 80 root on sd0a rootdev=0x400 rrootdev=0xd00 rawdev=0xd02 -8-- Old box fdisk
Re: P2V with VMWare - ERR M
Fabian Heusser wrote: Hello I have an old box (3.6) which makes a lot of noise, so i like to virtualize it. I made an Image with acronis and converted it with vmware converter. When i start the virtual machine Loading... ERR M is shown. (dmesg at the bottom) I loaded cd36.iso as cdrom and at the boot prompt tried the following: machine boot hd0b - ERR M I'm surprised you get THAT error, but it is a nonsense command. boot hd0a:/bsd - Invalid argument failed(22). will try /bsd also with hd0b, hd0c um. did you really think that /bsd might be on the b, c, or d partitions?? if i boot with the cd, select shell and run the following # mount /dev/sd0c /mnt i get Inappropriate filetype or format. also with /dev/sd0a - d I'd *hope* you can't mount sd0c like that. If i run # cp /usr/mdec/boot /boot # /usr/mdec/installboot -v /boot /usr/mdec/biosboot sd0 i get the following output: -8-- boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c /usr/mdec/biosboot: entry point 0 proto bootblock size 512 installboot: cross-device install -8-- but the error persists. You couldn't read the file system, so you figured you would just run a utility to alter a random sector someplace on the disk. Did you notice the little error message? cross-device install??? Read the man page, read the FAQ, and think about that command. Does anyone have an idea what i'm doing wrong? Almost everything so far. You can't just type random commands without understanding what you are saying to the computer. What you are doing is very, very dangerous. If you want to get some idea what went wrong, boot a CD, and do a disklabel sd0 and fdisk sd0, see what that tells you. There was obviously something that went very wrong with your imaging transfer process, which doesn't surprise me, the process of migrating OpenBSD is so simple, it is hard to get anyone worried about making a special tool, 'specially since it wouldn't have this kind of flexibility. Quit using special tools, and use the OS. SIMPLE way: dump(8) each existing partition to a file, move the file, then restore(8) the files to the partitions of the new disk. Install your boot loader (PROPERLY this time), and done. And YES, I am being deliberately vague about how to do this. You need to spend some time with the man pages and the FAQ and thinking about how things work, not magic commands to type. The PROPER way of doing this, however, being this is a many year old, unmaintained install, is to build a new 4.2 or 4.3 system, install the apps, and transfer the data files. I'm guessing it is a screwed up system, or it would have been properly maintained and be running 4.2 now. So, why would you want to blindly migrate a mess to new hardware? Nick.
