Hi all,
I have 2 FreeBSD-10.1-STABLE working as virtual machines on an old Ubuntu server 17.04. This server is inherited and I had never configured it.
ps -ax returns:
qemu-system-x86_64 -enable-kvm -name dns -smp 2 -m 2048 -vnc :04 -daemonize -localtime -usb -usbdevice tablet -net nic,macaddr=00:16:3e:00:00:04,model=e1000 -net tap,ifname=tap04 -pidfile /var/log/kvm/dns.pid -boot c -drive index=0,media=disk,if=ide,file=/home2/kvm/system/dns.qcow2 -drive index=2,media=cdrom,if=ide,file=/home2/kvm/iso /FreeBSD-10.1-STABLE-amd64-disc1.iso
it is similar for the second virtual machine.
I try to move the two virtual machines on a new debian 12 server with QEMU emulator version 7.2.9, but when I start the VM, the starting process begins and hangs
the last rows are:
virtio_pci2: negotiated features: 0
uart0: <16550 or compatible> port 0x3f8-0x-3ff irq4 flags 0x10 on acpi0
atkbdc0: <Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
As a matter of fact after several attempts to start it one time it started completely, but I don't know why
and why it was only one single time.
Does anyone have an idea?
PP the result is the same, independent if I start the VM via virtual manager or via command prompt.
I have 2 FreeBSD-10.1-STABLE working as virtual machines on an old Ubuntu server 17.04. This server is inherited and I had never configured it.
ps -ax returns:
qemu-system-x86_64 -enable-kvm -name dns -smp 2 -m 2048 -vnc :04 -daemonize -localtime -usb -usbdevice tablet -net nic,macaddr=00:16:3e:00:00:04,model=e1000 -net tap,ifname=tap04 -pidfile /var/log/kvm/dns.pid -boot c -drive index=0,media=disk,if=ide,file=/home2/kvm/system/dns.qcow2 -drive index=2,media=cdrom,if=ide,file=/home2/kvm/iso /FreeBSD-10.1-STABLE-amd64-disc1.iso
it is similar for the second virtual machine.
I try to move the two virtual machines on a new debian 12 server with QEMU emulator version 7.2.9, but when I start the VM, the starting process begins and hangs
the last rows are:
virtio_pci2: negotiated features: 0
uart0: <16550 or compatible> port 0x3f8-0x-3ff irq4 flags 0x10 on acpi0
atkbdc0: <Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
As a matter of fact after several attempts to start it one time it started completely, but I don't know why
and why it was only one single time.
Does anyone have an idea?
PP the result is the same, independent if I start the VM via virtual manager or via command prompt.
