Re: Date/Time 4 hours ahead - Ubuntu 20 host/ Windows 10 guest
Am 07.06.21 um 21:26 schrieb Weiss, Howard: > Whenever I start my guest OS, the date/time is 4 hours ahead. I disable > synchronization with Internet Time and correct the date/time, then > restarted the guest. The time reverted to being 4 hours ahead. Do you live on the US East Coast? ;-P Try telling Windows that its BIOS is using UTC: https://superuser.com/questions/975717/does-windows-10-support-utc-as-bios-time Alternatively you can tell qemu to use local time as the RTC base: https://qemu-project.gitlab.io/qemu/system/invocation.html (grep for -rtc) -- Philipp
Date/Time 4 hours ahead - Ubuntu 20 host/ Windows 10 guest
Whenever I start my guest OS, the date/time is 4 hours ahead. I disable synchronization with Internet Time and correct the date/time, then restarted the guest. The time reverted to being 4 hours ahead.
Re: Windows 9x - which graphic?
Am 07.06.21 um 16:27 schrieb Simon Becherer: > I tried minport vbe driver > (https://web.archive.org/web/20191129030225/https://bearwindows.zcm.com.au/vbe9x.htm#2) > with cirrus/vga/vmga card > and cirrus driver with cirrus card - but without sucess. > Both 95 and 98 hangs during shutting down :( > > Any hints? Cirrus should work fine with the stock drivers included in Windows. Personally I'm using vmware with the official VMware driver. You can extract the driver for Win9x from preWin2k.iso shipped with VMware. Bonus: set vmport=on (may be default) an install the vmmouse driver from said ISO, and try vmxnet3 if you need networking.
Re: Windows 9x - which graphic?
Am 06.06.21 um 14:19 schrieb Kamil Jońca: > > I try to install my windows 9x instances under qemu. Although > installation finished successuflly, and I can log in into newly > installed guest I cannot achieve an graphic mode better than 640x480 (in > particular I would use 1024x768) > I tried minport vbe driver > (https://web.archive.org/web/20191129030225/https://bearwindows.zcm.com.au/vbe9x.htm#2) > with cirrus/vga/vmga card > and cirrus driver with cirrus card - but without sucess. > Both 95 and 98 hangs during shutting down :( > > Any hints? > KJ > > I have not used win98 boxes since 4? years, but before, i have used win98 with cirrus, and if i remember correct also vesa. 1024x768. as i know i have not had problems. but i do not remember exactly if i have installed a fix for win98 shutdown problem. there must be somewhere a small microsoft fix for this. (not related to emulations, and i do not remember what was the cause for the shutdown problem) simoN -- www.becherer.de signature.asc Description: OpenPGP digital signature
RE: ubuntu on qemu -- Cannot open root device OR No working init found OR syncing: Attempted to kill init..
I tried using file 8G virt.disk which has a primary partition (fat32) and a secondary partition (ext4). And I also tried setting root=/dev/ram when I supplied ramdisk file. But both failed with Kernel panic - not syncing: Attempted to kill init! exitcode=0x0004. Hope to hear some advice and I wish qemu documents include a kind example of installing ubuntu from the .iso file. Thanks! Chan Kim From: c...@etri.re.kr Sent: Monday, June 7, 2021 6:36 PM To: 'qemu-discuss@nongnu.org' Subject: ubuntu on qemu -- Cannot open root device OR No working init found OR syncing: Attempted to kill init.. Hi, all, I'm having a difficulty so I'm asking it here again.. Sorry for the long email, but I can't figure out what is wrong. Recently, I tried installing ubuntu on a qemu virtual machine but I couldn't login to the ubuntu server because the password wasn't accepted: ( https://lists.nongnu.org/archive/html/qemu-discuss/2021-05/msg00053.html ) Today, I found this page for arm versatile-pb : https://qemu-project.gitlab.io/qemu/system/arm/versatile.html and tried it for an exercise.. BTW, the page above doesn't say anything about how I should make the "debian-buster-armel-rootfs.ext4" file, so I just created a qcow2 disk image and used it(this part I'm not sure if is ok or not). try 1 : ## This is the command I tried (after installing the needed toolchain): BLD=build SRC=../../../LinuxDevDrv/linux-5.4.21 make O=$BLD -C $SRC ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- versatile_defconfig make O=$BLD -C $SRC ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- menuconfig # added CONFIG_PCI, CONFIG_PCI_VERSATILE, CONFIG_SCSI, CONFIG_SCSI_SYM5C8XX_2 above.. make O=$BLD -C $SRC ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- make O=$BLD -C $SRC ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- dtbs # made versatile-pb.dtb file ln -s $SRC/build/arch/arm/boot/zImage zImage ln -s $SRC/build/arch/arm/boot/dts/versatile-pb.dtb versatile-pb.dtb qemu-img create -f qcow2 debian-buster-armel-rootfs.qcow2 1T ../../qemu-5.1.0/build/arm-softmmu/qemu-system-arm -machine type=versatilepb \ -serial mon:stdio \ -drive if=scsi,driver=file,filename=debian-buster-armel-rootfs.qcow2 \ -kernel zImage \ -dtb versatile-pb.dtb \ -append "console=ttyAMA0 ro root=/dev/sda" When I ran the final booting with zImage, I get (. continued.) rtc-ds1307 0-0068: setting system clock to 2021-06-07T06:37:00 UTC (1623047820) input: ImExPS/2 Generic Explorer Mouse as /devices/platform/amba/amba:fpga/10007000.kmi/serio1/input/input2 VFS: Cannot open root device "sda" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: 01004096 ram0 (driver?) 01014096 ram1 (driver?) (. continued..) 010e4096 ram14 (driver?) 010f4096 ram15 (driver?) 1f00 65536 mtdblock0 (driver?) Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper Not tainted 5.4.21 #2 Hardware name: ARM-Versatile (Device Tree Support) [] (unwind_backtrace) from [] (show_stack+0x10/0x14) [] (show_stack) from [] (panic+0xe8/0x2e4) [] (panic) from [] (mount_block_root+0x1f4/0x2b8) [] (mount_block_root) from [] (prepare_namespace+0x15c/0x1b0) [] (prepare_namespace) from [] (kernel_init+0x8/0xe8) [] (kernel_init) from [] (ret_from_fork+0x14/0x34) Exception stack(0xc7821fb0 to 0xc7821ff8) I thought there should be just some arguments missing in the command, for example initrd argument. BTW, what is block device 0, 0? Could anyone please tell me what is missing? Why does the page not give initrd argument? Try 2 : ## Then, I tried adding initrd by adding option "-initrd ../../../busybox-1.32.1/initramfs.cpio.gz " This rd image was made for aarch64 before, and the initrd image contained /dev/console (char dev major 5, minor 1), and /dev/ram (block dev major 1, minor 0. It also contained /init script with contents. #!/bin/sh echo "### INIT SCRIPT ###" mkdir /proc /sys /tmp mount -t proc none /proc mount -t sysfs none /sys mount -t tmpfs none /tmp echo -e "\nThis boot took $(cut -d' ' -f1 /proc/uptime) seconds\n" ifconfig eth0 10.0.2.15 netmask 255.255.255.0 up route add default gw 10.0.2.2 exec /bin/sh The /bin directory has all the executables from busybox. And this time the boot log ends like this (with initrd) : (. continue..) Run /sbin/init as init process request_module: kmod_concurrent_max (0) close to 0 (max_modprobes: 50), for module binfmt-464c, throttling... request_module: modprobe binfmt-464c cannot be processed, kmod busy with 50 threads for more than 5 seconds now Starting init: /sbin/init exists but couldn't execute it (error -8) Run /etc/init as init process Run /bin/init as init process Run /bin/sh as init process request_module:
ubuntu on qemu -- Cannot open root device OR No working init found OR syncing: Attempted to kill init..
Hi, all, I'm having a difficulty so I'm asking it here again.. Sorry for the long email, but I can't figure out what is wrong. Recently, I tried installing ubuntu on a qemu virtual machine but I couldn't login to the ubuntu server because the password wasn't accepted: ( https://lists.nongnu.org/archive/html/qemu-discuss/2021-05/msg00053.html ) Today, I found this page for arm versatile-pb : https://qemu-project.gitlab.io/qemu/system/arm/versatile.html and tried it for an exercise.. BTW, the page above doesn't say anything about how I should make the "debian-buster-armel-rootfs.ext4" file, so I just created a qcow2 disk image and used it(this part I'm not sure if is ok or not). try 1 : ## This is the command I tried (after installing the needed toolchain): BLD=build SRC=../../../LinuxDevDrv/linux-5.4.21 make O=$BLD -C $SRC ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- versatile_defconfig make O=$BLD -C $SRC ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- menuconfig # added CONFIG_PCI, CONFIG_PCI_VERSATILE, CONFIG_SCSI, CONFIG_SCSI_SYM5C8XX_2 above.. make O=$BLD -C $SRC ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- make O=$BLD -C $SRC ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- dtbs # made versatile-pb.dtb file ln -s $SRC/build/arch/arm/boot/zImage zImage ln -s $SRC/build/arch/arm/boot/dts/versatile-pb.dtb versatile-pb.dtb qemu-img create -f qcow2 debian-buster-armel-rootfs.qcow2 1T ../../qemu-5.1.0/build/arm-softmmu/qemu-system-arm -machine type=versatilepb \ -serial mon:stdio \ -drive if=scsi,driver=file,filename=debian-buster-armel-rootfs.qcow2 \ -kernel zImage \ -dtb versatile-pb.dtb \ -append "console=ttyAMA0 ro root=/dev/sda" When I ran the final booting with zImage, I get (. continued.) rtc-ds1307 0-0068: setting system clock to 2021-06-07T06:37:00 UTC (1623047820) input: ImExPS/2 Generic Explorer Mouse as /devices/platform/amba/amba:fpga/10007000.kmi/serio1/input/input2 VFS: Cannot open root device "sda" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: 01004096 ram0 (driver?) 01014096 ram1 (driver?) (. continued..) 010e4096 ram14 (driver?) 010f4096 ram15 (driver?) 1f00 65536 mtdblock0 (driver?) Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper Not tainted 5.4.21 #2 Hardware name: ARM-Versatile (Device Tree Support) [] (unwind_backtrace) from [] (show_stack+0x10/0x14) [] (show_stack) from [] (panic+0xe8/0x2e4) [] (panic) from [] (mount_block_root+0x1f4/0x2b8) [] (mount_block_root) from [] (prepare_namespace+0x15c/0x1b0) [] (prepare_namespace) from [] (kernel_init+0x8/0xe8) [] (kernel_init) from [] (ret_from_fork+0x14/0x34) Exception stack(0xc7821fb0 to 0xc7821ff8) I thought there should be just some arguments missing in the command, for example initrd argument. BTW, what is block device 0, 0? Could anyone please tell me what is missing? Why does the page not give initrd argument? Try 2 : ## Then, I tried adding initrd by adding option "-initrd ../../../busybox-1.32.1/initramfs.cpio.gz " This rd image was made for aarch64 before, and the initrd image contained /dev/console (char dev major 5, minor 1), and /dev/ram (block dev major 1, minor 0. It also contained /init script with contents. #!/bin/sh echo "### INIT SCRIPT ###" mkdir /proc /sys /tmp mount -t proc none /proc mount -t sysfs none /sys mount -t tmpfs none /tmp echo -e "\nThis boot took $(cut -d' ' -f1 /proc/uptime) seconds\n" ifconfig eth0 10.0.2.15 netmask 255.255.255.0 up route add default gw 10.0.2.2 exec /bin/sh The /bin directory has all the executables from busybox. And this time the boot log ends like this (with initrd) : (. continue..) Run /sbin/init as init process request_module: kmod_concurrent_max (0) close to 0 (max_modprobes: 50), for module binfmt-464c, throttling... request_module: modprobe binfmt-464c cannot be processed, kmod busy with 50 threads for more than 5 seconds now Starting init: /sbin/init exists but couldn't execute it (error -8) Run /etc/init as init process Run /bin/init as init process Run /bin/sh as init process request_module: kmod_concurrent_max (0) close to 0 (max_modprobes: 50), for module binfmt-464c, throttling... request_module: modprobe binfmt-464c cannot be processed, kmod busy with 50 threads for more than 5 seconds now Starting init: /bin/sh exists but couldn't execute it (error -8) Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. CPU: 0 PID: 1 Comm: swapper Not tainted 5.4.21 #2 Hardware name: ARM-Versatile (Device Tree Support) [] (unwind_backtrace) from [] (show_stack+0x10/0x14) [] (show_stack) from [] (panic+0xe8/0x2e4) [] (panic)
