[opensuse] VirtuaBox on Tumbleweed
I have a 32-bit openSUSE 13.1 VirtualBox image that I run on 64-bit openSUSE 42.3. That works fine. I would like to run this image on 64-bit Tumbleweed (up-to-date). So I exported/imported it. No complaints in those two steps. When I try to start the image, I get the boot screen and it then wants to start the kernel. Initially, it prints the stuff like the following. FATAL: Module ohci_hcd not found. FATAL: Module uhci_hcd not found. This is expected. Or at least I recall seeing these message all the time. Then the boot stops for a long time (more than a minute). Then the geeko on a branch is shown. If I press ESC to see what is happening, I see it prints things like: Trying manual resume from /dev/disk/by-id/ata-VBOX_HARDDISK/VBZZZZZZZZZZZZZZ-part2 But it then complains it cannot be found. After trying a few other partition names, it asks: Want me to fall back to /dev/disk/by-id/ata-VBOX_HARDDISK/VBZZZZZZZZZZZZZZ-part1 (Y/n) Pressing Y does nothing. The machine is stopped. The same happened when I just copied the image files. But then I suspected it was because I just copied the files. I thought that export/import should do the right thing. Since I exported the machine, I would expect the partition stuff to be correct. Have I missed the obvious? Is there a preferred export format? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
17.07.2019 21:12, Roger Oberholtzer пишет:
I have a 32-bit openSUSE 13.1 VirtualBox image that I run on 64-bit openSUSE 42.3. That works fine. I would like to run this image on 64-bit Tumbleweed (up-to-date). So I exported/imported it. No complaints in those two steps.
When I try to start the image, I get the boot screen and it then wants to start the kernel.
Initially, it prints the stuff like the following.
FATAL: Module ohci_hcd not found. FATAL: Module uhci_hcd not found.
This is expected. Or at least I recall seeing these message all the time. Then the boot stops for a long time (more than a minute). Then the geeko on a branch is shown. If I press ESC to see what is happening, I see it prints things like:
Trying manual resume from /dev/disk/by-id/ata-VBOX_HARDDISK/VBZZZZZZZZZZZZZZ-part2
ZZZ is not very informative. But most likely disk serial number that VB emulates changed because this is new "hardware" (it is probably randomly generated for new VM). Either find some way to change this information in VB to the same value as in original VM or change your openSUSE to use something else (like UUID). Actually in VM you can simply use device names, they are unlikely to change.
But it then complains it cannot be found. After trying a few other partition names, it asks:
Want me to fall back to /dev/disk/by-id/ata-VBOX_HARDDISK/VBZZZZZZZZZZZZZZ-part1 (Y/n)
Pressing Y does nothing. The machine is stopped.
The same happened when I just copied the image files. But then I suspected it was because I just copied the files. I thought that export/import should do the right thing.
Since I exported the machine, I would expect the partition stuff to be correct.
Have I missed the obvious? Is there a preferred export format?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 18 Jul 2019, at 05:30, Andrei Borzenkov <arvidjaar@gmail.com>
ZZZ is not very informative. But most likely disk serial number that VB emulates changed because this is new "hardware" (it is probably randomly generated for new VM). Either find some way to change this information in VB to the same value as in original VM or change your openSUSE to use something else (like UUID). Actually in VM you can simply use device names, they are unlikely to change.
Yes it is the disk serial number. I thought managing this was one of the things export/import did that one does not get by just copying the images. I don’t see the number in the .vbox file. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Resending due to "Mailinglist outage yesterday" - was sent at 13:33 UTC 18/7 On 18/07/2019 06.49, Roger Oberholtzer wrote:
On 18 Jul 2019, at 05:30, Andrei Borzenkov <arvidjaar@gmail.com>
ZZZ is not very informative. But most likely disk serial number that VB emulates changed because this is new "hardware" (it is probably randomly generated for new VM). Either find some way to change this information in VB to the same value as in original VM or change your openSUSE to use something else (like UUID). Actually in VM you can simply use device names, they are unlikely to change.
Yes it is the disk serial number. I thought managing this was one of the things export/import did that one does not get by just copying the images. I don’t see the number in the .vbox file.
But "managing" does not include editing fstab, grub, and regenerating initrd. All that you have to do yourself. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
participants (3)
-
Andrei Borzenkov -
Carlos E. R. -
Roger Oberholtzer