Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
ok, we are missing a:
cache=none
in
-drive file=/nfs/windows10.raw,if=none,id=drive-virtio-disk0,format=raw
For migration to work reliablely.
But not sure that is the problem we are having here.
Hi Juan,
I have reproduced this issue with qemu-kvm-0.12.1.2-2.479.el6.x86_64, with command line [1], which has cache=none.
And could not reproduce it with qemu-kvm-0.12.1.2-2.456.el6.x86_64, with same command line.
Hope it helps.
[1] /usr/libexec/qemu-kvm -name linux -m 2048 -cpu Westmere,check -realtime mlock=off -smp 4,sockets=2,cores=1,threads=1 -uuid 7bef3814-631a-48bb-bae8-2b1de75f7a13 -nodefaults -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot order=c,menu=on -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/nfs/rhel68-64-virtio.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0 -msg timestamp=on -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -vga cirrus -monitor stdio -vnc :3 -device e1000,netdev=hostnet0,id=net0,mac=D4:AE:52:E9:57:36 -netdev tap,id=hostnet0 --incoming tcp::1234
Thanks. Problem was introduced in
qemu-kvm-0.12.1.2-2.459.el6
I even found the guilty commit, but it is not obvious why it is creating the error. Initial assessment is that the error message shouldn't be printed, not that there is any problem.
Later, Juan.
> I have reproduced this issue with qemu-kvm-0.12.1.2-2.479.el6.x86_64, with
> command line [1], which has cache=none.
> And could not reproduce it with qemu-kvm-0.12.1.2-2.456.el6.x86_64, with
> same command line.
Can you try qemu-kvm-0.12.1.2-2.497.el6?
Possibly this is a bug 1294941 duplicate.