[Qemu-devel] Question about io mode & cache mode

[Qemu-devel] Question about io mode & cache mode

[morgenlette madeBy]

Hello.

I sent mail for question about io mode and cache mode.

When I set VM to I/O mode = native and cache mode = none,

Vm cannot boot and vm is turn off automatically.

Why cannot VM boot?

[Qemu-devel] Question about io mode & cache mode

[morgenlette madeBy]

Hello.

I sent mail for question about io mode and cache mode.

When I set VM to I/O mode = native and cache mode = none,

Vm cannot boot and vm is turn off automatically.

Why cannot VM boot?

Re: [Qemu-devel] Question about io mode & cache mode

[Stefan Hajnoczi]

[-- Attachment #1: Type: text/plain, Size: 435 bytes --]

On Thu, Jan 12, 2017 at 01:25:35PM +0900, morgenlette madeBy wrote:
> I sent mail for question about io mode and cache mode.
> 
> When I set VM to I/O mode = native and cache mode = none,
> 
> Vm cannot boot and vm is turn off automatically.
> 
> Why cannot VM boot?

You didn't provide enough information to give an answer.

What is your QEMU command-line?

What do you mean by "vm is turn off automatically"?

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

Re: [Qemu-devel] Question about io mode & cache mode

[Stefan Hajnoczi]

On Mon, Jan 23, 2017 at 8:59 AM, morgenlette madeBy <sgh8183@gmail.com> wrote:

Please keep qemu-devel@nongnu.org CCed so the discussion stays on the
mailing list where others can follow it.

> I am sorry to bother you.
>
> so, Where is the part that I have to check additionally?

Failing syscalls can be debugged using kernel function graph tracing:
https://www.kernel.org/doc/Documentation/trace/ftrace.txt

It shows you the code path executed by the kernel.  You can
cross-reference the kernel source to see why an error return path is
being taken.

There are other approaches, like adding printks to the kernel.

Before you embark on any of this, it might be a good idea to write a
tiny test program that opens the file exactly the same way you are
doing it in QEMU.  See if it fails in the same way.

Stefan

> On Mon, Jan 23, 2017 at 5:31 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
>>
>> On Mon, Jan 23, 2017 at 7:43 AM, morgenlette madeBy <sgh8183@gmail.com>
>> wrote:
>> > I am using Centos 7.
>> >
>> > So I set up SELinux=disabled...
>> >
>> > /dev/mydev is operated by root and its permission is 0777.
>> >
>> > 6 S root      3221     1 14  80   0 - 409221 poll_s 16:40 ?
>> > 00:00:14
>> > /usr/libexec/qemu-kvm -name centos6.5-1 -S -machine
>> > pc-i440fx-rhel7.0.0,accel=kvm,usb=off -cpu
>> > SandyBridge,+vme,+f16c,+rdrand,+fsgsbase,+smep,+erms -m 1024 -realtime
>> > mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid
>> > c1878d8a-0902-42f1-9c20-509302412f45 -no-user-config -nodefaults
>> > -chardev
>> >
>> > socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-centos6.5-1/monitor.sock,server,nowait
>> > -mon chardev=charmonitor,id=monitor,mode=control -rtc
>> > base=utc,driftfix=slew
>> > -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -global
>> > PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on
>> > -device
>> > ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device
>> >
>> > ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6
>> > -device
>> > ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1
>> > -device
>> > ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2
>> > -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive
>> >
>> > file=/var/lib/libvirt/images/centos6.5-1.qcow2,format=qcow2,if=none,id=drive-virtio-disk0
>> > -device
>> >
>> > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
>> > -drive if=none,id=drive-ide0-0-0,readonly=on -device
>> > ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev
>> > tap,fd=26,id=hostnet0,vhost=on,vhostfd=28 -device
>> >
>> > virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:f2:d9:fa,bus=pci.0,addr=0x3
>> > -chardev pty,id=charserial0 -device
>> > isa-serial,chardev=charserial0,id=serial0 -chardev
>> >
>> > socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-1-centos6.5-1/org.qemu.guest_agent.0,server,nowait
>> > -device
>> >
>> > virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0
>> > -chardev spicevmc,id=charchannel1,name=vdagent -device
>> >
>> > virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0
>> > -device usb-tablet,id=input0,bus=usb.0,port=1 -spice
>> >
>> > port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on
>> > -vga qxl -global qxl-vga.ram_size=67108864 -global
>> > qxl-vga.vram_size=67108864 -global qxl-vga.vgamem_mb=16 -device
>> > intel-hda,id=sound0,bus=pci.0,addr=0x4 -device
>> > hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev
>> > spicevmc,id=charredir0,name=usbredir -device
>> > usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 -chardev
>> > spicevmc,id=charredir1,name=usbredir -device
>> > usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 -device
>> > virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on
>> >
>> > QEMU file is also operated by root.
>> >
>> > I can't understand what is problem...
>> >
>> > In qemu, is open function disabled???
>>
>> No, it is not.
>>
>> Stefan
>
>